From: Chris Wilson <chris@chris-wilson.co.uk>
To: Pekka Enberg <penberg@kernel.org>
Cc: Tomas Winkler <tomasw@gmail.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Daniel Vetter <daniel@ffwll.ch>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Disable all outputs early, before KMS takeover
Date: Tue, 05 Apr 2011 15:27:54 +0100 [thread overview]
Message-ID: <1bdc18$k44m31@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <BANLkTins76X1mOFepqXEQjMEh_hd4Vgw1Q@mail.gmail.com>
On Tue, 5 Apr 2011 17:11:56 +0300, Pekka Enberg <penberg@kernel.org> wrote:
> [ 9.310010] <IRQ> [<ffffffff8168cd0c>] panic+0x91/0x19e
> [ 9.310010] [<ffffffff816909ea>] oops_end+0xea/0xf0
> [ 9.310010] [<ffffffff8106afbb>] no_context+0xfb/0x260
> [ 9.310010] [<ffffffff8106b245>] __bad_area_nosemaphore+0x125/0x1e0
> [ 9.310010] [<ffffffff8106b313>] bad_area_nosemaphore+0x13/0x20
> [ 9.310010] [<ffffffff816930c0>] do_page_fault+0x310/0x4c0
> [ 9.310010] [<ffffffff810ac06f>] ? up+0x2f/0x50
> [ 9.310010] [<ffffffff8108652f>] ? console_unlock+0x17f/0x1d0
> [ 9.310010] [<ffffffff8168fd25>] page_fault+0x25/0x30
> [ 9.310010] [<ffffffffa0061628>] ? i915_handle_error+0x198/0xed0 [i915]
> [ 9.310010] [<ffffffff8137d04a>] ? scsi_next_command+0x4a/0x60
> [ 9.310010] [<ffffffff8137ddd6>] ? scsi_io_completion+0x2f6/0x630
> [ 9.310010] [<ffffffffa0064c62>] i915_driver_irq_handler+0x472/0x17f0 [i915]
>
> This is the same pre-2.6.39-rc1 kernel with the two patches applied.
> I'll try latest Linus master next to see if the same problem triggers.
Hmm. Looks like we don't prevent the PGTBL_ER with those patches (or we
provoke another), and trigger the error before we can handle it.
Double ungood. Thanks,
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-04-05 14:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 11:34 [git pull] drm fixes for -rc1 Dave Airlie
2011-03-28 18:43 ` Pekka Enberg
2011-03-28 18:53 ` Pekka Enberg
2011-03-28 19:09 ` Chris Wilson
2011-03-29 7:11 ` Pekka Enberg
2011-03-29 7:49 ` Chris Wilson
2011-03-29 10:46 ` [PATCH] drm/i915: Disable all outputs early, before KMS takeover Chris Wilson
2011-03-29 12:23 ` [PATCH] drm/i915: Move the irq wait queue initialisation into the ring init Chris Wilson
2011-03-29 13:05 ` Pekka Enberg
2011-03-29 13:22 ` Chris Wilson
2011-03-29 13:39 ` Pekka Enberg
2011-03-29 14:22 ` Pekka Enberg
2011-03-29 14:32 ` Chris Wilson
2011-03-29 15:21 ` Pekka Enberg
2011-04-01 11:44 ` [Intel-gfx] [PATCH] drm/i915: Disable all outputs early, before KMS takeover Daniel Vetter
2011-04-01 11:51 ` Pekka Enberg
2011-04-05 10:21 ` Tomas Winkler
2011-04-05 10:30 ` Chris Wilson
2011-04-05 10:37 ` Pekka Enberg
2011-04-05 11:55 ` Tomas Winkler
2011-04-05 14:11 ` Pekka Enberg
2011-04-05 14:27 ` Chris Wilson [this message]
2011-04-05 14:31 ` Pekka Enberg
2011-04-05 14:34 ` Chris Wilson
2011-04-05 15:11 ` Pekka Enberg
2011-04-05 15:32 ` Chris Wilson
2011-04-05 15:44 ` Pekka Enberg
2011-04-05 14:42 ` [Intel-gfx] " Linus Torvalds
2011-04-05 15:01 ` Keith Packard
2011-04-05 15:12 ` Chris Wilson
2011-04-05 15:35 ` Pekka Enberg
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='1bdc18$k44m31@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=akpm@linux-foundation.org \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=tomasw@gmail.com \
--cc=torvalds@linux-foundation.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