The Linux Kernel Mailing List
 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@lxorguk.ukuu.org.uk
Subject: Re: 2.5.45 / boottime oops (pnp bios I think)
Date: Mon, 4 Nov 2002 16:15:04 +0000	[thread overview]
Message-ID: <20021104161504.GA316@neo.rr.com> (raw)
In-Reply-To: <20021104025458.GA3088@zip.com.au>

On Mon, Nov 04, 2002 at 01:54:59PM +1100, CaT wrote:
> When I unselect PNP BIOS the kernel boots fine. With it I get the
> oops below. Please note that it was typed out manually and that that was
> all that I could get as I could not scroll up or down in any way.
>
> The PC is a Gateway laptop.
>
> If you need more info, please holler.
>

Instead of adding your PnP BIOS to the black list, I may know a way to 
support it completely even though it is broken.

To prove this idea could you please do the following:

1.) apply patch 1 (attached below) to a clean kernel (2.5.45).  Compile the 
kernel with PnP BIOS support and list the last few messages that start with 
"pnp!!!:" before it panics.  You probably will want to have kernel debugging
off so it doesn't scroll the messages off the screen.

2.) Apply patch 2 (attached below) to a clean kernel (2.5.45).  Compile the 
kernel with PnP BIOS support.  It should start up completely without a panic.  
This is not a complete fix however.  Anyway attach a copy of the output from 
dmesg.

If my theory is correct I will have a fix out soon.

thanks,
Adam


patch 1---------------------------------------------------------------------

diff -ur stock/drivers/pnp/pnpbios/core.c debug/drivers/pnp/pnpbios/core.c
--- stock/drivers/pnp/pnpbios/core.c	Thu Oct 31 00:41:38 2002
+++ debug/drivers/pnp/pnpbios/core.c	Mon Nov  4 15:48:56 2002
@@ -1421,6 +1421,7 @@
 		memcpy(dev->name,"Unknown Device",13);
 		dev->name[14] = '\0';
 		pnpid32_to_pnpid(node->eisa_id,id);
+		printk(KERN_ERR "PNP!!!: Node number: 0x%x EISA ID: %s\n", (unsigned int)thisnodenum, id);
 		memcpy(dev_id->id,id,8);
 		pnp_add_id(dev_id, dev);
 		pos = node_current_resource_data_to_dev(node,dev);



patch 2---------------------------------------------------------------------

diff -ur stock/drivers/pnp/pnpbios/core.c debug/drivers/pnp/pnpbios/core.c
--- stock/drivers/pnp/pnpbios/core.c	Thu Oct 31 00:41:38 2002
+++ debug/drivers/pnp/pnpbios/core.c	Mon Nov  4 15:50:41 2002
@@ -1405,7 +1405,7 @@
 		 * asking for the "current" config causes some
 		 * BIOSes to crash.
 		 */
-		if (pnp_bios_get_dev_node(&nodenum, (char )0 , node))
+		if (pnp_bios_get_dev_node(&nodenum, (char )1 , node))
 			break;
 		nodes_got++;
 		dev =  pnpbios_kmalloc(sizeof (struct pnp_dev), GFP_KERNEL);
@@ -1421,6 +1421,7 @@
 		memcpy(dev->name,"Unknown Device",13);
 		dev->name[14] = '\0';
 		pnpid32_to_pnpid(node->eisa_id,id);
+		printk(KERN_ERR "PNP!!!: Node number: 0x%x EISA ID: %s\n", (unsigned int)thisnodenum, id);
 		memcpy(dev_id->id,id,8);
 		pnp_add_id(dev_id, dev);
 		pos = node_current_resource_data_to_dev(node,dev);

  parent reply	other threads:[~2002-11-04 21:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04  2:54 2.5.45 / boottime oops (pnp bios I think) CaT
2002-11-04 13:05 ` Alan Cox
2002-11-04 13:46   ` CaT
2002-11-04 14:21     ` Alan Cox
2002-11-07 14:33   ` David Woodhouse
2002-11-07 14:51     ` Dave Jones
2002-11-07 14:55       ` David Woodhouse
2002-11-07 15:46         ` Dave Jones
2002-11-07 15:50           ` David Woodhouse
2002-11-07 15:54         ` Brian Gerst
2002-11-04 16:15 ` Adam Belay [this message]
2002-11-04 23:54   ` CaT
2002-11-04 20:28     ` Adam Belay
2002-11-05  2:06       ` CaT
2002-11-04 21:24         ` Adam Belay
2002-11-05  2:29           ` CaT

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=20021104161504.GA316@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox