10de:0a3c System freeze due to "angry" nouveau driver

[Witold Szczeponik]

Starting with the 3.19 kernels (Vivid), the system frequently freezes in the nouveau driver, with the following lines (w/ out timestamp and hostname) always being reported in "/var/log/kern.log" and/or "/var/log/syslog" just before the system becomes unresponsive and a hard reset becomes necessary.

nouveau E[ PFIFO][0000:01:00.0] still angry after 101 spins, halt

The bug is also reported in https://bugs.freedesktop.org/show_bug.cgi?id=87244, and the fix seems to be to cherry pick https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=adc346b133c952ec6988d90f6fa79cbe0a3eb7ef which is included in Linux 4.0 (if I am not mistaken).

Here's some more info:

lsb_release -rd:
Description: Ubuntu 14.04.3 LTS
Release: 14.04

Affected package:
linux-generic-lts-vivid-3.19.0.28.15

(As the affected package breaks my system reliably several times a day, I reverted to linux-generic-lts-utopic.)
---
ApportVersion: 2.14.1-0ubuntu3.13
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: de107192 2480 F.... pulseaudio
 /dev/snd/controlC0: de107192 2480 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2015-07-17 (61 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: LENOVO 43892DG
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-50-generic root=/dev/mapper/SETEC-UBUNTU ro rootflags=subvol=@ quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-50-generic N/A
 linux-backports-modules-3.16.0-50-generic N/A
 linux-firmware 1.127.15
Tags: trusty
Uname: Linux 3.16.0-50-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/03/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6NET84WW (1.45 )
dmi.board.name: 43892DG
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:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn43892DG:pvrThinkPadW510:rvnLENOVO:rn43892DG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 43892DG
dmi.product.version: ThinkPad W510
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

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

apport-collect 1496290

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.

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[Witold Szczeponik (wsz)]

apport information

[penalvch (penalvch)]

Witold Szczeponik, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[Witold Szczeponik (wsz)]

Installed Linux 4.2 and after the problem seems to be resolved (cf. commit adc346b133c952ec6988d90f6fa79cbe0a3eb7ef in Linux 4.0).

[penalvch (penalvch)]

Witold Szczeponik, to clarify, you personally tested commit adc346b133c952ec6988d90f6fa79cbe0a3eb7ef to fix your issue (and reverting it breaks functionality)?

[Witold Szczeponik (wsz)]

I tested the upstream Linux 4.2 kernel.

As per https://bugs.freedesktop.org/show_bug.cgi?id=87244#c10, applying said commit solves the problem. When time permits, I will create a 3.19 kernel with the cherry-picked commit and give it a try.

[Witold Szczeponik (wsz)]

I have back-ported commit adc346b133c952ec6988d90f6fa79cbe0a3eb7ef to Ubuntu-lts-3.19.0-30.33_14.04.1 from git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git and I can confirm that the bug has not manifested itself ever since.

How can I contribute the back-ported patch into the Ubuntu kernel 3.19?

[Witold Szczeponik (wsz)]

Removed all unrelated attachments.

[Witold Szczeponik (wsz)]

Bug #1502459 seems to be duplicate.

[Witold Szczeponik (wsz)]

There has been no update in the past four weeks. What needs to be done in order to progress the resolution of this bug?

[Witold Szczeponik (wsz)]

Another five weeks passed by...

[Witold Szczeponik (wsz)]

As Vivid has reached its "End of Life", this bug can be safely closed.