All of lore.kernel.org
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.2-rc in BK: Oops loading parport_pc.
Date: 26 Jan 2004 23:46:46 GMT	[thread overview]
Message-ID: <bv48t6$71r$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 20040126010832.GA5462@merlin.emma.line.org

In article <20040126010832.GA5462@merlin.emma.line.org>,
Matthias Andree  <matthias.andree@gmx.de> wrote:
| On Sun, 25 Jan 2004, Andrew Morton wrote:
| 
| > Matthias Andree <matthias.andree@gmx.de> wrote:
| > >
| > >  Loading the parport_pc modules crashes in 2.6.2-rc; I have recently done
| > >  a "bk pull" and enabled some PNP options, among them ISA PNP.
| > 
| > Often this is because some other, unrelated module left things registered
| > after it was removed.  Or otherwise wrecked shared data structures.
| 
| The breakage is somehow related to CONFIG_PNP. I set that option to N,
| ran "make oldconfig ; make", installed the kernel, rebooted, problem
| gone.

2.6.2-rc2:
  root> grep PNP .config
  CONFIG_PNP=y
  CONFIG_PNP_DEBUG=y
  CONFIG_ISAPNP=y
  CONFIG_PNPBIOS=y
  # CONFIG_BLK_DEV_IDEPNP is not set
  CONFIG_IP_PNP=y
  CONFIG_IP_PNP_DHCP=y
  CONFIG_IP_PNP_BOOTP=y
  CONFIG_IP_PNP_RARP=y

Boots and loads parport_pc just fine, so it looks as if either it got
fixed (likely) or other evildoers are at work.
-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

  parent reply	other threads:[~2004-01-26 23:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25 11:51 2.6.2-rc in BK: Oops loading parport_pc Matthias Andree
2004-01-25 23:14 ` Andrew Morton
2004-01-26  1:08   ` Matthias Andree
2004-01-26 19:31     ` Adam Belay
2004-01-27 11:22       ` Matthias Andree
2004-01-26 23:46     ` bill davidsen [this message]
2004-01-29 10:44   ` Matthias Andree

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='bv48t6$71r$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.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.