intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Winkler <tomasw@gmail.com>
To: Pekka Enberg <penberg@kernel.org>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Disable all outputs early, before KMS takeover
Date: Tue, 5 Apr 2011 13:21:08 +0300	[thread overview]
Message-ID: <BANLkTimUZY+2E=kXG-as8-moAAS4+F5bTg@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik6njOQTLGsB4KzPP-J=fE=p4CHopAyvsDzdDSF@mail.gmail.com>

On Fri, Apr 1, 2011 at 2:51 PM, Pekka Enberg <penberg@kernel.org> wrote:
> On Fri, Apr 1, 2011 at 2:44 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Tue, Mar 29, 2011 at 11:46:29AM +0100, Chris Wilson wrote:
>>> If the outputs are active and continuing to access the GATT when we
>>> teardown the PTEs, then there is a potential for us to hang the GPU.
>>> The hang tends to be a PGTBL_ER with either an invalid host access or
>>> an invalid display plane fetch.
>>
>> This patch seems to fix resume flakiness (that recently developed
>> complete reliability in hanging the gpu) on my i855gm. Captured
>> error_states look as described here. Latest -staging merged into latest
>> -linus is now again fully reliable at s/r.
>>
>> Tested-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> Unfortunately I get a blank screen with after boot:
> Nacked-by: Pekka Enberg <penberg@kernel.org>

Not sure this is related, but when I enable DRM_I915_KMS=y I'm got
stuck after boot too. When KMS is disabled I can at least get to the
console (no graphics)
This is with kernel 2.6.39-rc1.  It worked fine with 2.6.38. I don't
have much time bisect and reboot.  Shell I  try to pull drm-fixes for
rc2 or use try this patch?


lspci -vv
00:02.0 VGA compatible controller: Intel Corporation Core Processor
Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
	Subsystem: Intel Corporation Device 0036
	Flags: bus master, fast devsel, latency 0, IRQ 42
	Memory at fe000000 (64-bit, non-prefetchable) [size=4M]
	Memory at d0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f160 [size=8]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915

Thanks
Tomas

  reply	other threads:[~2011-04-05 10:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=VqkYjdiDLJvM-OfmBSGx-EkRkt=4XCDEnvZsU@mail.gmail.com>
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   ` [PATCH] drm/i915: Disable all outputs early, before KMS takeover Daniel Vetter
2011-04-01 11:51     ` [Intel-gfx] " Pekka Enberg
2011-04-05 10:21       ` Tomas Winkler [this message]
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
2011-04-05 14:31                 ` [Intel-gfx] " 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           ` Linus Torvalds
2011-04-05 15:01             ` Keith Packard
2011-04-05 15:12             ` [Intel-gfx] " 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='BANLkTimUZY+2E=kXG-as8-moAAS4+F5bTg@mail.gmail.com' \
    --to=tomasw@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@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;
as well as URLs for NNTP newsgroup(s).