> when debugging drivers using printk i've the problem that most often
> the msg passed to printk don't show up on the console since the machine
> crashed before. i also what to use my own ASSERT macros which halt the
printk writes to the console synchronously unless you have configured
syslogk to process the messages and log them itself. You may want to boot
with syslogk disabled and see if that is your problem.
2.4 also supports serial console which can be useful when the box insists on
crashing in X11
-
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 : Fri Sep 07 2001 - 21:00:30 EST