Bug 581574 - Xorg 1.8.0 has intel lockup
Summary: Xorg 1.8.0 has intel lockup
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 14
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: [cat:lockup]
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-12 16:27 UTC by Ben Boeckel
Modified: 2018-04-11 08:07 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-07-19 12:02:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ben Boeckel 2010-04-12 16:27:09 UTC
Description of problem:
I visited a webpage with uzbl (will test again once bug is filed) and the intel driver locked up with the error:

(EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: Input/output buffer

Restarting X didn't help things (a reboot did). Keys were still being accepted by xmonad but the display was indeed frozen.

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.8.0-1.fc13.i686
xorg-x11-drv-intel-2.10.0-4.fc13.i686

How reproducible:
Further testing needed.

Comment 1 Ben Boeckel 2010-04-12 16:38:31 UTC
Failed to reproduce with the same webpage as the first lockup. libdrm was also upgraded to 2.4.20-1.fc13.i686 from libdrm-2.4.19-1.fc13.i686, so it may be the real culprit.

Comment 2 Matěj Cepl 2010-04-14 08:22:50 UTC
(In reply to comment #1)
> Failed to reproduce with the same webpage as the first lockup. libdrm was also
> upgraded to 2.4.20-1.fc13.i686 from libdrm-2.4.19-1.fc13.i686, so it may be the
> real culprit.    

So, in other words, this has been fixed in your opinion in libdrm-2.4.20?

Comment 3 Ben Boeckel 2010-04-14 14:48:59 UTC
Ah, no. I should have separated it into 2 paragraphs. I meant that libdrm was upgraded at the same time as Xorg was to 1.8.0 and may be the real culprit.

Comment 4 adam 2010-06-04 21:04:43 UTC
I am seeing a problem on my laptop using intel graphics that may be relevant here.

Card is 945GM
xorg-x11-server-Xorg-1.8.0-12.fc13.i686
xorg-x11-drv-intel-2.11.0-4.fc13.i686

I am seeing a variety of issues when trying to use the Hydrogen drum machine program.
A. There is a panel within the Hydrogem program that has "scrambled" lines.
B. When I close this program I often find other programs or even desktop elements have "scambled" lines in their graphics. 
C. Once i close Hydrogen I can no longer restart X, I just get a black screen
D. Just as a note... this "new" version of Hydrogen is using QT4 vs the previous QT3.
E. Also of note... Hydrogen works find within a virtual (VirtualBox-OSE) version of fedora13 running on the same laptop... It fails with the symptoms I've listed above every time on my intel laptop.

Not related to Hydrogen
A. I attempted to configure Xorg to use vesa graphics instead of intel using system-config-display. When I did this I was presented with a black screen in run level 5, no buttons worked (not even ctrl+alt+num) and I was forced to shutdown using the power button.

I wasn't able to find any useful output in /var/log/Xorg.0.log.
I know this isn't the place to diagnose "Hydrogen" problems but I'm not sure what else could be causing this besides X.

... hope this helps.

Comment 5 Bug Zapper 2010-07-30 11:18:50 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Adam Williamson 2010-10-06 21:55:57 UTC
Ben, are you still seeing this? Have you come up with a reliable reproducer yet?

Comment 7 Ben Boeckel 2011-06-25 18:24:02 UTC
I haven't seen this since (it has also since rode the wave to F16-Rawhide-dom).

Comment 8 Matěj Cepl 2011-07-12 14:27:32 UTC
OK, so could we close it as unreproducible then?

Comment 9 Ben Boeckel 2011-07-12 14:39:40 UTC
Sounds good to me.

Comment 10 Matěj Cepl 2011-07-19 12:02:51 UTC
Thank you for letting us know.


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