Suspend fails with nouveau problem

Bug #1329689 reported by Kevin Dalley
40
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Suspend works with linux-image-extra-3.13.0-24-generic, but fails with linux-image-extra-3.13.0-27-generic

Here is a message from syslog:

Jun 13 02:00:56 nereocystis kernel: [ 59.696022] sd 0:0:0:0: [sda] Stopping disk
Jun 13 02:00:56 nereocystis kernel: [ 59.722745] nouveau [ DRM] waiting for kernel channels to go idle...
Jun 13 02:00:56 nereocystis kernel: [ 59.722770] nouveau [ DRM] suspending client object trees...
Jun 13 02:00:56 nereocystis kernel: [ 59.723158] nouveau [ DRM] suspending kernel object tree...
Jun 13 02:00:56 nereocystis kernel: [ 61.725016] nouveau E[ PDISP][0000:01:00.0][0xc000857c][ffff8800a28d3b80] fini timeout, 0xc2061008
Jun 13 02:00:56 nereocystis kernel: [ 61.725017] nouveau E[ PDISP][0000:01:00.0][0xc000857c][ffff8800a28d3b80] failed suspend, -16
Jun 13 02:00:56 nereocystis kernel: [ 61.725019] nouveau E[ DRM] 0xd1500000:0xd15c7c00 suspend failed with -16
Jun 13 02:00:56 nereocystis kernel: [ 61.725042] nouveau E[ DRM] 0xdddddddd:0xd1500000 suspend failed with -16
Jun 13 02:00:56 nereocystis kernel: [ 61.725153] nouveau E[ DRM] 0xffffffff:0xdddddddd suspend failed with -16
Jun 13 02:00:56 nereocystis kernel: [ 61.725625] nouveau E[ DRM] 0xffffffff:0xffffffff suspend failed with -16
Jun 13 02:00:56 nereocystis kernel: [ 61.725733] nouveau [ DRM] resuming display...
Jun 13 02:00:56 nereocystis kernel: [ 61.752906] pci_pm_suspend(): nouveau_pmops_suspend+0x0/0xb0 [nouveau] returns -16
Jun 13 02:00:56 nereocystis kernel: [ 61.752920] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16
Jun 13 02:00:56 nereocystis kernel: [ 61.752922] PM: Device 0000:01:00.0 failed to suspend async: error -16
Jun 13 02:00:56 nereocystis kernel: [ 61.752934] PM: Some devices failed to suspend, or early wake event detected
Jun 13 02:00:56 nereocystis kernel: [ 61.752987] mei_me 0000:00:16.0: irq 45 for MSI/MSI-X
Jun 13 02:00:56 nereocystis kernel: [ 61.769256] snd_hda_intel 0000:00:1b.0: irq 48 for MSI/MSI-X
Jun 13 02:00:56 nereocystis kernel: [ 61.856994] pciehp 0000:00:1c.5:pcie04: Device 0000:04:00.0 already exists at 0000:04:00, cannot hot-add
Jun 13 02:00:56 nereocystis kernel: [ 61.856997] pciehp 0000:00:1c.1:pcie04: Device 0000:03:00.0 already exists at 0000:03:00, cannot hot-add
Jun 13 02:00:56 nereocystis kernel: [ 61.856999] pciehp 0000:00:1c.5:pcie04: Cannot add device at 0000:04:00
Jun 13 02:00:56 nereocystis kernel: [ 61.857001] pciehp 0000:00:1c.1:pcie04: Cannot add device at 0000:03:00
Jun 13 02:00:56 nereocystis kernel: [ 62.097072] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jun 13 02:00:56 nereocystis kernel: [ 62.097105] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 13 02:00:56 nereocystis kernel: [ 62.097879] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Jun 13 02:00:56 nereocystis kernel: [ 62.097996] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
Jun 13 02:00:56 nereocystis kernel: [ 62.097999] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Jun 13 02:00:56 nereocystis kernel: [ 62.099477] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Jun 13 02:00:56 nereocystis kernel: [ 62.099569] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
Jun 13 02:00:56 nereocystis kernel: [ 62.099570] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Jun 13 02:00:56 nereocystis kernel: [ 62.099923] ata2.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
Jun 13 02:00:56 nereocystis kernel: [ 62.099925] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Jun 13 02:00:56 nereocystis kernel: [ 62.100186] ata1.00: configured for UDMA/133
Jun 13 02:00:56 nereocystis kernel: [ 62.105023] ata5: SATA link down (SStatus 0 SControl 300)
Jun 13 02:00:56 nereocystis kernel: [ 62.106057] ata2.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
Jun 13 02:00:56 nereocystis kernel: [ 62.106060] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Jun 13 02:00:56 nereocystis kernel: [ 62.108022] ata2.00: configured for UDMA/100
Jun 13 02:00:56 nereocystis kernel: [ 62.113114] sd 0:0:0:0: [sda] Starting disk
Jun 13 02:00:56 nereocystis kernel: [ 64.091258] PM: resume of devices complete after 2337.685 msecs
Jun 13 02:00:56 nereocystis kernel: [ 64.091849] PM: Finishing wakeup.
Jun 13 02:00:36 nereocystis whoopsie[1581]: online
Jun 13 02:00:56 nereocystis whoopsie[1581]: offline
Jun 13 02:00:56 nereocystis kernel: [ 64.091850] Restarting tasks ... done.
Jun 13 02:00:56 nereocystis kernel: [ 64.102356] video LNXVIDEO:00: Restoring backlight state
Jun 13 02:00:56 nereocystis kernel: [ 64.102630] video LNXVIDEO:02: Restoring backlight state
Jun 13 02:00:56 nereocystis anacron[4281]: Anacron 2.3 started on 2014-06-13
Jun 13 02:00:56 nereocystis anacron[4281]: Will run job `cron.daily' in 5 min.
Jun 13 02:00:56 nereocystis anacron[4281]: Jobs will be executed sequentially
Jun 13 02:00:57 nereocystis kernel: [ 64.303326] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 13 02:00:57 nereocystis kernel: [ 64.310766] iwlwifi 0000:03:00.0: Radio type=0x0-0x0-0x3
Jun 13 02:00:57 nereocystis NetworkManager[1046]: <info> wake requested (sleeping: yes enabled: yes)
Jun 13 02:00:57 nereocystis NetworkManager[1046]: <info> waking up and re-enabling...
Jun 13 02:00:57 nereocystis NetworkManager[1046]: <info> WWAN now enabled by management service

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-27-generic 3.13.0-27.50
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kevin 10207 F.... pulseaudio
CurrentDesktop: Unity
Date: Fri Jun 13 02:13:05 2014
HibernationDevice: RESUME=UUID=8434466e-40aa-4c19-990f-adc570555efa
InstallationDate: Installed on 2013-06-02 (375 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 13d3:5120 IMC Networks
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK Computer Inc. U30Jc
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-27-generic N/A
 linux-backports-modules-3.13.0-27-generic N/A
 linux-firmware 1.127.2
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-04-24 (49 days ago)
dmi.bios.date: 01/24/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U30Jc.217
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: U30Jc
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU30Jc.217:bd01/24/2011:svnASUSTeKComputerInc.:pnU30Jc:pvr1.0:rvnASUSTeKComputerInc.:rnU30Jc:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: U30Jc
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
Kevin Dalley (nereocystis) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Kevin Dalley (nereocystis) wrote :

By the way, the problem still exists in
linux-tools-3.13.0-29-generic

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.15 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.15-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-bisect regression-update
Revision history for this message
Mariusz Gieparda (mkgiepard) wrote :

I faced similar problem.
With upstream kernel buggy behavior is not changed, still it's not possible to suspend the system as it goes back to login screen immediately.

I'm happy to provide more info, let me know what is needed.

---------------------
~$ uname -a
Linux orion3 3.15.0-031500-generic #201406131105 SMP Fri Jun 13 15:06:46 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Mariusz Gieparda (mkgiepard) wrote :

and with 3.15.2 it doesn't work either

---------------------
~$ uname -a
Linux orion3 3.15.2-031502-generic #201406261639 SMP Thu Jun 26 20:40:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Conrad Knight (iestynapmwg) wrote :

Has there been any resolution to this? Suspend stopped working for me after kernel 3.13.0-24 was upgraded to 3.13.0-27, with the same nouveau errors in syslog and dmesg. When i reported it at the time, i also tested upstream 3.15-rc7. That seemed to suspend correctly a few times, but then started to give the same errors.

This was my original report:
https://bugs.launchpad.net/bugs/1324697

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
Revision history for this message
Marcello Nuccio (marcenuc) wrote :

The easiest workaround is installing the proprietary drivers as explained at http://askubuntu.com/a/507299/11223

Revision history for this message
penalvch (penalvch) wrote :

Marcello Nuccio, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Revision history for this message
Kevin Dalley (nereocystis) wrote :

Suspend now works with
linux-image-extra-3.13.0-36-generic

I have not tested new kernels for while, so I'm not sure when the change happened.

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.