Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 342205

Summary: PPC-Kernel: ATI Radeon 9000: Corrupt output and system crash
Product: Gentoo Linux Reporter: Johannes Geiss <johannes.geiss>
Component: [OLD] Core systemAssignee: Gentoo X packagers <x11>
Status: RESOLVED UPSTREAM    
Severity: normal CC: ppc
Priority: High    
Version: unspecified   
Hardware: PPC   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: Corrupt output of glxgears (Speed seems to be OK, but there are no gears visible, only some lines for some milliseconds)
Corrupt output of blender
Here is the Xorg log.
The dmesg log.
The syslog. I found a crach at 06:42:15.
Wrong colours while SW rendering

Description Johannes Geiss 2010-10-22 15:28:16 UTC
The kernel for PowerPC (G4) linux-2.6.34-gentoo-r1 shows corrupt hardware accelerated graphics and crashes often the system while resizing a window (e.g. xterm console with fvwm). At least th Screen goes black and no Ctrl-Alt-Fn works. Only reboot via Alt-S-Req-r/s/u/b.

Kernel version linux-2.6.33-gentoo-r2 works fine.

The graphics card is VGA compatible controller: ATI Technologies Inc Radeon RV250 If [Radeon 9000] (rev 01).
Comment 1 Johannes Geiss 2010-10-22 15:29:56 UTC
Created attachment 251597 [details]
Corrupt output of glxgears (Speed seems to be OK, but there are no gears visible, only some lines for some milliseconds)
Comment 2 Johannes Geiss 2010-10-22 15:31:02 UTC
Created attachment 251599 [details]
Corrupt output of blender
Comment 3 Chí-Thanh Christopher Nguyễn gentoo-dev 2010-10-23 07:57:21 UTC
Please also post dmesg and Xorg.0.log.
Are you still able to reach the computer with ping/ssh?
Comment 4 Johannes Geiss 2010-10-23 11:12:45 UTC
Created attachment 251675 [details]
Here is the Xorg log.
Comment 5 Johannes Geiss 2010-10-23 11:13:39 UTC
Created attachment 251677 [details]
The dmesg log.
Comment 6 Johannes Geiss 2010-10-23 11:17:22 UTC
Created attachment 251679 [details]
The syslog. I found a crach at 06:42:15.
Comment 7 Johannes Geiss 2010-10-23 11:21:30 UTC
(In reply to comment #3)
> Are you still able to reach the computer with ping/ssh?

I haven't tried yet. But if you need to know, just say it and I will test this scenario again.

For now I have added dmesg, Xorg.0.log and syslog. Maybe these help.
Comment 8 Johannes Geiss 2010-10-23 11:36:40 UTC
I forgot to mention, that I always patch include/drm/drmP.h:

diff -Naur linux/include/drm/drmP.h polaris/include/drm/drmP.h
--- linux/include/drm/drmP.h    2010-08-31 07:55:28.000000000 +0200
+++ polaris/include/drm/drmP.h  2010-08-31 08:01:41.000000000 +0200
@@ -1074,7 +1074,7 @@
 #ifdef __alpha__
 #define drm_get_pci_domain(dev) dev->hose->index
 #else
-#define drm_get_pci_domain(dev) 0
+#define drm_get_pci_domain(dev) 1
 #endif
 
 #if __OS_HAS_AGP

I change the drm_get_pci_domain(dev) 0 to 1 because my only one graphics card lies in domain 1 and hardware acceleration wouldn't work otherwise:

0001:01:08.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 If [Radeon 9000] (rev 01)

I do this for a long time whenever I compile a new kernel but I don't think it has much to do with this bug because if I would leave it to 0 hardware acceleration would not work at all and older kernel versions all worked.
Comment 9 Chí-Thanh Christopher Nguyễn gentoo-dev 2010-10-31 18:19:18 UTC
You are using radeonfb. This is not compatible with recent X and mesa.

Use KMS instead of radeonfb if you can.
Comment 10 Johannes Geiss 2010-11-08 11:37:13 UTC
Created attachment 253615 [details]
Wrong colours while SW rendering

I used KMS (i.e. I removed /etx/X11/xorg.conf). It worked, but I had no HW accelleration at all. Even if I remove the patch (see Comment #8). In xorg.conf is nothing except the Driver "radeon" and BusOption "PCI".

Furthermore the SW rendered graphics have wrong colours. See attachement "glxgears2.png".
Comment 11 Matt Turner gentoo-dev 2015-02-22 02:13:15 UTC
There's not really anything Gentoo developers can do to solve this. Please file a bug upstream https://bugs.freedesktop.org/enter_bug.cgi?product=DRI if the problem persists.