From: Frederic Weisbecker <fweisbec@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, David Airlie <airlied@linux.ie>
Subject: Re: [BISECTED] agp/intel: revert "Remove confusion of stolen entries not stolen memory"
Date: Fri, 21 Jan 2011 00:24:14 +0100 [thread overview]
Message-ID: <20110120232410.GA19405@nowhere> (raw)
In-Reply-To: <0d30dc$kh41r4@orsmga001.jf.intel.com>
On Mon, Dec 20, 2010 at 09:06:47PM +0000, Chris Wilson wrote:
> On Mon, 20 Dec 2010 21:52:38 +0100, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Monday 20 December 2010 20:52:07 Chris Wilson wrote:
> > >
> > > Also, which modules do you have loaded when using VESA? i.e. is the
> > > i915.ko loaded, but in UMS mode (i915.modeset=0)?
> >
> > This doesn't seem to matter, as far as I can tell, i915 can be loaded
> > or now.
>
> Thanks, that rules out the likely explanation that we [i915] loaded the
> GTT with some conflicting entries. Instead it is likely the initialisation
> of the GTT to point to the scratch page that is triggering the problem.
> Can you try disabling it with:
Hi,
I have the problem too with -rc1, and even with latest linus tree.
I too bisected back to:
"agp/intel: Remove confusion of stolen entries not stolen memory)"
(c64f7ba5f1006d8c20eacafecf98d4d00a6902a0)
Symptom is I see a big vertical cursor blinking in my screen and
nothing else. If something tries to be displayed it gets very messy.
next prev parent reply other threads:[~2011-01-20 23:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 18:12 [BISECTED] agp/intel: revert "Remove confusion of stolen entries not stolen memory" Arnd Bergmann
2010-12-20 18:53 ` Chris Wilson
2010-12-20 19:47 ` Arnd Bergmann
2010-12-20 19:52 ` Chris Wilson
2010-12-20 20:52 ` Arnd Bergmann
2010-12-20 21:06 ` Chris Wilson
2010-12-20 21:54 ` Arnd Bergmann
2010-12-20 22:08 ` Dave Airlie
2011-01-20 23:24 ` Frederic Weisbecker [this message]
2011-01-21 10:58 ` [PATCH] drm/i915,agp/intel: Do not clear stolen entries Chris Wilson
2011-01-21 16:26 ` Jiri Olsa
2011-01-23 1:12 ` Frederic Weisbecker
2011-01-23 11:01 ` Chris Wilson
2011-01-23 17:59 ` Frederic Weisbecker
2011-01-24 7:40 ` Hugh Dickins
2011-01-24 10:10 ` Chris Wilson
2011-01-26 21:39 ` Arnd Bergmann
2011-01-28 22:00 ` Hugh Dickins
2011-01-29 2:59 ` Mario Kleiner
2011-01-30 0:28 ` Hugh Dickins
2011-01-30 4:13 ` Mario Kleiner
2011-01-30 9:55 ` Chris Wilson
2011-01-31 10:57 ` [PATCH] drm/i915: Suppress spurious vblank interrupts Chris Wilson
2011-02-01 17:34 ` Hugh Dickins
2011-02-01 17:46 ` Chris Wilson
2011-02-01 17:46 ` Jesse Barnes
2011-02-01 18:08 ` Jesse Barnes
2011-02-01 18:46 ` Hugh Dickins
2011-02-01 19:32 ` Jesse Barnes
2011-02-02 3:37 ` Hugh Dickins
2011-02-02 17:18 ` Jesse Barnes
2011-02-08 19:52 ` Hugh Dickins
2011-02-10 10:16 ` [PATCH] drm/i915/tv: Use polling rather than interrupt-based hotplug Chris Wilson
2011-02-11 6:34 ` Hugh Dickins
2011-02-11 18:21 ` [PATCH] drm/i915: Suppress spurious vblank interrupts Mario Kleiner
2011-02-14 17:41 ` Hugh Dickins
2011-06-18 4:40 ` Hugh Dickins
2011-01-30 8:52 ` [PATCH] drm/i915,agp/intel: Do not clear stolen entries Chris Clayton
2011-01-21 16:05 ` [BISECTED] agp/intel: revert "Remove confusion of stolen entries not stolen memory" Jiri Olsa
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=20110120232410.GA19405@nowhere \
--to=fweisbec@gmail.com \
--cc=airlied@linux.ie \
--cc=arnd@arndb.de \
--cc=chris@chris-wilson.co.uk \
--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