Bug 715069

Summary: [KMS:X1400] Radeon Mobility X1400 locks up on boot with KMS
Product: [Fedora] Fedora Reporter: E Järvinen <ejarvinen>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: bugzilla, mcepl, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 16:30: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:
Attachments:
Description Flags
dmesg output after the manual loading of kernel modules and local lockup.
none
output of lspci -v
none
/var/log/messages
none
Xorg.0.log none

Description E Järvinen 2011-06-21 18:59:49 UTC
Created attachment 505877 [details]
dmesg output after the manual loading of kernel modules and local lockup.

Description of problem:

Hard lockup on boot with kms, boots a bit slowly with nomodeset
ThinkPad R60, ATI Radeon Mobility X1400

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

Fully updated F15 as of 2011-06-20:

kernel-PAE-2.6.38.8-32.fc15.i686
xorg-x11-drv-ati-6.14.1-1.20110504gita6d2dba6.fc15.i686

How reproducible:

Try booting without nomodeset, locks up hard with black screen at the point where X tries to start

Steps to Reproduce:
1. Turn on computer, boot with regular kernel options
2.
3.
  
Actual results:

Black screen, hard lockup

Expected results:

Normal Fedora boot, login screen
Additional info:

When booted with nomodeset, I logged in as root and issued telinit 3. Proceeded to remove kernel modules, as per 
http://www.x.org/wiki/radeonBuildHowTo#radeon-KMSissues

----
[root@orlando ~]# modprobe -v -r drm radeon
rmmod /lib/modules/2.6.38.8-32.fc15.i686.PAE/kernel/drivers/gpu/drm/radeon/radeon.ko
rmmod /lib/modules/2.6.38.8-32.fc15.i686.PAE/kernel/drivers/gpu/drm/ttm/ttm.ko
rmmod /lib/modules/2.6.38.8-32.fc15.i686.PAE/kernel/drivers/gpu/drm/drm_kms_helper.ko
rmmod /lib/modules/2.6.38.8-32.fc15.i686.PAE/kernel/drivers/gpu/drm/drm.ko
rmmod /lib/modules/2.6.38.8-32.fc15.i686.PAE/kernel/drivers/i2c/algos/i2c-algo-bit.ko
[root@orlando ~]# modprobe -v drm debug=1
insmod /lib/modules/2.6.38.8-32.fc15.i686.PAE/kernel/drivers/gpu/drm/drm.ko debug=1
----

So far, so good - X is not on, all virtual consoles work as expected.

----
[root@orlando ~]# modprobe -v radeon modeset=1
insmod /lib/modules/2.6.38.8-32.fc15.i686.PAE/kernel/drivers/i2c/algos/i2c-algo-bit.ko 
insmod /lib/modules/2.6.38.8-32.fc15.i686.PAE/kernel/drivers/gpu/drm/drm_kms_helper.ko 
insmod /lib/modules/2.6.38.8-32.fc15.i686.PAE/kernel/drivers/gpu/drm/ttm/ttm.ko 
insmod /lib/modules/2.6.38.8-32.fc15.i686.PAE/kernel/drivers/gpu/drm/radeon/radeon.ko modeset=1
Tapettu
---

(The last row is "Killed" in Finnish). At this point the screen goes black and computer is unresponsive to keyboard, but remains responsive through ssh. Won't respond to a "shutdown -h now", though - locks up instead and goes offline.

dmesg seems to give loads of probably interesting stuff, from this onward:

[  466.974574] BUG: unable to handle kernel NULL pointer dereference at 00000124

Unfortunately I can't debug this myself. If you need me to run more tests, just say so. I'd really like to have a working gnome-shell on my secondary laptop as well. dmesg output attached, will attach lspci -v.

Comment 1 E Järvinen 2011-06-21 19:00:38 UTC
Created attachment 505878 [details]
output of lspci -v

Comment 2 Matěj Cepl 2011-06-22 22:16:47 UTC
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, if available),
* X server log file (/var/log/Xorg.*.log)
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 3 E Järvinen 2011-06-23 06:21:56 UTC
Created attachment 506119 [details]
/var/log/messages

Comment 4 E Järvinen 2011-06-23 06:23:03 UTC
Created attachment 506120 [details]
Xorg.0.log

Comment 5 E Järvinen 2011-06-23 06:24:34 UTC
Added messages and Xorg.0.log, xorg.conf does not exist.

Comment 6 Jason Smith 2012-05-26 16:45:37 UTC
Thank you for taking the time to report this bug.  I was reviewing this report and noticed that updates to this package have been released since it was first reported. If you have time to update the package and re-test, please do so and report the results here. You can obtain the updated package by typing 'yum update xorg-x11-drv-ati' or using the graphical updater, Software Update.

If this error is persistient on current release software, please respond and I'll be happy to triage this report for further review.

---
Jason
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 7 Fedora End Of Life 2012-08-07 16:30:10 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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