Suspend fails after external display has been used

Bug #873941 reported by Andreas Nilsson
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

With nouveau, after using an external monitor the machine hangs indefinatly on suspend to ram.

According to https://bugzilla.redhat.com/show_bug.cgi?id=689044 it's a xrandr related bug, possibly in the xserver.

WORKAROUND: With nvidia-current it works just fine.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-12-generic 3.0.0-12.20
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: andrnils 1795 F.... pulseaudio
 /dev/snd/controlC0: andrnils 1795 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2420000 irq 45'
   Mixer name : 'Conexant CX20585'
   Components : 'HDA:14f15069,17aa218b,00100302'
   Controls : 8
   Simple ctrls : 5
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
   Mixer name : 'Nvidia GPU 0b HDMI/DP'
   Components : 'HDA:10de000b,10de0101,00100100'
   Controls : 16
   Simple ctrls : 4
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6MHT44WW-1.19'
   Mixer name : 'ThinkPad EC 6MHT44WW-1.19'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Fri Oct 14 09:17:38 2011
EcryptfsInUse: Yes
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110901)
MachineType: LENOVO 43494JG
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=5d904fe3-2eac-4e43-a9f7-dd53916e59a9 ro pcie_aspm=force quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 linux-firmware 1.60
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:

dmi.bios.date: 03/29/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6MET84WW (1.44 )
dmi.board.name: 43494JG
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:bvr6MET84WW(1.44):bd03/29/2011:svnLENOVO:pn43494JG:pvrThinkPadT510:rvnLENOVO:rn43494JG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 43494JG
dmi.product.version: ThinkPad T510
dmi.sys.vendor: LENOVO

Revision history for this message
Andreas Nilsson (andrnils) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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 . Please test the release candidate kernel versus the daily build. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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. Please let us know your results.

Thanks in advance.

tags: added: needs-upstream-testing
Revision history for this message
Andreas Nilsson (andrnils) wrote :

Sorry for the delay... The short answer is, there is fix upstream :)

I tested as follows:

Test with external screen at home (1280x1024)

Linux bowmore 3.1.0-0301rc9-generic #201110050905 SMP Wed Oct 5 09:15:03 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Works :) Some graphics tearing while resuming and switching between monitors.

Linux bowmore 3.1.0-999-generic #201110040905 SMP Tue Oct 4 09:10:44 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Works as well :) Same kind of graphics tearing while resuming and switching between monitors.

Linux bowmore 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Hangs after vt-switch to plymouth? splash.

For both mainline kernels I did two suspend cycles.

I also noticed that on boot both mainline kernels hands off to plymouth nicely, while 3.0.0-12 does the vt-switch to a "broken" terminal, i.e. half blue, half black plus some tearing.

Please let me know if you need any more testing done.
Best regards
Andreas

tags: removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Triaged
tags: added: kernel-fixed-upstream
Revision history for this message
Andreas Nilsson (andrnils) wrote :

Just as a followup, today after using the external screen at the office the computer hung while suspending again. This was on the same 3.1-rc9 kernel that worked with the monitor at home.

The laptop has a native res. of 1600x900, the monitor at the office has 1920x1280 and the one at home has 1280x1024.

Anything else that can be tried?

Best regards
Andreas

Revision history for this message
Andreas Nilsson (andrnils) wrote :

Another followup:

After using the computer at work some more days, it is still problematic to suspend after using external monitor. With 3.1-rc9 the computer at least does not hang, just comes back up, often with stack traces in dmesg. Is there any use of posting these? They seem to occur in different modules each time.

Regards
Andreas

tags: added: kernel-fixed-upstream-v3.1-rc9
removed: kernel-fixed-upstream
Revision history for this message
penalvch (penalvch) wrote :

Andreas Nilsson, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, 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.

description: updated
tags: added: bios-outdated-1.52 needs-upstream-testing regression-potential
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.