[Lenovo b575e] Display remains blank after resuming from suspend

[Jure Repinc]

I suspend and after wakeup the display remains blank and never displays the desktop. I tested upstream kernel v3.14-rc5-trusty and the problem remains.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-18-generic 3.11.0-18.32
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: marjana 1876 F.... pulseaudio
 /dev/snd/controlC0: marjana 1876 F.... pulseaudio
Date: Sat Apr 5 20:28:48 2014
HibernationDevice: RESUME=UUID=040b5729-2fbb-4c08-b5ba-b0e8650035b0
InstallationDate: Installed on 2014-02-26 (37 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: LENOVO 20189
MarkForUpload: True
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=25900576-2137-4e56-8cf7-e2b9f74c3ec7 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-18-generic N/A
 linux-backports-modules-3.11.0-18-generic N/A
 linux-firmware 1.116.2
SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: HPET68WW(1.06)
dmi.board.asset.tag: Not Available
dmi.board.name: 20189
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrHPET68WW(1.06):bd12/26/2012:svnLENOVO:pn20189:pvrLenovoB575e:rvnLENOVO:rn20189:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20189
dmi.product.version: Lenovo B575e
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Jure Repinc, could you please test the latest upstream kernel available (3.14-trusty) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.14

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Jure Repinc (jlp)]

I installed upstream kernel 3.14-trusty. After reboot laptop resumed 2 times just fine. But after that screen again remains blank.

[Alberto Milone (albertomilone)]

Can you ssh into the machine after resume to collect the following files please?

1) the output of dmesg
2) your /var/log/Xorg.0.log and /var/log/Xorg.0.log.old

[penalvch (penalvch)]

Jure Repinc, did this problem not occur in a release prior to Saucy?

As well, could you please provide the missing information from https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[xbmc50 (xbmc50)]

This bug still happens in Ubuntu 14.04 Trusty Tahr.

[penalvch (penalvch)]

xbmc50, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[xbmc50 (xbmc50)]

New Trusty Tahr bug report made. Should it be marked as duplicate with this? I'm not sure.

14.04 report made by me is here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311214

[Jure Repinc (jlp)]

Sorry for delayed response. The laptop is my mom's and I visit her about once per month. Anyways. I have just now upgraded Kubuntu to version 14.04 and the problem remains. Will do other steps right away now.

[Jure Repinc (jlp)]

I now tested with 3.15-rc3-utopic and the problem persists. I can't ssh into the laptop after coming back from resume, looks like it is frozen. Also I don't know if versions of Kubuntu older than 13.10 work as I didn't have the laptop before. I will attach dmesg and Xorg log from a running system before suspend. After that I will work on info from comment #6

[Jure Repinc (jlp)]

cat /proc/acpi/wakeup > wakeup

[penalvch (penalvch)]

Jure Repinc, for regression testing purposes, could you please test http://old-releases.ubuntu.com/releases/12.04.0/ and advise if this is reproducible?

[Jure Repinc (jlp)]

I tried with 12.04.3 and the problem is the same. No screen, freeze and caps-lock led blinking.

[penalvch (penalvch)]

Jure Repinc, 12.04.3 is equivalent to Raring, so that would not be early enough. Could you please test exactly http://old-releases.ubuntu.com/releases/12.04.0/ubuntu-12.04-desktop-amd64.iso and advise to the results?

[Jure Repinc (jlp)]

Tested with 12.04.0 now and the problem remains the same.

[penalvch (penalvch)]

Jure Repinc, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

[Jure Repinc (jlp)]

I reported the bug upstream → https://bugzilla.kernel.org/show_bug.cgi?id=101351

[penalvch (penalvch)]

Jure Repinc, my apologies as I was a little premature.

As per http://support.lenovo.com/us/en/products/laptops-and-netbooks/lenovo-b-series-laptops/lenovo-b575e-notebook an update to your computer's buggy and outdated BIOS is available (1.07). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed.

Thank you for your understanding.

[Jure Repinc (jlp)]

I downloaded the ISO from the page, burnt the CD and updated BIOS from it. No change at all. Laptop still freezes on wakup and the screen is blank.

The output of dmidecode is:
HPET63WW(1.01)
09/03/2012

Which is strange and it looks like it downgraded my BIOS instead of upgrading to 1.07.

[Jure Repinc (jlp)]

I think I know what's up with version numbers. I just checked the BIOS setup and there are 2 versions. One for UEFI BIOS (1.01) and one for Embedded Controller (1.07). I think that the previous BIOS was actually 1.00/1.06, but previously the EC version was reported in dmidecode, but now in new BIOS the UEFI version is reported. Anyways, As I said. No improvement in wakeup behaviour:(

[penalvch (penalvch)]

Jure Repinc, to clarify, which update did you apply, the UEFI piece, and/or EC?

[Jure Repinc (jlp)]

Both were updated. Both are in the same updaate file and can't be updated sperately.

[penalvch (penalvch)]

Jure Repinc, could you please contact Lenovo to confirm this result?

I've never seen this phenomenon across hundreds of BIOS updates for Lenovo devices (both linux and Windows), so it's a little strange to say the least to see the version number and date go backwards on a "newer" BIOS update.