public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: jdthood@home.dhs.org (Thomas Hood)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stelian Pop <stelian.pop@fr.alcove.com>
Date: 05 Oct 2001 10:57:12 -0600	[thread overview]
Message-ID: <m1vghuxbx3.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20011003153550.0A0D85AC@thanatos.toad.net>
In-Reply-To: <20011003153550.0A0D85AC@thanatos.toad.net>

jdthood@home.dhs.org (Thomas Hood) writes:

> Stelian Pop wrote:
> >> Well, the funny thing is, the same kernel doesn't boot on a Dell Inspiron 
> >> laptop either, if PNP is enabled -- and the oops is the same. So it's not 
> >> just Sony...
> >
> >Maybe we'll need to test against something like 'pnp_broken' 
> >variable instead of is_sony_vaio_laptop in PnP drivers, and
> >add the callbacks in dmi_scan to initialize pnp_broken...
> 
> Yes, the "pnp_bios_dont_use_current_config" flag in the driver
> can be set based on additional criteria.
> 
> I notice that both the Vaio and the Inspiron have Phoenix BIOSes.
> So perhaps there is a class of Phoenix BIOSes we should be testing
> for.  For the time being, we will need to add Ion Badulescu's Inspiron
> to the dmi_blacklist.  Ion, can you give us the exact product name,
> exact BIOS vendor name, exact BIOS version and exact BIOS date?
> Also, let us know all the results of your tests of various kernels.
> 
> It's interesting to note that my IBM ThinkPad BIOS has a bug that
> is similar to the bug in your BIOS.  After Linux is run, on the
> subsequent boot the "current" config is not initialized from the
> "boot" config; instead, all devices are left disabled.  This does
> not happen if Windows was the previous OS run, or if the BIOS
> is initialized before the boot.  My sneaking suspicion is that this
> behavior is a "feature" of the BIOS: when certain of its functions
> are accessed it deduces that it is being used by a Plug-n-Play
> operating system (tm) and so refrains from configuring devices other
> than the vital ones.  

Hmm. If you are using an AC kernel I seriously suspect the bootflag code,
because that is what the code is telling the BIOS to do explicitly.

> My workaround for now is to use "setpnp" to
> switch on all the configurable devices.  The "right" solution may
> be to use the ESCD functions of the BIOS.  Or it may be to stop
> doing whatever it is that suggests to the BIOS that Linux is a
> PnP OS.

Suggests.  With the bootflag stuff we are saying treat as a pnpos we
know what we are doing.

Eric




  parent reply	other threads:[~2001-10-05 17:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03 15:35 Stelian Pop <stelian.pop@fr.alcove.com> Thomas Hood
2001-10-03 21:34 ` Ion Badulescu
2001-10-05 16:57 ` Eric W. Biederman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-03 21:46 Thomas Hood
2001-10-03 22:04 ` Ion Badulescu

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=m1vghuxbx3.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=jdthood@home.dhs.org \
    --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