[arch-general] Failure to resume on kernel >3.9.9
Hi list, I realise this email comes with a deplorable paucity of informaton, but I haven't found *any* logs relating to this event. I also realise I've waited what may be considered overlong to ask for help, but I was hoping the bug would be fixed in a later kernel release and it wasn't. Google has failed me, so now I come to you for help. My laptop is an HP Pavilion g7. The system suspends normally, but fails to resume leaving a powered-off screen and no responsiveness to keyboard input, including the magic sysrq, but the caps lock light turns on and off. At first I suspected fglrx, but it happens with or without fglrx loaded, and with or without nomodeset on the kernel command line. Further, it happens identically inside or outside of X. I tried git-bisect on the kernel but gave up after many hours of compiling and testing — anyone know of a faster/easier way to do this? I'm currently running kernel 3.9.8, but am perfectly willing to update again and generate a failure to provide any logs someone thinks may help — I haven't found anything, but I may not be looking in the right place. Thank you, ~Celti
On 12/05/13 at 01:54am, Patrick Burroughs (Celti) wrote:
Hi list,
I realise this email comes with a deplorable paucity of informaton, but I haven't found *any* logs relating to this event. I also realise I've waited what may be considered overlong to ask for help, but I was hoping the bug would be fixed in a later kernel release and it wasn't. Google has failed me, so now I come to you for help.
My laptop is an HP Pavilion g7. The system suspends normally, but fails to resume leaving a powered-off screen and no responsiveness to keyboard input, including the magic sysrq, but the caps lock light turns on and off.
At first I suspected fglrx, but it happens with or without fglrx loaded, and with or without nomodeset on the kernel command line. Further, it happens identically inside or outside of X.
I tried git-bisect on the kernel but gave up after many hours of compiling and testing — anyone know of a faster/easier way to do this?
I'm currently running kernel 3.9.8, but am perfectly willing to update again and generate a failure to provide any logs someone thinks may help — I haven't found anything, but I may not be looking in the right place.
Thank you, ~Celti
Sounds like https://bugzilla.kernel.org/show_bug.cgi?id=61781 -- Jelle van der Waa
On Thu, Dec 5, 2013 at 6:05 AM, Jelle van der Waa <jelle@vdwaa.nl> wrote:
Sounds like https://bugzilla.kernel.org/show_bug.cgi?id=61781
That showed up in 3.11 and is fixed by reverting to 3.10, and also appears to be i686 only. I did find an Ubuntu bug-report for the same apparent issue last night, but with no helpful information: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1238203. ~Celti
On Thu, Dec 5, 2013 at 1:54 AM, Patrick Burroughs (Celti) <celticmadman@gmail.com> wrote:
Hi list,
[unnecessary babble clipped]
Hi again list, Just wanted to say that this is partially fixed with 3.12.7 (or possibly a bit earlier, haven't tested) and the radeon driver: the screen stays off and nothing short of a reboot will reactivate it; and fully fixed with 3.12.7 and fglrx. Time for me to go update bug reports. Regards, ~Celti
participants (2)
-
Jelle van der Waa
-
Patrick Burroughs (Celti)