You are not logged in.

#1 2011-01-09 15:52:23

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,597
Website

[kernel 2.6.37] - NMI watchdog disabled for cpu0/cannot boot

I just put the 2.6.37 kernel from [testing] on an older machine (Athlon XP/Asus A7M266 motherboard).  Upon rebooting once, everything was fine.  After a 2nd reboot, I was presented with:

NMI watchdog disabled for cpu0: unable to create perf event: -95
ERROR: Unable to locate IOAPIC for GSI 8
ERROR: Unable to locate IOAPIC for GSI 13
ERROR: Unable to locate IOAPIC for GSI 6
ERROR: Unable to locate IOAPIC for GSI 7
ERROR: Unable to locate IOAPIC for GSI 4
ERROR: Unable to locate IOAPIC for GSI 3
ERROR: Unable to locate IOAPIC for GSI 1
ERROR: Unable to locate IOAPIC for GSI 12
<<< Hard lock >>>

I booted to a live environment, chrooted in and rebuild the kernel images.  Upon rebooted, same error message/hard lock.  For no apparent reason hours later, I booted it again and it loaded-up just fine.  I have rolled back to 2.6.36-ARCH.  Is this bug worthy?  I'm thinking it's more of an upstream problem.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#2 2011-01-15 14:51:29

pjezek
Member
From: Praha - CZ
Registered: 2005-05-19
Posts: 79

Re: [kernel 2.6.37] - NMI watchdog disabled for cpu0/cannot boot

I have been facing this random hard lock on booting several days, no reason why. I suspect bios battery low voltage or some bug in I/O identification during boot... Any other can report?

Last edited by pjezek (2011-01-15 14:51:49)


Our tomcat for your mice! Archlinux for your comps! Alfa Romeo for your roads! Faster running guaranted!

Offline

#3 2011-01-29 09:02:13

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,597
Website

Re: [kernel 2.6.37] - NMI watchdog disabled for cpu0/cannot boot

Rolled back to 2.6.36 but I am seeing these guys appear in the dmesg but they are not hard locking on boot-up.

Switching to clocksource tsc
pnp: PnP ACPI init
ACPI: bus type pnp registered
ERROR: Unable to locate IOAPIC for GSI 8
ERROR: Unable to locate IOAPIC for GSI 13
ERROR: Unable to locate IOAPIC for GSI 6
ERROR: Unable to locate IOAPIC for GSI 7
ERROR: Unable to locate IOAPIC for GSI 4
ERROR: Unable to locate IOAPIC for GSI 3
ERROR: Unable to locate IOAPIC for GSI 1
ERROR: Unable to locate IOAPIC for GSI 12
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered

I found this thread which indicates that these are harmless.  I can't explain the hardlock...

These are just warning telling you it cant override something because it doesn't exist. The outcome is the same. If you had IOAPICS, then ACPI would override them. Since you don't have them, then ACPI doesn't need to override them and can do it's thing normally.

and

>> [ 0.089969] ERROR: Unable to locate IOAPIC for GSI 13
>> [ 0.090556] ERROR: Unable to locate IOAPIC for GSI 8
>> [ 0.091104] ERROR: Unable to locate IOAPIC for GSI 12
>> [ 0.091375] ERROR: Unable to locate IOAPIC for GSI 1
>> [ 0.093195] ERROR: Unable to locate IOAPIC for GSI 4
>> [ 0.094342] ERROR: Unable to locate IOAPIC for GSI 10
>> [ 0.096335] ERROR: Unable to locate IOAPIC for GSI 6
>
>The new warning originates from acpi_get_override_irq, which I changed to
>use helper functions that warn when they fail.
>
>When IOAPICs and ACPI are enabled in a kernel and run on ACPI hardware
>that doesn't use the ioapics the pnp acpi code calls this function,
>looking for ACPI irq overrides. ACPI irq overrides exist only in the
>ioapic case so this function will never succeed. So make the function
>fail fast so we don't call into help functions that legitimately
>complain when they fail.
>
>Tested-by: Avinash Kurup <kurup.avinash [at] gmail>
>Signed-off-by: "Eric W. Biederman" <ebiederm [at] xmission>

Last edited by graysky (2011-01-29 09:05:24)


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#4 2011-01-29 11:59:58

ferda
Member
Registered: 2010-02-05
Posts: 67

Re: [kernel 2.6.37] - NMI watchdog disabled for cpu0/cannot boot

Have you tried booting with boot codes like noapic/noacpi/acpi=off ?

Offline

#5 2011-01-29 12:26:26

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,597
Website

Re: [kernel 2.6.37] - NMI watchdog disabled for cpu0/cannot boot

@ferda - Not yet.  I plan to when I have a some time to play with it.  I found that suggestion through googling around as well.  Thank you the post.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#6 2011-01-29 21:15:53

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,597
Website

Re: [kernel 2.6.37] - NMI watchdog disabled for cpu0/cannot boot

Update: if I use kernel26-lts I don't see these errors at all.  Any speculation as to their cause?  Something in the config or the kernel?  There are numerous diffs between the lts config and the current config from [testing].

Last edited by graysky (2011-01-29 21:24:31)


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

Board footer

Powered by FluxBB