Raring wake up from S3 broken

[Anca Emanuel]

It was working before some updates (not kernel).

I was testing Raring some weeks ago (have kernel 3.5) and there was no problems.
Then testing updates, including kernel 3.7
After other updates, I discovered that I have an black screen after S3 sleep.

I can do Control+Alt+F1, username, password, test commands, like sudo reboot.
(blindness)

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5
Uname: Linux 3.7.0-2-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.6.2-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Fri Nov 23 12:07:03 2012
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI RS780M/RS780MN [Mobility Radeon HD 3200 Graphics] [1002:9612] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1062]
 Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] [1002:95c4] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1875]
InstallationDate: Installed on 2012-11-17 (5 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121117)
MachineType: ASUSTeK Computer Inc. X71TL
MarkForUpload: True
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic root=UUID=7a5f18e2-e748-4cce-8d9d-4fc3c746bfd1 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X71TL
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr303:bd10/14/2008:svnASUSTeKComputerInc.:pnX71TL:pvr1.0:rvnPEGATRONCORPORATION:rnX71TL:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: X71TL
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.40-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.13-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1
xserver.bootTime: Fri Nov 23 11:56:33 2012
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.13.0-0ubuntu8
xserver.video_driver: radeon
---
ApportVersion: 2.6.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: emanuel 1973 F.... pulseaudio
 /dev/snd/controlC0: emanuel 1973 F.... pulseaudio
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=6433010e-6c54-4069-998d-e304f780bd6e
InstallationDate: Installed on 2012-11-17 (5 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121117)
MachineType: ASUSTeK Computer Inc. X71TL
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 radeondrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic root=UUID=7a5f18e2-e748-4cce-8d9d-4fc3c746bfd1 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5
RelatedPackageVersions:
 linux-restricted-modules-3.7.0-2-generic N/A
 linux-backports-modules-3.7.0-2-generic N/A
 linux-firmware 1.97
Tags: raring running-unity
Uname: Linux 3.7.0-2-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 10/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X71TL
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr303:bd10/14/2008:svnASUSTeKComputerInc.:pnX71TL:pvr1.0:rvnPEGATRONCORPORATION:rnX71TL:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: X71TL
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[Anca Emanuel (anca-emanuel)]

apport information

[zikaface (zikaface)]

Similar problem but a bit heavier: When this happens I do not have access to tty*, only help comes from REISUB...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[zikaface (zikaface)]

Forgot to say: for now on I've solved this by adding apm=off to kernel line...

[Anca Emanuel (anca-emanuel)]

Tested apm=off.
Not working for me.

[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.7 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.7-rc6-raring/

[Anca Emanuel (anca-emanuel)]

I will repeat: this is NOT a kernel regression. 3.7-rc4 and 3.5 were both working before some userspace updates. After that, I tested both 3.7-rc4 and 3.5, I get an black screen.

I'm compiling now 3.7-rc7. I can git bisect it, but there is no point since I already tested 3.5 and is not working.

[Anca Emanuel (anca-emanuel)]

Tested kernel 3.7-rc7. The same as all other kernels.
dmesg obtained typing blind.

[Joseph Salisbury (jsalisbury)]

Thanks for testing, Anca. I'll re-assign this to xorg for additional review.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Timo Aaltonen (tjaalton)]

so the candidates are:
- mesa upgrade to 9.0.1 (stable release)
- libdrm upgrade to 2.4.40
- unity minor update

Can you tell when the problem started? The bug has dpkg.log if you want to check when the updates were applied.

[Anca Emanuel (anca-emanuel)]

> Can you tell when the problem started?

I installed rarring on 13.nov.2012: http://forum.ubuntu.ro/viewtopic.php?pid=153808#p153808
Tested updates. Updated to kernel 3.7 with "Software Updater". It was working.
I do not remember what other updates caused the problem.

Then I decided to test install from Live CD on 15.nov.2012
(successfully installed on 17.nov: http://iso.qa.ubuntu.com/qatracker/milestones/243/builds/27678/testcases/1302/results )

[Anca Emanuel (anca-emanuel)]

Progress report.

I connected a second (turned off) vga monitor to the laptop.
SOLVED !!!

Tried second suspend with the vga cable removed. It works !

[Anca Emanuel (anca-emanuel)]

I think this bug is related to wayland.

https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-system-compositor
Quote: Wayland can pick the wrong video card if you have two.

[Anca Emanuel (anca-emanuel)]

Ping Robert

[Bryce Harrington (bryce)]

Are you running wayland?

There hasn't been much in the way of X changes in raring so far; Timo listed the candidates all of which are fairly minor changes. You can test downgrading each in turn to identify what caused it if it is indeed X. (I'm guessing it's *not* X, since these types of bugs almost never are typically, but easy enough for you to verify.) If you can pinpoint it to the updated package, it should be a short list of changes to review.

[Anca Emanuel (anca-emanuel)]

I am running the stock raring ringtail, and after I noticed that
upgrade to libwayland0 version 1.0.2 and something, I decided to:
sudo apt-install weston
but nothing hapened.

Quote: "There hasn't been much in the way of X changes in raring so far;"
I can confirm that the shape of the startup messages from kernel are changed.
I khow how they are before, and I can allays compare with my precise install.

On Mon, Dec 3, 2012 at 9:04 PM, Bryce Harrington
<email address hidden> wrote:
> Are you running wayland?
>
> There hasn't been much in the way of X changes in raring so far; Timo
> listed the candidates all of which are fairly minor changes. You can
> test downgrading each in turn to identify what caused it if it is indeed
> X. (I'm guessing it's *not* X, since these types of bugs almost never
> are typically, but easy enough for you to verify.) If you can pinpoint
> it to the updated package, it should be a short list of changes to
> review.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1082314
>
> Title:
> Raring wake up from S3 broken
>
> Status in “mesa” package in Ubuntu:
> Incomplete
>
> Bug description:
> It was working before some updates (not kernel).
>
> I was testing Raring some weeks ago (have kernel 3.5) and there was no problems.
> Then testing updates, including kernel 3.7
> After other updates, I discovered that I have an black screen after S3 sleep.
>
> I can do Control+Alt+F1, username, password, test commands, like sudo reboot.
> (blindness)
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.04
> Package: xorg 1:7.7+1ubuntu4
> ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5
> Uname: Linux 3.7.0-2-generic x86_64
> .tmp.unity.support.test.0:
>
> ApportVersion: 2.6.2-0ubuntu5
> Architecture: amd64
> CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
> CompositorRunning: compiz
> Date: Fri Nov 23 12:07:03 2012
> DistUpgraded: Fresh install
> DistroCodename: raring
> DistroVariant: ubuntu
> ExtraDebuggingInterest: Yes, including running git bisection searches
> GraphicsCard:
> Advanced Micro Devices [AMD] nee ATI RS780M/RS780MN [Mobility Radeon HD 3200 Graphics] [1002:9612] (prog-if 00 [VGA controller])
> Subsystem: ASUSTeK Computer Inc. Device [1043:1062]
> Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] [1002:95c4] (prog-if 00 [VGA controller])
> Subsystem: ASUSTeK Computer Inc. Device [1043:1875]
> InstallationDate: Installed on 2012-11-17 (5 days ago)
> InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121117)
> MachineType: ASUSTeK Computer Inc. X71TL
> MarkForUpload: True
> ProcEnviron:
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic root=UUID=7a5f18e2-e748-4cce-8d9d-4fc3c746bfd1 ro quiet splash vt.handoff=7
> SourcePackage: xorg
> Symptom: display
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 10/14/2008
> dmi.bios.ven...

[Anca Emanuel (anca-emanuel)]

After today updates http://i.imgur.com/41g7j.png
the problem is solved for me. Thanks.