Bug 1214663 - Complete hardlock after some time when using lockscreen or kmenu
Summary: Complete hardlock after some time when using lockscreen or kmenu
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-23 10:26 UTC by Bernd Putsche
Modified: 2015-12-04 00:12 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-18 19:13:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Xorg.0.log after reboot (504.41 KB, text/plain)
2015-04-23 18:33 UTC, Bernd Putsche
no flags Details
Xorg.0.log before reboot, after hardlock (527.33 KB, text/plain)
2015-04-23 18:34 UTC, Bernd Putsche
no flags Details
xsession-errors after reboot (66.89 KB, text/plain)
2015-04-23 18:35 UTC, Bernd Putsche
no flags Details


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 76414 0 None None None Never

Description Bernd Putsche 2015-04-23 10:26:32 UTC
Description of problem:
After a few minutes (>5) the system runs into a complete hardlock when opening kmenu, or activating the lockscreen on an i7 sandybridge with nvidia gtx680 and nouveau.

Version-Release number of selected component (if applicable):
kde 5 on fedora 22 beta (same problem existed in alpha)

How reproducible:
login into kde, do something or leave the system idle an wait for the screen lock. system freezes completely.

Steps to Reproduce:
1. Login and wait until screen lock becomes active or activate manually or use kmenu after a few minutes (5-15)
2. System runs into a hardlock.

Actual results:
Complete hardlock

Expected results:
No hardlock :-)

Additional info:

Comment 1 Rex Dieter 2015-04-23 12:13:42 UTC
If you can change VT's, can you get some log entries?

Anything interesting from /var/log/Xorg.0.log and/or ~/.xsession-errors would be nice.

Else, getting that information after rebooting too.

The evidence here so far is pointing to a video driver issue.

Comment 2 Bernd Putsche 2015-04-23 18:33:24 UTC
Created attachment 1018108 [details]
Xorg.0.log after reboot

Comment 3 Bernd Putsche 2015-04-23 18:34:19 UTC
Created attachment 1018109 [details]
Xorg.0.log before reboot, after hardlock

Comment 4 Bernd Putsche 2015-04-23 18:35:46 UTC
Created attachment 1018111 [details]
xsession-errors after reboot

Sorry but there is no file from before

Comment 5 Bernd Putsche 2015-04-23 18:47:36 UTC
the only thing from nouveau i have in messages from before the crash is this:
Apr 23 19:34:47 starscream kernel: nouveau E[   PFIFO][0000:01:00.0] read fault at 0x0000011000 [UNSUPPORTED_KIND] from PBDMA0/HOST on channel 0x007edb2000 [unknown]

but there is still another entry after that from 19:34:53 regarding journal activities. this is the last entry.

journalctl shows something similiar direct after detecting the screen lock event which caused the hardlock:

Apr 23 19:34:47 starscream.cosmonate.net org.kde.kglobalaccel[1339]: Got XKeyPress event
Apr 23 19:34:47 starscream.cosmonate.net org.kde.kglobalaccel[1339]: "Ctrl+Alt+L" = "Lock Session"
Apr 23 19:34:47 starscream.cosmonate.net kernel: nouveau E[   PFIFO][0000:01:00.0] read fault at 0x0000011000 [UNSUPPORTED_KIND] from PBDMA0/HOST on channel 0x007edb2000 [unknown]

Comment 6 Rex Dieter 2015-04-23 19:02:24 UTC
OK, now we may be getting somewhere.  Anything in /var/log/messages and/or dmesg?

I got it hit on,
https://bugs.freedesktop.org/show_bug.cgi?id=76414

on the message about PFIFO read fault...

Comment 7 Bruno Gambarini 2015-12-04 00:12:23 UTC
I have the same problem in 3 computers
1 with i7 3820 chipset x79, MB Asus Rampage IV Formula, nvidia gtx 690
2 with i7  960 chipset x58, MB Intel DX58SO, nvidia 220/560

In others computers the instalation complete perfect
I whant help, please, let me know what to do for help with this insue

Serching in google i found something in common in all similar bugs is the presence of core i7

both motherboards I tried disabling all extra features making just functional board
I I disabled all secondary chips beyond the x79 / x58, audio, network, cpu processes, UEFI, overclocking, and more
The bug continued to freeze the screen

A note in the core i7 960 freezes less

The system also bug using the video minimum installation option

This problem also occurs with opensuse 42.1 (kernel4)

This problem does not occur with Ubuntu 15 (kernel4)


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