mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, Dave Airlie <airlied@redhat.com>,
	dri-devel@lists.sourceforge.net
Subject: Re: [regression] drm: display arifacts when X.Org is stopped
Date: Sun, 28 Jun 2009 11:44:11 +1000	[thread overview]
Message-ID: <21d7e9970906271844t15540ef8x57df641e87ab71fc@mail.gmail.com> (raw)
In-Reply-To: <200906271852.57388.elendil@planet.nl>

On Sun, Jun 28, 2009 at 2:52 AM, Frans Pop<elendil@planet.nl> wrote:
> With 2.6.31-rc1 I'm getting fairly serious display artifacts when X.Org
> is stopped and the display switches modes. This happens when I reboot the
> system (on the switch back to VT1), but also when I just restart the X
> server from the kdm splash screen.
>
> My text consoles use the VESA framebuffer (vga=791).
> I'm not using GEM.
>

you can't not use GEM, you can not use kernel modesetting which is
what I assume you are saying.

I'll try and reproduce this if I can, it seems quite strange. have you
> 4GB RAM btw?

Dave.

> I've bisected this to commit: 07613ba2f464f59949266f4337b75b91eb610795
>    agp: switch AGP to use page array instead of unsigned long array
>
>    This switches AGP to use an array of pages for tracking the
>    pages allocated to the GART. This should enable GEM on PAE to work
>    a lot better as we can pass highmem pages to the PAT code and it will
>    do the right thing with them.
>
>    Signed-off-by: Dave Airlie <airlied@redhat.com>
>

  reply	other threads:[~2009-06-28  1:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-27 16:52 Frans Pop
2009-06-28  1:44 ` Dave Airlie [this message]
2009-06-28  6:36   ` Frans Pop

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=21d7e9970906271844t15540ef8x57df641e87ab71fc@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=elendil@planet.nl \
    --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

Powered by JetHome