All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Lawrence Walton <lawrence@the-penguin.otak.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Opps on boot 2.6.0-pre9-mm4
Date: Thu, 20 Nov 2003 21:09:53 +0000	[thread overview]
Message-ID: <20031120210953.GA25417@neo.rr.com> (raw)
In-Reply-To: <20031120160601.6b1fbd53.akpm@osdl.org>

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.

Andrew, could you please review this patch for your tree.

# --------------------------------------------
# 03/11/15	ambx1@neo.rr.com	1.1447
# [PnP] reserve resources specified by the PnPBIOS properly
#
# A bug prevents the PnP layer from reserving some of the resources
# specified by the PnPBIOS.  As a result some systems will have
# unpredicable (random crashes etc.) problems because of resource
# conflicts, especially when PCMCIA support is enabled.  This patch
# fixes the problem by ensuring that the proper resource data is
# reserved.
# --------------------------------------------
#
diff -Nru a/drivers/pnp/system.c b/drivers/pnp/system.c
--- a/drivers/pnp/system.c	Sun Nov 16 00:25:14 2003
+++ b/drivers/pnp/system.c	Sun Nov 16 00:25:14 2003
@@ -54,7 +54,7 @@
 	int i;

 	for (i=0;i<PNP_MAX_PORT;i++) {
-		if (pnp_port_valid(dev, i))
+		if (!pnp_port_valid(dev, i))
 			/* end of resources */
 			continue;
 		if (pnp_port_start(dev, i) == 0)


  reply	other threads:[~2003-11-21  2:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 19:33 Opps on boot 2.6.0-pre9-mm4 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 [this message]
2003-11-21 17:09         ` Lawrence Walton

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=20031120210953.GA25417@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=akpm@osdl.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.