From: <er...@he...> - 2003-10-22 21:21:03
|
On Tue, Oct 21, 2003 at 12:48:27PM -0400, Nicholas Henke wrote: > On Tue, 2003-10-21 at 11:54, er...@he... wrote: > > I got an oops out of the NMI watchdog which was enlightening (or at > > least indicated which code was at fault). The following patch may > > have fixed it for me. I say "may have" since I've had some trouble > > reproducing the problem reliably. > > > > This patch turns off "sigbypass" which is a little optimization where > > a process sending a signal to a ghost doesn't bother the ghost. > > Instead it just throws a signal forwarding message right on the > > message queue. I'm not sure how the code is broken. I haven't had > > time to look into it yet. > > > > Please give it a try and let me know if you still see the deadlock. > > Thanks for the quick patch, I am running now to see if it deadlocks. > > BTW -- did you do anything special to get NMI to dump an oops for you? > Can you tell me the basic setup -- I am just booting with > nmi_watchdog=1, and I see the interrupts in /proc/interrupts. Does > something more need to be done ? That's all I did. - Erik |