Re: [2.6.17-rc5-mm2] crash when doing second suspend: BUG inarch/i386/kernel/nmi.c:174

[Andrew Morton]

On Mon, 05 Jun 2006 00:37:22 -0700
Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:

> Jeremy Fitzhardinge wrote:
> > I'm trying to get suspend/resume working properly on my Thinkpad X60.
> > This is a dual-core machine, so its running in SMP mode.
> >
> > Now that I have a set of patches to make AHCI resume properly, I'm
> > getting a crash on the second suspend.  I can't get an actual listing of
> > the oops, but I have a set of screenshots if anyone needs more details.
> >
> > The gist is that there's a BUG_ON failing at arch/i386/kernel/nmi.c:174
> > (BUG_ON(counter > NMI_MAX_COUNTER_BITS)), in release_evntsel_nmi.  The
> > backtrace is:
> >
> >     release_evntsel_nmi
> >     stop_apci_nmi_watchdog
> >     on_each_cpu
> >     disable_lapic_nmi_watchdog
> >     lapic_nmi_suspend
> >     sysdev_suspend
> >     device_power_down
> >     suspend_enter
> >     enter_state
> >     state_store
> >     subsys_attr_store
> >     sysfs_write_file
> >     vfs_write
> >     sys_write
> >     sysenter_past_esp
> 
> This BUG_ON was introduced by the patch 
> x86_64-mm-add-performance-counter-reservation-framework-for-up-kernels.patch.
> 

http://bugzilla.kernel.org/show_bug.cgi?id=6647 has details.

Do you think the suspend breakage is related to that patch?

Miles also reports that every second suspend fails for him.  Miles, does
'nmi_watchdog=0' make it better?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/