On Sat, 26 Aug 2000 11:47:30 -0500,
Brian Capouch <brianc@palaver.net> wrote:
>I also need to see where to find info on interpreting the following type
>of message. I am getting these (this much, by the way--exactly 5 lines
>of message--and no more; no OOPs or anything) eight or ten times a day.
>
>Aug 25 16:38:39 minauros kernel: Unable to handle kernel paging request
>at virtual address 43494843
>Aug 25 16:38:39 minauros kernel: current->tss.cr3 = 08a44000, %cr3 =
>08a44000
>Aug 25 16:38:39 minauros kernel: *pde = 00000000
>Aug 25 16:38:39 minauros kernel: current->tss.cr3 = 08a44000, %cr3 =
>08a44000
>Aug 25 16:38:39 minauros kernel: *pde = 00000000
That smells like the known problem in klogd where it dies trying to
process an Oops log. I always run klogd as "klogd -x" simply because
the standard klogd oops decoder is badly broken. Change the klogd
start command in /etc/rc.d/init.d/syslog.d to "klogd -x" and restart
klogd. Or you could apply the last section (ksym.c) of the patch in
ftp://ftp.ocs.com.au/pub/ksymoops/v2.3/patch-sysklogd-1-3-31-ksymoops-1.gz
Slightly off topic. Does anybody maintain klogd and syslogd nowadays?
The maintainer (Dr. Greg Wettstein) changed jobs and I have not seen
anything from him for over a year. There were rumours of a new log
daemon being written from scratch (syslog-ng?) but distributions are
still shipping old versions of sysklogd, complete with oops decoding
annoyances and bugs.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 31 2000 - 21:00:20 EST