From: Steven Cole <elenstev@mesatop.com>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Thomas Molina <tmolina@cox.net>
Subject: Re: 2.5.39 Oops on boot (device_attach+0x3a)
Date: 01 Oct 2002 08:24:00 -0600 [thread overview]
Message-ID: <1033482240.32404.116.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <20021001053957.GA5177@kroah.com>
On Mon, 2002-09-30 at 23:39, Greg KH wrote:
> On Mon, Sep 30, 2002 at 07:13:02PM -0600, Steven Cole wrote:
> > I tried to boot 2.5.39 on my home machine and got the
> > following oops on boot with CONFIG_KALLSYMS=y (thanks Ingo!).
>
> Do you have CONFIG_ISAPNP enabled? If so, search the archives for the
> fix for this. If not, please post your whole .config.
Although I don't have that test box in front of me now, I'm almost
certain that I do have CONFIG_ISAPNP enabled. Searching the archives
turned up a fix similar to the one below which is part of 2.5.40, (which
I haven't been able to download yet). I won't be able to test this
until tonight, but perhaps Thomas can see if this fixes the same oops
for him in the meantime.
Thanks,
Steven
--- 1.13/drivers/pnp/isapnp.c Fri Sep 27 04:10:46 2002
+++ 1.14/drivers/pnp/isapnp.c Sun Sep 29 18:19:31 2002
@@ -2281,7 +2281,9 @@
EXPORT_SYMBOL(isapnp_register_driver);
EXPORT_SYMBOL(isapnp_unregister_driver);
-static struct device_driver isapnp_device_driver = {};
+static struct device_driver isapnp_device_driver = {
+ .devices = LIST_HEAD_INIT(isapnp_device_driver.devices),
+};
static inline int isapnp_init_device_tree(void)
{
next prev parent reply other threads:[~2002-10-01 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 1:13 2.5.39 Oops on boot (device_attach+0x3a) Steven Cole
2002-10-01 2:50 ` Thomas Molina
2002-10-01 3:38 ` Steven Cole
2002-10-01 8:10 ` Thomas Molina
2002-10-01 5:39 ` Greg KH
2002-10-01 8:15 ` Thomas Molina
2002-10-01 14:24 ` Steven Cole [this message]
2002-10-01 17:06 ` Steven Cole
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=1033482240.32404.116.camel@spc9.esa.lanl.gov \
--to=elenstev@mesatop.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@cox.net \
/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;
as well as URLs for NNTP newsgroup(s).