Bug 19956 - Xorg server crashes on exit when using radeon driver and 2 cards
Summary: Xorg server crashes on exit when using radeon driver and 2 cards
Status: NEW
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
Depends on:
Reported: 2009-02-04 12:10 UTC by Chris Tyler
Modified: 2009-02-04 13:15 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Note You need to log in before you can comment on or make changes to this bug.
Description Chris Tyler 2009-02-04 12:10:02 UTC
The radeon driver (installed as the package xorg-x11-drv-ati-6.10.0-1.fc10.x86_64 from fedora-updates-testing on 2009-02-03) causes the Xorg server to crash on exit when used in a dual-card configuration with R710 cards.

- two Asus EAH 4550 cards (R710) - PCI-Ex16 in x16 slots
- system board: Asus P5E3 Premium, 8G DDR3, Intel Core2 Quad Q6600

Steps to recreate:
1. Base system is Fedora 10 with current updates. Xorg server is 1.5.3, radeon driver is the package xorg-x11-drv-ati-6.10.0-1.fc10.x86_64 from fedora-updates-testing

2. Create default X.org file: X -configure  # Note: /root/xorg.conf.new is written, but X does not exit -- must be killed with KILL signal (TERM does not work).

3. Run: X -config /root/xorg.conf.new # Both screens start up OK

4. Terminate X server by zapping or sending TERM or KILL signal.

5. Result: System lockup (video, keyboard, network interfaces).
Expected: X server terminates, returns to text console.

Notes: Native LCD resolution is 1680x1050, correctly probed from monitor. Two evdev keyboards and mice present.
Comment 1 Chris Tyler 2009-02-04 13:15:30 UTC
Additional info:

- Confirmed lockup when one X server accesses one card (with BusID option to select the card) but two cards are present.

- Confirmed normal operation when 2nd video card is physically removed.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.