From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 28622] New: radeon video lookup
Date: Tue, 8 Feb 2011 17:48:23 GMT [thread overview]
Message-ID: <bug-28622-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=28622
Summary: radeon video lookup
Product: Drivers
Version: 2.5
Kernel Version: 2.6.37
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: bugzilla.kernel.org@poelzi.org
Regression: No
Radeon got very unstable from 2.6.36 to 2.6.37 on my system. This is at least
one lockup I'm having when swtiching X Servers. KMS is enabled. Disable KMS
will crash video in like 30-300 seconds.
[81121.199055] INFO: task Xorg:1791 blocked for more than 120 seconds.
[81121.199059] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[81121.199061] Xorg D ffff8801261549d8 0 1791 1743 0x00400004
[81121.199066] ffff880123b4bb78 0000000000000082 ffff880123b4bd70
0000000000000000
[81121.199069] 00000000000139c0 ffff880126154640 ffff8801261549d8
ffff880123b4bfd8
[81121.199072] ffff8801261549e0 00000000000139c0 ffff880123b4a010
00000000000139c0
[81121.199076] Call Trace:
[81121.199083] [<ffffffff8115e687>] ? inode_init_always+0x1c7/0x1d0
[81121.199088] [<ffffffff815671e7>] __mutex_lock_slowpath+0xf7/0x180
[81121.199091] [<ffffffff815670cb>] mutex_lock+0x2b/0x50
[81121.199127] [<ffffffffa0157924>] radeon_bo_create+0x114/0x2c0 [radeon]
[81121.199146] [<ffffffffa016d30b>] radeon_gem_object_create+0x8b/0x110
[radeon]
[81121.199163] [<ffffffffa016d3e8>] radeon_gem_create_ioctl+0x58/0xd0 [radeon]
[81121.199180] [<ffffffffa00458d3>] drm_ioctl+0x433/0x4f0 [drm]
[81121.199198] [<ffffffffa016d390>] ? radeon_gem_create_ioctl+0x0/0xd0
[radeon]
[81121.199202] [<ffffffff81157a29>] do_vfs_ioctl+0xa9/0x5a0
[81121.199205] [<ffffffff81157fa1>] sys_ioctl+0x81/0xa0
[81121.199209] [<ffffffff8100b002>] system_call_fastpath+0x16/0x1b
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
--
next reply other threads:[~2011-02-08 17:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 17:48 bugzilla-daemon [this message]
2011-02-08 17:48 ` [Bug 28622] radeon video lockup bugzilla-daemon
2011-02-08 18:00 ` bugzilla-daemon
2011-02-08 18:24 ` bugzilla-daemon
2011-02-08 18:28 ` bugzilla-daemon
2011-02-08 19:05 ` bugzilla-daemon
2011-02-08 20:59 ` bugzilla-daemon
2011-02-13 10:56 ` bugzilla-daemon
2011-02-13 22:20 ` bugzilla-daemon
2011-03-13 19:13 ` bugzilla-daemon
2011-03-29 21:13 ` bugzilla-daemon
2011-06-04 0:34 ` bugzilla-daemon
2011-06-04 0:36 ` bugzilla-daemon
2012-07-02 13:51 ` bugzilla-daemon
2012-07-02 20:21 ` bugzilla-daemon
2012-11-20 16:58 ` 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-28622-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.