Bug 90486 - Lockups on GTX 680
Summary: Lockups on GTX 680
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-16 20:53 UTC by Tavian Barnes
Modified: 2019-12-04 08:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg output (89.25 KB, text/plain)
2015-05-16 20:53 UTC, Tavian Barnes
no flags Details

Description Tavian Barnes 2015-05-16 20:53:45 UTC
Created attachment 115843 [details]
dmesg output

Since installing Plasma 5, I'm getting a lot of lockups even with compositing disabled.  As far as I can tell, the relevant part of dmesg is

[ 2043.225653] nouveau E[   PFIFO][0000:08:00.0] read fault at 0x0000490000 [PTE] from GR/S\
CC on channel 0x007edf8000 [kwin_x11[2256]]
[ 2043.225660] nouveau E[   PFIFO][0000:08:00.0] PGR engine fault on channel 12, recovering\
...
[ 2092.200410] nouveau E[   PFIFO][0000:08:00.0] PBDMA1: SIGNATURE
[ 2092.200416] nouveau E[   PFIFO][0000:08:00.0] PBDMA1: ch 13 [vlc[4136]] subc 0 mthd 0x00\
00 data 0x00000000
[ 2092.200430] nouveau E[   PFIFO][0000:08:00.0] PBDMA1: SIGNATURE
[ 2092.200433] nouveau E[   PFIFO][0000:08:00.0] PBDMA1: ch 13 [vlc[4136]] subc 0 mthd 0x00\
00 data 0x00000000
[ 2092.200446] nouveau E[   PFIFO][0000:08:00.0] PBDMA1: GPPTR PBENTRY SIGNATURE
[ 2092.200450] nouveau E[   PFIFO][0000:08:00.0] PBDMA1: ch 13 [vlc[4136]] subc 0 mthd 0x00\
00 data 0x00000000
[ 2092.200463] nouveau E[   PFIFO][0000:08:00.0] PBDMA1: GPPTR SIGNATURE
[ 2092.200465] nouveau E[   PFIFO][0000:08:00.0] PBDMA1: ch 13 [vlc[4136]] subc 0 mthd 0x00\
00 data 0x00000000
[ 2092.200478] nouveau E[   PFIFO][0000:08:00.0] PBDMA1: SIGNATURE
[ 2092.200481] nouveau E[   PFIFO][0000:08:00.0] PBDMA1: ch 13 [vlc[4136]] subc 0 mthd 0x00\
00 data 0x00000000
[ 2092.200494] nouveau E[   PFIFO][0000:08:00.0] PBDMA1: SIGNATURE
[ 2092.200496] nouveau E[   PFIFO][0000:08:00.0] PBDMA1: ch 13 [vlc[4136]] subc 0 mthd 0x00\
00 data 0x00000000
[ 2092.200511] nouveau E[   PFIFO][0000:08:00.0] read fault at 0x0000000000 [PDE] from UNK0\
a/HOST on channel 0x007ecf9000 [unknown]
[ 2092.200706] nouveau 0000:08:00.0: Direct firmware load for nouveau/nve4_fuc084 failed wi\
th error -2
[ 2092.200716] nouveau 0000:08:00.0: Direct firmware load for nouveau/nve4_fuc084d failed w\
ith error -2
[ 2092.200718] nouveau E[  PMSVLD][0000:08:00.0] unable to load firmware data
[ 2092.200719] nouveau E[  PMSVLD][0000:08:00.0] init failed, -2
[ 2107.210428] nouveau E[vlc[4136]] failed to idle channel 0xcccc0001 [vlc[4136]]
[ 2122.222450] nouveau E[vlc[4136]] failed to idle channel 0xcccc0001 [vlc[4136]]
[ 2152.018150] nouveau 0000:08:00.0: Direct firmware load for nouveau/nve4_fuc084 failed wi\
th error -2
[ 2152.018161] nouveau 0000:08:00.0: Direct firmware load for nouveau/nve4_fuc084d failed w\
ith error -2

In this case vlc triggered it, but often it's some other process like Xorg.bin.  Interestingly the machine was usable for a few minutes after this but then locked up.  The display froze and ssh would prompt for a password but hang before the shell started.  Rebooting with magic SysRq worked.

dmesg output attached.  Let me know what else I can do to collect debugging information.

Hardware is

# lspci | grep VGA
01:01.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 10)
08:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 680] (rev a1)
Comment 1 Martin Peres 2019-12-04 08:59:35 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/191.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.