On Mon, Nov 2, 2009 at 7:02 PM, Len Brown <lenb@xxxxxxxxxx> wrote: >> > I get this when modprobing some module I am working on. I figured it >> > was the module's fault but the EIP points to something else so I am >> > not sure. I get the following repeating about 4 times on 2.6.32-rc5: >> >> >> you can get this if your own code leaves interrupts disabled in a >> kernel thread and then lets the cpu go idle... > > Unclear. > > acpi_enter_idle_bm() assumes that it is entered with irqs enabled, > and so it we unconditionally disables IRQs. > > Then we unconditionally re-enable them. > > The problem seems to be that right after we enable them, > we find that they are actually disabled, perhaps as > a side-effect of SMM. > > Is your machine a Dell, per chance? Nope. > Please test the patches in this bug report: > http://bugzilla.kernel.org/show_bug.cgi?id=14101 In my case it was as Arjan pointed out and I've fixed it in my driver. Sorry for not reporting back and thanks for your review. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
