lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 02 Nov 2009 22:02:43 -0500 (EST) From: Len Brown <lenb@...nel.org> To: Arjan van de Ven <arjan@...radead.org> Cc: "Luis R. Rodriguez" <mcgrof@...il.com>, linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org Subject: Re: scheduling while atomic acpi_idle_enter_bm > > 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? Please test the patches in this bug report: http://bugzilla.kernel.org/show_bug.cgi?id=14101 thanks, Len Brown, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists