I have a machine that has worked fine for years on CentOS5. kernel-PAE-2.6.18-164.15.1.el5 is the last "works fine" kernel, but kernel-PAE-2.6.18-194.3.1.el5 crashes at boot every time.
I tried banging on the side of the monitor to no avail.
All kidding aside, here are pictures of my monitor when booting 194 in case that is helpful. http://jt-socal.com/sites/jt-socal.com/files/kernel-panic.jpg http://jt-socal.com/sites/jt-socal.com/files/just-before-crashing.jpg
Any suggestions on fixing this?
On Sun, Jun 6, 2010 at 7:35 AM, John Thomas gmane-2006-04-16@jt-socal.com wrote:
I have a machine that has worked fine for years on CentOS5. kernel-PAE-2.6.18-164.15.1.el5 is the last "works fine" kernel, but kernel-PAE-2.6.18-194.3.1.el5 crashes at boot every time.
I tried banging on the side of the monitor to no avail.
All kidding aside, here are pictures of my monitor when booting 194 in case that is helpful. http://jt-socal.com/sites/jt-socal.com/files/kernel-panic.jpg http://jt-socal.com/sites/jt-socal.com/files/just-before-crashing.jpg
Any suggestions on fixing this?
Let's see - you're running a Dell and the second photo is out of focus....
Sorry, I just couldn't resist.
I'm wondering if is has something to do with the PAE kernel vs. your machine. Can you elaborate on that at all?
mhr
Let's see - you're running a Dell and the second photo is out of focus....
It's worse than that. It's a Dell monitor on a custom built machine by someone who does not know what they are doing (me). Would a more focused picture help?
Sorry, I just couldn't resist.
No worries, just keeping helping ;)
I'm wondering if is has something to do with the PAE kernel vs. your machine. Can you elaborate on that at all?
Not sure what to do here. I am at hobbyist skill level.
With your question, I tried using the regular (non-PAE) kernel. The system halted after udev [ok] and no other on-screen information.
Thank anyhow!
On Jun 6, 2010, at 1:11 PM, John Thomas wrote:
Let's see - you're running a Dell and the second photo is out of focus....
It's worse than that. It's a Dell monitor on a custom built machine by someone who does not know what they are doing (me). Would a more focused picture help?
Sorry, I just couldn't resist.
No worries, just keeping helping ;)
I'm wondering if is has something to do with the PAE kernel vs. your machine. Can you elaborate on that at all?
Not sure what to do here. I am at hobbyist skill level.
With your question, I tried using the regular (non-PAE) kernel. The system halted after udev [ok] and no other on-screen information.
Thank anyhow!
One option is to just continue to run a working kernel, depending on what you are doing on the system, and hope that the next kernel is fixed.
I've had the problem with some revs of the kernel, both at work where we use the upstream provider and at home with CentOS, and eventually a later version worked. It apparently affected a paying customer who reported it.
On Sun, Jun 6, 2010 at 11:11 AM, John Thomas gmane-2006-04-16@jt-socal.com wrote:
I'm wondering if is has something to do with the PAE kernel vs. your machine. Can you elaborate on that at all?
Not sure what to do here. I am at hobbyist skill level.
With your question, I tried using the regular (non-PAE) kernel. The system halted after udev [ok] and no other on-screen information.
It sounds like you have a non-standard driver that is not compatible with the latest kernel.
Can you post more details about the machine, say info from a working kernel? Things like configuration, drivers, etc.
mhr
It sounds like you have a non-standard driver that is not compatible with the latest kernel.
Hmm, using nvidia video driver from ELRepo and I don't remember anything else. I tried without the nvidia driver, but same problem.
Can you post more details about the machine, say info from a working kernel? Things like configuration, drivers, etc.
Hmm, not sure how to do that. How about this: CentOS55[root@home ~]# lspci 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) 00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1) 00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2) 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1) 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2) 00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV40 [GeForce 6800 GT] (rev a1) 02:08.0 RAID bus controller: 3ware Inc 9xxx-series SATA-RAID 02:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 46) 02:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
CentOS55[root@home ~]# lsusb Bus 002 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 Bus 001 Device 002: ID 11b0:6888 ATECH FLASH TECHNOLOGY
mhr
Thanks for your helpl!!
On Sun, Jun 6, 2010 at 3:14 PM, John Thomas gmane-2006-04-16@jt-socal.com wrote:
00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1)
It is possible that your problem is related to this bug:
http://bugs.centos.org/view.php?id=4335 ( sound and system problems in CentOS 5.5 with Nvidia controllers )
In any event, it would not hurt to try the workaround in there and see what happens.
Edit /etc/modprobe.conf to have the following line and reboot:
options snd-hda-intel index=0 enable_msi=0
Akemi
On Sun, Jun 6, 2010 at 3:14 PM, John Thomas gmane-2006-04-16@jt-socal.com wrote:
It sounds like you have a non-standard driver that is not compatible with the latest kernel.
Hmm, using nvidia video driver from ELRepo and I don't remember anything else. I tried without the nvidia driver, but same problem.
Can you post more details about the machine, say info from a working kernel? Things like configuration, drivers, etc.
Hmm, not sure how to do that. How about this: CentOS55[root@home ~]# lspci 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) 00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1) 00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2) 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1) 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2) 00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV40 [GeForce 6800 GT] (rev a1) 02:08.0 RAID bus controller: 3ware Inc 9xxx-series SATA-RAID 02:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 46) 02:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
CentOS55[root@home ~]# lsusb Bus 002 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 Bus 001 Device 002: ID 11b0:6888 ATECH FLASH TECHNOLOGY
I'd run the 64-bit distro on an Opteron, not PAE or 32-bit. That shouldn't make a difference, but....
Have you checked your /lib/modules directories for non-standard drivers? If there are any, you might try disabling them and if that works, put them back one at a time to see which one kills it.
I haven't done much with ELREPO, but I use the rpmforge nVidia driver for my video card (a cheapo GeForce 7200gs) and it doesn't give me any problems at all.
Do you know which motherboard you have? I doubt that this would be it, but it doesn't hurt to check. Sometimes you need to turn on or off certain switches (mine's an ECS GeForce 6100PM-M2, and I have to turn off APIC because the motherboard goes haywire with it enabled). I'd expect this to have shown up in earlier kernels.
You might see if Dell is any help....
Anyone else?
mhr
Anyone recall what kernel runs on the centos 5.5 live cd? Might be worth trying to boot off that to eliminate local config or modules as a problem and confirm a kernel only issue.
James
Sent from Android mobile
On Jun 7, 2010 5:12 AM, "MHR" mhullrich@gmail.com wrote:
On Sun, Jun 6, 2010 at 3:14 PM, John Thomas
gmane-2006-04-16@jt-socal.com wrote:
It sounds like you have a non-standard driver that is not compatible with the latest kernel.
...
I'd run the 64-bit distro on an Opteron, not PAE or 32-bit. That shouldn't make a difference, but....
Have you checked your /lib/modules directories for non-standard drivers? If there are any, you might try disabling them and if that works, put them back one at a time to see which one kills it.
I haven't done much with ELREPO, but I use the rpmforge nVidia driver for my video card (a cheapo GeForce 7200gs) and it doesn't give me any problems at all.
Do you know which motherboard you have? I doubt that this would be it, but it doesn't hurt to check. Sometimes you need to turn on or off certain switches (mine's an ECS GeForce 6100PM-M2, and I have to turn off APIC because the motherboard goes haywire with it enabled). I'd expect this to have shown up in earlier kernels.
You might see if Dell is any help....
Anyone else?
mhr
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.c...
On Sun, 2010-06-06 at 15:14 -0700, John Thomas wrote:
CentOS55[root@home ~]# lsusb Bus 002 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 Bus 001 Device 002: ID 11b0:6888 ATECH FLASH TECHNOLOGY
--- For kicks try unpluging the USB Drive and try booting again.
JOhn
I have a machine that has worked fine for years on CentOS5. kernel-PAE-2.6.18-164.15.1.el5 is the last "works fine" kernel, but kernel-PAE-2.6.18-194.3.1.el5 crashes at boot every time.
FYI i am having anaconda issues with 2.6.18-194 - basically anaconda crashes randomly both on x4100's and some r610's
These are bare metal installs and happen on CentOS and RHEL - I have a work around but would be nice to know whats going on.
Hi,
I had an issue with this kernel upgrade too. All worked fine until the 194 Kernel then hung on boot on 4 machines all with identical motherboards. All had USB keyboards, when replaced with PS2 keyboards all worked fine! What is to blame? - motherboard, kernel or keyboard.. I have no idea.
I have also seen similar hangs on boot with asrock motherboards and there crazy version of a VGA slot that only too certain cards. Does you machine have an onboard graphics adapter you could try booting with?
Steve
On Sun, 6 Jun 2010, John Thomas wrote:
I have a machine that has worked fine for years on CentOS5. kernel-PAE-2.6.18-164.15.1.el5 is the last "works fine" kernel, but kernel-PAE-2.6.18-194.3.1.el5 crashes at boot every time.
I tried banging on the side of the monitor to no avail.
All kidding aside, here are pictures of my monitor when booting 194 in case that is helpful. http://jt-socal.com/sites/jt-socal.com/files/kernel-panic.jpg http://jt-socal.com/sites/jt-socal.com/files/just-before-crashing.jpg
Any suggestions on fixing this?
-
Akemi Yagi -
James Hogarth -
John Thomas -
JohnS -
Kevin Krieser -
MHR -
Steve Brooks -
Tom Brown