https://bugzilla.kernel.org/show_bug.cgi?id=30812
Summary: radeon module fails to initialize with modeset=1 on PPC32 with RV280 Product: Drivers Version: 2.5 Kernel Version: 2.6.35 to 2.6.38-rc6 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri@kernel-bugs.osdl.org ReportedBy: bugzilla_kernel_org@nguyen.vg Regression: No
Created an attachment (id=50462) --> (https://bugzilla.kernel.org/attachment.cgi?id=50462) output of dmesg after boot (radeon as module, modeset=0) and rmmod of radeon
Hardware: MacMini G4 (ppc-32). Graphic adaptor: Radeon 9200 (RV280) probably a 'mac' version. Symptoms:
with modprobe radeon modeset=0, everything works fine. Machine boots normally, X works, xrandr and Xv too.
with modeset=1, modeprobe never returns and gets stucked durring initialization. More specifically, the call to radeon_fence_wait in r100_ib_test (r100.c) loops endlessly (or at least for several hours). I'm attaching dmesg of a modified driver with more printk.
I have tried several combination of putting AGPART/FBCON/RADEON in kernel or as modules, tried with and without OFFB and so on, same results. Also attaching output of lspci and .config used for the dmesg trace and output of radeontool regs '*'.
https://bugzilla.kernel.org/show_bug.cgi?id=30812
--- Comment #1 from Kim Nguyen bugzilla_kernel_org@nguyen.vg 2011-03-09 13:59:27 --- Created an attachment (id=50472) --> (https://bugzilla.kernel.org/attachment.cgi?id=50472) dmesg of modified module after insmod radeon.ko modeset=1
https://bugzilla.kernel.org/show_bug.cgi?id=30812
--- Comment #2 from Kim Nguyen bugzilla_kernel_org@nguyen.vg 2011-03-09 13:59:54 --- Created an attachment (id=50482) --> (https://bugzilla.kernel.org/attachment.cgi?id=50482) output of radeontool regs '*'
https://bugzilla.kernel.org/show_bug.cgi?id=30812
--- Comment #3 from Kim Nguyen bugzilla_kernel_org@nguyen.vg 2011-03-09 14:00:22 --- Created an attachment (id=50492) --> (https://bugzilla.kernel.org/attachment.cgi?id=50492) output of lspci -vvv
https://bugzilla.kernel.org/show_bug.cgi?id=30812
--- Comment #4 from Kim Nguyen bugzilla_kernel_org@nguyen.vg 2011-03-09 14:01:06 --- Created an attachment (id=50502) --> (https://bugzilla.kernel.org/attachment.cgi?id=50502) .config used for dmesg
https://bugzilla.kernel.org/show_bug.cgi?id=30812
--- Comment #5 from Kim Nguyen bugzilla_kernel_org@nguyen.vg 2011-03-09 14:13:38 --- Created an attachment (id=50512) --> (https://bugzilla.kernel.org/attachment.cgi?id=50512) modified radeon_fence.c with additional DRM_INFO added.
https://bugzilla.kernel.org/show_bug.cgi?id=30812
--- Comment #6 from Kim Nguyen bugzilla_kernel_org@nguyen.vg 2011-03-09 14:28:03 --- Actually after trying again with 2.6.35 I get an oops after modprobe radeon modeset=1 which does is not present in 2.6.36 and after. dmesg attached.
https://bugzilla.kernel.org/show_bug.cgi?id=30812
--- Comment #7 from Kim Nguyen bugzilla_kernel_org@nguyen.vg 2011-03-09 14:29:08 --- Created an attachment (id=50522) --> (https://bugzilla.kernel.org/attachment.cgi?id=50522) dmsg after segfault of modprobe radeon modeset=1 on 2.6.35
https://bugzilla.kernel.org/show_bug.cgi?id=30812
--- Comment #8 from Michel Dänzer michel@daenzer.net 2011-03-09 14:42:27 --- Have you tried radeon.agpmode=1 or radeon.agpmode=-1? There's a uninorth AGP driver issue which prevents higher AGP transfer rates from working reliably with KMS.
Actually, I see you mentioned on IRC that you tried radeon.agpmode=-1 but it didn't help. Can you provide the corresponding dmesg output? Maybe for =1 as well.
One thing that seems special about your card is that the PCI aperture is larger than VRAM. Maybe there's a problem related to that, e.g. a mixup or incorrect handling of the various *_vram_size fields.
https://bugzilla.kernel.org/show_bug.cgi?id=30812
--- Comment #9 from Kim Nguyen bugzilla_kernel_org@nguyen.vg 2011-03-09 15:32:53 --- radeon.agpmode=1 works! Seems X is happy too, glxinfo shows direct rendering. actually agpmode=-1 or agpmode > 1 both trigger the bug.
Would it be easy to default to 1 if uninorth agp is detected ? (maybe not worth it, there are not so many ppc32 configs out there. So it might just be enough to advertise on the radeon faq/howto page that agpmode=1 is recommended for uninorth agp).
https://bugzilla.kernel.org/show_bug.cgi?id=30812
Alan alan@lxorguk.ukuu.org.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |alan@lxorguk.ukuu.org.uk Resolution| |OBSOLETE
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠bugzilla.kernel.org