From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92891] New: Maschine hangs forever at loading the radeon module
Date: Sat, 07 Feb 2015 10:42:27 +0000 [thread overview]
Message-ID: <bug-92891-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=92891
Bug ID: 92891
Summary: Maschine hangs forever at loading the radeon module
Product: Drivers
Version: 2.5
Kernel Version: v3.14.31-rt28 /
e1a0d6d8b023c54a5677310e68222e7a58b11f91 /
linux-stable-rt
Hardware: All
OS: Linux
Tree: PREEMPT_RT
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: georg@schorsch-tech.de
Regression: No
Created attachment 166041
--> https://bugzilla.kernel.org/attachment.cgi?id=166041&action=edit
Kernel config
Hi all,
recently i changed my Gfx card from a evergreen/hd5770 to a pitcairn/r290
(Chipset: "PITCAIRN" (ChipID = 0x6811)).
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Curacao PRO [Radeon R9 270] [1002:6811]
On a second partition a realtime system without any problems. The system ran
for a year with the kernel 3.10.20-rt17 perfect fine.
Now as i updated my hardware with the new gfx card i started the RT system, i
assumed the problem is the gfx card driver. I updated the kernel to the latest
in
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git . The
first try was v3.14.31-rt28. But it froze like the old (v3.10.20-rt17) kernel.
After some testing i found out that the old (3.10) and the new (3.14) kernel
start the machine when i disable KMS (radeon.modeset = 0).
The exact point in the startup procedure is "Waiting for uevents". At this
stage udev get started and loads the modules.
After testing various kernel versions i picked 3.14.31-rt28 this did start the
machine without the commandline "radeon.modeset=0" and i thought i have a
working commit, but X did not start and i tried to load the module manually. At
this point (modprobe radeon) the machine froze again.
I attached the old evergreen card in the machine and tested with this card what
configuration runs. I got the following results:
Evergreen:
v3.10.20-rt17 Ok
v3.14.20-rt17 Not Ok (freeze)
Pitcairn:
v3.10.20-rt17 Not Ok (freeze)
v3.14.20-rt17 Not Ok (freeze)
So i just filled this bugreport against the newest version i tried.
What info should i add?
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-02-07 10:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 10:42 bugzilla-daemon [this message]
2015-02-07 10:43 ` [Bug 92891] Maschine hangs forever at loading the radeon module bugzilla-daemon
2015-02-07 10:45 ` bugzilla-daemon
2015-02-09 15:29 ` bugzilla-daemon
2015-02-09 17:59 ` bugzilla-daemon
2015-02-09 18:00 ` bugzilla-daemon
2015-02-09 18:01 ` bugzilla-daemon
2015-02-09 18:03 ` bugzilla-daemon
2015-02-09 19:29 ` bugzilla-daemon
2015-02-09 19:59 ` bugzilla-daemon
2015-02-09 20:02 ` bugzilla-daemon
2015-02-09 20:03 ` bugzilla-daemon
2015-02-11 18:00 ` bugzilla-daemon
2015-02-11 18:02 ` bugzilla-daemon
2015-02-11 18:24 ` bugzilla-daemon
2015-02-11 19:58 ` bugzilla-daemon
2015-02-11 20:05 ` bugzilla-daemon
2015-02-11 20:11 ` 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-92891-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.