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 linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 12 Apr 2009 14:11:57 +0100 From: Alan Jenkins <alan-jenkins@...fmail.co.uk> To: Bjorn Helgaas <bjorn.helgaas@...com> CC: linux-acpi@...r.kernel.org, linux-kernel <linux-kernel@...r.kernel.org>, Kernel Testers List <kernel-testers@...r.kernel.org> Subject: [BISECTED] EEE PC hangs when booting off battery Alan Jenkins wrote: > Tzy-Jye Daniel Lin wrote: > >> On Sat, Apr 11, 2009 at 5:41 AM, Alan Jenkins >> <alan-jenkins@...fmail.co.uk> wrote: >> >> >>> Regression #6 on latest git! (last known good is 2.6.29-rc8) >>> >>> Magic SysRQ keys work though. Unfortunately, SysRq-W / SysRq-T generate >>> too much output, so the useful bits immediately scroll off the top of >>> the screen. I can't press SysRq-P (even if that would help), because >>> the SysRQ key on my laptop is accessed using a Fn modifier key, which >>> also turns the left hand side of the keyboard into a numeric pad. >>> >>> >> I don't own an Eee, but having played with one, the key sequence >> >> Alt down >> Fn down >> SysRq down, up >> Fn up >> P down, up >> Alt up >> >> should work just fine. As long as you keep holding Alt, you don't >> need to continue holding SysRq after the initial keypress. >> >> >> >>> Magic SysRQs on my USB keyboard generate no response. (Sometimes the >>> numlock key seems to work though. I can't tell on the laptop keyboard >>> because the laptop doesn't have a numlock led). >>> >>> >> SysRq over USB has never worked. On PC hardware, Magic SysRq depends >> on features of the built-in i8042 controller, which only handles PS/2 >> input. >> >> > Great, thanks a lot! > > I was able to run SysRq-P, and found the following backtrace - > > Pid: 0 > EIP is at acpi_idle_enter_bm+0x1df/0x208 [processor] > cpud_idle_call > cpu_idle > rest_init > start_kernel > i386_start_kernel > 7ec0a7290797f57b780f792d12f4bcc19c83aa4f is first bad commit commit 7ec0a7290797f57b780f792d12f4bcc19c83aa4f Author: Bjorn Helgaas <bjorn.helgaas@...com> Date: Mon Mar 30 17:48:24 2009 +0000 ACPI: processor: use .notify method instead of installing handler directly This patch adds a .notify() method. The presence of .notify() causes Linux/ACPI to manage event handlers and notify handlers on our behalf, so we don't have to install and remove them ourselves. Signed-off-by: Bjorn Helgaas <bjorn.helgaas@...com> CC: Zhang Rui <rui.zhang@...el.com> CC: Zhao Yakui <yakui.zhao@...el.com> CC: Venki Pallipadi <venkatesh.pallipadi@...el.com> CC: Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com> Signed-off-by: Len Brown <len.brown@...el.com> However, reverting this commit from v2.6.30-rc1 doesn't solve the hang. Alan -- 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