From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjanv@redhat.com>
Subject: Re: Linux 2.6.6 "IDE cache-flush at shutdown fixes"
Date: Mon, 10 May 2004 23:52:24 +0200 [thread overview]
Message-ID: <200405102352.24091.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <409FF068.30902@keyaccess.nl>
On Monday 10 of May 2004 23:13, you wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > Rene, can you test these (incremental) patches?
> >
> > + if (drive->usage != 1)
> > + return 0;
>
> Only this one does not make a change.
>
> > - if (drive->usage != 1)
> > + if (drive->usage != 1 || !drive->removable)
Thanks.
Rene, can you send me copies of /proc/ide/hda/identify and
/proc/ide/hdc/identify? I still would like to know why these
drives don't accept flush cache commands (or it is a driver's bug?).
> With this one, the cache flushing noise is no more, but still a problem
> unfortunately. With or without these patches, 2.6.6 powers down the
> drive during reboot. This is very annoying, seeing as how it immediately
> needs to spin up again for POST.
There is a problem with new 2.6 generic ->shutdown framework,
it doesn't differentiate between reboot / halt and power_off.
We may try to fix it or revert to 2.4 way of doing things if
this is too big change for 2.6.
Thanks,
Bartlomiej
next prev parent reply other threads:[~2004-05-11 0:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 9:20 Rene Herman
2004-05-10 11:32 ` Gene Heskett
2004-05-10 12:04 ` Rene Herman
2004-05-10 20:28 ` Arjan van de Ven
2004-05-10 19:25 ` Bartlomiej Zolnierkiewicz
2004-05-10 21:13 ` Rene Herman
2004-05-10 21:52 ` Bartlomiej Zolnierkiewicz [this message]
2004-05-11 4:56 ` Andrew Morton
2004-05-11 5:17 ` Andrew Morton
2004-05-11 11:24 ` Rene Herman
[not found] ` <200405111537.23535.bzolnier@elka.pw.edu.pl>
[not found] ` <40A1073E.3030605@keyaccess.nl>
2004-05-11 19:06 ` Rene Herman
[not found] ` <200405120236.00085.bzolnier@elka.pw.edu.pl>
2004-05-12 14:44 ` Rene Herman
2004-05-11 21:22 ` Mike Houston
2004-05-11 22:05 ` Bill Davidsen
2004-05-14 3:26 ` Pavel Machek
2004-05-15 0:53 ` Andrew Morton
2004-05-15 0:59 ` Andrew Morton
2004-05-15 1:05 ` Bartlomiej Zolnierkiewicz
2004-05-15 5:53 ` Herbert Xu
2004-05-15 6:16 ` Andrew Morton
2004-05-17 22:13 ` Greg KH
2004-05-17 22:55 ` Andrew Morton
2004-05-14 3:25 ` Pavel Machek
2004-05-11 11:24 ` Rene Herman
2004-05-11 12:56 ` Craig Bradney
2004-05-11 15:51 ` Athanasius
2004-05-11 16:10 ` dobrev
2004-05-12 18:07 ` Bartlomiej Zolnierkiewicz
2004-05-12 18:45 ` dobrev
2004-05-13 0:24 ` Patrick Wildi
2004-05-13 9:55 ` dobrev
2004-05-10 21:59 ` Rene Herman
2004-05-10 23:36 ` Mike Houston
2004-05-14 21:49 ` scsi shutdown flush, journaled fses Tom Vier
[not found] <fa.jr282gn.1ni2t37@ifi.uio.no>
[not found] ` <fa.cmd38j8.1tgg9ro@ifi.uio.no>
2004-05-12 6:09 ` Linux 2.6.6 "IDE cache-flush at shutdown fixes" Robert Hancock
2004-05-12 18:52 ` Eric D. Mudama
2004-05-12 19:55 ` Rene Herman
2004-05-12 21:05 ` Bartlomiej Zolnierkiewicz
2004-05-12 22:27 ` Rene Herman
2004-05-12 21:28 ` Gene Heskett
2004-05-13 17:41 ` Eric D. Mudama
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=200405102352.24091.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
--cc=torvalds@osdl.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®