From: SPATZ1@t-online.de (Frank Schneider)
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: AIC + RAID1 error? (was: Re: aic7xxx errors)
Date: Tue, 11 Sep 2001 00:55:13 +0200 [thread overview]
Message-ID: <3B9D44D1.E96C831F@t-online.de> (raw)
In-Reply-To: <200109102242.f8AMgpY21341@aslan.scsiguy.com>
"Justin T. Gibbs" schrieb:
>
> >> Something other made me wonder:
> >> I ran the machine several times with the *new* aic7xxx-driver (TCQ=32)
> >> and the "aic7xxx=verbose" commandline, and i noticed the following:
> >> At every reboot (made by "reboot", RH7.1), the machine was not able to
> >> stop the raid5 correctly...it un-mounted the mountpoint (/home) and then
> >> it normaly wants to stop the raid...(you see the messages "mdrecoveryd
> >> got waken up...") but that did not work and after some time (30sec) the
> >> kernel Ooopsed.
>
> ...
>
> >Same behaviour for RAID1 and the new aic7xxx driver for me at nearly every
> >reboot. The old driver works just fine (2.4.9).
>
> The new driver registers a "reboot notifier" with the system. If MD
> continues to perform I/O after the aic7xxx driver's notification routine
> is called, the result is undefined. The aic7xxx driver has already
> shutdown the hardware. Perhaps I should use a different event to indicate
> it is safe for me to clean up the hardware?
What about a kind of timer ?
If the driver gets the "reboot"-note, watch for activity and shut down
the hardware 5 or 10 secs after the last activity ?
Shutting down the Userprocesses is done in a similar way..."Send
term"...sleep 5...Send Kill..."...and when this happens, all unmounts
and kills should have already occured, so it can only be a question of
<5 secs until the last (raid-) process has exited.
Other possibility would only be to let the kernel send this message just
before he reboots the maschine via a BIOS-call...but even then you would
have to wait a little until the hardware reacts...difficult problem...
Solong...
Frank
--
Frank Schneider, <SPATZ1@T-ONLINE.DE>.
Microsoft isn't the answer.
Microsoft is the question, and the answer is NO.
... -.-
next prev parent reply other threads:[~2001-09-10 22:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 6:21 aic7xxx errors Joseph Mathewson
2001-09-05 7:58 ` Olaf Zaplinski
2001-09-05 9:04 ` Frank Schneider
2001-09-05 10:27 ` Antonio Miguel Trindade
2001-09-05 10:44 ` Frank Schneider
2001-09-05 11:21 ` Thorsten Kranzkowski
2001-09-05 13:05 ` Frank Schneider
2001-09-07 20:32 ` AIC + RAID1 error? (was: Re: aic7xxx errors) Olaf Zaplinski
2001-09-07 22:32 ` Justin T. Gibbs
2001-09-07 22:51 ` Frank Schneider
2001-09-07 23:37 ` Justin T. Gibbs
2001-09-10 13:50 ` Olaf Zaplinski
2001-09-10 19:11 ` Frank Schneider
2001-09-10 22:29 ` Andreas Steinmetz
2001-09-10 22:42 ` Justin T. Gibbs
2001-09-10 22:55 ` Frank Schneider [this message]
2001-09-10 23:06 ` Justin T. Gibbs
2001-09-10 23:37 ` Andreas Steinmetz
2001-09-10 23:46 ` Justin T. Gibbs
2001-09-11 0:00 ` Andreas Steinmetz
2001-09-11 12:10 ` Frank Schneider
2001-09-11 16:51 ` Justin T. Gibbs
2001-09-10 23:05 ` Andreas Steinmetz
2001-09-10 22:46 ` Frank Schneider
2001-09-11 15:00 ` Olaf Zaplinski
2001-09-08 20:25 ` Frank Schneider
2001-09-08 22:07 ` Justin T. Gibbs
2001-09-05 20:23 ` aic7xxx errors Justin T. Gibbs
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=3B9D44D1.E96C831F@t-online.de \
--to=spatz1@t-online.de \
--cc=gibbs@scsiguy.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