Bug 561970

Summary: KMS broken on Intel 855GM broken with 2.6.32/33
Product: [Fedora] Fedora Reporter: Michal Nowak <mnowak>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: anton, dougsland, gansalmon, itamar, jonathan, kernel-maint, ohudlick
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 23:18:08 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:
Attachments:
Description Flags
lspci -v
none
dmesg none

Description Michal Nowak 2010-02-04 20:46:20 UTC 
Created attachment 388889 [details]
lspci -v

Description of problem:

With 2.6.32 and 2.6.33-rc5 I noticed that system with Intel 855GM is not booting anymore. After Grub and kernel start hang with completely black screen happens, no key stroke works (not even Magic SysRq) and have to power of it.

When I add 'nomodeset' it boots just fine until X starts problem with non-KMS+X arrives, this is actually bug 522551 (it's not expected this to be ever fixed) and /var/log/Xorg.log is empty.

Kernel 2.6.33-rc4 (+ recent intel xorg driver 2.10) is necessary for this box to enable Xv when KMS enabled.

Just to stress that boxes with Intel 855 might be totally unusable with kernels 2.6.32+ - KSM broken in kernel and non-KSM usabe broken on X level. 2.6.31.x is fine.

Version-Release number of selected component (if applicable):

kernel-2.6.32.7-37.fc12.i686
xorg-x11-drv-intel-2.9.1-1.fc12.i686

How reproducible:

always


I likely try to boot with most recent F13 kernel and report later back.
Comment 1 Michal Nowak 2010-02-04 20:50:25 UTC 
Created attachment 388892 [details]
dmesg
Comment 2 Bug Zapper 2010-11-03 23:01:14 UTC 
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 to the applicable version.  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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 3 Bug Zapper 2010-12-03 23:18:08 UTC 
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.