public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: Andrew Morton <akpm@digeo.com>, Justin A <ja6447@albany.edu>,
	greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: pnpbios oops on boot w/ 2.5.47
Date: Sat, 16 Nov 2002 23:25:28 +0000	[thread overview]
Message-ID: <20021116232528.GA1273@neo.rr.com> (raw)
In-Reply-To: <3DD6F655.4214A594@digeo.com>

On Sat, Nov 16, 2002 at 05:52:21PM -0800, Andrew Morton wrote:
> Andrew Morton wrote:
> > 
> > Justin A wrote:
> > >
> > > Hi :)
> > >
> > > I tried to "port" kmsgdump to 2.5.47 and for some reason, it worked.
> > >
> > > Attached is the full dmesg
> > >
> > > Alan: I ran dmidecode under 2.4.19 which said simply "PNP BIOS present"
> > >
> > > This is a thinkpad 760e, really old..I don't even think I need pnpbios
support


If it was calling pnpbios_set_resources you probably do.  This means it was
trying to activate a device.  If a device is not active you cannot use it.
This device was most likely a serial port or modem.  Try turning on PnP
Debug after applying the below patch and see if a device is activated.


> > > for anything.  2.5.47/2.5.47-ac5 boot with pnpbios turned off, so I think 
you
> > > just need to add this to your blacklist?
> > >
> > 
> > The BUG in slab indicates that something overran the end of a kmalloced
> > buffer.  That'll be either pnp_bios_get_dev_node() or node_set_resources()
> > ran off the end of `node'.
> 
> err...
> 
>         node = pnpbios_kmalloc(node_info.max_node_size, GFP_KERNEL);
> 
> max_node_size appears to never be initialised.


Oops.  I put the pnpbios_kmalloc in the wrong place.  It's amazing it still 
worked on my test box.  Here's a patch that should fix it.  Justin: could you
please try it.

Thanks,
Adam

The typo appears to be in pnpbios_set_resources.  Andrew: Is this where you 
found it?


--- a/drivers/pnp/pnpbios/core.c	Wed Nov  6 17:51:53 2002
+++ b/drivers/pnp/pnpbios/core.c	Sat Nov 16 23:03:00 2002
@@ -1285,9 +1285,9 @@
 		return -EBUSY;
 	if (flags == PNP_DYNAMIC && !pnp_is_dynamic(dev))
 		return -EPERM;
-	node = pnpbios_kmalloc(node_info.max_node_size, GFP_KERNEL);
 	if (pnp_bios_dev_node_info(&node_info) != 0)
 		return -ENODEV;
+	node = pnpbios_kmalloc(node_info.max_node_size, GFP_KERNEL);
 	if (!node)
 		return -1;
 	if (pnp_bios_get_dev_node(&nodenum, (char )1, node))


  reply	other threads:[~2002-11-17  4:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-16 22:00 pnpbios oops on boot w/ 2.5.47 Justin A
2002-11-16 22:08 ` Andrew Morton
2002-11-17  1:52   ` Andrew Morton
2002-11-16 23:25     ` Adam Belay [this message]
2002-11-17  4:35       ` Andrew Morton
2002-11-17 17:34         ` Adam Belay
2002-11-18 17:35           ` Alan Cox
2002-11-17  6:00       ` Justin A
2002-11-17 18:05         ` Adam Belay
2002-11-17 23:41           ` Justin A

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=20021116232528.GA1273@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=akpm@digeo.com \
    --cc=greg@kroah.com \
    --cc=ja6447@albany.edu \
    --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