Bug 1475994 - Clicked on a link in google-chrome, window system froze up
Clicked on a link in google-chrome, window system froze up
Status: NEW
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau (Show other bugs)
26
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ben Skeggs
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-27 13:46 EDT by Tom Horsley
Modified: 2017-07-27 13:46 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
The Xorg.0.log file from the system when it froze. (35.84 KB, text/plain)
2017-07-27 13:46 EDT, Tom Horsley
no flags Details

  None (edit)
Description Tom Horsley 2017-07-27 13:46:47 EDT
Created attachment 1305616 [details]
The Xorg.0.log file from the system when it froze.

Description of problem:

google-chrome was in the middle of rendering a new web page (from cnn.com) when everything stopped working. No mouse movement, no scrolling, screen totally frozen. Ssh was still talking, so I was able to ssh into the system and reboot.

Version-Release number of selected component (if applicable):
xorg-x11-drv-nouveau-1.0.15-1.fc26.x86_64
kernel-4.11.11-300.fc26.x86_64
google-chrome-stable-60.0.3112.78-1.x86_64


How reproducible:
Apparently random. I had been booted into fedora 26 for a few hours and used chrome previously, so nothing obvious triggered this.

Steps to Reproduce:
1.see above
2.
3.

Actual results:
I find this junk in the logs from when it froze:

Jul 27 13:27:29 tomh kernel: nouveau 0000:01:00.0: fifo: read fault at ecab9ea000 engine 00 [GR] client 0d [GPC0/GCC] reason 00 [PDE] on channel 4 [007f5010
Jul 27 13:27:29 tomh kernel: nouveau 0000:01:00.0: fifo: channel 4: killed
Jul 27 13:27:29 tomh kernel: nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
Jul 27 13:27:29 tomh kernel: nouveau 0000:01:00.0: fifo: engine 0: scheduled for recovery
Jul 27 13:27:29 tomh kernel: nouveau 0000:01:00.0: fifo: engine 5: scheduled for recovery
Jul 27 13:27:29 tomh kernel: nouveau 0000:01:00.0: Xorg[1599]: channel 4 killed!


Expected results:
Screen keeps working.

Additional info:
I'm off to install the rpmfusion nvidia binaries, so the next time I test this will probably be fedora 27 (it failed in much the same way on fedora 24 previously).

Note You need to log in before you can comment on or make changes to this bug.