Hi.
On FreeBSD-10.2 on AMD64 we get random X server crashes with the radeon driver.
This is a problem that dates back for quite a while. On FreeBSD-9.x running xorg-7.5.2 the server would default to the exa acceleration method, which the manual described as "the newer acceleration architecture with better performance for the Render and Composite extensions." Xwindows would periodically crash with this driver. So for a long time now, we have been forcing our machines to use xaa acceleration method, which the manual described as "the traditional acceleration architecture". It has run stable.
/etc/xorg.conf:
On FreeBSD-10.2 running xorg-7.7_2 from the binary package, the manual no longer mentions "xaa" as an option. It just says
I recently upgraded a clients machine to FreeBSD-10.2 and now he is getting periodic X server crashes. It can run just fine for several days before it happens.
He is running the same video card as I am, RV370 5B60 [Radeon X300 (PCIE)] on an AMD64 machine.
The display will sometimes just lock up and require a reboot to correct it. Right after, the system log shows
The output of
This, of course is not the entire list of what's loaded. I can provide it if there are possibly other related modules.
Any help on resolving this would be appreciated.
On FreeBSD-10.2 on AMD64 we get random X server crashes with the radeon driver.
This is a problem that dates back for quite a while. On FreeBSD-9.x running xorg-7.5.2 the server would default to the exa acceleration method, which the manual described as "the newer acceleration architecture with better performance for the Render and Composite extensions." Xwindows would periodically crash with this driver. So for a long time now, we have been forcing our machines to use xaa acceleration method, which the manual described as "the traditional acceleration architecture". It has run stable.
/etc/xorg.conf:
Code:
Section "Device"
...
Option "AccelMethod" "xaa"
EndSection
Code:
Option "AccelMethod" "string"
Chooses between available acceleration architectures. Valid values
are EXA (for pre-TAHITI GPUs) and glamor (for R300 or higher). The
default is glamor as of TAHITI, otherwise EXA.
He is running the same video card as I am, RV370 5B60 [Radeon X300 (PCIE)] on an AMD64 machine.
The display will sometimes just lock up and require a reboot to correct it. Right after, the system log shows
Code:
Aug 26 17:11:31 xxx kernel: drmn0: error: GPU lockup CP stall for more than 10000msec
Aug 26 17:11:31 xxx kernel: drmn0: warning: GPU lockup (waiting for 0x000000000085960 1 last fence id 0x0000000000859536)
Aug 26 17:11:31 xxx kernel: error: [drm:pid985:r100_gui_wait_for_idle] *ERROR* radeon : wait for empty RBBM fifo failed ! Bad things might happen.
Aug 26 17:11:31 xxx kernel: error: [drm:pid985:r100_cp_disable] *ERROR* Failed to wai t GUI idle while programming pipes. Bad things might happen.
Aug 26 17:11:31 xxx kernel: drmn0: info: Saved 6491 dwords of commands on ring 0.
Aug 26 17:11:31 xxx kernel: drmn0: info: (r300_asic_reset:395) RBBM_STATUS=0x8401C100
Aug 26 17:11:31 xxx kernel: drmn0: info: (r300_asic_reset:414) RBBM_STATUS=0x8401C100
kldstat shows these modules loaded.
Code:
12 1 0xffffffff81de4000 11785a radeonkms.ko
17 1 0xffffffff81f56000 f6c radeonkmsfw_R300_cp.ko
13 1 0xffffffff81efc000 522db drm2.ko
Any help on resolving this would be appreciated.