From: Russell King <rmk@arm.linux.org.uk>
To: meissner@spectacle-pond.org (Michael Meissner)
Cc: ookhoi@dds.nl (Ookhoi),
meissner@spectacle-pond.org (Michael Meissner),
linux-kernel@vger.kernel.org
Subject: Re: The advantage of modules?
Date: Mon, 8 Jan 2001 21:50:55 +0000 (GMT) [thread overview]
Message-ID: <200101082150.f08Lots13085@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20010108140521.C11682@munchkin.spectacle-pond.org> from "Michael Meissner" at Jan 08, 2001 02:05:21 PM
Michael Meissner writes:
> Quoting from drivers/scsi/scsi.c:
>
> /*
> * Usage: echo "scsi add-single-device 0 1 2 3" >/proc/scsi/scsi
> * with "0 1 2 3" replaced by your "Host Channel Id Lun".
> * Consider this feature BETA.
> * CAUTION: This is not for hotplugging your peripherals. As
> * SCSI was not designed for this you could damage your
> * hardware !
> * However perhaps it is legal to switch on an
> * already connected device. It is perhaps not
> * guaranteed this device doesn't corrupt an ongoing data transfer.
> */
>
> so my take is unless you explicitly use hotplug devices (I wasn't), that
> it is much safer to unload the driver, unattach/attach scsi devices, and
> then reload the driver (which will scan the scsi bus for devices), which
> you need modules for.
I don't believe that is what it's trying to say. There have been instances
in the past where unplugging a SCSI device from a powered on SCSI bus can
result in blown terminator power fuses and the like. Whether this still
applies today, I don't know (are active terminators better or worse than
passive when it comes to this type of thing?) However, what I do know is
the following, and I learnt it the hard way:
I once had a machine and other stuff on a 4-way mains connector block
that has been used for many years. Unknown to me, the earth wire
had become intermittent. I was just about to connect another peripheral
which was directly connected to the wall socket to this computer, and
I happened to touch the connector body on both the peripheral and the
computer. I now know what a shock of >120V feels like.
Now, imagine what would happen if you connect a SCSI device, where this
condition exists, and the first thing that makes contact is the SCSI
databus. Say goodbye to most, if not all devices on that SCSI bus.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-08 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 4:50 The advantage of modules? Evan Thompson
2001-01-06 5:31 ` Drew Bertola
2001-01-06 10:02 ` J . A . Magallon
2001-01-08 16:49 ` Michael Meissner
2001-01-08 16:47 ` Michael Meissner
2001-01-08 18:26 ` Ookhoi
2001-01-08 19:05 ` Michael Meissner
2001-01-08 21:50 ` Russell King [this message]
2001-01-08 22:16 ` Dan Hollis
2001-01-08 22:14 ` Russell King
2001-01-08 22:40 ` Dan Hollis
2001-01-08 23:06 ` Richard B. Johnson
2001-01-08 23:49 ` Alan Cox
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=200101082150.f08Lots13085@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=meissner@spectacle-pond.org \
--cc=ookhoi@dds.nl \
/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.