From: Arjan van de Ven <arjanv@redhat.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6] don't put IDE disks in standby mode on halt on Alpha
Date: Thu, 27 May 2004 18:26:33 +0200 [thread overview]
Message-ID: <1085675193.7179.5.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20040527194920.A1709@jurassic.park.msu.ru>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
On Thu, 2004-05-27 at 17:49, Ivan Kokshaysky wrote:
> Spinning the disks down across a 'halt' on Alpha is even
> worse than doing that on reboot on i386 (assuming the
> boot device is IDE disk).
> Typically, the sequence to boot another kernel is:
> # halt
> kernel shuts down, firmware re-initializes,
> then on firmware prompt we type something like
> >>> boot -file new_kernel_image.gz
>
> Unfortunately, the firmware does not expect the IDE drive
> to be in standby mode and reports 'bootstrap failure' on
> the first and all subsequent boot attempts until the
> drive spins up, which is extremely annoying and
> confuses users a lot.
how do you flush the disks' writecache then? Halting the disk seems to
be the only reliable way to do so.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-27 16:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 15:49 Ivan Kokshaysky
2004-05-27 16:26 ` Arjan van de Ven [this message]
2004-05-27 17:11 ` Ivan Kokshaysky
2004-05-27 17:12 ` Arjan van de Ven
2004-05-27 17:41 ` Miquel van Smoorenburg
2004-05-27 16:54 ` Bartlomiej Zolnierkiewicz
2004-05-27 17:08 ` Ivan Kokshaysky
2004-05-27 17:40 ` Bartlomiej Zolnierkiewicz
2004-05-28 15:10 ` Ivan Kokshaysky
2004-05-28 15:40 ` Bartlomiej Zolnierkiewicz
2004-05-28 21:37 ` Ivan Kokshaysky
2004-05-29 18:07 ` Bartlomiej Zolnierkiewicz
2004-05-28 10:34 ` Mark McClelland
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=1085675193.7179.5.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=ink@jurassic.park.msu.ru \
--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
all inboxes | Powered by JetHome®