All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Albrecht Dre? <albrecht.dress@arcor.de>
Cc: mlan@cpu.lu, linuxppc-dev@lists.linuxppc.org
Subject: Re: Kernel Gurus: Module insertion deadlock? [Was: SCSI system freeze w/2.4.18]
Date: 08 Apr 2002 00:32:29 +0200	[thread overview]
Message-ID: <1018218750.1868.772.camel@tibook> (raw)
In-Reply-To: <20020407143312.GA927@regulus>


On Sun, 2002-04-07 at 16:33, Albrecht Dre? wrote:
>
> I played a little more with this, and got the following picture:
>
> * scsi cd support built into the kernel: the access works without a cd in
>    the drive
>
> * scsi cd support built as module
>    - do a "modprobe sr_mod" (which inserts sr_mod.o and cdrom.o): access
>      works like support built fixed into the kernel;
>    - remove sr_mod (cdrom.o may still be loaded): access leads to the hang as
>      described.
>
> So I think there is some kind of deadlock between dd and the module
> insertion (which includes a disk access to read/load the module). As I do
> not see this on an iMac with a ide cd drive, it might be a problem either in
> sr_mod or in the scsi stuff. However, the iMac has two separate ide busses
> for the cd and the disk, so the hang might be "same bus" related.

Indeed, I've experienced the same problem on a Cube where both HD and CD-ROM
are on the first IDE bus. Used to work before around 2.4.10, don't remember
exactly.


--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-04-07 22:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04 19:52 SCSI system freeze w/2.4.18 Albrecht Dre?
2002-04-04 22:42 ` Andrew Bradley
2002-04-05 19:35 ` Michel Lanners
2002-04-07 14:33   ` Kernel Gurus: Module insertion deadlock? [Was: SCSI system freeze w/2.4.18] Albrecht Dre?
2002-04-07 22:32     ` Michel Dänzer [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=1018218750.1868.772.camel@tibook \
    --to=michel@daenzer.net \
    --cc=albrecht.dress@arcor.de \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mlan@cpu.lu \
    /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.