10de:1244 [Asus MAXIMUS IV GENE-Z] Nouveau Sleep/Wake problem in Ubuntu 13.04+

Bug #1224221 reported by Glenn Chugg
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

I am using a nVidia Graphics with default drivers and I am unable to wake up my system without it being crashed with garbage on the screen. This happens in LiveCD mode or installed and all versions of Kubuntu/Ubuntu/Gbunutu that I have tested, all of them are the same result. This has stopped moving to Linux when I need it most (Windows 8/8.1 is terrible) I had reported that I thought it was due to dual graphics (Switchable) but I've disabled the intel graphics in BIOS and the problem persisted. I think this is a Kernel level problem or perhaps xOrg related. I can offer no other information as the only thing I can do is reboot the system and disable sleep entirely.

This bug affects all distro's using the same (Above April 2012) kernel versions, all buntu versions, Fedora, SUSE and Mint (these are the only ones I've tested for this bug).

WORKAROUND: Use nvidia drivers in 13.10 (Only tested with the Ubuntu distribution).

WORKAROUND: Using nouveau (This worked for 12.04 and less in my testing on the same hardware reported in initial bug, it doesn't fix the graphical bug in 13.04 or 13.10, this may be an unrelated workaround):
sudo su
vim /etc/pm/sleep.d/05_xhci

Here is the content of this file:
#!/bin/sh
# Fix some issues with USB3
if [ "$1" = "suspend" ]
then
        modprobe -r xhci_hcd
fi
if [ "$1" = "resume" ]
then
        modprobe xhci_hcd
fi

# Change access right (not sure it's necessary)
chmod 755 /etc/pm/sleep.d/05_xhci

---
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 6220 F.... pulseaudio
CasperVersion: 1.331
DistroRelease: Ubuntu 13.04
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: System manufacturer System Product Name
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: bootkbd=us console-setup/layoutcode=en_US console-setup/variantcode=nodeadkeys locale=us_us persistent noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz splash --
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: raring
Uname: Linux 3.8.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 11/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MAXIMUS IV GENE-Z/GEN3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMAXIMUSIVGENE-Z/GEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Glenn Chugg (livefreedead) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1224221

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: raring
Revision history for this message
Glenn Chugg (livefreedead) wrote : Re: Problem with Sleep/Wake in Ubuntu 13.04 and greater

There is no report, I can not access the terminal or anything, the PC is fully crashed but low CPU cycles (Fan not full RPM)

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 kernel[0].

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.11-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Glenn Chugg (livefreedead) wrote :

No change when using the very latest mainline kernel, I did notice that the mouse continues to work and the Kubuntu cursor is still uncorrupted after waking.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-v3.11 needs-apport-collect regression-potential
removed: crash kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Glenn Chugg (livefreedead) wrote :

yeah I would if it worked!

glenn@glenn-System-Product-Name:~$ apport-collect 1224221
You need to run 'sudo apt-get install python-apport' for apport-collect to work.

https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1150335

Tried to hunt a fix for this but nothing found, I am using Kubuntu Daily (2 days old) with mainline kernel.

I'll see about downloading 13.04 and re-installing that to my PC for testing.

Revision history for this message
Glenn Chugg (livefreedead) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Glenn Chugg (livefreedead) wrote : BootDmesg.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : CRDA.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : HookError_cloud_archive.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : IwConfig.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : Lspci.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : Lsusb.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : ProcModules.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : PulseList.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : UdevDb.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : UdevLog.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : WifiSyslog.txt

apport information

Revision history for this message
Glenn Chugg (livefreedead) wrote : Re: Problem with Sleep/Wake in Ubuntu 13.04 and greater

I left Ubuntu 13.04 for over 60 seconds on that crashed screen. Then it came back to a semi usable system for me to type in the password the graphics were corrupted still but not as bad (jumbled controls out of position). So I rebooted and tried to do the same for my Kubuntu.

It said something about Xorg Failed twice (on a black terminal screen) then brought up the logon screen (not wake logon password request), I typed my password and it showed the kubuntu loading screen (that has icons appearing) and solid crashed (no mouse control, no HDD activity).

So it's still a regression in the kernel that is affecting the display manager after wake.

penalvch (penalvch)
tags: added: latest-bios-3603
tags: added: needs-crash-log
Revision history for this message
Glenn Chugg (livefreedead) wrote :

I am making it now, can you tell me how to get the crash log or where it would write to, now I can semi recover the system I'll keep trying to get the information needed to properly find the problem package. If it still happens in the latest Daily that is :) I'll be back soon with some answers.

Revision history for this message
Glenn Chugg (livefreedead) wrote :

The latest build hard crashes (no mouse control, keyboard locks (no num/caps led control)) and doesn't recover. I am back to my Kubuntu to see if I can get a terminal open before it locks up on me.

Revision history for this message
Glenn Chugg (livefreedead) wrote :

I pressed Ctrl+Alt+F1 and logged in to a terminal, then typed sudo pm-suspend, once the PC was asleep I woke it up, it went back to the terminal without any problems, I then pressed Ctrl+Alt+F4 to get back to xOrg, but it had the usual crashed graphics and then hard crashed so I couldn't get back to terminal either.

Revision history for this message
Glenn Chugg (livefreedead) wrote :

Sorry last post until I here back, doing the above Terminal trick I put it to sleep, I woke it up and typed startx, it proceeded to load the GUI again fine without corruption or lag.

Revision history for this message
Glenn Chugg (livefreedead) wrote :

Pressing Ctrl+Alt+F7 to get back to previous GUI session brought up the corrupted graphics. This is only happening if the OS has previously been asleep, if I don't run the pm-suspend I am able to switch between the old sessions and new startx session without it being corrupted.

penalvch (penalvch)
tags: added: saucy
tags: added: needs-upstream-testing
removed: needs-apport-collect
Revision history for this message
Glenn Chugg (livefreedead) wrote :

I managed to capture the problem (I think), not sure what the logs will show as it's a lot of information, it does have the suspend info and all the attempted waking info in there, so hopefully it'll help :) This is from my Kubuntu daily OS from 2 days ago as it was the only version I was able to recover enough to get to terminal to run the sysrq commands (I think)

Revision history for this message
penalvch (penalvch) wrote :

Glenn Chugg, unfortunately, this didn't capture a kernel oops (e.g. call trace) or xorg crash (e.g. backtrace). Please ensure you are not compressing attachments as this makes it more difficult for others to view your attachments.

Despite this, could you please attach the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

Revision history for this message
Glenn Chugg (livefreedead) wrote :

I tried to run the dmesg commands but all I got back was a file filled with:
[ 475.705526] nouveau E[ PGRAPH][0000:01:00.0] SHADER 0xa004021e
[ 475.705539] nouveau E[ PGRAPH][0000:01:00.0] TRAP ch 2 [0x023fbfe000 Xorg[1208]]

Here's the other requested information:
Device S-state Status Sysfs node
P0P1 S4 *disabled
RP01 S4 *disabled pci:0000:00:1c.0
PXSX S4 *disabled
RP02 S4 *disabled
PXSX S4 *disabled
RP03 S4 *disabled
PXSX S4 *disabled
RP04 S4 *disabled
PXSX S4 *disabled
RP05 S4 *disabled pci:0000:00:1c.4
PXSX S4 *enabled pci:0000:03:00.0
RP06 S4 *disabled pci:0000:00:1c.5
PXSX S4 *enabled pci:0000:04:00.0
RP07 S4 *disabled pci:0000:00:1c.6
PXSX S4 *disabled pci:0000:05:00.0
RP08 S4 *disabled
PXSX S4 *disabled
PEG0 S4 *disabled pci:0000:00:01.0
PEGP S4 *disabled
PEG1 S4 *disabled
PEG2 S4 *disabled
PEG3 S4 *disabled
GLAN S4 *enabled pci:0000:00:19.0
EHC1 S4 *enabled pci:0000:00:1d.0
EHC2 S4 *enabled pci:0000:00:1a.0
XHC S4 *disabled
HDEF S4 *disabled pci:0000:00:1b.0
PWRB S4 *enabled

penalvch (penalvch)
tags: added: regression-release
removed: regression-potential
Revision history for this message
Glenn Chugg (livefreedead) wrote :

I ran a few more tests last night on other distro's

Fedora 19.0.1 fails same results, it uses kernel 3.9 so this bug has been about for a while.
SUSE 13.1 Beta 1 - Kernel 3.11.1 also failed with this one.

I don't think these tests are useful, so I'll just assume that this bug will not be fixed any time soon, if I could get the alt+sysrq+1 and +t commands to actually work I'd capture the oops, but it's pretty obvious that the kernel and graphics are not resetting the xorg correctly after waking the system, I figure as I am one of the few people this bug affects that it's probably only some hardware configurations, but as this is my main PC that I use it has been enough to stop me switching back to developing for Linux, I may just install Kubuntu in a VM and develop from that, but it's never the same as using real hardware :'(

Revision history for this message
Glenn Chugg (livefreedead) wrote :

3.12 is still similar, when it first wakes it's black for 3 - 4 seconds, then it goes to the distorted screen for 50 - 60 seconds, this time I saw a black terminal type window for the first time (it said "Failed To Idle Channel" it said that twice on the screen. Then it went to the resume logon screen with a 1/8th wrap on it's screen position, I was able to type in the password and when I pressed enter it started fading in the first KDE icon and stopped 1/2 way through doing that, it wasn't hard crashed, but the mouse would lock up every 8 seconds for about 3 seconds, the num lock continues to work at this stage but it's given up trying to load the KDE desktop.

Seeing as it's trying so hard to recover, I'll try getting the Unity version of Ubuntu and see how that is going with the daily build and then with the MainLine kernel.

Revision history for this message
Glenn Chugg (livefreedead) wrote :

The current Ubuntu daily still does it (kernel 3.11.0.7) and it's installer is broken so I am unable to test a new kernel with it.

I tried to change more BIOS settings, but nothing seems to make any difference. Let me know if there is anything else I can do to help fix this, but I'll keep testing updates every now and then in hopes someone fixes it while working on other code. My own coding skills are limited to Basic, scripting and I have no need to learn Python or C, so will probably not be much help with these kinds of things - Especially working with Kernels and Drivers.

Revision history for this message
Glenn Chugg (livefreedead) wrote :

I thought I'd try 12.04 LTS again for the first time in ages, to make sure the sleep bug still didn't affect this PC with it, but now it does:

It stays on a black screen and doesn't resume at all anymore, pressing ctrl + alt F1 showed

nouveau called panic error (shown in terminal under the initializing section).

So this PC may have bigger compatibility issues with the Linux Kernels than I thought. I fixed it last time (From not waking) by making it shutdown then reboot the USB stack at shutdown/wake tho. So I know this kernel can work properly with it. I thought it was 12.10 that I had to add the USB commands to the proc files, which is why I said 13.04 was the first time the fix no longer worked for me. I'll try to find the USB fix again and see if that makes a difference to all the problems I am having with my power management, I just wish I could use the SysRq captures to report the proper oops, but it says this function isn't available when I try to use them.

Revision history for this message
Glenn Chugg (livefreedead) wrote :

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/522998/comments/42

The link above is the USB3 fix I implemented with 12.10 to get it to sleep and wake with this hardware I am currently using. It makes no effect to the 13.04+ kernel graphics corruption bug tho.

penalvch (penalvch)
description: updated
Revision history for this message
Glenn Chugg (livefreedead) wrote :

I sort of fixed it in Ubuntu 13.10 Daily.

I managed to figure out that the link/icon calling su ubiquity to install from the LiveCD fails in the current daily images, so I ran sudo ubiquity from terminal and got Ubuntu to install, I then was able to install the Propietary nVidia drivers and restart. The very next time I booted my PC I was able to sleep and wake without any problems at all. So the issue must lay in the nouevau driver and not the kernel or xorg (or be an incompatibility with them and the default driver).

Well I'd prefer to be using Kubuntu but as it's additional drivers app crashes whenever I try and run it I'll have to wait until the final 13.10 Build to switch back. but for now I am very happy to have a Linux OS that sleeps properly.

I didn't need to apply any work arounds, kernel updates or special packages to have it work, just the drivers.

penalvch (penalvch)
summary: - Problem with Sleep/Wake in Ubuntu 13.04 and greater
+ Problem with Sleep/Wake in Ubuntu 13.04 and greater with nouveau
description: updated
summary: - Problem with Sleep/Wake in Ubuntu 13.04 and greater with nouveau
+ 10de:1244 [Asus MAXIMUS IV GENE-Z] Problem with Sleep/Wake in Ubuntu
+ 13.04 and greater with nouveau
description: updated
summary: - 10de:1244 [Asus MAXIMUS IV GENE-Z] Problem with Sleep/Wake in Ubuntu
- 13.04 and greater with nouveau
+ 10de:1244 [Asus MAXIMUS IV GENE-Z] Nouveau Sleep/Wake problem in Ubuntu
+ 13.04+
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Glenn Chugg, 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 make a comment to this.

If reproducible, could you please test the latest upstream kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc2-trusty/ and advise to the results?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Glenn Chugg (livefreedead) wrote :

I downloaded the current trusty image, Live OS had same problem, Installed OS had same problem.

I updated mainline kernel and had similar problem. The screen came back corrupted for 1/2 a second, then it went to a black screen with a mouse cursor (movable), so the recent changes are doing something different, but not what I need, even if it would restart the GUI session if it times out (stops responding) instead of locking up/giving up on the x session, I could live with that.

I was unable to get it to re-start a new x session using ctrl+alt + F1 and typing startx like I could with previous tests.

penalvch (penalvch)
tags: added: trusty
tags: added: kernel-bug-exists-upstream-v3.13-rc2
removed: kernel-bug-exists-upstream-v3.11 needs-upstream-testing
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Glenn Chugg, 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#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Please provide a direct URL to your post once you have made it so that it may be tracked.

Thank you for your understanding.

tags: removed: regression-release
Changed in linux (Ubuntu):
status: Incomplete → Triaged
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.