From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67571] New: BUG: unable to handle kernel paging in amd E350 hdmi init
Date: Mon, 23 Dec 2013 18:07:46 +0000 [thread overview]
Message-ID: <bug-67571-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=67571
Bug ID: 67571
Summary: BUG: unable to handle kernel paging in amd E350 hdmi
init
Product: Drivers
Version: 2.5
Kernel Version: 3.13.0-rc5
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: eric.valette@free.fr
Regression: No
Created attachment 119351
--> https://bugzilla.kernel.org/attachment.cgi?id=119351&action=edit
complete dmesg
Here is an extract of the dmeg log. We are several to be bitten by the same bug
as described here:
http://forum.xbmc.org/showthread.php?tid=174854&pid=1577781#pid1577781
[drm] Found smc ucode version: 0x00010200
[ 40.117359] BUG: unable to handle kernel paging request at ffffec2000000900
[ 40.117377] IP: [<ffffffff810a796f>] kfree+0x41/0xe2
[ 40.117396] PGD 0
[ 40.117404] Oops: 0000 [#1] PREEMPT SMP
[ 40.117413] Modules linked in: radeon cfbfillrect cfbimgblt cfbcopyarea
i2c_algo_bit backlight drm_kms_helper ttm drm fb fbdev
[ 40.117445] CPU: 1 PID: 3029 Comm: Xorg Not tainted 3.13.0-rc5 #6
[ 40.117454] Hardware name: To be filled by O.E.M. To be filled by
O.E.M./Inagua CRB, BIOS 4.6.4 06/15/2011
[ 40.117463] task: ffff88013ba5f2c0 ti: ffff88009d1ce000 task.ti:
ffff88009d1ce000
[ 40.117470] RIP: 0010:[<ffffffff810a796f>] [<ffffffff810a796f>]
kfree+0x41/0xe2
[ 40.117484] RSP: 0018:ffff88009d1cfa40 EFLAGS: 00010286
[ 40.117492] RAX: ffffea0000000000 RBX: 0000100000024414 RCX:
0000000000000000
[ 40.117499] RDX: 0000000000010005 RSI: 0000000000005f78 RDI:
0000100000024414
[ 40.117505] RBP: 0000000000000c00 R08: ffffec2000000900 R09:
0000000000000c00
[ 40.117512] R10: ffffffffa00a7da5 R11: ffffffffa00a7f08 R12:
ffff8800a2c01200
[ 40.117518] R13: ffff88013b298000 R14: 0000000000000000 R15:
ffff88013aaa6b00
[ 40.117526] FS: 00007f94df8fe980(0000) GS:ffff88013fd00000(0000)
knlGS:0000000000000000
[ 40.117533] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 40.117539] CR2: ffffec2000000900 CR3: 00000000a36e3000 CR4:
00000000000007e0
[ 40.117544] Stack:
[ 40.117549] ffff88013b298000 ffffffffa00f11e2 00007c44a00f62be
00007d2c00007c48
[ 40.117559] ffff8800a2c01200 0000000000000003 0000000000000000
ffffffffa01750b1
[ 40.117569] 0000100000024414 0000188000024414 0000180000028488
ffffffff00024414
[ 40.117579] Call Trace:
[ 40.117686] [<ffffffffa00f11e2>] ? evergreen_hdmi_setmode+0x3cc/0x7e1
[radeon]
[ 40.117705] [<ffffffffa0071732>] ? drm_crtc_helper_set_mode+0x30a/0x40a
[drm_kms_helper]
[ 40.117726] [<ffffffffa007248c>] ? drm_crtc_helper_set_config+0x5ff/0x842
[drm_kms_helper]
[ 40.117798] [<ffffffffa00b4392>] ? radeon_crtc_set_config+0x41/0xe8
[radeon]
[ 40.117843] [<ffffffffa001d3e7>] ? drm_mode_set_config_internal+0x44/0xac
[drm]
[ 40.117885] [<ffffffffa001f8cb>] ? drm_mode_setcrtc+0x3e8/0x499 [drm]
[ 40.117917] [<ffffffffa00148b3>] ? drm_ioctl+0x26f/0x394 [drm]
[ 40.117957] [<ffffffffa001f4e3>] ? drm_mode_setplane+0x335/0x335 [drm]
[ 40.118015] [<ffffffffa0096045>] ? radeon_drm_ioctl+0x45/0x77 [radeon]
[ 40.118028] [<ffffffff810b962a>] ? do_vfs_ioctl+0x356/0x421
[ 40.118039] [<ffffffff810b9743>] ? SyS_ioctl+0x4e/0x7b
[ 40.118054] [<ffffffff8147a322>] ? system_call_fastpath+0x16/0x1b
[ 40.118059] Code: 00 00 00 80 ff 77 00 00 49 01 f8 48 0f 42 05 b9 86 96 00
49 01 c0 48 b8 00 00 00 00 00 ea ff ff 49 c1 e8 0c 49 c1 e0 06 49 01 c0 <49> 8b
00 f6 c4 80 74 04 4d 8b 40 30 49 8b 00 a8 80 75 22 49 f7
[ 40.118149] RIP [<ffffffff810a796f>] kfree+0x41/0xe2
[ 40.118160] RSP <ffff88009d1cfa40>
[ 40.118165] CR2: ffffec2000000900
[ 40.118173] ---[ end trace e7d41f7cbae99794 ]---
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2013-12-23 18:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 18:07 bugzilla-daemon [this message]
2013-12-23 18:08 ` [Bug 67571] BUG: unable to handle kernel paging in amd E350 hdmi init bugzilla-daemon
2013-12-23 18:15 ` bugzilla-daemon
2013-12-23 18:19 ` bugzilla-daemon
2013-12-23 18:33 ` bugzilla-daemon
2013-12-23 18:42 ` bugzilla-daemon
2013-12-23 18:47 ` bugzilla-daemon
2013-12-23 18:47 ` bugzilla-daemon
2013-12-23 18:50 ` bugzilla-daemon
2013-12-24 9:38 ` bugzilla-daemon
2013-12-24 16:17 ` bugzilla-daemon
2013-12-24 19:12 ` bugzilla-daemon
2013-12-24 20:34 ` bugzilla-daemon
2013-12-24 20:38 ` bugzilla-daemon
2013-12-24 20:39 ` bugzilla-daemon
2013-12-24 20:52 ` bugzilla-daemon
2013-12-24 20:54 ` bugzilla-daemon
2013-12-25 10:31 ` bugzilla-daemon
2013-12-25 10:32 ` bugzilla-daemon
2014-02-01 15:15 ` [Bug 67571] BUG: amd E350 GPU hangs when loading uvd image 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-67571-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;
as well as URLs for NNTP newsgroup(s).