> The console locking changes have I suspect broken your bandaid. I guess
> this time you need to fix it properly. Garbled panics normally occur when
> both cpus panic in parallel. That really wants some kind of timed spinlock
> to try and dump them one after the other
Humpf. You mean I've got to get rid of my disgusting hack? Sigh ... OK. ;-)
FWIW, I still think that means that the console locking changes are broken
-
adding a printk shouldn't panic the kernel. I'll go look at the console
locking
changes (*and* fix my disgusting hack ;-) )
M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Sep 30 2001 - 21:01:04 EST