Just had a few oopses in (plain vanilla) 2.1.92 causing me to have to reboot the system. They occurred (every time) the program start-stop-daemon was run. The program died with a SIGSEGV after oopsing.
(is there by the way a point to resetting the mouse (serial ports) on every printk? it is _very_ annoying since fixing requires me to rip the cover of my mouse, pull out the serial connector, hold a button while inserting it again, and putting the cover on... also the printk's are sloow, printing the oops text takes ~5-10 seconds)
At the the time the oopses started the system had been running (essentially) idle for a few hours. After a few oopses my console was dead and I used sysrq to boot the system.
I've been using the system for a few hours since, and nothing evil has happened yet, so I'm not sure about the reproducability. Unfortunately I didn't write the oopses down by hand, so this information is not so valuable as it could be. Perhaps anyone recognizes the problem though?
My system:
Debian GNU/Linux 2.0
i586 166MHz
64M
i430TX
kernel compiled by egcs-2.90.27 with -march=pentium
-- Jakob Borg <jb@k2.lund.se> Finger for PGP key or info- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu