Bug 483623
Summary: | Intel GMA4500 dvi/vga support | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Alan Matsuoka <alanm> | ||||||||||||
Component: | xorg-x11-drv-i810 | Assignee: | Adam Jackson <ajax> | ||||||||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | desktop-bugs <desktop-bugs> | ||||||||||||
Severity: | medium | Docs Contact: | |||||||||||||
Priority: | high | ||||||||||||||
Version: | 5.3 | CC: | ahabig, cmeadors, cww, ddm, dmair, jwest, xgl-maint | ||||||||||||
Target Milestone: | rc | Keywords: | Triaged | ||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | All | ||||||||||||||
OS: | Linux | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2011-10-16 04:34:24 UTC | Type: | --- | ||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||
Documentation: | --- | CRM: | |||||||||||||
Verified Versions: | Category: | --- | |||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
Embargoed: | |||||||||||||||
Bug Depends On: | |||||||||||||||
Bug Blocks: | 590060, 668575, 726826 | ||||||||||||||
Attachments: |
|
Description
Alan Matsuoka
2009-02-02 16:43:48 UTC
Created attachment 331238 [details]
dmesg from sosreport
Created attachment 331239 [details]
messages from sosreport
Created attachment 331240 [details]
xorg.conf from sosreport
Created attachment 331241 [details]
Xorg.0.log from sosreport
Can confirm this bug on the same hardware. Some more details: The failure seems to occur on X start. This has happened when booting from CD to install, when first entering runlevel 5, or when logging out and gdm restarts X. Switching to the "vesa" X driver (rather than "intel") restores stability. Minimal xorg.conf as generated by the install. It is not a 100% thing. The first machine I tried had about a 50% failure rate. The one I'm trying to install now has worked once out of about 8 tries. Smells like a race condition which might be hardware timing dependent. When the driver fails, not only does the screen go black and the fans speed up to max, but the machine powers off. Pretty hard - /var/log/messages lists the last thing happening as the desktop's gconfd exiting, then the restart when I reach over and power the box back on. Yay for journaling file systems. The fan speeding up thing is a lenovo bios feature, many lenovos ramp the fans to max speed temporarily upon power on as a functionality check, although this desktop model does not. So I suspect that this is a red herring, unless it's a hint as to what BIOS call is being thwacked to cause the powerdown. Is there a verbosity switch I could set on the intel driver that might shed more light on the situation? This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. QA_NAK 5.4 No capacity for this. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. |