From: Eric Anholt <eric@anholt.net>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: David Airlie <airlied@linux.ie>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [resend] intel_agp: Don't oops with zero stolen memory
Date: Fri, 02 Jul 2010 13:57:36 -0700 [thread overview]
Message-ID: <87zky9iou7.fsf@pollan.anholt.net> (raw)
In-Reply-To: <201007022159.21848.linux@rainbow-software.org>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
On Fri, 2 Jul 2010 21:59:20 +0200, Ondrej Zary <linux@rainbow-software.org> wrote:
> On Friday 02 July 2010 00:44:39 Eric Anholt wrote:
> > On Wed, 16 Jun 2010 10:13:52 +0200, Ondrej Zary <linux@rainbow-software.org>
> wrote:
> > > When "onboard video memory" is set do "disabled" in BIOS on Asus
> > > P4P800-VM board (i865G), kernel oopses with memory corruption:
> > > https://bugs.freedesktop.org/show_bug.cgi?id=28430
> > >
> > > Fix that by cleanly aborting the initialization.
> > >
> > > Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
> >
> > I haven't seen a system with that option before. Is the integrated
> > graphics still supposed to work at that point, or is it "graphics is
> > disabled."? What do other OSes do here?
>
> Testing it right now with Windows XP. Integrated graphics works as secondary
> only when the "onboard video memory" is set to "disabled"! If anything other
> is set (e.g. 1MB or 32MB), the driver does not load (code 10).
OK, I was thinking in that case that we should fix the AGP driver's math
so that it correctly set up a chip with no stolen memory allocation. On
the other hand, I don't think we know what the correct math is, so maybe
we should just go ahead with disabling AGP in that case.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-07-02 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 8:13 Ondrej Zary
2010-07-01 22:44 ` Eric Anholt
2010-07-02 19:59 ` Ondrej Zary
2010-07-02 20:57 ` Eric Anholt [this message]
2010-07-02 21:54 ` Ondrej Zary
2010-07-05 16:54 ` Eric Anholt
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=87zky9iou7.fsf@pollan.anholt.net \
--to=eric@anholt.net \
--cc=airlied@linux.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.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