From: Rogier Wolff <R.E.Wolff@Harddisk-recovery.com>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
andersen@codepoet.org, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] prevent module unloading for legacy IDE chipset drivers
Date: Mon, 26 Apr 2004 08:31:37 +0200 [thread overview]
Message-ID: <20040426063137.GB11567@bitwizard.nl> (raw)
In-Reply-To: <20040422103355.GC15176@harddisk-recovery.com>
On Thu, Apr 22, 2004 at 12:33:55PM +0200, Erik Mouw wrote:
> On Thu, Apr 22, 2004 at 02:50:15AM +0200, Bartlomiej Zolnierkiewicz wrote:
> > On Thursday 22 of April 2004 02:41, Erik Andersen wrote:
> > > Out of curiosity, what would be needed to make it safe to unload
> > > all ide modules from a system with a scsi rootfs?
> >
> > It doesn't matter - you still may end up unloading modules which are in use.
>
> FWIW, with the old IDE code I've been unloading IDE modules for years
> without a single problem.
Hmm. Not completely true: It crashes on our VIA EPIA board. Would
anybody have an idea why it works on most systems, but crashes
hard on the VIA EPIA? (I'm not sure wether it crashes the hardware
or the software).
Roger.
--
+-- Rogier Wolff -- www.harddisk-recovery.nl -- 0800 220 20 20 --
| Files foetsie, bestanden kwijt, alle data weg?!
| Blijf kalm en neem contact op met Harddisk-recovery.nl!
prev parent reply other threads:[~2004-04-26 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 20:19 [PATCH] prevent module unloading for legacy IDE chipset drivers Bartlomiej Zolnierkiewicz
2004-04-22 0:41 ` Erik Andersen
2004-04-22 0:50 ` Bartlomiej Zolnierkiewicz
2004-04-22 10:33 ` Erik Mouw
2004-04-22 14:35 ` Bartlomiej Zolnierkiewicz
2004-04-26 13:50 ` Erik Mouw
2004-04-26 14:50 ` Bartlomiej Zolnierkiewicz
2004-04-26 15:02 ` Bartlomiej Zolnierkiewicz
2004-04-26 15:23 ` Erik Mouw
2004-04-26 15:54 ` Bartlomiej Zolnierkiewicz
2004-04-26 6:31 ` Rogier Wolff [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=20040426063137.GB11567@bitwizard.nl \
--to=r.e.wolff@harddisk-recovery.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=andersen@codepoet.org \
--cc=erik@harddisk-recovery.com \
--cc=linux-ide@vger.kernel.org \
--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 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.