> The "stuck" message just means that the spin_lock() routine (really
> debug_spin_lock()) thinks that it has waited too long to get the particular
> lock.
In looking over debug_spin_lock() I see that it uses a hard coded value as
an indicator of "too long":
stuck = 1L << 28;
Is it possible that this value (as large as it is) is too small for some of
the newer CPUs?
> > Sometimes, the machine goes completely catatonic and should be
> > resetted. Less often the system really crashes. My estimate is that
There may be situations (e.g. certain paths during interrupt handling) where
doing a printk to the console is a bad idea. I have seen this on the other
OSs.
Pat
-- Patrick O'Rourke orourke@missioncriticallinux.com- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:24 EST