Bug 571058 - GPU hung at login F12 2.6.32.9-67 2.6.32.9-70
Summary: GPU hung at login F12 2.6.32.9-67 2.6.32.9-70
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 573400 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-06 17:46 UTC by John
Modified: 2010-12-03 21:56 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 21:56:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
messages and Xorg.log (94.13 KB, application/x-gzip)
2010-03-06 17:46 UTC, John
no flags Details

Description John 2010-03-06 17:46:41 UTC
Created attachment 398231 [details]
messages and Xorg.log

Description of problem:After upgrade, screen goes blank at login.


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


How reproducible:Always


Steps to Reproduce:
1.Reboot, login
2.
3.
  
Actual results:Blank screen


Expected results:Desktop display


Additional info:Can still boot to old kernel (2.6.31.12-174.2.22.fc12.i686) without problems.

Comment 1 John 2010-03-09 00:47:50 UTC
shturm at 
http://forums.fedoraforum.org/showthread.php?t=241902
reports the same problem and also indicates that 
"Upgrade to 2.6.32.9-70 did not help - I was getting the same errors (X crashes)."

Comment 2 John 2010-03-09 17:20:15 UTC
Updated to 
xorg-x11-server-Xorg-1.7.5.901-1.fc12.i686.
It did not fix the problem.

Comment 3 John 2010-03-10 17:26:36 UTC
Updated to 
2.6.32.9-70.fc12.i686
It did not fix the problem.
nomodeset makes things much worse.
Can login using tty4.
gdm log shows no problems.

Comment 4 Rick Richardson 2010-03-11 19:15:52 UTC
Same here!  I have had to refuse the updates for kernels 2.6.31.12-174.2.22.

Comment 5 Rick Richardson 2010-03-11 19:16:58 UTC
Same here!  I have had to refuse the updates for kernels *greater than* 2.6.31.12-174.2.22

Comment 6 John 2010-03-12 01:47:21 UTC
1) Sometimes the system freezes before the login screen is reached.

2) If I'm quick enough after entering my password and pressing <Enter>, I can start tty4, wait until the disk stops making noise, and then return to tty1 with a working desktop. Logging out from this state usually freezes the system.

Comment 7 Edwin Lee 2010-03-14 07:30:29 UTC
i'm facing the same problem as well...

No solution in sight. Have just increased the installonly_limit in yum.conf and waiting to see if anything comes around...

Comment 8 Hans de Goede 2010-03-15 12:51:05 UTC
*** Bug 573400 has been marked as a duplicate of this bug. ***

Comment 9 Philip Walden 2010-03-16 17:19:27 UTC
I am having similar problems, except I have a nvidia TNT2 card and using the nouveau driver.

Should I submit as separate bug?

kernel: [drm] nouveau 0000:01:00.0: 32 MiB VRAM
kernel: agpgart-intel 0000:00:00.0: AGP 2.0 bridge
walden3 kernel: agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
kernel: pci 0000:01:00.0: putting AGP V2 device into 4x mode
kernel: [drm] nouveau 0000:01:00.0: 64 MiB GART (aperture)
kernel: [drm] nouveau 0000:01:00.0: Allocating FIFO number 0
walden3 kernel: [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 0
kernel: [drm] nouveau 0000:01:00.0: Allocating FIFO number 1
kernel: [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 1
kernel: [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 1
gdm-binary[1349]: WARNING: GdmDisplay: display lasted 1.421672 seconds
abrt[1442]: saved core dump of pid 1395 (/usr/bin/Xorg) to /var/cache/abrt/ccpp-1268758042-1395.new/coredump (2355200 bytes)

Comment 10 John Bouras 2010-03-21 23:24:31 UTC
I got the same problem. I have a Lenovo T61p with the nVidia Quadro FX 570M (rev a1) using the xorg-x11-drv-nouveau-1:0.0.15-20.20091105gite1c2efd.fc12 (i686) and kernel version 2.6.31.5-127.fc12.i686.PAE.

I got it used, tore the windoze license sticker off and put Fedora 12 on. It took me about 6 reinstalls before I was able to figure out that this driver won't work with kernel 2.6.32.9-70.fc12.i686.

As long as I don't install the later kernel, x will start.

Comment 11 John 2010-03-24 19:10:26 UTC
My problems have been resolved. 

My problem stems from the size of my monitor (2048x1152). Another monitor (1600x1200) worked OK.  The solution to my problem is not relevant to users with nvidia graphics. 

http://bugs.freedesktop.org/show_bug.cgi?id=27100.

Comment 12 shturm 2010-04-05 07:50:11 UTC
Updated kernel to latest 2.6.32.10-90 and Xorg to 1.7.6-1 - the same problem remains - X crashes on startup.
Rolled back kernel to 2.6.31.12-174 - everything is fine.

Comment 13 Philip Walden 2010-04-05 13:19:58 UTC
For the folks with nVidia cards, make sure you remove any nomodeset from the kernel boot parameters. See bug 566619

Comment 14 Chuck Ebbert 2010-04-06 10:31:14 UTC
kernel-2.6.32.11-99.fc12 has been submitted for testing but may not fix this bug.

Does abrt have any crashes saved? Open Applications | System Tools | Automatic Bug Reporting Tool or use the abrt-cli program to check.

Comment 15 Edouard Bourguignon 2010-04-07 08:51:29 UTC
no crashes saved in abrt. bug #566619 didn't help me too :( but I can boot with intel_iommu=off
Will try kernel-2.6.32.11-99.fc12

Comment 16 Charles Buenzli 2010-04-08 00:02:50 UTC
I have the same problem with my Dell Latitude D400 with an  Intel Corporation 82852/855GM Integrated Graphics Device rev 2. I'm stuck in  2.6.31.12-174. If I had a desktop, I'd replace the graphics card. With a laptop, I have no choice!

Comment 17 shturm 2010-04-20 03:03:24 UTC
Updated kernel to latest 2.6.32.11-99 - the same problem remains - X crashes on startup.
Rolled back kernel to 2.6.31.12-174 - everything is fine.

Comment 18 Charles Buenzli 2010-04-20 16:13:40 UTC
2.6.32.11-99 has the same problem (see comment 16 above). I can log in okay with just the laptop screen enabled but it crashes in a couple of minutes. If I have the laptop screen and an external monitor enabled, it never displays the login prompt. 2.6.31.12-174 is not a solution, since the display freezes after an hour or so of use. I'm willing to help with testing, just let me know what I need to do.

Comment 19 Bug Zapper 2010-11-03 20:38:10 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 20 Bug Zapper 2010-12-03 21:56:58 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.


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