[Bug 450256] New: System freezes during resume from disk
https://bugzilla.novell.com/show_bug.cgi?id=450256 Summary: System freezes during resume from disk Product: openSUSE 11.1 Version: RC 1 Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: radomir.cernoch@gmail.com QAContact: qa@suse.de Found By: Community User When resuming the system from "suspend to disk", the machine freezes completely. I am using a fresh openSUSE 11.1-RC1 with 2.6.27.7-4-default kernel on IBM ThinkPad T42. It is very likely that the problem is related to the graphical card as it hangs approximately around the time, when X server gets started. Moreover after the freeze CapsLock LED starts blinking, which resemlbes me the struggle with proprietal ATI drivers on a different notebook. The problem does not occur during suspend/resume to/from RAM. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c1 --- Comment #1 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-11-29 10:07:19 MST --- Created an attachment (id=256746) --> (https://bugzilla.novell.com/attachment.cgi?id=256746) /var/log/pm-suspend.log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c2 --- Comment #2 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-11-29 10:08:26 MST --- Created an attachment (id=256747) --> (https://bugzilla.novell.com/attachment.cgi?id=256747) Output of 'lshal' -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |seife@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c3 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rjw@novell.com, pavel@novell.com, | |seife@novell.com AssignedTo|seife@novell.com |sndirsch@novell.com Component|Kernel |X.Org QAContact|qa@suse.de |xorg-maintainer-bugs@forge.provo.novell.com --- Comment #3 from Stefan Seyfried <seife@novell.com> 2008-12-01 04:20:33 MST --- The log file shows that the machine suspends and resumes wonderfully, so if it hangs when switching back to X it is most likely a X server issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User mhopf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c4 Matthias Hopf <mhopf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |radomir.cernoch@gmail.com --- Comment #4 from Matthias Hopf <mhopf@novell.com> 2008-12-01 08:17:13 MST --- Can you verify by switching to console before suspending whether the machine crashes upon resume as well? Or only after you switch back manually after that? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c5 --- Comment #5 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-12-01 11:50:25 MST --- I have done some more testing today and after a few dozens of suspend/resume I am quite sure that: 1) The problem is independent of being on the console or in X. 2) It is also independent of whether the X server running when suspending from console. 3) It is independent of using the standard framebuffer or the 'radeonfb' module. 4) I haven't tested switching the X from 'radeon' driver to 'vesa'. Should I? But!!! I have realized that the system freezes during resume if and only if the power was removed and reattached during the hibernation. There is a 100% accurancy on this. I think that the problem is caused by erasing the graphical chip's memory when the power adaptor is removed. It would explain the fact, that the system works well until it switches from the "suspend console" (the one which shows the progress of suspend/resume; sorry for not knowing the right name) to either the normal console (tty0..5) or X server. Moreover it would also fit the perfectly reliable suspending to RAM (the graphic card memory's power supply should be still on during s2ram). However I am not sure, in which part of the system the bug has appeared. I just know that the suspend to disk worked well on openSUSE 10.3... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 Radomír Černoch <radomir.cernoch@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|radomir.cernoch@gmail.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c6 Rafael Wysocki <rjw@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trenn@novell.com Status|ASSIGNED |NEEDINFO Info Provider| |radomir.cernoch@gmail.com --- Comment #6 from Rafael Wysocki <rjw@novell.com> 2008-12-01 14:33:19 MST --- This almost certainly is a kernel issue. Your observation that the failure only happens if AC power is removed during hibernation seems to indicate and ACPI problem. What happens if you hibernate and resume on battery? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c7 Radomír Černoch <radomir.cernoch@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|radomir.cernoch@gmail.com | --- Comment #7 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-12-01 15:09:31 MST --- Suspend/resume (s&r) from battery causes a freeze always. The only difference is that the blinking CapsLock blinks slower as the CPU frequency is lower ;-). I have even tried pluging in the AC during the hibernation, but without a success. Actually the ACPI was the first thing that came to my mind. But why would the system freeze always at the point when the "suspend console" (Does it have a proper name?) switches back to either X server or normal console (tty)? The memory corruption of GPU seems more logical, doesn't it? And do you know any way, how this could be debugged? In case it was a kernel (or X?) bug, who should I contact first? And is there a way how to some kind of kernel oops in such conditions? Sorry for lots of questions. :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c8 Rafael Wysocki <rjw@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |radomir.cernoch@gmail.com --- Comment #8 from Rafael Wysocki <rjw@novell.com> 2008-12-01 15:35:34 MST --- (In reply to comment #7 from Radomír Černoch)
Suspend/resume (s&r) from battery causes a freeze always. The only difference is that the blinking CapsLock blinks slower as the CPU frequency is lower ;-). I have even tried pluging in the AC during the hibernation, but without a success.
So, the box always crashes during resume from hibernation if it has been hibernated on battery power. Is that correct? If that is the case, have you tried to unload the battery module before hibernation?
Actually the ACPI was the first thing that came to my mind. But why would the system freeze always at the point when the "suspend console" (Does it have a proper name?) switches back to either X server or normal console (tty)?
Devices are being resumed at that point.
The memory corruption of GPU seems more logical, doesn't it?
Not necessarily. Your observations made in comment #5 pretty much exclude an X issue, unless they are incorrect. ;-)
And do you know any way, how this could be debugged?
In case it was a kernel (or X?) bug, who should I contact first? And is there a way how to some kind of kernel oops in such conditions?
First, as I said before, I think it is a kernel issue. Second, as you said the box worked correctly with the kernel from openSUSE 10.3, do you have any experience with building and installing the kernel yourself? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c9 Radomír Černoch <radomir.cernoch@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|radomir.cernoch@gmail.com | --- Comment #9 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-12-01 16:25:57 MST ---
So, the box always crashes during resume from hibernation if it has been hibernated on battery power. Is that correct?
Not exactly. Putting all evidence together the notebook crashes always when it goes on battery (at least for a while) during the hibernation (when it is already turned off). Running the actual process of suspending or hibernation from battery or AC makes no difference.
If that is the case, have you tried to unload the battery module before hibernation?
Wow, this helps! Unloading the battery makes the hibernation safe. (tested 3x)
Devices are being resumed at that point. ... Not necessarily. Your observations made in comment #5 pretty much exclude an X issue, unless they are incorrect. ;-)
Oh, I didn't know. It seems that I'm faster writing than thinking :-) Sorry.
First, as I said before, I think it is a kernel issue. Second, as you said the box worked correctly with the kernel from openSUSE 10.3, do you have any experience with building and installing the kernel yourself?
There should not be any problem about it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c10 --- Comment #10 from Thomas Renninger <trenn@novell.com> 2008-12-02 01:12:39 MST ---
And do you know any way, how this could be debugged? And is there away how to some kind of kernel oops in such conditions? Serial console? IBM ThinkPad T42 This should still have one? There is a boot option (I do not find it in kernel-parameters?), to keep the console up during suspend/resume. You might want to increase the ACPI output first: echo 0x1f >/sys/module/acpi/parameters/debug_level or even (can be a lot output): echo 0x21f >/sys/module/acpi/parameters/debug_level
Then suspend and check the last lines it executes you see on serial console (with this boot param to not disable serial) when it freezes. If it points to ACPI, attach acpidump output of the system. Rafael/Pavel might want to correct/enhance my comments. BTW: Is this possibly related to a Docking station? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c11 --- Comment #11 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-12-02 17:35:50 MST --- (In reply to comment #10 from Thomas Renninger)
Serial console? This should still have one?
Unfortunately not. A serial port can be accessed through the docking station, which I do not have. Do you think it would be possible to do this through USB-serial converter if the appropriate module was inserted into initrd?
If it points to ACPI, attach acpidump output of the system.
Doesn't the fact, that removal of 'battery' module makes the system work reliably, actually show that it is an ACPI problem? I would like to give you the info from the serial console, but currently I am lacking the equipment..
BTW: Is this possibly related to a Docking station?
The notebook is not attached to a docking station. Nevertheless I cannot rule out the possibility that some part of openSUSE responsible of docking is actually causing the trouble. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c12 Thomas Renninger <trenn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |radomir.cernoch@gmail.com Priority|P5 - None |P3 - Medium --- Comment #12 from Thomas Renninger <trenn@novell.com> 2008-12-03 07:00:22 MST ---
Do you think it would be possible to do this through USB-serial converter No, it could be done via firewire (firescope), but I doubt you have that HW.
I expect all we can do is what Rafael already suggested: - If that is the case, have you tried to unload the battery module before hibernation? - Second, as you said the box worked correctly with the kernel from openSUSE 10.3, do you have any experience with building and installing the kernel yourself For the latter, he probably thinks about git bisecting. You have to get the latest git kernel and use git bisect (passing the last kernel which you know worked). You then have build, install and boot the newly built kernel. Then tell git bisect whether it worked or not and it will choose the next set of patches worth testing until the offending patch is found. On a first round you might want try out with the latest vanilla kernels (.28-rcX -> maybe it's already fixed?, .27 -> maybe it's a SUSE patch?, .26 -> if it works it's a nice starting point for git bisect). For getting the latest Linux kernel git sources do: git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 linux-2.6 Finding the offending patch can be cumbersome, maybe someone has a better idea, I do not have any. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c13 Radomír Černoch <radomir.cernoch@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|radomir.cernoch@gmail.com | --- Comment #13 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-12-03 07:36:18 MST --- (In reply to comment #12 from Thomas Renninger)
No, it could be done via firewire (firescope), but I doubt you have that HW.
Right, I do not have this device. :-(
I expect all we can do is what Rafael already suggested: - If that is the case, have you tried to unload the battery module before hibernation?
As I have already written, unloading the "battery" module helps and the suspend/resume becomes reliable.
For the latter, he probably thinks about git bisecting.
Ok, I will try the bisecting. I already have some experience with building a custom vanilla kernel. But from the last time I tried it (~ 2.6.14), something must have changed in the system: When doing the sequence # make oldconfig # make # make install # make modules_install # mkinitrd the newly installed kernel can no longer find the root partition. Is there a turotial for building vanilla kernels on openSUSE? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User mhopf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c14 Matthias Hopf <mhopf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sndirsch@novell.com |trenn@novell.com Status|ASSIGNED |NEW --- Comment #14 from Matthias Hopf <mhopf@novell.com> 2008-12-03 08:01:40 MST --- As this is not X related, I reassign this to you Thomas, ok? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c15 Radomír Černoch <radomir.cernoch@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |radomir.cernoch@gmail.com --- Comment #15 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-12-03 11:50:00 MST --- (In reply to comment #13 from Radomír Černoch)
I already have some experience with building a custom vanilla kernel. But from the last time I tried it (~ 2.6.14), something must have changed in the system: When doing the sequence # make oldconfig # make # make install # make modules_install # mkinitrd the newly installed kernel can no longer find the root partition. Is there a turotial for building vanilla kernels on openSUSE?
I do no longer need the help (just a few modules got renamed from vanilla to SUSE flavour). I am starting the bisection... 4000 revisions to go... I will let you know ASAP. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c16 --- Comment #16 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-12-04 08:09:07 MST --- Created an attachment (id=258046) --> (https://bugzilla.novell.com/attachment.cgi?id=258046) Result of bisection After the bisection, git produced the output, which is attached as 'git_message.txt'. Should I post it to LKML as well? PS: I found bisection as quite an interesting process, just like playing golf. More strokes you make, the smaller leaps to the pin you make. But the price of all of them is the same. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 Radomír Černoch <radomir.cernoch@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|radomir.cernoch@gmail.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Should I post it to LKML as well That's Rafael to decide, he probably will be the one who will look at this in
https://bugzilla.novell.com/show_bug.cgi?id=450256 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c17 Thomas Renninger <trenn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|trenn@novell.com | AssignedTo|trenn@novell.com |rjw@novell.com Status|ASSIGNED |NEW --- Comment #17 from Thomas Renninger <trenn@novell.com> 2008-12-04 08:18:55 MST --- Wow! Well done and thanks! Rafael, this looks like a bug for you... the end anyway? Also posting on linux-acpi list should be enough to make this more public. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c18 --- Comment #18 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-12-04 08:23:00 MST --- (In reply to comment #17 from Thomas Renninger)
That's Rafael to decide, he probably will be the one who will look at this in the end anyway?
Ok, so far I am not posting anything anywhere. If you needed some more info or testing, just drop me an e-mail. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c19 Radomír Černoch <radomir.cernoch@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |radomir.cernoch@gmail.com --- Comment #19 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-12-04 17:37:09 MST --- Sorry, it is very likely that I gave you misleading information. The most recent version of the kernel, which does not have the bug, has crashed today. Currently I do not know anything more about the possible flaw -- this revision was already tested. I will let you know when more (and repeatitive) tests will be done. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c20 Radomír Černoch <radomir.cernoch@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #258046|0 |1 is obsolete| | Status|NEEDINFO |NEW Info Provider|radomir.cernoch@gmail.com | --- Comment #20 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-12-05 13:07:45 MST --- Created an attachment (id=258385) --> (https://bugzilla.novell.com/attachment.cgi?id=258385) Result of bisection v2 The final result of bisecting the kernel is in the attachment. Sorry once more for sending you wrong info. This time both kernels (last good and first bad) have been tested 4 times, double checking that the version of tested kernel is the same as in git. The good kernel has never crashed during resume and the bad one has crashed always. I hope that there can't be a flaw any more. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c21 --- Comment #21 from Rafael Wysocki <rjw@novell.com> 2008-12-07 17:21:41 MST --- Please add the 'acpi_sleep=s4_nohwsig' option to the kernel command line. Apparently, your BIOS doesn't handle the ACPI hardware signature correctly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c22 --- Comment #22 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-12-08 12:55:33 MST --- I can confirm that passing 'acpi_sleep=s4_nohwsig' helps and the machine resumes correctly. What should I do next? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c23 --- Comment #23 from Rafael Wysocki <rjw@novell.com> 2008-12-08 13:05:40 MST --- Please provide the output of 'dmidecode' from your system, so that I can prepare a blacklisting patch for it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c24 --- Comment #24 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-12-08 15:50:22 MST --- Created an attachment (id=258754) --> (https://bugzilla.novell.com/attachment.cgi?id=258754) Output of 'dmidecode' By the way, do you have an idea, how many systems could be affected, by this? I was just wondering, whether it is worth adding any kind of GUI checkbox somewhere in YaST to activate the workaroung you sent me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c25 --- Comment #25 from Rafael Wysocki <rjw@novell.com> 2008-12-09 16:57:37 MST --- (In reply to comment #24 from Radomír Černoch)
Created an attachment (id=258754) --> (https://bugzilla.novell.com/attachment.cgi?id=258754) [details] Output of 'dmidecode'
Thanks, I'm going to take care of this tomorrow.
By the way, do you have an idea, how many systems could be affected, by this? I was just wondering, whether it is worth adding any kind of GUI checkbox somewhere in YaST to activate the workaroung you sent me.
Well, you're the first person reporting it and so far the only one, so I guess not too many. ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c26 --- Comment #26 from Rafael Wysocki <rjw@novell.com> 2008-12-10 15:52:01 MST --- Created an attachment (id=259283) --> (https://bugzilla.novell.com/attachment.cgi?id=259283) Prevent Thinkpad T42 from using the ACPI S4 hardware signature With this patch applied your box should successfully resume from hibernation without the acpi_sleep=s4_nohwsig command line parameter. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 Luc Verhaegen <lverhaegen@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lverhaegen@novell.com Component|X.Org |Kernel QAContact|xorg-maintainer-bugs@forge.provo.novell.com |qa@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c27 Radomír Černoch <radomir.cernoch@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #27 from Radomír Černoch <radomir.cernoch@gmail.com> 2008-12-15 06:49:01 MST --- Sorry for the delay. I can confirm that this patch works well for my machine; 'acpi_sleep=s4_nohwsig' is no longer needed. Thanks for help. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c28 --- Comment #28 from Rafael Wysocki <rjw@novell.com> 2008-12-15 13:29:39 MST --- Thanks for testing. I'm still waiting for the confirmation that other T42s are also affected. If this problem occurs on your system only, I'd prefer not to apply the patch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c29 Rafael Wysocki <rjw@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #29 from Rafael Wysocki <rjw@novell.com> 2008-12-15 13:31:57 MST --- I'll close the bug when it is known if all T42s are affected. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 Rafael Wysocki <rjw@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User lmuelle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c30 Lars Müller <lmuelle@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lmuelle@novell.com --- Comment #30 from Lars Müller <lmuelle@novell.com> 2009-01-04 11:08:57 MST --- A X31 ThinkPad shows sometimes the the same behavior while resume resume after suspend to disk. Before the upgrade from 10.3 to 11.1 resume after suspend to disk worked well. I've added "acpi_sleep=s4_nohwsig" to the kernel command line and suspended and resumed five times without seeing the issue again. Output of dmidecode of the X31 system follows. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User lmuelle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c31 --- Comment #31 from Lars Müller <lmuelle@novell.com> 2009-01-04 11:11:30 MST --- Created an attachment (id=263119) --> (https://bugzilla.novell.com/attachment.cgi?id=263119) stdout of dmidecode on a ThinkPad x31 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User lmuelle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c32 Lars Müller <lmuelle@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #263119|0 |1 is obsolete| | --- Comment #32 from Lars Müller <lmuelle@novell.com> 2009-01-04 16:24:23 MST --- Created an attachment (id=263122) --> (https://bugzilla.novell.com/attachment.cgi?id=263122) Stdtout of dmidecode on a ThinkPad x31 Output of dmidecode after the update of the embedded controller (1.08) and the BIOS (3.02) of the X31. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c33 --- Comment #33 from Stefan Seyfried <seife@novell.com> 2009-01-08 06:32:03 MST --- Lars, it might be interesting to test if you sill need s4_nohwsig after the BIOS update (yes, IBM/Lenovo sometimes fix stuff in their BIOS updates ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User lmuelle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c34 Lars Müller <lmuelle@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |radomir.cernoch@gmail.com --- Comment #34 from Lars Müller <lmuelle@novell.com> 2009-01-09 10:54:14 MST --- After an update of the embedded controller (1.08) and the BIOS (3.02) s4_nohwsig is no longer required by the X31 for a working suspend and resume. I've tested it more than ten times. @Radomír: Your embedded controller is up to date. But your BIOS isn't Lenovo offers version 3.23 while you're at 3.13. After my experience with the X31 I like to see you updating the BIOS. See http://www.thinkwiki.org/wiki/BIOS_Upgrade/X_Series approach #7 if you don't like to create bootable floppy disks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 Lars Müller <lmuelle@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #258754|application/octet-stream |text/plain mime type| | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c35 Radomír Černoch <radomir.cernoch@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|radomir.cernoch@gmail.com | --- Comment #35 from Radomír Černoch <radomir.cernoch@gmail.com> 2009-01-13 11:40:13 MST --- Yes, I can confirm that after the BIOS update, 's4_nohwsig' is not needed to make suspend/resume work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c36 --- Comment #36 from Rafael Wysocki <rjw@novell.com> 2009-01-13 13:06:33 MST --- So in fact this turns out to be a BIOS bug. I think we can close this entry now, any objections? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c37 --- Comment #37 from Radomír Černoch <radomir.cernoch@gmail.com> 2009-01-14 11:35:42 MST --- I am just thinking, whether we should force users of all affected systems to update their BIOS. It is not a user-friendly process without Windows. Is the "ACPI hardware signature" so important? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c38 --- Comment #38 from Rafael Wysocki <rjw@novell.com> 2009-01-14 13:32:10 MST --- It's a hardware feature we're supposed to use and it works with the vast majority of hardware from what I can tell. The general policy is to blacklist systems that have problems with it, but since on Thinkpads the BIOS update evidently helps, I don't think we should blacklist them. The users of affected system who don't want to upgrade their BIOSes can still use the acpi_sleep=s4_nohwsig kernel option as a workaround to make hibernation work (that's what the option is for after all). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c39 --- Comment #39 from Radomír Černoch <radomir.cernoch@gmail.com> 2009-01-14 13:53:38 MST --- OK, what you wrote is reasonable. Anyway there should be a notice about this problem somewhere. Shall I put a short notice in http://en.opensuse.org/S2disk ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c40 --- Comment #40 from Rafael Wysocki <rjw@novell.com> 2009-01-14 16:00:51 MST --- Please do. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rodelrod@hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c41 Rodrigo Daunoravicius <rodelrod@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rodelrod@hotmail.com --- Comment #41 from Rodrigo Daunoravicius <rodelrod@hotmail.com> 2009-02-25 04:23:40 MST --- I'm running Ubuntu 8.10 Intrepid, not OpenSuse, but as this seems to be a kernel problem and as I can't find the issue discussed anywhere else I'll report here. With the kernel 2.6.27-11-generic on a Thinkpad X32, even after updating the BIOS (3.02) and embedded controller (1.08), I experience the same problems resuming if the AC power is unplugged during hibernation. With the 'acpi_sleep=s4_nohwsig' kernel option, it resumes correctly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User radomir.cernoch@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c42 --- Comment #42 from Radomír Černoch <radomir.cernoch@gmail.com> 2009-03-11 17:56:30 MST --- Rodrigo, do you have any peripherals attached during the suspend/resume? USB, PCMCIA, external display, ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rodelrod@hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c43 --- Comment #43 from Rodrigo Daunoravicius <rodelrod@hotmail.com> 2009-03-12 02:28:02 MST --- Without 'acpi_sleep=s4_nohwsig': Resume from hibernate always fails if the AC power is unplugged at any point, even if no periferals are attached, wether or not there is a battery in the unit. With 'acpi_sleep=s4_nohwsig': Resume works even if AC power is unplugged but (this I found later) there is one case where resume from both suspend and hibernate fail: when I resume/hibernate while docked, it won't resume after undocked, wether or not there is a battery on the unit and wether or not there are any peripherals (one external monitor, network, AC power) attached to the UltraDock. The reverse case works fine, I can hibernate/suspend while undocked and resume once docked. For now I settled for setting 'acpi_sleep=s4_nohwsig' and keeping a battery on the unit at all times, even when docked, so that I don't have to hibernate it to undock it. In previous experience, keeping Li-ion batteries on laptos while working 10-12 hour workdays plugged into AC has tended to burn my batteries in less than six months, but this one seems to be holding out OK. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450256 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450256#c44 --- Comment #44 from Rafael Wysocki <rjw@novell.com> 2009-03-12 06:48:40 MST --- (In reply to comment #43)
Without 'acpi_sleep=s4_nohwsig':
Resume from hibernate always fails if the AC power is unplugged at any point, even if no periferals are attached, wether or not there is a battery in the unit.
With 'acpi_sleep=s4_nohwsig':
Resume works even if AC power is unplugged but (this I found later) there is one case where resume from both suspend and hibernate fail: when I resume/hibernate while docked, it won't resume after undocked, wether or not there is a battery on the unit and wether or not there are any peripherals (one external monitor, network, AC power) attached to the UltraDock. The reverse case works fine, I can hibernate/suspend while undocked and resume once docked.
I think this is an upstream bug. To verify this you can test the kernel from ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD/ (ie. 2.6.29-rc7+). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com