Hello all,
there was a suggestion posted to l-k a while ago about how to keep ALL
output from printk(), so that you get consistent data in syslog. The
note was in respect to capturing OOPS information correctly, but there
is a lot of "oops" in the l-k archives, so searching is difficult.
It was on the order of a couple of lines patch to the kernel.
I'm writing a module, and I need to be able to track debugging info from
printk, but it drops out occasionally when there is lots of output, and
makes it hard to follow the flow of execution.
Any help is appreciated.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
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 : Sun Jan 23 2000 - 21:00:18 EST