Red Hat Bugzilla – Bug 244416
intel experimental video driver crashes system
Last modified: 2018-04-11 15:36:18 EDT
Description of problem:
When using the Intel experimental video driver on my thinkpad T60 with intel 945
gm, often my system will freeze, and the screen will show a bunch of gray block
on a black screen moving around. If I switch to the 810 drivers, I don't have
Version-Release number of selected component (if applicable):
not very--this is intermittent. However, it happens usually on logout or system
Steps to Reproduce:
1. logout or shutdown
system freezes with lots of gray blocks on a black screen
successful logout or shutdown
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243760 for the
Just a note that I'm able to reproduce this in nearly 100 % of cases using the
xrandr command as described here:
And it seems they fixed this upstream. I haven't tested it yet, though. (and I'm
not running Fedora on this HW, anyway)
Should be commit eecd3ccedee6c4acf101591f7e60673660379e62 in master branch of
xf86-video-intel. (I wanted to paste a link to gitweb, but gitweb.fd.o seems dead)
Yeah, 9xx should be pretty solid at this point. Please retest when you can
and update the bug.
(as far as I'm concerned, that single patch -- which I applied manually -- fixed
all my problems and X+intel have been really solid since)
Tomas, I know this isn't really a Fedora issue at this point since you
manually applied the patch, but I wonder if you could test upstream git? I
made some changes in this area recently and hopefully things will still work
for you. If not, I'd definitely appreciate if you could file a bug at
freedesktop.org against the intel driver for the problem.
I updated to latest git and things seem to work. If they stop, I'll make a note
about it :)
I guess, this is not NEEDINFO anymore.
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Thank you for the bug report. Closing bug as per comment #7.
If you still experience this problem after updating to our latest Fedora
release, reopen this bug against that version if this bug exists there.