Bug 710548

Summary: [Cantiga] X server crashes after resuming from suspend
Product: [Fedora] Fedora Reporter: Jiri Eischmann <eischmann>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: ajax, elad, jmccann, mcepl, rstrode, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: [cat:crash]
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-01 19:48:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
messages, xorg and suspend logs in tar
none
hardware profile of my laptop
none
X.org log
none
log of system messages
none
log of pm-suspend
none
hardware-profile.txt from the archive
none
messages from the archive
none
pm-suspend.log from the archive
none
Xorg.0.log.old from the archive
none
output of dmesg
none
system log
none
Xorg log
none
Xorg log - old
none
Xsession Errors none

Description Jiri Eischmann 2011-06-03 16:42:44 UTC
Created attachment 502859 [details]
messages, xorg and suspend logs in tar

Description of problem:
X server crashes after the system resumes from suspend. The suspend itself seems to work well because the desktop environment shows up. After a moment (one sec), X server crashes and GDM shows up.

Version-Release number of selected component (if applicable):
Updated Fedora, gnome-session 3.0.1

How reproducible:
To suspend and resume the system. It doesn't happen every time, but most times 80-90 %).

Additional info:

I attached messages, xorg and suspend logs and hardware profile.

Comment 1 Elad Alfassa 2011-06-05 05:09:26 UTC
X server crash can't be client fault. moving to Xorg.
Please attach the relevant logs in separate, plain-text, non-compressed attachments. 




-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Jiri Eischmann 2011-06-05 13:35:49 UTC
Created attachment 503084 [details]
hardware profile of my laptop

Comment 3 Jiri Eischmann 2011-06-05 13:36:30 UTC
Created attachment 503085 [details]
X.org log

Comment 4 Jiri Eischmann 2011-06-05 13:37:49 UTC
Created attachment 503086 [details]
log of system messages

Comment 5 Jiri Eischmann 2011-06-05 13:38:29 UTC
Created attachment 503087 [details]
log of pm-suspend

Comment 6 Matěj Cepl 2011-06-06 10:50:14 UTC
Created attachment 503190 [details]
hardware-profile.txt from the archive

Comment 7 Matěj Cepl 2011-06-06 10:50:29 UTC
Created attachment 503191 [details]
messages from the archive

Comment 8 Matěj Cepl 2011-06-06 10:50:36 UTC
Created attachment 503192 [details]
pm-suspend.log from the archive

Comment 9 Matěj Cepl 2011-06-06 10:50:43 UTC
Created attachment 503193 [details]
Xorg.0.log.old from the archive

Comment 10 Matěj Cepl 2011-06-06 11:26:38 UTC
(In reply to comment #1)
> Please attach the relevant logs in separate, plain-text, non-compressed
> attachments. 

When the reporter provides logs in some (any) form, don't ask her to submit it again, please. Just repackage them for our better consumption (there are tools how to create a multiple attachments to bugzilla).

Comment 11 Matěj Cepl 2011-06-06 20:53:46 UTC
(In reply to comment #9)
> Created attachment 503193 [details]
> Xorg.0.log.old from the archive

Actually, looking at it now, I am afraid this is not the Xorg.0.log we need ... there is nowhere trace of the crash. Could you please provide us with a log which (most likely) ends with the word Backtrace: on separate line followed by the actual backtrace and couple more lines please?

Thank you

Comment 12 Jiri Eischmann 2011-06-07 07:43:24 UTC
OK, I'll try to reproduce it (which shouldn't so difficult) when I get to my personal computer. Can you give me advice what I should upload? Just Xorg.log or are there any other logs (besides those I've already uploaded) which might be useful?

Comment 13 Matěj Cepl 2011-06-07 15:58:58 UTC
This is the standard request for this situation:

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 14 Jiri Eischmann 2011-06-09 16:28:56 UTC
Created attachment 503936 [details]
output of dmesg

Comment 15 Jiri Eischmann 2011-06-09 16:29:50 UTC
Created attachment 503937 [details]
system log

Comment 16 Jiri Eischmann 2011-06-09 16:31:46 UTC
Created attachment 503938 [details]
Xorg log

Ends with the crash.

Comment 17 Jiri Eischmann 2011-06-09 16:33:41 UTC
Comment on attachment 503938 [details]
Xorg log

Starts with the crash.

Comment 18 Jiri Eischmann 2011-06-09 16:34:52 UTC
Created attachment 503939 [details]
Xorg log - old

Ends with the crash.

Comment 19 Jiri Eischmann 2011-06-09 16:35:58 UTC
Created attachment 503940 [details]
Xsession Errors

Comment 20 Jiri Eischmann 2011-06-09 16:42:10 UTC
I've uploaded new logs, but personally I didn't find anything leading to the crash. It's also hard to reproduce now, I've been trying it for two days and done about 10-12 suspends until the crash.

Comment 21 Jiri Eischmann 2011-09-29 15:05:07 UTC
This problem doesn't occur to me after the upgrade to the kernel 2.6.40, so I think it can be closed.

Comment 22 Matěj Cepl 2011-10-01 19:48:53 UTC
Thank you for letting us know.