From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pekka Enberg Subject: Re: [Intel-gfx] [PATCH] drm/i915: Disable all outputs early, before KMS takeover Date: Tue, 5 Apr 2011 17:31:10 +0300 Message-ID: References: <1301395589-8121-1-git-send-email-chris@chris-wilson.co.uk> <20110401114429.GA3526@viiv.ffwll.ch> <1bdc18$k44m31@fmsmga002.fm.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <1bdc18$k44m31@fmsmga002.fm.intel.com> Sender: linux-kernel-owner@vger.kernel.org To: Chris Wilson Cc: Tomas Winkler , intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, Daniel Vetter , Linus Torvalds , Andrew Morton List-Id: intel-gfx@lists.freedesktop.org On Tue, Apr 5, 2011 at 5:27 PM, Chris Wilson = wrote: > On Tue, 5 Apr 2011 17:11:56 +0300, Pekka Enberg = wrote: >> [ =A0 =A09.310010] =A0 =A0[] panic+0x91/0x19e >> [ =A0 =A09.310010] =A0[] oops_end+0xea/0xf0 >> [ =A0 =A09.310010] =A0[] no_context+0xfb/0x260 >> [ =A0 =A09.310010] =A0[] __bad_area_nosemaphore+0x= 125/0x1e0 >> [ =A0 =A09.310010] =A0[] bad_area_nosemaphore+0x13= /0x20 >> [ =A0 =A09.310010] =A0[] do_page_fault+0x310/0x4c0 >> [ =A0 =A09.310010] =A0[] ? up+0x2f/0x50 >> [ =A0 =A09.310010] =A0[] ? console_unlock+0x17f/0x= 1d0 >> [ =A0 =A09.310010] =A0[] page_fault+0x25/0x30 >> [ =A0 =A09.310010] =A0[] ? i915_handle_error+0x198= /0xed0 [i915] >> [ =A0 =A09.310010] =A0[] ? scsi_next_command+0x4a/= 0x60 >> [ =A0 =A09.310010] =A0[] ? scsi_io_completion+0x2f= 6/0x630 >> [ =A0 =A09.310010] =A0[] i915_driver_irq_handler+0= x472/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 trigger= s. > > 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. I'm guessing it's the same PGTBL_ER I've seen for the past two-three kernel releases during boot. It seems to be harmless otherwise.