|Summary:||T510 43495KG won't resume with 32bit installation|
|Product:||Power Management||Reporter:||Marc B. (kernel.org)|
|Severity:||high||CC:||florian, jrnieder, lenb, maciej.rutecki, rjw|
|Bug Depends on:|
|Bug Blocks:||7216, 36912|
Description Marc B. 2011-06-30 22:39:05 UTC
As briefly described in I cannot resume the box after successful suspend with 3.0.0-rc5 with the following configuration:
Comment 5 Marc B. 2011-06-30 22:52:33 UTC
As briefly described in 20110630220050.GB30291@marc.osknowledge.org I cannot resume the box after successful suspend with 3.0.0-rc5 with the following configuration:
Comment 6 Marc B. 2011-07-21 18:05:44 UTC
Hi there, has anyone been testing this? I re-tested it with git HEAD some minutes ago and the issue still persists. As I assume 3.0.0 will be released very soon it would be great if anyone could advise me what to do or send me patches I could test. I really consider this a show stopper... Marc
Comment 7 Marc B. 2011-07-28 06:25:20 UTC
Changed the affected kernel version to rc1.
Comment 8 Len Brown 2011-08-02 02:53:18 UTC
did 2.6.39 work? does 3.0 work or fail? If Yes and No, respectively, can you bisect to find what commit broke the feature? you mention 32-bit in the description, does that mean 64-bit works and 32-bit fails? have you tried the debug steps here? Documentation/power/basic-pm-debugging.txt
Comment 9 Marc B. 2011-08-02 05:41:33 UTC
OK, here goes: a) 188.8.131.52 works absolutely fine. b) 3.0 final doesn't work c) 3.0-rc1 didn't work either d) I cannot bisect it as already stated on LKML due to having not much time currently e) I use 32-bit instalation on the 64-bit hardware, but I did not try a 64-bit installation. Thus I cannot say if 64-bit is broken as well. d) Does testing that make sense? The box hibernates as usual, but upon resume the screens stays black (no backlight). Testing proc freezing and such might not bring me any further, does it? Regards, Marc
Comment 10 Rafael J. Wysocki 2011-08-14 19:00:52 UTC
(In reply to comment #9) > Testing proc freezing and such might not bring me any further, does it? In fact, it might give us a clue. Without any more information we can't really do anything here. Do you use i915?
Comment 11 Marc B. 2011-08-14 20:00:43 UTC
Hi Rafael, so, I still have no time to bisect it right now. I guess when I have time for it at least 3.1 will be out thus that won't bring us any further. I'm really sorry I can't do that, but you know there's nothing more bad and time-consuming to bisect than resume issues. I do not use i915, just nouveau or maybe the blob when I need CUDA. Please come back to me in case you need any more info... Regards, Marc
Comment 12 Rafael J. Wysocki 2011-08-14 20:54:14 UTC
I suspect your hibernate problem is related to the graphics driver. Perhaps you can verify this somehow?
Comment 13 Marc B. 2011-08-16 13:46:58 UTC
Hi Rafael, I suspended the box without the blob and/or nouveau loaded. It didn't resume as before. I attach the current .config of the box. Regards, Marc
Comment 14 Marc B. 2011-08-16 13:48:48 UTC
Created attachment 68982 [details] .config 3.1.0-rc2-dezzy-00324-g93ee7a9-dirty
Comment 15 Jonathan Nieder 2011-08-26 20:57:33 UTC
(In reply to comment #9) > The box hibernates as usual, but upon resume > the screens stays black (no backlight). Does capslock toggle its LED? Does networking work --- can you log into the machine remotely? When you switch between a graphical and a text console with ctrl-alt-f1 / f7, does that affect the backlist? Can you get a log from this state (for example using netconsole)?
Comment 16 Jonathan Nieder 2011-08-29 04:34:21 UTC
s/backlist/backlight, sorry. (In reply to comment #11) > so, I still have no time to bisect it right now. If you get a chance, please try reverting 983bbf1af066 (x86: Don't unmask disabled irqs when migrating them, 2011-05-06).
Comment 17 Marc B. 2011-08-29 17:41:56 UTC
Hey all, I reverted the commit on to of current HEAD but no luck - the box still hangs. The backlight doesn't turn on and NUMLOCK doesn't toggle. It hangs in such an early stage that not even disc IO happens (besides one short flashing of the disc LED which is most probably the disc spinning up or something). Now that I read it - you meant CAPSLOCK, not NUMLOCK. Wait, I'll give it a second try...
Comment 18 Marc B. 2011-08-29 17:48:33 UTC
OK, CAPSLOCK toggles... :)
Comment 19 Marc B. 2012-01-13 20:32:57 UTC
I close this one (finally after the long downtime) as I cannot reproduce this anymore. I was able to trigger this even with 184.108.40.206 and thus it's a .config option triggered issue that makes this happen. However, I lost the .config which resulted in this issue to happen.