From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 35192] New: BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300]
Date: Mon, 16 May 2011 00:02:46 GMT [thread overview]
Message-ID: <bug-35192-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=35192
URL: http://bugs.gentoo.org/show_bug.cgi?id=359281
Summary: BUG() in radeon driver with ATI Technologies Inc RV515
[Radeon X1300]
Product: Drivers
Version: 2.5
Kernel Version: 2.6.37 and 2.6.38
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: blueness@gentoo.org
Regression: Yes
A regression in kernels 2.6.37 up to 2.6.38.6 hits a BUG() in the radeon driver
with the following hardware (as reported by lspci -kv)
02:00.0 VGA compatible controller: ATI Technologies Inc RV515 [Radeon X1300]
(prog-if 00 [VGA controller])
Subsystem: ATI Technologies Inc All-in-Wonder 2006 PCI-E Edition
Flags: bus master, fast devsel, latency 0, IRQ 40
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at fd9f0000 (64-bit, non-prefetchable) [size=64K]
I/O ports at ce00 [size=256]
Expansion ROM at fd9c0000 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Express Endpoint, MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: radeon
The BUG() is
kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
BUG: unable to handle kernel paging request at ffffffff81c0e711
IP: [<ffffffff81c0e711>] platform_device_register_resndata+0x0/0x8c
PGD 1ae5067 PUD 1ae9063 PMD 3c473063 PTE 8000000001c0e163
Oops: 0011 [#1] SMP
last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map
CPU 0
Pid: 1627, comm: X Tainted: G W 2.6.38.6 #1 HP Pavilion 061
ER900AA-ABA a1430n/NAGAMI
RIP: 0010:[<ffffffff81c0e711>] [<ffffffff81c0e711>]
platform_device_register_resndata+0x0/0x8c
RSP: 0018:ffff88003a2b3d30 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff88003cb81000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff81a41cbb RDI: 0000000000000000
RBP: ffff88003a2b3d88 R08: 0000000000000000 R09: 0000000000000000
R10: ffff88003a340000 R11: 00000000effff000 R12: 0000000000000000
R13: ffff88003cb80800 R14: ffff88003abeaa80 R15: 0000000000000001
FS: 00007f40b4c72880(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffff81c0e711 CR3: 000000003a2a8000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process X (pid: 1627, threadinfo ffff88003a2b2000, task ffff88003d3ef1a0)
Stack:
ffffffff8133aa29 0000000000000000 0000000000000001 ffff88003a2b3de8
ffffffff811681fc ffff88003a2b3df8 ffff88003abeaa80 ffff88003cb80800
0000000000000040 0000000040786440 0000000000000078 ffff88003a2b3ea8
Call Trace:
[<ffffffff8133aa29>] ? radeon_cp_init+0xd79/0x1180
[<ffffffff811681fc>] ? ext4_file_write+0x6c/0x2a0
[<ffffffff81317439>] drm_ioctl+0x389/0x4d0
[<ffffffff81339cb0>] ? radeon_cp_init+0x0/0x1180
[<ffffffff8110ddfb>] do_vfs_ioctl+0x9b/0x510
[<ffffffff8110e2bf>] sys_ioctl+0x4f/0x80
[<ffffffff81002e2b>] system_call_fastpath+0x16/0x1b
Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
RIP [<ffffffff81c0e711>] platform_device_register_resndata+0x0/0x8c
RSP <ffff88003a2b3d30>
CR2: ffffffff81c0e711
---[ end trace f569524e57c84b79 ]---
More detail is avaiable in the following gentoo bug:
http://bugs.gentoo.org/show_bug.cgi?id=359281
We're looking into doing the git-bisect now.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next reply other threads:[~2011-05-16 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 0:02 bugzilla-daemon [this message]
2011-05-16 23:38 ` [Bug 35192] BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300] bugzilla-daemon
2011-05-18 21:53 ` bugzilla-daemon
2011-05-18 22:56 ` bugzilla-daemon
2011-05-18 22:58 ` bugzilla-daemon
2011-05-19 14:05 ` bugzilla-daemon
2011-05-19 18:16 ` bugzilla-daemon
2011-07-05 10:31 ` bugzilla-daemon
2012-06-13 15:05 ` bugzilla-daemon
2012-06-13 15:06 ` 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-35192-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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.