Asus CUV4X-D, 2.4.3 crashes at boot
Hi,
I've compiled kernel 2.4.3 on the following RH7 system, and I'm now getting random crashes at boot, during IO-APIC initialisation. Random meaning that sometimes it boots fine, other times it doesn't, and it hangs in different places (but always around IO-APIC stuff). It almost always hangs after a cold boot - if I do a Ctrl+Alt+Del then it will usually boot up OK.
System: Asus CUV4X-D motherboard, Dual P3 800EB.
The last thing I see on the screen when it hangs is, for example:
CPU1: Intel Pentium III (Coppermine) stepping 06 CPU has booted.
Before bogomips.
Total of 2 processors activated (3207.98 BogoMIPS). Before bogocount - setting activated=1. Boot done.
ENABLING IO-APIC IRQs
...changing IO-APIC physical APIC ID to 2 ... ok. Synchronizing Arb IDs.
...TIMER: vector=49 pin1=2 pin2=0
Sometimes it gets a little further, but it's always somewhere near the IO-APIC
stuff.
When it does boot, I get:
CPU1: Intel Pentium III (Coppermine) stepping 06
CPU has booted.
Before bogomips.
Total of 2 processors activated (3207.98 BogoMIPS).
Before bogocount - setting activated=1.
Boot done.
ENABLING IO-APIC IRQs
...changing IO-APIC physical APIC ID to 2 ... ok. Synchronizing Arb IDs.
init IO_APIC IRQs
IO-APIC (apicid-pin) 2-5, 2-10, 2-11, 2-13, 2-19, 2-20, 2-21, 2-22, 2-23
not connected.
..TIMER: vector=49 pin1=2 pin2=0
number of MP IRQ sources: 17.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................
IO APIC #2......
.... register #00: 02000000
....... : physical APIC id: 02
.... register #01: 00178011
....... : max redirection entries: 0017
....... : IO APIC version: 0011
WARNING: unexpected IO-APIC, please mail
to [email protected]
.... register #02: 00000000
....... : arbitration: 00
Full dmesg output:
http://www.expio.co.nz/~sgarner/orion/smp/dmesg.txt
My kernel .config:
http://www.expio.co.nz/~sgarner/orion/smp/config.txt
Output from lspci -xx:
http://www.expio.co.nz/~sgarner/orion/smp/lspcixx.txt
Any ideas?
Thanks in advance,
Simon Garner
Quoted 11 lines · Simon Garner
Hi,
I've compiled kernel 2.4.3 on the following RH7 system, and I'm now getting random crashes at boot, during IO-APIC initialisation. Random meaning that sometimes it boots fine, other times it doesn't, and it hangs in different places (but always around IO-APIC stuff). It almost always hangs after a cold boot - if I do a Ctrl+Alt+Del then it will usually boot up OK.
System: Asus CUV4X-D motherboard, Dual P3 800EB.
The last thing I see on the screen when it hangs is, for example:
[snip]
I've seen the exact same behavior with my CUV4X-D (2x1GHz) under 2.4.2 (debian woody). In addition, the kernel would sometimes hang around NMI watchdog enable. At least, I think it's trying to `enable'. The hang would occur around 50% of boot attempts. Once booted, everything was stable. A non-SMP 2.4.2 kernel (no IO-APIC either, sorry, didn't test that) always booted without hangs.
Strangely, (happily for me,) the boot hangs stopped with 2.4.3. I've booted maybe 10 times (hot and cold) since I built 2.4.3 and I've had no hangs. When I get back to the box, I'll try booting a few dozen more times and see if I can confirm your observation.
Signature · 2 lines
Allen Campbell [email protected]
Quoted 3 lines
I've seen the exact same behavior with my CUV4X-D (2x1GHz) under 2.4.2 (debian woody). In addition, the kernel would sometimes hang around NMI watchdog enable. At least, I think it's trying to
Known problem. Thats one reason why -ac trees had nmi watchdog turned off.
From: "Alan Cox" <[email protected]>
Quoted 5 lines
Quoted 3 lines
I've seen the exact same behavior with my CUV4X-D (2x1GHz) under 2.4.2 (debian woody). In addition, the kernel would sometimes hang around NMI watchdog enable. At least, I think it's trying to
Known problem. Thats one reason why -ac trees had nmi watchdog turned off.
It still crashes with nmi_watchdog turned off.
Running with noapic fixes it but then the system crashes if you access the RTC with hwclock (and probably creates a hundred other problems...).
How can I get this chipset/motherboard supported properly under Linux? I'm happy to test patches etc. on the box. *pleading*
Cheers
Simon Garner
Quoted 8 lines · Simon Garner
From: "Alan Cox" <[email protected]>
Quoted 5 lines
Quoted 3 lines
I've seen the exact same behavior with my CUV4X-D (2x1GHz) under 2.4.2 (debian woody). In addition, the kernel would sometimes hang around NMI watchdog enable. At least, I think it's trying to
Known problem. Thats one reason why -ac trees had nmi watchdog turned off.
Quoted 7 lines
It still crashes with
nmi_watchdogturned off.Running with noapic fixes it but then the system crashes if you access the RTC with hwclock (and probably creates a hundred other problems...).
How can I get this chipset/motherboard supported properly under Linux? I'm happy to test patches etc. on the box. *pleading*
Patience is likely to be effective. The chipset isn't exactly rare being on SMP boards from Gigabyte, MSI, Tyan and Asus, and likely others. I'm betting it will be fixed soon enough. UP and 2.2.x kernels worked fine here if you're really desperate. OTOH, the board is stable once you get past the boot problems... What sort of production system needs frequent unattended boots?
Sorry about this, I just don't remember signing any paychecks for what I know is likely to be a non-issue probably before the next time I actually have to do something drastic, like reboot.
Signature · 2 lines
Allen Campbell | Lurking at the bottom of the [email protected] | gravity well, getting old.
From: "Allen Campbell" <[email protected]>
Quoted 7 lines
Patience is likely to be effective. The chipset isn't exactly rare being on SMP boards from Gigabyte, MSI, Tyan and Asus, and likely others. I'm betting it will be fixed soon enough. UP and 2.2.x kernels worked fine here if you're really desperate. OTOH, the board is stable once you get past the boot problems... What sort of production system needs frequent unattended boots?
I was planning to install the box as a colocated production webserver in 1-2 weeks' time.
I don't want to colocate a box that I cannot reboot, so I'll just have to sit on it until it's fixed I guess.
Regards
Simon Garner
From: "Allen Campbell" <[email protected]>
Quoted 6 lines
I've seen the exact same behavior with my CUV4X-D (2x1GHz) under 2.4.2 (debian woody). In addition, the kernel would sometimes hang around NMI watchdog enable. At least, I think it's trying to `enable'. The hang would occur around 50% of boot attempts. Once booted, everything was stable. A non-SMP 2.4.2 kernel (no IO-APIC either, sorry, didn't test that) always booted without hangs.
Yep, sounds like the same problem.
Quoted 6 lines
Strangely, (happily for me,) the boot hangs stopped with 2.4.3. I've booted maybe 10 times (hot and cold) since I built 2.4.3 and I've had no hangs. When I get back to the box, I'll try booting a few dozen more times and see if I can confirm your observation.
Please do test it. I think you'll find the problem is still very much present.
Cheers
Simon Garner
Quoted 13 lines · Simon Garner
From: "Allen Campbell" <[email protected]>
Quoted 6 lines
I've seen the exact same behavior with my CUV4X-D (2x1GHz) under 2.4.2 (debian woody). In addition, the kernel would sometimes hang around NMI watchdog enable. At least, I think it's trying to `enable'. The hang would occur around 50% of boot attempts. Once booted, everything was stable. A non-SMP 2.4.2 kernel (no IO-APIC either, sorry, didn't test that) always booted without hangs.
Yep, sounds like the same problem.
Quoted 1 line
Quoted 8 lines
Quoted 5 lines
Strangely, (happily for me,) the boot hangs stopped with 2.4.3. I've booted maybe 10 times (hot and cold) since I built 2.4.3 and I've had no hangs. When I get back to the box, I'll try booting a few dozen more times and see if I can confirm your observation.
Please do test it. I think you'll find the problem is still very much present.
Yeah, still there. Cold boot only.