mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15.1 Oops: rmmod ide-scsi
Date: Tue, 17 Jan 2006 10:02:03 +0100	[thread overview]
Message-ID: <58cb370e0601170102l491c1a1o7494416c6ae133d@mail.gmail.com> (raw)
In-Reply-To: <20060116235103.GA9664@merlin.emma.line.org>

Hi Matthias,

Unfortunately this a known bug since at least 2.6.8 days:

http://bugzilla.kernel.org/show_bug.cgi?id=3568

Fixing would probably require adding reference counting on SCSI host.

On 1/17/06, Matthias Andree <matthias.andree@gmx.de> wrote:
> Greetings,
>
> playing with 2.6.15.1 a bit, I found that unloading ide-scsi causes two
> reproducible Oopsen here, and then the system locks up a short while
> later (with SysRq still functional so I can SysRq+B, but this corrupted
> an innocent .pyo file unrelated and even unaccessed during this time...)
>
> Procedure to reproduce:
>
> boot with init=/bin/bash added
>
> rmmod ide-cd      # SUSE loads this module from initrd
> modprobe ide-scsi
> rmmod ide-scsi    # <- oopses right after that with Oops #1
>                   #    and a few seconds later with Oops #2
>
> Enclosed: (1) the full dmesg and (2) .config (I fed the latter through
> egrep to ditch the comments and blank lines and sorted it for easy "is
> option XYZ set" retrieval).
>
> I don't think ide-cd is the culprit here, I can unload and reload it
> several times in a row without Oops.
>
> There be more dragons inside that module,
> but that's a different tale
> not to be told today.
>
> Regards,
>
> --
> Matthias Andree

      reply	other threads:[~2006-01-17  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-16 23:51 Matthias Andree
2006-01-17  9:02 ` Bartlomiej Zolnierkiewicz [this message]

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=58cb370e0601170102l491c1a1o7494416c6ae133d@mail.gmail.com \
    --to=bzolnier@gmail.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

all inboxes | Powered by JetHome®