Bug 473198
| Summary: | KMS:R480:X850XT modesetting panic; hard lockup. X does not work. "bad things may or may not happen" | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gregory Maxwell <gmaxwell> |
| Component: | kernel | Assignee: | Dave Airlie <airlied> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 12 | CC: | awilliam, kernel-maint, vedran |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-12-05 07:05:38 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: | 513462 | ||
|
Description
Gregory Maxwell
2008-11-27 01:24:25 UTC
By creating an xorg.conf with a BusID I was able to get the system working with a single card while kernel modesetting is disabled. Two cards still results in various issues. (This isn't relevant for the bug reported here, but it may be helpful to other users in the same situation. Here is the configuration which works for a single card: Boot with nomodeset and use the following as /etc/X11/xorg.conf Section "Device" Identifier "Videocard0" Driver "radeon" BusID "PCI:3:0:0" EndSection ) With 2.6.29.4-168.fc11.x86_64 the 'bad things may happen' and hard lock still happens with this hardware configuration, although now the message is displayed on two heads rather than one. (the nomodeset workaround still works) On the same hardware testday-20090908 also fails w/ Modesetting. The system panics at boot but continues booting only to later hang in udev probing. Without kernel modesetting it books fine. The system doesn't have a serial port, so I'm unable to capture the panic. (Spent the day yesterday trying to find someplace to buy a @#$@ db9 connector for the header on the motherboard but I couldn't) I've copied out the start of the backtrace from the panic by hand. This is 100% reproducible, so if more detail is required I can grab it. [drm:radeon_invalid_rreg] *ERROR* Invalid callback to read register 0x0072 --- kernel BUG at drivers/gpu/drm/radeon/radeon_device.c:239! invalid opcode: 0000 [#1] SMP last sysfs file: [changes each time] CPU 0 Modules linked in: Radeon+ [more stuff] Pid: 158, comm: work_for_cpu Not tainted 2.6.31-0.212.rc9.git1.fc12.x86_64 #1 132-CK-NF78 RIP 0010:[<fff...a0072d7e>] ... The backtrace is: cail_mc_read+0x2f/0x45 [radeon] atom_get_src_int+0x46a/0x576 [radeon] ? atom_execute_table+0x11f/0x262 [radeon] atom_get_dst+0x50/0x6 [radeon] can you attach your bios? cd /sys/bus/pci/devices/<pciid>/ echo 1 > rom cat rom > /tmp/r480.rom echo 0 > rom replace pciid with gpu pci id. This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reporter, can you retest with F13 Alpha? --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers 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 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. |