From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 80901] New: [radeon] loading corrupts lspci entry + unloading crashes kernel
Date: Tue, 22 Jul 2014 14:00:38 +0000 [thread overview]
Message-ID: <bug-80901-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=80901
Bug ID: 80901
Summary: [radeon] loading corrupts lspci entry + unloading
crashes kernel
Product: Drivers
Version: 2.5
Kernel Version: 3.16.0
Hardware: IA-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: amerryfellow@gmail.com
Regression: No
Created attachment 143901
--> https://bugzilla.kernel.org/attachment.cgi?id=143901&action=edit
lspci w/ radeon
Hi all. I've been searching the internet for quite a while now, but couldn't
find any solution to my problem. I currently am on a laptop Dell Inspiron 15R
SE, with a i7 3632QM cpu ( which embeds a i915 intel card ) and a discrete
AMD/ATI Radeon HD 773M.
I know this kind of hybrid graphics setup's support is getting better more
recently, but I still am facing some problems with the open source driver.
The main problem is that, I don't really know if ( with PRIME ) my card is
working at all. This is because when I tried the tool radeontop, it couldn't
find my card. This is due, I suspect, to the fact that whenever I load my
"radeon" module, I think it messes up the device. This seems confirmed by the
fact that I get a clean lspci -vvv when the module is unloaded, and a "unknown
header type 7f" when the module is loaded. See attachments please.
Also, it takes a few seconds to load the module itself, and when I unload it (
modprobe -r radeon ) it crashes my machine, right after a few seconds. The
system log shows a dereference problem, but "live" I can only see the stack
trace the kernel outputs and nothing more.
Steps to Reproduce:
modprobe radeon
modprobe -r radeon
Actual Results:
Radeon's LSPCI entry is messed up and card is not recognized by tools. On
unloading, crashes.
Expected Results:
Radeon's LSPCI entry is ok, radeon card is recognized and on unloading,
nothing.
Build Date & Hardware:
Laptop Dell Inspiron 15R SE
Intel i7 3632QM
AMD Radeon HD 7730M Cape Verde
Software:
Arch Linux
Custom Kernel 3.16.0-rc6
Xorg-server 1.16.0-2
xf86-video-intel 2.99.912-4
xf86-video-ati 1:7.4.0-3
Additional Builds and Platforms:
Problem encountered also with stock kernel config and with kernel version 3.13.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-07-22 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 14:00 bugzilla-daemon [this message]
2014-07-22 14:02 ` [Bug 80901] [radeon] loading corrupts lspci entry + unloading crashes kernel bugzilla-daemon
2014-07-22 14:04 ` bugzilla-daemon
2014-07-22 14:05 ` bugzilla-daemon
2014-07-22 14:05 ` bugzilla-daemon
2014-07-22 14:05 ` bugzilla-daemon
2014-07-22 14:29 ` bugzilla-daemon
2014-07-22 14:36 ` bugzilla-daemon
2014-07-22 14:37 ` bugzilla-daemon
2014-07-22 16:13 ` bugzilla-daemon
2014-07-22 18:00 ` bugzilla-daemon
2014-07-22 18:30 ` bugzilla-daemon
2014-07-22 18:41 ` bugzilla-daemon
2014-07-22 20:57 ` bugzilla-daemon
2014-07-22 22:22 ` 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-80901-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.