Ubuntu
xorg package

System freezes with noveau and GT210 card when Chromium or any video/audio application is started

Bug #1611482 reported by HugoHirsch on 2016-08-09

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xorg (Ubuntu)	Expired	Medium	Unassigned

Bug Description

This is a vanilla installation of 16.0.4 without any nvidia drivers, just the default noveau installation.

When I launch chromium or a podcast via gpodder/totem the screen gets marbled and the machine hangs /no reaction on mouse movements or keyboard clicks or numlock on/off).

When I ssh into the machine I see loads of log spam:

[ 145.789168] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00000000, e20: 00001100, e24: 00030000
[ 145.789173] nouveau 0000:01:00.0: gr: 00200000 [] ch 7 [001f8db000 totem[5048]] subc 3 class 8597 mthd 1224 data 00000001
[ 145.789186] nouveau 0000:01:00.0: fb: trapped write at 004055c200 on channel 7 [1f8db000 totem[5048]] engine 00 [PGRAPH] client 0b [PROP] subclient 00 [RT0] reason 00000000 [PT_NOT_PRESENT]
[ 145.789207] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - 00000040 [RT_FAULT] - Address 0040529600
[ 145.789212] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00180190, e20: 00001100, e24: 00030000
[ 145.789218] nouveau 0000:01:00.0: gr: 00200000 [] ch 7 [001f8db000 totem[5048]] subc 3 class 8597 mthd 1224 data 00000001
[ 145.789235] nouveau 0000:01:00.0: fb: trapped write at 004052d100 on channel 7 [1f8db000 totem[5048]] engine 00 [PGRAPH] client 0b [PROP] subclient 00 [RT0] reason 00000000 [PT_NOT_PRESENT]
[ 145.789252] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - 00000040 [RT_FAULT] - Address 0040533500
[ 145.789256] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00140230, e20: 00001100, e24: 00030000
[ 145.789262] nouveau 0000:01:00.0: gr: 00200000 [] ch 7 [001f8db000 totem[5048]] subc 3 class 8597 mthd 1224 data 00000001
[ 145.789274] nouveau 0000:01:00.0: fb: trapped write at 0040536700 on channel 7 [1f8db000 totem[5048]] engine 00 [PGRAPH] client 0b [PROP] subclient 00 [RT0] reason 00000000 [PT_NOT_PRESENT]
[ 145.789290] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - 00000040 [RT_FAULT] - Address 0040537a00
[ 145.789294] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00280270, e20: 00001100, e24: 00030000
[ 145.789300] nouveau 0000:01:00.0: gr: 00200000 [] ch 7 [001f8db000 totem[5048]] subc 3 class 8597 mthd 1224 data 00000001
[ 145.789312] nouveau 0000:01:00.0: fb: trapped write at 0040535c00 on channel 7 [1f8db000 totem[5048]] engine 00 [PGRAPH] client 0b [PROP] subclient 00 [RT0] reason 00000000 [PT_NOT_PRESENT]
[ 145.789328] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - 00000040 [RT_FAULT] - Address 004052fe00
[ 145.789332] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 003801f0, e20: 00001100, e24: 00030000
[ 145.789338] nouveau 0000:01:00.0: gr: 00200000 [] ch 7 [001f8db000 totem[5048]] subc 3 class 8597 mthd 1224 data 00000001
[ 145.789350] nouveau 0000:01:00.0: fb: trapped write at 004052b800 on channel 7 [1f8db000 totem[5048]] engine 00 [PGRAPH] client 0b [PROP] subclient 00 [RT0] reason 00000000 [PT_NOT_PRESENT]
[ 145.789369] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - 00000040 [RT_FAULT] - Address 0040525900
[ 145.789373] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00240150, e20: 00001100, e24: 00030000
[ 145.789378] nouveau 0000:01:00.0: gr: 00200000 [] ch 7 [001f8db000 totem[5048]] subc 3 class 8597 mthd 1224 data 00000001
[ 145.789390] nouveau 0000:01:00.0: fb: trapped write at 0040522f00 on channel 7 [1f8db000 totem[5048]] engine 00 [PGRAPH] client 0b [PROP] subclient 00 [RT0] reason 00000000 [PT_NOT_PRESENT]
[ 145.789407] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - 00000040 [RT_FAULT] - Address 004051df00
[ 145.789411] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 003c00d0, e20: 00001100, e24: 00030000
[ 145.789416] nouveau 0000:01:00.0: gr: 00200000 [] ch 7 [001f8db000 totem[5048]] subc 3 class 8597 mthd 1224 data 00000001
[ 145.789428] nouveau 0000:01:00.0: fb: trapped write at 0040519800 on channel 7 [1f8db000 totem[5048]] engine 00 [PGRAPH] client 0b [PROP] subclient 00 [RT0] reason 00000000 [PT_NOT_PRESENT]
[ 145.789445] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - 00000040 [RT_FAULT] - Address 0040513a00
[ 145.789449] nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00280030, e20: 00001100, e24: 00030000
[ 145.789454] nouveau 0000:01:00.0: gr: 00200000 [] ch 7 [001f8db000 totem[5048]] subc 3 class 8597 mthd 1224 data 00000001
[ 145.789467] nouveau 0000:01:00.0: fb: trapped write at 0040511c00 on channel 7 [1f8db000 totem[5048]] engine 00 [PGRAPH] client 0b [PROP] subclient 00 [RT0] reason 00000000 [PT_NOT_PRESENT]
[ 145.796852] nouveau 0000:01:00.0: fb: trapped write at 0040542300 on channel 7 [1f8db000 totem[5048]] engine 00 [PGRAPH] client 0b [PROP] subclient 00 [RT0] reason 00000000 [PT_NOT_PRESENT]
[ 147.797122] nouveau 0000:01:00.0: gr: PGRAPH TLB flush idle timeout fail
[ 147.797129] nouveau 0000:01:00.0: gr: PGRAPH_STATUS 00800003 [BUSY DISPATCH TPC_MP]
[ 147.797134] nouveau 0000:01:00.0: gr: PGRAPH_VSTATUS0: 00000000 []
[ 147.797138] nouveau 0000:01:00.0: gr: PGRAPH_VSTATUS1: 00001000 [TPC_MP]
[ 147.797141] nouveau 0000:01:00.0: gr: PGRAPH_VSTATUS2: 00000000 []
[ 149.797486] nouveau 0000:01:00.0: gr: PGRAPH TLB flush idle timeout fail
[ 149.797492] nouveau 0000:01:00.0: gr: PGRAPH_STATUS 00800003 [BUSY DISPATCH TPC_MP]
[ 149.797495] nouveau 0000:01:00.0: gr: PGRAPH_VSTATUS0: 00000000 []
[ 149.797499] nouveau 0000:01:00.0: gr: PGRAPH_VSTATUS1: 00001000 [TPC_MP]
[ 149.797502] nouveau 0000:01:00.0: gr: PGRAPH_VSTATUS2: 00000000 []

Luckily the machine reboots with a sudo shutdown -r now after 5 minutes of waiting.

Is this a known situation? Does it make sense to switch to the proprietary drivers or can I add any more debug information before trying out the nvidia setup?

Since I've experienced similar problems with my old 14.04 I did a fresh install.

$ apt-cache policy xorg
xorg:
  Installed: 1:7.7+13ubuntu3
  Candidate: 1:7.7+13ubuntu3
  Version table:
*** 1:7.7+13ubuntu3 500
        500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:

CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Aug 9 21:03:11 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
Subsystem: CardExpert Technology GT218 [GeForce 210] [10b0:1401]
InstallationDate: Installed on 2016-08-02 (7 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Gigabyte Technology Co., Ltd. H55M-USB3
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=UUID=0bbbfd07-9a94-4df5-9346-76d0c813590c ro priority=low quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/01/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F11
dmi.board.name: H55M-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd11/01/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H55M-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Aug 9 20:59:02 2016
xserver.configfile: default
xserver.devices:
input Power Button KEYBOARD, id 6
input Power Button KEYBOARD, id 7
input USB Keyboard KEYBOARD, id 8
input USB Keyboard KEYBOARD, id 9
input ImPS/2 Logitech Wheel Mouse MOUSE, id 10
xserver.errors:
Failed to load module "nvidia" (module does not exist, 0)
Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.3
xserver.video_driver: nouveau

Tags:

Revision history for this message

HugoHirsch (ubuntubugs-aiki-it) wrote on 2016-08-09:

CurrentDmesg.txt Edit (70.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.6 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (1.5 MiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (8.1 KiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (13.4 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (15.5 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (26.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (674 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (112 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.3 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (199.6 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (568 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (45.8 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (57.3 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (4.8 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (116.5 KiB, text/plain; charset="utf-8")
xserver.outputs.txt Edit (624 bytes, text/plain; charset="utf-8")

Revision history for this message

HugoHirsch (ubuntubugs-aiki-it) wrote on 2016-08-09:

I've read the comments in #977588 and created this as a new bug.

Revision history for this message

HugoHirsch (ubuntubugs-aiki-it) wrote on 2016-08-19:

Interesting that noone reacted on the bug.

I was able to circumenvent the problem with the proprietary nvidia drivers. Actually I wanted to avoid this on a new installation, but I'm unable to work if the system freezes randomly if I enter a webpage with a video or launch a video podcast :-(

Revision history for this message

penalvch (penalvch) wrote on 2016-09-01:

HugoHirsch, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

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, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

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.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.