All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: CaT <cat@zip.com.au>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH][RFC] Possible PnP BIOS GPF Solution for Sony VAIO and other laptops
Date: Sun, 2 Feb 2003 22:59:10 +0000	[thread overview]
Message-ID: <20030202225910.GB22089@neo.rr.com> (raw)
In-Reply-To: <20030203020957.GE847@zip.com.au>

On Mon, Feb 03, 2003 at 01:09:57PM +1100, CaT wrote:
> On Sun, Feb 02, 2003 at 08:37:02PM +0000, Adam Belay wrote:
> > The PnP BIOS may be wandering into segement 0x40.  If that is the case,
> > this patch should fix the problem.  I do not have a buggy system so I
> > cannot test this patch but I'd be intersted to hear the results.  If you
> > have a system that has caused pnpbios problems in the past, I recommend
> > you try this patch.  If it works, the system will not panic on startup.
> > This patch is against 2.5.59 and separate from my other recent patches.
> 
> This boots fine here. Then again 2.5.59 booted fine aswell. :) I also
> don't get any oopses from reading /proc/bus/pnp stuff as I did before
> when I first reported issues. As with the bootup, I also don't get these
> issues with 2.5.59. (ie 2.5.59 works fine with or without this patch).

This can be explained.  When the pnpbios makes a get current resource call
on a buggy system it causes a GPF.  In 2.5.59 I designed the pnpbios driver
to avoid making this call when scanning for devices.  It uses a get boot
resource call instead.

In other words...

Without this patch, if you made the following change it would panic.

 		 * from devices that are can only be static such as
 		 * those controlled by the "system" driver.
 		 */
-		if (pnp_bios_get_dev_node(&nodenum, (char )1, node))
+		if (pnp_bios_get_dev_node(&nodenum, (char )0, node))
 			break;
 		nodes_got++;
 		dev =  pnpbios_kmalloc(sizeof (struct pnp_dev), GFP_KERNEL);

1 = boot config
0 = current config

Therefore it can be concluded that this patch does indeed solve the problem
for your system :-).

>
> Sorry for not getting back to you earlier btw... I lost almost a
> fortnights worth of email and yours was amongst them. :/
> 

Thank you for testing my patch.

Regards,
Adam

      reply	other threads:[~2003-02-03  3:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 20:37 [PATCH][RFC] Possible PnP BIOS GPF Solution for Sony VAIO and other laptops Adam Belay
2003-02-03  2:09 ` CaT
2003-02-02 22:59   ` Adam Belay [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=20030202225910.GB22089@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cat@zip.com.au \
    --cc=greg@kroah.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.