public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Kerin <eric@bootseg.com>
To: Alexander Nyberg <alexn@telia.com>
Cc: Andrew Morton <akpm@osdl.org>,
	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 01:05:25 -0500	[thread overview]
Message-ID: <1077602725.3172.19.camel@opiate> (raw)
In-Reply-To: <20040223160716.799195d0.akpm@osdl.org>

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.

Eric Kerin








  parent reply	other threads:[~2004-02-24  6: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 [this message]
2004-02-24  6:17     ` Andrew Morton
2004-02-24  7:07       ` Eric Kerin
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=1077602725.3172.19.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