[Bug 830475] New: partly broken openSUSE-12.3 kernel power management & wireless after suspend on Toshiba Z930 ultrabook
https://bugzilla.novell.com/show_bug.cgi?id=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c0 Summary: partly broken openSUSE-12.3 kernel power management & wireless after suspend on Toshiba Z930 ultrabook Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: lee_matheson@hotmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 64-bit openSUSE-12.3 (KDE4 desktop) when operating on battery fails to resume properly after a power management suspension on a Toshiba Satellite Z930 Ultrabook. The symptoms after resuming are wireless is broken, battery monitoring/management not functioning, and any subsequent shutdown of the Ultrabook can not be done via Software, but must be done by holding down the hardware power switch for 1/2-dozen seconds. This bug does not occur when operating with AC power, but only occurs when running on battery. This anomaly is documented impacting all GNU/Linux distributions in the Z930 linlap page: http://www.linlap.com/toshiba_portege_z930 . This is likely an issue specific to the Toshiba Z930 ACPI implementation. There is also an upstream ACPICA patch (kernel fix) for the anomaly reported here: https://github.com/acpica/acpica/commit/34f226fa2643f1d2e6527ea4edb24947cfe1... Reproducible: Always Steps to Reproduce: 1. allow Ultrabook to suspend when operating on battery power 2. 3. Actual Results: Battery monitoring gives an erroneous (0% charge) reading in KDE. Wireless does not function. It is not possible shutdown ultrabook without holding down power key for 1/2 dozen seconds or so. Even a 'shutdown -h now' results in PC hanging during shutdown. Expected Results: Both wireless and battery status/management should function correctly after resuming from suspend. It should be possible to shutdown the PC via openSUSE software. Additional information of the logs from this laptop can be provided per request. Note this is likely a Toshiba ACPICA issue addressed by an upstream kernel fix. It would be useful if this fix can be trialed in an openSUSE kernel update, as an interim until the upstream fix makes its way downstream. -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c1 --- Comment #1 from Lee Matheson <lee_matheson@hotmail.com> 2013-07-23 11:51:27 UTC --- My stating this only occurs when running on battery is not accurate. After leaving the Ultrabook on AC power for a couple of hours, and coming back, I note I obtained the same wireless not functional problem, and also the only way to shut down completely was to hold the POWER key down for a half dozen or so seconds. -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |jslaby@suse.com |ovo.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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c2 --- Comment #2 from Lee Matheson <lee_matheson@hotmail.com> 2013-09-15 09:47:12 UTC --- I tested the Toshiba Z930 with openSUSE-13.1 Milestone-4 (on a liveUSB stick) and there is different anomalous behaviour from that observed on openSUSE-12.3 KDE on an SSD drive installation. I booted the Toshiba Z930 to a USB stick (in a USB-3.0 port) with 64-bit openSUSE-13.1 M4 KDE liveDVD, unplugged the power cable (so that the Ultrabook was running on battery) and let it go to hibernation on two consecutive occasions during the same boot. When running on battery : (1) on the 1st suspend/resume cycle it resumed properly from Hibernation and the wireless was functioning again. (2) on the 2nd suspend/resume cycle, the screen remained black and the desktop did not come back. By touching the keyboard, the backlit keyboard did light up even though the desktop remained black. It was not possible to restore the desktop. Only a hard shutdown (holding power key for ~6 seconds) worked (it shut off the PC). The anomalous behaviour is repeatable after a hard shutdown and fresh start/boot. Since I was running openSUSE-13.1 M4 from a liveUSB stick in a USB-3.0 port on the Toshiba, I have insufficient knowledge to note if the behaviour is also USB port related and possibly confusing to an SSD/HD install bheaviour (ie is USB port behaviour under suspend/resume a factor in the liveDVD test ? ). Checking the change log for the kernel-desktop-3.10.1-3 and I see no reference for the kernel commit 34f226f, which suggests it may have not been approved (noting also I know nothing about kernel approval/testing process). Testing with a new fresh boot, after the 1st suspend/resume cycle, shut down works properly after the 1st suspend (but obviously not testable after a 2nd per the above). -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c3 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |lee_matheson@hotmail.com --- Comment #3 from Jiri Slaby <jslaby@suse.com> 2013-09-20 19:28:41 UTC --- The patch was added to 3.11. Could you try the kernel from: http://download.opensuse.org/repositories/Kernel:/stable/standard/ ? -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c4 --- Comment #4 from Lee Matheson <lee_matheson@hotmail.com> 2013-09-21 15:44:28 UTC --- I tried the kernel-desktop 3.11.1-2.1.g9182067_x86_64 and also the kernel-desktop-3.11-3.1.gfeeffbf9_86_64 kernels and they both have a power management problem (where after restoring the Ultra book from sleep both the wireless is not functioning, and the power management has stopped functioning (with a blank battery symbol giving no indication as to how much battery left). I do note thou, that the shutdown works with the 3.11 kernel (after this suspend). The problem manifests itself immediately upon the first resumption from suspend and not on the second. I note the KDE settings on my openSUSE-12.3 are after 2-minutes the display dims (its possible to recover multiple times from this) and after 5-minutes the screen goes black (and its possible to recover multiple times from this) and after 10-minutes the suspend session puts the Ultra book to sleep (which is where the problem occurs). I recognize this to be an upstream GNU/Linux problem, and I'll keep monitoring the various threads on this Ultra book (in different GNU/Linux websites) in case there is a subsequent fix. Once I learn about it, I will post any information here. I also hope to test in the next week openSUSE-13.1 beta-1 with this Toshiba Z930 Ultra book. A colleague from work borrowed my USB memory stick that has the liveDVD of openSUSE-13.1 beta-1 on it, and I will test with that beta1 version with the memory stick, once I obtain the USB stick back. This was the 1st time (that I recall) loading a kernel from factory on a PC of mine, and I had to disable the secure boot in the UEFI firmware of this Ultrabook to get it to load. That was no problem, as as soon as I saw the 'signature' error when I first booted, I recalled reading old posts (either on the mailing list or on the forum) advising that the factory kernels are not 'signed' for secure boot. Thanks for your support in this. . -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c Lee Matheson <lee_matheson@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|lee_matheson@hotmail.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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c5 Lee Matheson <lee_matheson@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lee_matheson@hotmail.com --- Comment #5 from Lee Matheson <lee_matheson@hotmail.com> 2013-09-22 08:02:44 UTC --- I plugged in an USB external DVD drive, and booted this Toshiba Z930 Ultrabook to 64-bit openSUSE-13.1-beta1 liveDVD (KDE version) which also has a 3.11.1 kernel version. Wireless worked fine upon booting, as did graphics. I unplugged the power cable, putting the Ultrabook on battery, and let the ultrabook go into a suspend (I disappeared for 45-minutes for breakfast). When I came back and attempted to resume, I only obtained a black screen where the while mouse arrow could be seen as I moved the mouse around. <CTRL><ALT><F2> did bring me to a full screen functional GNU/Linux text login. I was able to login as a regular user. Pressing <CTRL><ALT><F7> brought me back to the black screen where only mouse movement could be seen. <CTRL><ALT><F2> brought me back to the full screen text mode, where I was able to shut down the Ultrabook with 'shutdown -r now'. When I obtain my USB memory stick back I'll try booting 13.1 beta1 from that, but I don't anticipate different behaviour. -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c6 --- Comment #6 from Lee Matheson <lee_matheson@hotmail.com> 2013-09-22 08:03:59 UTC --- That 2013-09-22 08:02:44 UTC post should read, shutdown with 'shutdown -h now'. -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c7 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |lee_matheson@hotmail.com --- Comment #7 from Jiri Slaby <jslaby@suse.com> 2013-09-22 08:50:32 UTC --- (In reply to comment #5)
When I came back and attempted to resume, I only obtained a black screen where the while mouse arrow could be seen as I moved the mouse around. <CTRL><ALT><F2> did bring me to a full screen functional GNU/Linux text login. I was able to login as a regular user. Pressing <CTRL><ALT><F7> brought me back to the black screen where only mouse movement could be seen.
Ok, that would mean Xorg crashed. When this happens, could you collect /var/log/Xorg.0.log and output of dmesg and attach here? -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c8 --- Comment #8 from Lee Matheson <lee_matheson@hotmail.com> 2013-09-22 10:08:30 UTC --- Ok - when I reproduce this behaviour I will provide the Xorg.0.log and dmesg output. I went into the Ultrabook BIOS after the last test, and changed a BIOS setting for power management (now enabling in BIOS a setting to resume from suspend when keyboard button is pressed, as opposed to the previous setting which only relied on the 'power switch' to resume from suspend) . I then booted to the 64-bit openSUSE-13.1-beta liveDVD and I am trying to reproduce the error. Thus far I think I've survived two resumptions from suspend, ... so I need to do more scientific testing (precisely measuring suspend time) before I can be more precise on this. I'll leave the NEEDINFO flag set while I investigate this. I'll also retest openSUSE-12.3 with the 3.11 kernel with this updated BIOS setting. It doesn't help that I'm struggling with a headcold/flu, I am making mistakes, and I can't concentrate focus on this totally :( ... -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c9 Lee Matheson <lee_matheson@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|lee_matheson@hotmail.com | --- Comment #9 from Lee Matheson <lee_matheson@hotmail.com> 2013-09-22 14:38:57 UTC --- With the updated BIOS setting in my Toshiba Z930 Ultrabook ( see http://www.imagebam.com/image/4a5d27277491065 ) to enable "Critical Battery Wakeup" I again tested openSUSE-12.3 with 3.7 kernel, tested openSUSE-12.3 with factory kernel-desktop-3.11-3.1.gfeeffbf9_86_64 kernel, and tested a 64-bit openSUSE-13.1 beta1 booting from liveDVD (KDE). openSUSE-12.3 does not resume completely from a suspend with either kernel. openSUSE-12.3 with factory kernel-desktop-3.11-3.1.gfeeffbf9_86_64 kernel will resume from a suspend (of 30 minutes) but the network manager is not properly functioning (ie no wireless functionality). Upon resumption from suspend in the lower right corner there is a red box with a white 'x' in it, for the network manager. When I select the network manager it shows no networks available (when there are many in our neighbourhood). When I select "Manage connections" I obtain a dialog box with the "KDE Crash handler". Shutdown from this state works with openSUSE-12.3 with the 3.11 kernel but shutdown from this state does not work with openSUSE-12.3 with the 3.7 kernel (it simply hangs at a nominal shutdown, requiring a 5-second press of the ON/OFF button). On the other hand, 64-bit openSUSE-13.1-beta1 from liveDVD (KDE) recovers properly from the suspend (of 30 minutes or longer) on multiple consecutive occasions. When recovering, I obtain the KDE desktop resume login screen asking for a password. I press <enter> for the KDE user liveDVD password, and KDE then asks for the KWallet password (that I setup in the liveDVD for this liveDVD instance). After entering that, the wireless connects to our home WLAN and I have internet access. So my current conclusion is this does function for openSUSE-13.1-beta1 (with the Ultrabook's current BIOS setting) but does not function for openSUSE-12.3 despite having an updated 3.11 kernel. Well done wrt 64-bit openSUSE-13.1 beta1 !! I'm looking forward to installing that in November when the GM is released. Do you still wish me to revert the BIOS setting and reproduce the Xorg crash ? I will be happy to close this bug report if openSUSE-13.1 GM version works as well as openSUSE-13.1 beta1. -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c10 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |lee_matheson@hotmail.com --- Comment #10 from Jiri Slaby <jslaby@suse.com> 2013-09-25 16:02:50 UTC --- (In reply to comment #9)
So my current conclusion is this does function for openSUSE-13.1-beta1 (with the Ultrabook's current BIOS setting) but does not function for openSUSE-12.3 despite having an updated 3.11 kernel.
..which supports my theory about the broken Xorg driver.
Do you still wish me to revert the BIOS setting and reproduce the Xorg crash ?
Yeah, it would be nice to see what the actual error was... -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c11 --- Comment #11 from Lee Matheson <lee_matheson@hotmail.com> 2013-09-29 19:45:31 UTC --- Created an attachment (id=560752) --> (http://bugzilla.novell.com/attachment.cgi?id=560752) Text file showing updates between 22-September and when I failed to reproduce Xorg crash. When I tested the kernel-desktop-3.11-3.1.gfeeffbf9_86_64 on 22-September (above) I reproduced the problem (Xorg crash) 3 times in a row, with a cold shutdown in between each occurrence. I can't reproduce it at all now. Upon resumption from suspend in the lower right corner there is a red box with a white 'x' in it, for the network manager. When I select the network manager it shows no networks available (when there are many in our neighbourhood). When I select "Manage connections" I obtain a dialog box with the "KDE Crash handler". Shutdown from this state works with openSUSE-12.3 with the 3.11 kernel but shutdown from this state does not work with openSUSE-12.3 with the 3.7 kernel (it simply hangs at a nominal shutdown, requiring a 5-second press of the ON/OFF button). The only difference between now and 22-September are some updates conducted on 22 and 25-September (see attachment) so while it is good Xorg is no longer functioning strange, apologies that I can not reproduce what I reported wrt X. However the partly broken power management/wiress suspend problem is still present with the kernel-desktop-3.11-3.1.gfeeffbf9_86_64 . I ran my battery down to 0% yesterday, trying to reproduce (unsuccessfully) the X problem. I note 13.1 RC1 will be out in just over a week, and I'll test it when it comes out. -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c Lee Matheson <lee_matheson@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|lee_matheson@hotmail.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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c12 --- Comment #12 from Lee Matheson <lee_matheson@hotmail.com> 2013-11-02 18:34:27 UTC --- I tested openSUSE-13.1 RC1 and RC2 (booting from the 64-bit openSUSE-13.1 KDE iso written to a USB stick with ImageWriter). Similar to 13.1-beta1, with RC1 and RC2 the power management works properly and the Toshiba Z930 recovers properly from suspend (of 30 minutes or longer) on multiple consecutive occasions. -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c13 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #13 from Jiri Slaby <jslaby@suse.com> 2013-11-06 12:52:58 UTC --- Ok, let's mark this fixed then... -- 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=830475 https://bugzilla.novell.com/show_bug.cgi?id=830475#c14 --- Comment #14 from Lee Matheson <lee_matheson@hotmail.com> 2013-11-07 06:52:08 UTC --- Many thanks for the fix in 13.1 :) -- 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