Skip to contentSkip to conversation

Asus CUV4X-D, 2.4.3 crashes at boot

DISCUSSION Simon Garner 3 participants 4 messages Apr 1, 2001

lore
Share & tools
lore
#0 lore raw

From: "Mikael Pettersson" <[email protected]>

Quoted 6 lines

Boot with "nmi_watchdog=0" as a boot parameter. Does it work now?

Some people have reported before here that the IO-APIC driven NMI watchdog itself can cause boot-time hangs.

/Mikael

Thanks, but I do not have watchdog support compiled into the kernel.

#1 lore raw
Quoted 11 lines · Simon Garner

From: "Mikael Pettersson" <[email protected]>

Quoted 6 lines

Boot with "nmi_watchdog=0" as a boot parameter. Does it work now?

Some people have reported before here that the IO-APIC driven NMI watchdog itself can cause boot-time hangs.

/Mikael

Thanks, but I do not have watchdog support compiled into the kernel.

Doesn't matter. The NMI-watchdog tries to detect SMP-lockups, and is always present. Unless you specifically disable it on boot.

/David Weinehall
_ _
// David Weinehall <[email protected]> /> Northern lights wander \\

//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </
#2 lore raw
Quoted 5 lines · David Weinehall
Quoted 1 line · Simon Garner

Thanks, but I do not have watchdog support compiled into the kernel.

Doesn't matter. The NMI-watchdog tries to detect SMP-lockups, and is always present. Unless you specifically disable it on boot.

Not any more. In 2.4.3-ac* the default is no watchdog and it must be specifically enabled at boot.

#3 lore raw

From: "Keith Owens" <[email protected]>

Quoted 6 lines
Quoted 2 lines

Doesn't matter. The NMI-watchdog tries to detect SMP-lockups, and is always present. Unless you specifically disable it on boot.

Not any more. In 2.4.3-ac* the default is no watchdog and it must be specifically enabled at boot.

nmi_watchdog 0 didn't help - the above would explain why.

Any more ideas? My expensive server is basically useless because of this. :(