I would try booting with the other kernel and see if that fixes the problem. From the logs you sent it stated:
Feb 4 08:35:30 localhost kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000960 For the kernel to panic like that and if it logs an error about a NULL pointer then there is most likely something wrong with the kernel... ie something isn't being initialized properly which is why it's saying it's NULL Cheers, -- Personal: Trevor Lauder Web: http://www.thelauders.net E-Mail: [EMAIL PROTECTED] Work: Trevor Lauder Technical Services Specialist Wireless Networks Inc. Web: http://www.wirelessnetworksinc.com E-Mail: [EMAIL PROTECTED] Jesse Kline said: > On Tue, 2003-02-04 at 12:54, Mark Lane wrote: > >> This won't happen to be Red Hat 8, would it? Has syslogd been crashing >> as well. > > It is RedHat 8.0. Would a syslog crash look something like this: > Feb 3 10:38:25Feb 3 12:25:11 localhost syslogd 1.4.1: restart.? > >> By any chance are you running redhat's 2.4.18-19.8 kernel? I know that >> before I re-installed Red Hat, I wasn't having these problems and the >> only real difference that I can pin down is the update to 2.4.18-19.8 >> from 2.4.18-19.7. > > Yes, these are the kernels that I have installed: > kernel-2.4.18-14 > kernel-2.4.18-19.8.0 > I am booting with the 2.4.18-19.8.0 kernel. What would you suggest I do? > Boot with the old kernel, or install the 8.1 beta maybe? > > Thank you, > > Jesse
