On Wed, 31 Aug 2005, Grant Kwok wrote: >I've attached the last bit of /var/log/messages that lead up to my last >crash (from this morning) as requested.
The problem with lockups is that /var/log/messages probably won't contain the exact final cause, as this would require the scheduler, syslogd/klogd, and the I/O subsystem to continue working for long enough before the "freeze" kicks in. To see a fatal kernel oops message (if any), you need to watch the text console, serial console (if configured), or some form of network console / netdump setup. As you've described things, I'm not sure how you'd prod the system in the right way to fall over without pressing buttons in X, which is no good :( Cheers, Phil ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
