public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86-boot: don't request VBE2 information
Date: Thu, 06 Mar 2008 07:16:16 -0800	[thread overview]
Message-ID: <47D00AC0.8010805@zytor.com> (raw)
In-Reply-To: <1204797405-18059-1-git-send-email-jacmet@sunsite.dk>

Peter Korsgaard wrote:
> The new x86 setup code (4fd06960f120) broke booting on an old P3/500MHz
> with an onboard Voodoo3 of mine. After debugging it, it turned out
> to be caused by the fact that the vesa probing now asks for VBE2 data.
> 
> Disassembing the video BIOS shows that it overflows the vesa_general_info
> structure when VBE2 data is requested because the source addresses for the
> information strings which get strcpy'ed to the buffer lie outside the 32K
> BIOS code (and hence contain long sequences of 0xff's).
> 

I'm slightly concerned about this, because we *do* use VBE2 data - just 
not the stuff that this particular BIOS seems to key on (and break.)

On the other hand, until we get an example on something that breaks with 
the change, we might as well try it, since we have an example on 
something that breaks with it.  We should monitor carefully, though.

	-hpa

  parent reply	other threads:[~2008-03-06 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06  9:56 [PATCH] x86-boot: don't request VBE2 information Peter Korsgaard
2008-03-06 10:24 ` Ingo Molnar
2008-03-06 15:16 ` H. Peter Anvin [this message]
2008-03-06 16:16   ` Peter Korsgaard

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=47D00AC0.8010805@zytor.com \
    --to=hpa@zytor.com \
    --cc=jacmet@sunsite.dk \
    --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