I assume that you have all the hardware updates are in place as well as the software ones from redhat, I also take it that this is a production system and cannot be built to a later RedHat 7.3/8.0 correct ?
On Tue, 2002-11-19 at 11:35, Dana Holland wrote: > Rechenberg, Andrew wrote: > > What kernel are your running? > > This is what I find in the message log: > Linux version 2.4.3-6smp ([EMAIL PROTECTED]) (gcc version > 2.9620000731 (Red Hat Linux 7.1 2.96-85)) #1 SMP Wed May 16 04:29:16 EDT 001 > > > What type of NIC's are in the box? > > Nov 18 17:36:05 sts kernel: eth0: Intel Corporation 82557 [Ethernet Pro > 100], 00:B0:D0:EA:37:55, I/O at 0xe8c0, IRQ 26. > Nov 18 17:36:05 sts kernel: eth1: OEM i82557/i82558 10/100 Ethernet, > 00:02:B3:8B:51:CE, I/O at 0xbcc0, IRQ 24. > > > Make sure that you are running the most up-to-date errata kernel from > > Red Hat as it usually has fixes for most problems that you may > > encounter. We had issues with kernels prior to about 2.4.16 and virtual > > memory that caused our boxes to hang but not reboot. Red Hat 7.1 comes > > with a VERY early 2.4 kernel (2.4.2-2 I believe) so that may be your > > problem. > > I found these messages in the logs which seem like they *might* be a > problem: > Nov 18 18:44:13 sts insmod: > lib/modules/2.4.3-6smp/kernel/drivers/parport/parport_pc.o: init_module: > Device or resource busy > Nov 18 18:44:13 sts insmod: Hint: insmod errors can be caused by > incorrect module parameters, including invalid IO or IRQ parameters > Nov 18 18:44:13 sts insmod: > /lib/modules/2.4.3-6smp/kernel/drivers/parport/parport_pc.o: insmod > parport_lowlevel failed > Nov 18 18:44:13 sts kernel: lp: driver loaded but no devices found > Nov 18 18:44:14 sts modprobe: modprobe: Can't locate module char-major-188 > Nov 18 18:45:28 sts kernel: probable hardware bug: clock timer > configuration lost - probably a VIA686a motherboard. > Nov 18 18:45:28 sts kernel: probable hardware bug: restoring chip > configuration. > > While searching for answers, I saw that some people had reported similar > behavior after they had done a reboot. We did reboot yesterday - and > then it rebooted itself an hour later. I know that at least once when > it rebooted itself it was under similar circumstances. We've decided to > reboot again and then watch it to see if it happens again. > > > > > -- > ************************************************** > Dana Holland [EMAIL PROTECTED] 903-875-7355 > Navarro College Corsicana, TX > http://www.nav.cc.tx.us/staff_pages/dana/dana.html > ************************************************** > All opinions stated are my own, and probably don't even vaguely resemble > those of Navarro College. :) > > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe > https://listman.redhat.com/mailman/listinfo/redhat-list -- Aly S.P Dharshi [EMAIL PROTECTED] Student and System Administrator ORS Servers "A good speech is like a good dress that's short enough to be interesting and long enough to cover the subject" -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
