From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28671] New: Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
Date: Tue, 22 Jun 2010 09:44:22 -0700 (PDT) [thread overview]
Message-ID: <bug-28671-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=28671
Summary: Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC
ATI Radeon AGP r420 JH.
Product: DRI
Version: unspecified
Platform: PowerPC
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: brett.witherspoon@comcast.net
Created an attachment (id=36419)
--> (https://bugs.freedesktop.org/attachment.cgi?id=36419)
Dmesg with call trace.
Mentioned on #radeon:
Hello, I have recently adopted a PowerMac G5 (machine7,3 circa 2003-04) with a
ATI Radeon x800 XT Mac edition (AGP chipset R420 JH). When attempting to use
the new KMS Radeon drivers (kernel v. 2.4.34) I get a seg. fault and kernel
Oops. I am using PPC gentoo linux with 64bit kernel and 32bit userland. I have
collected the call trace that is given after inserting the module with
modesetting enabled. Attached is my entire dmesg with the call trace at the
bottom. Inserting the module was done via SSH with no other fb or video drivers
enabled in the kernel.
Let me know if I can provide any additional information that would be useful
and I am happy to do any testing.
Thanks,
B. Witherspoon
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-06-22 16:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 16:44 bugzilla-daemon [this message]
2010-06-22 17:04 ` [Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH bugzilla-daemon
2010-06-22 17:05 ` bugzilla-daemon
2010-06-22 19:30 ` bugzilla-daemon
2010-06-22 19:32 ` bugzilla-daemon
2010-06-22 19:36 ` bugzilla-daemon
2010-06-22 20:24 ` bugzilla-daemon
2010-06-22 20:39 ` bugzilla-daemon
2010-06-22 20:42 ` bugzilla-daemon
2010-06-23 0:12 ` bugzilla-daemon
2010-06-23 0:17 ` bugzilla-daemon
2010-06-23 0:17 ` bugzilla-daemon
2010-06-23 5:51 ` bugzilla-daemon
2010-06-23 6:04 ` bugzilla-daemon
2010-06-23 20:19 ` bugzilla-daemon
2010-06-25 20:58 ` bugzilla-daemon
2010-06-25 21:02 ` bugzilla-daemon
2010-06-26 20:03 ` bugzilla-daemon
2010-06-26 21:47 ` bugzilla-daemon
2010-06-26 21:53 ` bugzilla-daemon
2010-06-27 1:47 ` bugzilla-daemon
2010-06-27 22:35 ` bugzilla-daemon
2010-06-27 23:46 ` bugzilla-daemon
2010-06-28 0:14 ` bugzilla-daemon
2010-06-28 0:16 ` bugzilla-daemon
2010-06-28 0:32 ` bugzilla-daemon
2010-06-28 5:45 ` bugzilla-daemon
2010-06-28 5:49 ` bugzilla-daemon
2010-06-28 5:50 ` bugzilla-daemon
2010-06-28 20:51 ` bugzilla-daemon
2010-06-28 21:09 ` bugzilla-daemon
2010-07-19 17:14 ` bugzilla-daemon
2010-07-22 0:05 ` bugzilla-daemon
2010-07-22 0:05 ` bugzilla-daemon
2010-09-05 3:39 ` bugzilla-daemon
2010-09-07 18:43 ` bugzilla-daemon
2010-09-13 19:12 ` 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-28671-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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.