From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73901] New: Kernel crash after modprobe radeon runpm=1
Date: Sat, 12 Apr 2014 18:44:19 +0000 [thread overview]
Message-ID: <bug-73901-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=73901
Bug ID: 73901
Summary: Kernel crash after modprobe radeon runpm=1
Product: Drivers
Version: 2.5
Kernel Version: 3.14
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: pali.rohar@gmail.com
Regression: No
After modprobing radeon driver with runpm=1 notebook display panel output is
immediatelly black (probably turned off) and after one or two seconds kernel
freeze/crash (sysrq not working too). I was able to dump & sync syslog kernel
output before freeze (called sync command in infinite loop on background). See
attachment where is log from syslog daemon after modprobing radeon kernel
module (with runpm=1). I'm not able to provide any other debug output as
display is off and kernel crashing... Problem is reproducable always on
notebook Dell Latitude E6440 which have muxless AMD Radeon HD 8690M graphic
card.
Black screen is probably caused by intel driver at line:
[ 171.913779] i915: switched off
And kernel crash by NULL derefence:
[ 173.442690] BUG: unable to handle kernel NULL pointer dereference at
0000000000000008
My AMD graphics card is identified by lspci -nn as:
01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun
XT [Radeon HD 8670A/8670M/8690M] [1002:6660]
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-04-12 18:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 18:44 bugzilla-daemon [this message]
2014-04-12 18:44 ` [Bug 73901] Kernel crash after modprobe radeon runpm=1 bugzilla-daemon
2014-04-12 18:45 ` bugzilla-daemon
2014-04-14 14:18 ` bugzilla-daemon
2014-04-14 15:28 ` bugzilla-daemon
2014-04-14 15:28 ` bugzilla-daemon
2014-04-14 16:57 ` bugzilla-daemon
2014-04-14 17:21 ` bugzilla-daemon
2014-04-14 17:22 ` bugzilla-daemon
2014-04-14 17:25 ` bugzilla-daemon
2014-04-14 17:31 ` bugzilla-daemon
2014-04-14 22:15 ` bugzilla-daemon
2014-04-14 23:06 ` bugzilla-daemon
2014-04-14 23:07 ` bugzilla-daemon
2014-04-15 8:02 ` bugzilla-daemon
2014-04-15 8:07 ` bugzilla-daemon
2014-04-15 13:22 ` bugzilla-daemon
2014-04-20 20:53 ` bugzilla-daemon
2014-04-22 20:12 ` bugzilla-daemon
2014-07-12 21:36 ` 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-73901-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox