From: Eric Kerin <eric@bootseg.com>
To: Andrew Morton <akpm@osdl.org>
Cc: alexn@telia.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: 2.6.3 oops at kobject_unregister, alsa & aic7xxx
Date: Tue, 24 Feb 2004 02:07:43 -0500 [thread overview]
Message-ID: <1077606462.3172.38.camel@opiate> (raw)
In-Reply-To: <20040223221740.5786b0b3.akpm@osdl.org>
On Tue, 2004-02-24 at 01:17, Andrew Morton wrote:
> Eric Kerin <eric@bootseg.com> wrote:
> >
> > On Mon, 2004-02-23 at 19:07, Andrew Morton wrote:
> > > Alexander Nyberg <alexn@telia.com> wrote:
> > > >
> > > > This happens at shutdown when alsa is to close down. I'm running debian
> > > > sid. NOTE: I recently removed my aic7xxx out of the motherboard, so the
> > > > driver obviously can't find it. But if I remove aic7xxx from the modules
> > > > list, this oops does _not_ happen.
> > >
> > > That's useful infomation. It indicates that the aic7xxx driver is screwing
> > > up the kobject lists.
> > >
> > > Just to confirm: are you saying that the aic7xxx driver is loaded at the
> > > tie of the oops, but there is no aic7xxx hardware present in the machine?
> >
> >
> > I stumbled up this in early January. I posted a patch to linux-scsi,
> > but it dosn't seem to be merged at this point. This problem will also
> > occur with the aic79xx driver.
> >
> > Here's the location of the original thread:
> > http://marc.theaimsgroup.com/?l=linux-scsi&m=107307695430108&w=2
> >
> > I just tried the patch on 2.6.3, and it still applies cleanly.
>
> hm, I was looking at that code but it seemed OK. You said "left a stale
> entry in the pci_device list". Is that correct, or was the entry in the
> PCI driver list? The latter, surely?
>
> If so, why is that a problem? ahc_linux_pci_exit() takes it out again?
You are correct it's the PCI driver list, I misspoke in my original
mail.
The AIC drivers are currently coded to unload (by returning -ENODEV from
the init function) if no devices are found, so the exit function never
gets called, leaving the stale entries.
There's a 2nd patch in the above thread that changes those modules to
stay loaded even if no devices are found, which Arjan V pointed out was
the preferred way for drivers to work.
Eric Kerin
next prev parent reply other threads:[~2004-02-24 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 14:30 2.6.3 oops at kobject_unregister, alsa & aic7xxx Alexander Nyberg
2004-02-24 0:07 ` Andrew Morton
2004-02-24 0:43 ` Alexander Nyberg
2004-02-24 6:05 ` Eric Kerin
2004-02-24 6:17 ` Andrew Morton
2004-02-24 7:07 ` Eric Kerin [this message]
2004-02-24 7:32 ` Andrew Morton
2004-02-24 7:54 ` Eric Kerin
2004-02-24 17:56 ` Justin T. Gibbs
2004-02-24 23:12 ` Jason Lunz
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=1077606462.3172.38.camel@opiate \
--to=eric@bootseg.com \
--cc=akpm@osdl.org \
--cc=alexn@telia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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