linux-kernel - Re: [Intel-gfx] [PATCH] drm/i915: Disable all outputs early, before KMS takeover

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1bdc18$k44m31@fmsmga002.fm.intel.com>
Date:	Tue, 05 Apr 2011 15:27:54 +0100
From:	Chris Wilson <chris@...is-wilson.co.uk>
To:	Pekka Enberg <penberg@...nel.org>
Cc:	Tomas Winkler <tomasw@...il.com>, intel-gfx@...ts.freedesktop.org,
	linux-kernel@...r.kernel.org, Daniel Vetter <daniel@...ll.ch>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Disable all outputs early, before KMS takeover

On Tue, 5 Apr 2011 17:11:56 +0300, Pekka Enberg <penberg@...nel.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/