notebook panel fails to be set up correctly by resume, xrandr [ Latitude E6510]

[John Lenton]

In Precise, the HD notebook panel on my Latitude E6510 fails to be set up correctly on resume. It also isn't set up correctly by xrandr: simply running `xrandr --output eDP1 --scale .9x.9` will make the panel blank (backlight still on), and only a hard power cycle brings it back. In case it bears mentioning, this was not the case in O.

Suspend works, but when it resumes the backlight comes up and capslock light works when in x, but nothing draws on the screen. I can even ctrl-alt-fN ctrl-alt-del to reboot cleanly (nevertheless I need to actually power down to get display back in ubuntu, even though the bios screen is visible, not even grub shows until i've power cycled).

I have been able to test with an external monitor, and it works, so this is only the hd panel (eDP1).

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/902657/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Fabio Marconi (fabiomarconi)]

Hello
You said:
Most of the times I suspend in P
Don't worry, but my brain is really small and cannot imagine what you are meaning with P ( I can only suppose Precise), so please be gentle and descriptive, expecially the model of the machine and some other usefull info.
Actualy i can only suppose e problem in the kernel so
Please reproduce the bug and attach here, using the button below 'Add attachment or patch' the files
/var/log/kern.log
/var/log/kern.log.1
/var/log/dmesg.0

Thanks
Fabio
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[John Lenton (chipaca)]

Yes, P is Ubuntu Precise Pangolin, sorry for being imprecise.
Do the logs have to be after a failed resume?

[Fabio Marconi (fabiomarconi)]

Yes John
Thanks
Fabio
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Fabio Marconi (fabiomarconi)]

From kern.log

Dec 12 20:04:05 localhost kernel: [34786.423975] WARNING: at /build/buildd/linux-3.2.0/kernel/power/suspend_test.c:53 suspend_test_finish+0x89/0x90()
Dec 12 20:04:05 localhost kernel: [34786.423977] Hardware name: Latitude E6510
Dec 12 20:04:05 localhost kernel: [34786.423978] Component: resume devices, time: 10516
Dec 12 20:04:05 localhost kernel: [34786.423979] Modules linked in: msr bnep rfcomm pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables bridge stp joydev kvm_intel kvm arc4 snd_hda_codec_hdmi snd_hda_codec_idt iwlwifi snd_hda_intel mac80211 snd_hda_codec btusb psmouse dell_wmi serio_raw bluetooth binfmt_misc sparse_keymap uvcvideo videodev snd_hwdep snd_pcm snd_seq_midi dell_laptop snd_rawmidi dcdbas intel_ips ppdev snd_seq_midi_event pcmcia cfg80211 snd_seq yenta_socket snd_timer pcmcia_rsrc pcmcia_core snd_seq_device snd parport_pc tpm_tis soundcore mei(C) snd_page_alloc coretemp lp parport dm_crypt btrfs zlib_deflate libcrc32c i915 drm_kms_helper drm i2c_algo_bit sdhci_pci sdhci e1000e wmi video [last unloaded: crc_itu_t]
Dec 12 20:04:05 localhost kernel: [34786.424023] Pid: 26435, comm: pm-suspend Tainted: G WC O 3.2.0-4-generic-pae #10-Ubuntu
Dec 12 20:04:05 localhost kernel: [34786.424024] Call Trace:
Dec 12 20:04:05 localhost kernel: [34786.424029] [<c105a1f2>] warn_slowpath_common+0x72/0xa0
Dec 12 20:04:05 localhost kernel: [34786.424031] [<c10982f9>] ? suspend_test_finish+0x89/0x90
Dec 12 20:04:05 localhost kernel: [34786.424033] [<c10982f9>] ? suspend_test_finish+0x89/0x90
Dec 12 20:04:05 localhost kernel: [34786.424035] [<c105a2c3>] warn_slowpath_fmt+0x33/0x40
Dec 12 20:04:05 localhost kernel: [34786.424037] [<c10982f9>] suspend_test_finish+0x89/0x90
Dec 12 20:04:05 localhost kernel: [34786.424039] [<c1098039>] suspend_devices_and_enter+0xd9/0x1a0
Dec 12 20:04:05 localhost kernel: [34786.424041] [<c10981bb>] enter_state+0xbb/0xf0
Dec 12 20:04:05 localhost kernel: [34786.424043] [<c1096eda>] state_store+0x8a/0x110
Dec 12 20:04:05 localhost kernel: [34786.424045] [<c1096e50>] ? pm_trace_dev_match_show+0x20/0x20
Dec 12 20:04:05 localhost kernel: [34786.424049] [<c12a9d5b>] kobj_attr_store+0x1b/0x30
Dec 12 20:04:05 localhost kernel: [34786.424052] [<c11a4b36>] sysfs_write_file+0xa6/0x100
Dec 12 20:04:05 localhost kernel: [34786.424055] [<c114431f>] vfs_write+0x8f/0x160
Dec 12 20:04:05 localhost kernel: [34786.424057] [<c11a4a90>] ? sysfs_poll+0x80/0x80
Dec 12 20:04:05 localhost kernel: [34786.424058] [<c11445fd>] sys_write+0x3d/0x70
Dec 12 20:04:05 localhost kernel: [34786.424062] [<c15a4c64>] syscall_call+0x7/0xb
Dec 12 20:04:05 localhost kernel: [34786.424064] ---[ end trace 8c2a7fedeba4096f ]---
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Fabio Marconi (fabiomarconi)]

And other repeated error even in the kern.log:

WARNING: at /build/buildd/linux-3.2.0/drivers/pci/pci-driver.c:607 pci_has_legacy_pm_support.isra.8+0x31/0x50()

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

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'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[John Lenton (chipaca)]

I've tested upstream and can confirm it still happens.
The failure I'm seeing now consistently is that when it resumes the backlight comes up and capslock light works when in x, but nothing draws on the screen. I can even ctrl-alt-fN ctrl-alt-del to reboot cleanly (nevertheless I need to actually power down to get display back in ubuntu, even though the bios screen is visible, not even grub shows until i've power cycled).

Attaching logs.

[John Lenton (chipaca)]

had to disable firewire to test 3.2-rc5 because it's got an even worse case of lp:894070.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[John Lenton (chipaca)]

3.2.0-5.11 still has the bug. I've got to test with an external display: I'm suspecting it's a timing issue with this HD panel, as per lp:600453.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[John Lenton (chipaca)]

I have been able to test with an external monitor, and it works. Notebook panel still fails to be set up correctly on resume. Further, notebook panel fails to be set up correctly by xrandr: simply running `xrandr --output eDP1 --scale 1x1` will make the panel blank, and only a hard power cycle brings it back. In case it bears mentioning, this was not the case in O.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Manuel Carro (mcarro)]

FWIW, my dell e6510 has the same problem with kernel 3.3.0-999_3.3.0-999.201202090430 (from the mainline builds): screen is blank upon suspension -> resumption and also upon hibernation -> resumption. The last ubuntu kernel which did not have that problem for me was 3.0.0-14 .

Cheers!

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Manuel Carro (mcarro)]

@John Lenton,

I have compiled and installed kernel 3.2.0-16.25 and it seems to work for me so far (including suspension and resumption - only tried a couple of times and it worked). Does it work for you too?

[John Lenton (chipaca)]

I just tried a quick suspend-resume cycle while docked, and the notebook panel worked after that. So that's promising; I need to test full suspend-resume cycles while not docked to make sure. xrandr --output eDP1 --scale .9x.9 now scales the panel. Changing it back to 1x1 just hung the computer, but that might be something else (for a different bug). --rotate also works.