laptop / computer hardlocks during execution of 32bit applications(binaries) on 64bit system (Gentoo)
Quoted 5 lines
Quoted 3 lines
- if yes, does booting with "nmi_watchdog=2 idle=poll" give you a working NMI watchdog? (working NMI watchdog means the NMI counts increase for all cores in
/proc/interrupts).booting with the above gives me an incrementing NMI counter in
/proc/interrupts
Ingo,
Is there anything else that needs to be set in the kernel config for the nmi watchdog to trigger?
I ask because I just had a hang but nothing showed on the _serial_ console - I waited a couple of minutes before rebooting.... Is there any other way to verify the watchdog is working?
I seem to need X active with mix of 32 and 64 bit applications active to get hung here. A massivily threaded 64 bit java app along with 32 bit firefox and a wine active will eventually trigger things here. If I had to guess I would say that it the switch from 32 to 64 (or vise versa) that triggers the isuue.
TIA & test/debug patches welcome,
Ed Tomlinson
Quoted 7 lines · Ed Tomlinson
Quoted 6 lines
Quoted 3 lines
- if yes, does booting with "nmi_watchdog=2 idle=poll" give you a working NMI watchdog? (working NMI watchdog means the NMI counts increase for all cores in
/proc/interrupts).booting with the above gives me an incrementing NMI counter in
/proc/interrupts
Quoted 8 lines
Ingo,
Is there anything else that needs to be set in the kernel config for the nmi watchdog to trigger?
I ask because I just had a hang but nothing showed on the _serial_ console - I waited a couple of minutes before rebooting.... Is there any other way to verify the watchdog is working?
if you cause a hard lockup intentionally via an infinite irqs-off loop:
# cat > lockupcli.c
main ()
{
iopl(3);
for (;;) asm("cli");
}
Ctrl-D
make lockupcli
./lockupclidoes the NMI watchdog properly trigger? If not, does booting with idle=poll change the situation?
Ingo