From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 30812] New: radeon module fails to initialize with modeset=1 on PPC32 with RV280
Date: Wed, 9 Mar 2011 13:58:45 GMT [thread overview]
Message-ID: <bug-30812-2300@https.bugzilla.kernel.org/> (raw)
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 '*'.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next reply other threads:[~2011-03-09 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 13:58 bugzilla-daemon [this message]
2011-03-09 13:59 ` [Bug 30812] radeon module fails to initialize with modeset=1 on PPC32 with RV280 bugzilla-daemon
2011-03-09 13:59 ` bugzilla-daemon
2011-03-09 14:00 ` bugzilla-daemon
2011-03-09 14:01 ` bugzilla-daemon
2011-03-09 14:13 ` bugzilla-daemon
2011-03-09 14:28 ` bugzilla-daemon
2011-03-09 14:29 ` bugzilla-daemon
2011-03-09 14:42 ` bugzilla-daemon
2011-03-09 15:32 ` bugzilla-daemon
2012-08-20 14:50 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-30812-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.