From: Alex Bennee <kernel-hacker@bennee.com>
To: Eric Anholt <eric@anholt.net>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: i915_gem_retire_requests oops on 2.6.30-rc7
Date: Wed, 27 May 2009 08:50:11 +0100 [thread overview]
Message-ID: <b2cdc9f30905270050s63a355f8u51644cb076cf7be6@mail.gmail.com> (raw)
In-Reply-To: <1243373914.8400.29.camel@gaiman.anholt.net>
2009/5/26 Eric Anholt <eric@anholt.net>:
> On Tue, 2009-05-26 at 13:20 +0100, Alex Bennee wrote:
>> Hi,
>>
>> I've just had X crash on me with an attendant oops in the kernel as it did so:
>
> That's not an oops, that's a WARN_ON. The hardware wasn't caught up by
> the time we gave up when shutting down the harwdare for VT switching.
> That's bad. But we don't know how long we should wait, since the GPU
> may be hung, and waiting forever would be bad. So we warn that
> Something Bad may have happened.
I can restart X afterwards so it can't be that hung. Would you like a
reg dump next the problem occurs?
>
> It's gone with KMS since we never shut down the GPU.
>
Although I'm not switching to KMS yet due to the other issues I'm
seeing (see xorg mails). But with KMS enabled we still see some things
like:
[ 660.644103] [drm] TMDS-8: set mode 2f
[ 960.272242] INFO: task events/0:9 blocked for more than 120 seconds.
[ 960.272245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[ 960.272248] events/0 D ffff8800b70a58c0 0 9 2
[ 960.272254] ffff8800b70b5de0 0000000000000046 ffff8800b103dc41
ffff880001028980
[ 960.272260] 0000000000004000 0000000000010dc0 000000000000ca38
ffff8800b0d31678
[ 960.272265] ffff8800b70b5d60 ffff8800b70a58c0 ffffffff80648350
ffff8800b70a5c48
[ 960.272270] Call Trace:
[ 960.272280] [<ffffffff804bfce6>] ? thread_return+0x3e/0xaa
[ 960.272285] [<ffffffff804c0589>] __mutex_lock_slowpath+0xdf/0x129
[ 960.272290] [<ffffffff804c092d>] mutex_lock+0x23/0x3b
[ 960.272295] [<ffffffff803cecd3>] i915_gem_retire_work_handler+0x2d/0x6b
[ 960.272301] [<ffffffff80247666>] worker_thread+0x176/0x20f
[ 960.272306] [<ffffffff803ceca6>] ? i915_gem_retire_work_handler+0x0/0x6b
[ 960.272311] [<ffffffff8024b463>] ? autoremove_wake_function+0x0/0x3d
[ 960.272315] [<ffffffff802474f0>] ? worker_thread+0x0/0x20f
[ 960.272319] [<ffffffff802474f0>] ? worker_thread+0x0/0x20f
[ 960.272323] [<ffffffff8024b061>] kthread+0x5b/0x88
[ 960.272329] [<ffffffff8020c0ba>] child_rip+0xa/0x20
[ 960.272333] [<ffffffff8024b006>] ? kthread+0x0/0x88
[ 960.272337] [<ffffffff8020c0b0>] ? child_rip+0x0/0x20
So are you sure this is a !KMS related thing?
--
Alex, homepage: http://www.bennee.com/~alex/
CV: http://www.bennee.com/~alex/cv.php
next prev parent reply other threads:[~2009-05-27 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 12:20 Alex Bennee
2009-05-26 21:38 ` Eric Anholt
2009-05-27 7:50 ` Alex Bennee [this message]
2009-05-27 17:42 ` Eric Anholt
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=b2cdc9f30905270050s63a355f8u51644cb076cf7be6@mail.gmail.com \
--to=kernel-hacker@bennee.com \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®