Messages in this thread | | | From | (H. Peter Anvin) | Subject | Re: OOPS problems (vaguely humorous) | Date | 5 Jan 1999 00:08:02 GMT |
| |
Followup to: <Pine.LNX.3.96.990104040711.28601A-100000@yme.mo.himolde.no> By author: Erik Inge Bolso <knan@mo.himolde.no> In newsgroup: linux.dev.kernel > > A slightly amusing trouble here relating to OOPS logging: > > An oops occurred early Sunday morning, for some reason that will never be > known, other than the fact that it occured in the middle of a bash > process. This was running a stable kernel (2.0.34) on somewhat > questionable hardware. (EIDE drive w/hard errors as root...) But it wasn't > a very severe oops, the machine was still up & running. > > So I went hunting in the system logs for the Oops log. Sure enough, there > it was, 06:48:50 a Sunday morning... > > "Jan 3 06:48:50 balder kernel: Unable to handle kernel paging request"... > "..." > "..." > "..." > "Jan 3 06:48:50 balder kernel: CPU: 0" > "Jan 3 06:48:59 balder syslogd 1.3-3#26: restart." > > Syslogd had suddenly decided to restart, *in the middle of* logging an > Oops... :-) >
Not surprising. The first oops was nonfatal, but the corrupt data structure quickly thereafter caused a fatal oops which killed syslog.
-hpa -- PGP: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD 1E DF FE 69 EE 35 BD 74 See http://www.zytor.com/~hpa/ for web page and full PGP public key I am Bahá'í -- ask me about it or see http://www.bahai.org/ "To love another person is to see the face of God." -- Les Misérables
- 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/
| |