mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lawrence Walton <lawrence@the-penguin.otak.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Opps on boot 2.6.0-pre9-mm4
Date: Fri, 21 Nov 2003 09:09:33 -0800	[thread overview]
Message-ID: <20031121170933.GA1269@the-penguin.otak.com> (raw)
In-Reply-To: <20031120210953.GA25417@neo.rr.com>

Adam Belay [ambx1@neo.rr.com] wrote:
> On Thu, Nov 20, 2003 at 04:06:01PM -0800, Andrew Morton wrote:
> > Lawrence Walton <lawrence@the-penguin.otak.com> wrote:
> > >
> > > > Looks like it died inside the machine's BIOS.
> > > >
> > > > Please try reverting the three pnp patches:
> > > >
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm4/broken-out/pnp-fix-3.patch
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm4/broken-out/pnp-fix-2.patch
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm4/broken-out/pnp-fix-1.patch
> > > >
> > > > and let us know?
> > > >
> > > I reverted these and it works great!
> > >
> > >
> > >
> > > > - Upgrade the bios
> > > The bios is the latest so updating it would not of been a option.
> > >
> >
> > OK, thanks.   Adam, those pnp patches are suspect...
> 
> Hmm, well it couldn't be patch 3 because it relates to isapnp.  Patch
> 1 is the only patch that changes the PnPBIOS calls, and it has been
> known to fix problems for some systems.  Also it does what the actual
> specifications recommend.  You may just have a buggy system that's
> triggered by the static resource calls.  If so, we could use dynamic
> instead resources when the DMI scan matches with this system.  Patch
> 2 provides an option to disable the PnPBIOS proc interface, but it
> should not affect PnPBIOS calls.
> 
> Lawrence, could you please test this again, only this time excluding
> patch 1 and no others.  If that doesn't work try excluding patch 2.
> 
> Thanks,
> Adam
> 
> P.S.

Adam this worked great too. 
My guess is that this board is a little different.
It's a Asus A7V333 with fireiwire and the raid.


-- 
*--* Mail: lawrence@otak.com
*--* Voice: 425.739.4247
*--* Fax: 425.827.9577
*--* HTTP://www.otak-k.com/~lawrence/
--------------------------------------
- - - - - - O t a k  i n c . - - - - - 



      reply	other threads:[~2003-11-21 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 19:33 Lawrence Walton
2003-11-20 21:19 ` Andrew Morton
2003-11-20 23:30   ` Lawrence Walton
2003-11-21  0:06     ` Andrew Morton
2003-11-20 21:09       ` Adam Belay
2003-11-21 17:09         ` Lawrence Walton [this message]

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=20031121170933.GA1269@the-penguin.otak.com \
    --to=lawrence@the-penguin.otak.com \
    --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

all inboxes | Powered by JetHome®