Bug 497455 - hitting assert on resume
Summary: hitting assert on resume
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: rawhide
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Kristian Høgsberg
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F11Blocker, F11FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2009-04-23 23:55 UTC by Matěj Cepl
Modified: 2018-04-11 08:33 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-04-25 10:01:16 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
/var/log/gdm/:0.log.1 (42.93 KB, text/plain)
2009-04-23 23:55 UTC, Matěj Cepl 		no flags Details
/var/log/Xorg.0.log (48.81 KB, text/plain)
2009-04-23 23:57 UTC, Matěj Cepl 		no flags Details
/var/log/dmesg (37.90 KB, text/plain)
2009-04-23 23:57 UTC, Matěj Cepl 		no flags Details
View All

Description Matěj Cepl 2009-04-23 23:55:38 UTC 
Created attachment 341038 [details]
/var/log/gdm/:0.log.1

Description of problem:
Every resume ends up in gdm login screen, which I guess means that X server crashes. Presented my logs to Dave Airlie and this is what I got:

<airlied> mcepl: oh it hits a nasty assert on resume
<airlied> you should file it with :0.log.1 attached.

so attaching that plus my beloved combo /var/log/Xorg.0.log and /var/log/dmesg (/etc/X11/xorg.conf contains just switching on Ctrl-Alt-Backspace).

Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.7.0-1.fc11.x86_64

How reproducible:
100%

Steps to Reproduce:
1.suspend-to-ram
2.resume
3.
  
Actual results:
gdm login screen

Expected results:
wherever I was before

Additional info:
Comment 1 Matěj Cepl 2009-04-23 23:57:11 UTC 
Created attachment 341039 [details]
/var/log/Xorg.0.log
Comment 2 Matěj Cepl 2009-04-23 23:57:30 UTC 
Created attachment 341040 [details]
/var/log/dmesg
Comment 3 Matěj Cepl 2009-04-25 10:01:16 UTC 
Seems to be fixed in xorg-x11-drv-intel-2.7.0-2.fc11.x86_64

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