On 8/15/05, D. ShadowWolf <[EMAIL PROTECTED]> wrote: > Decided to take the latest git kernel for a run and ran into the following > oops when shutting the system down to try it from a cold-boot situation. I > wasn't able to capture the oops as it happened, but thankfully syslog was > still running and I managed to trap it there. >
serial console, netconsole, console on line-printer are all useful for capturing Oops data. There are detailed guides in Documentation/ > When the oops occurred the system was almost shut down, but the command that > was executing at the time was to save the sync the hardware clock to Linux (I > think)... the trap from my kernel logs (I have each class of kernel event > redirected to a different file. This leads to some huge files in a short > span, but is useful for debugging a new kernel) > The kernel is tainted by the lt modem drivers (lt_modem & lt_serial) however > the problem does not appear to be in either of those, and they function > properly under 2.6.12.3 > > I'm running a basic Slackware 10 distribution (other than the ltmodem drivers > (gone inside the next month)) > I've tried to reproduce the Oops here with your config, but my hardware is too different to match your config, so I had to make some changes to get the kernel running. In the end I was not able to reproduce it. Can you reproduce the crash reliably? Can you reproduce the crash with a non-tainted kernel? -- Jesper Juhl <[EMAIL PROTECTED]> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
