From: Jiri Slaby <jirislaby@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Jiri Slaby <jirislaby@gmail.com>,
airlied@linux.ie, eric@anholt.net, keithp@keithp.com,
dri-devel@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: i915 X lockup
Date: Fri, 27 Feb 2009 11:12:25 +0100 [thread overview]
Message-ID: <49A7BC89.6040407@gmail.com> (raw)
In-Reply-To: <1235728867.24401.82.camel@laptop>
On 27.2.2009 11:01, Peter Zijlstra wrote:
> would be good to have sysrq-w output
There was nothing but events. So this is rather an intel driver
userspace bug?
SysRq : Show Blocked State
task PC stack pid father
events/1 D 0000000000000000 0 11 2
ffff8801cb231da0 0000000000000046 ffff8801cb231d00 ffffffff80231ef8
0000003800000010 0000000000010180 ffff880028053840 ffff880028057180
ffff8801cb20c790 ffff8801cb20ca38 00000001ca3f90e8 00000000ffff7a0e
Call Trace:
[<ffffffff80231ef8>] ? dequeue_entity+0x18/0x1a0
[<ffffffff80230b50>] ? dequeue_task+0xb0/0xf0
[<ffffffff805fca2a>] __mutex_lock_slowpath+0xea/0x170
[<ffffffff803f60a0>] ? i915_gem_retire_work_handler+0x0/0x90
[<ffffffff805fc6f6>] mutex_lock+0x26/0x50
[<ffffffff803f60d8>] i915_gem_retire_work_handler+0x38/0x90
[<ffffffff80250792>] worker_thread+0x172/0x250
[<ffffffff80254da0>] ? autoremove_wake_function+0x0/0x40
[<ffffffff80250620>] ? worker_thread+0x0/0x250
[<ffffffff802549be>] kthread+0x9e/0xb0
[<ffffffff8020d3da>] child_rip+0xa/0x20
[<ffffffff80254920>] ? kthread+0x0/0xb0
[<ffffffff8020d3d0>] ? child_rip+0x0/0x20
next prev parent reply other threads:[~2009-02-27 10:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 9:28 i915 X lockup Jiri Slaby
2009-02-27 10:01 ` Peter Zijlstra
2009-02-27 10:12 ` Jiri Slaby [this message]
2009-02-27 10:14 ` Jiri Slaby
2009-02-27 10:32 ` Andrew Morton
2009-02-27 13:04 ` Sitsofe Wheeler
2009-02-27 13:49 ` Jiri Slaby
2009-02-27 23:12 ` Sitsofe Wheeler
2009-02-28 0:20 ` Eric Anholt
2009-02-28 8:31 ` Jiri Slaby
2009-02-28 8:47 ` Andrew Morton
2009-02-28 9:00 ` Eric Anholt
2009-02-28 18:24 ` Bruno Prémont
2009-02-28 19:57 ` Eric Anholt
2009-02-28 17:11 ` Keith Packard
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=49A7BC89.6040407@gmail.com \
--to=jirislaby@gmail.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=eric@anholt.net \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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