From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105711] New: amdgpu: no monitor signal and kernel panic
Date: Fri, 09 Oct 2015 17:49:31 +0000 [thread overview]
Message-ID: <bug-105711-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=105711
Bug ID: 105711
Summary: amdgpu: no monitor signal and kernel panic
Product: Drivers
Version: 2.5
Kernel Version: 4.3-rc4
Hardware: x86-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: polynomial-c@gmx.de
Regression: No
Created attachment 189801
--> https://bugzilla.kernel.org/attachment.cgi?id=189801&action=edit
kernel dmesg output
As soon as the driver gets loaded the monitor looses the signal and doesn't get
it back. After a while the kernel panics so even network connections get lost:
[ 751.713493] Task dump for CPU 7:
[ 751.713496] modprobe R running task 0 2994 2968 0x0000000a
[ 751.713506] ffff88063a72ae00 ffffffff818809f9 ffff88063a72ae00
0000000000000007
[ 751.713513] ffff88063a72ae00 0000000000000000 ffff8800a6658000
00000000ffffffff
[ 751.713519] 0000000000000000 ffff8800a6658000 ffff880634b20000
ffffffff818814b2
[ 751.713525] Call Trace:
[ 751.713532] [<ffffffff818809f9>] ? 0xffffffff818809f9
[ 751.713536] [<ffffffff818814b2>] ? 0xffffffff818814b2
[ 751.713539] [<ffffffff81885180>] ? 0xffffffff81885180
[ 751.713543] [<ffffffffa00232ca>] ? 0xffffffffa00232ca
[ 751.713547] [<ffffffff814f6c8c>] ? 0xffffffff814f6c8c
[ 751.713550] [<ffffffffa005933c>] ? 0xffffffffa005933c
[ 751.713553] [<ffffffffa005c69e>] ? 0xffffffffa005c69e
[ 751.713557] [<ffffffffa0018cba>] ? 0xffffffffa0018cba
[ 751.713560] [<ffffffffa001a5c1>] ? 0xffffffffa001a5c1
[ 751.713563] [<ffffffff815c7893>] ? 0xffffffff815c7893
[ 751.713566] [<ffffffff815c9589>] ? 0xffffffff815c9589
[ 751.713569] [<ffffffff81526b58>] ? 0xffffffff81526b58
[ 751.713572] [<ffffffff81526abf>] ? 0xffffffff81526abf
[ 751.713575] [<ffffffff81527193>] ? 0xffffffff81527193
[ 751.713578] [<ffffffff815e4334>] ? 0xffffffff815e4334
[ 751.713581] [<ffffffff815e458d>] ? 0xffffffff815e458d
[ 751.713584] [<ffffffff815e4500>] ? 0xffffffff815e4500
[ 751.713586] [<ffffffff815e2585>] ? 0xffffffff815e2585
[ 751.713589] [<ffffffff815e3af1>] ? 0xffffffff815e3af1
[ 751.713592] [<ffffffffa0088000>] ? 0xffffffffa0088000
[ 751.713595] [<ffffffff815e4b42>] ? 0xffffffff815e4b42
[ 751.713598] [<ffffffffa0088000>] ? 0xffffffffa0088000
[ 751.713601] [<ffffffff8100036b>] ? 0xffffffff8100036b
[ 751.713604] [<ffffffff8113065c>] ? 0xffffffff8113065c
[ 751.713607] [<ffffffff810fb8d4>] ? 0xffffffff810fb8d4
[ 751.713610] [<ffffffff810f94d0>] ? 0xffffffff810f94d0
[ 751.713615] [<ffffffff810fbe42>] ? 0xffffffff810fbe42
[ 751.713618] [<ffffffff81884697>] ? 0xffffffff81884697
[ 751.713626] rcu_preempt kthread starved for 24577 jiffies! g2247 c2246 f0x0
s3 ->state=0x0
Same problem happens with vanilla kernel-4.2.3
--
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-10-09 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 17:49 bugzilla-daemon [this message]
2015-10-09 17:52 ` [Bug 105711] amdgpu: no monitor signal and kernel panic bugzilla-daemon
2015-10-09 17:54 ` bugzilla-daemon
2016-03-19 10:43 ` [Bug 105711] amdgpu: no monitor signal (modprobe amdgpu fails) bugzilla-daemon
2016-03-19 10:46 ` bugzilla-daemon
2016-03-19 10:48 ` bugzilla-daemon
2016-03-19 10:49 ` bugzilla-daemon
2016-03-21 12:02 ` bugzilla-daemon
2016-05-09 3: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-105711-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