Laptop screen turned off with kernel 3.8.0 in raring

[Nicola Heald]

I have a Lenovo Y580 Ideapad. When booting with the 3.8.0 kernel, the screen turns off when the ubuntu logo and progress bar should display. Xorg starts, I can hear the startup sound, but the screen is turned off. Booting on the 3.5.0 kernel works fine.
---
ApportVersion: 2.12.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 2974 F.... pulseaudio
CasperVersion: 1.336ubuntu1
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131120)
MachineType: LENOVO 2099
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --
ProcVersionSignature: Ubuntu 3.12.0-3.8-generic 3.12.0
RelatedPackageVersions:
 linux-restricted-modules-3.12.0-3-generic N/A
 linux-backports-modules-3.12.0-3-generic N/A
 linux-firmware 1.117
Tags: trusty
Uname: Linux 3.12.0-3-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 08/23/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 5DCN89WW(V8.00)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 31900003WIN8 STD MLT
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y580
dmi.modalias: dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr31900003WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
dmi.product.name: 2099
dmi.product.version: Lenovo IdeaPad Y580
dmi.sys.vendor: LENOVO

[Fabio Marconi (fabiomarconi)]

Hallo Mike
are you using raring or quantal with 3.8 kernel ?
Boot the 3.8 kernel, restart system with magic keys, boot 3.5 and attach here
/var/log/syslog
/var/log/dmesg
/var/log/Xorg.0.log.old
Thanks
Fabio
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Logan Rosen (logan)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc3-raring/

[Nicola Heald (notnownikki)]

Have done so, the bug still exists.

If there are any more tests I can do, or debugging information I can get to help fix this, please let me know.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Grzegorz Galezowski (spectral)]

I just noticed that in my case, the display isn't totally disabled, but the brightness is turned down to minimum so that nothing is visible on the screen. When I use Fn + up arrow multiple times to increase brightness, the screen comes back.

[Brad Figg (brad-figg)]

Mike,

I'm assuming that you've updated to the release version of Raring. Are you still having this issue with the latest Raring kernel?

[Nicola Heald (notnownikki)]

Yes, this bug is still present with raring up to date as of today.

[Nicola Heald (notnownikki)]

I'd better confirm that, same as @spectral, this is a brightness bug. The brightness is at the very lowest level, so it appears as if the laptop screen is off.

[Nicola Heald (notnownikki)]

Upgraded to saucy, running kernel 3.11.0-4-generic, bug is still present.

[penalvch (penalvch)]

Mike Heald, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) 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-v3.12

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.

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

apport information

[Nicola Heald (notnownikki)]

Problem is still present in the trusty livecd, as of today.

Tested with the mainline kernel,

mikeh@bones:~$ uname -a
Linux bones 3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
mikeh@bones:~$

and the problem is present there too.

[penalvch (penalvch)]

Mike Heald, the next step is to fully commit bisect from Raring to Saucy, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Nicola Heald (notnownikki)]

Kernel update came through this morning, to:

    3.11.0-15-generic #22-Ubuntu SMP Mon Dec 2 23:35:23 UTC 2013

and this seems to have fixed it for me!

[penalvch (penalvch)]

Mike Heald, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1099204/comments/31 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.