I reported this problem with 2.1.102 previously, and it seems to have
happened again in 2.1.103.
After 6 days' uptime with 2.1.103, I needed to boot into MSDOS, so I
executed shutdown -r now. It promptly did an OOPS right after the message
"Killing processes". Needless to say, this time, I did force a sync before
doing this so I was glad to see no filesystem corruption when I returned
to Linux.
Unfortunately the OOPS was not logged; and the machine rebooted before I
could write the OOPS down. :o(
I find it quite sinister that this has happened previously with 2.1.102
and now with this release after a few days' uptime.
There is something undecidedly spooky going on. Any ideas?
I shall be running this system for a couple of days and then reboot - if
the OOPS occurs then I shall again bring it up again for another few days,
and then explictly unload all modules before shutting down, if this
doesn't do an OOPS, then we have the culprit.
Configuration:
Linux tahallah 2.1.103 #16 Wed May 20 23:58:02 EDT 1998 i486 unknown
Kernel modules found
Gnu C 2.7.2.3
Binutils 2.9.1.0.4
Linux C Library 5.4.44
Dynamic Linker (ld.so) 1.9.6
Linux C++ Library 27.2.8
Procps 1.2.7
Mount 2.7l
Net-tools (1998-03-02)
Kbd 0.93
Sh-utils 1.16
Cheers,
Alex
-- /\_/\ Legalise cannabis now! ( o.o ) Smoke some cannabis today! > ^ < Peace, Love, Unity and Respect to all.http://www.tahallah.demon.co.uk
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu