From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jens Axboe <axboe@suse.de>
Cc: Erik Mouw <erik@harddisk-recovery.com>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
ide <linux-ide@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
jgarzik <jgarzik@pobox.com>
Subject: Re: [PATCH 1/4] SATA ACPI build (applies to 2.6.16-git9)
Date: Mon, 16 Jan 2006 23:00:36 +0000 [thread overview]
Message-ID: <1137452436.15553.93.camel@localhost.localdomain> (raw)
In-Reply-To: <20060116224626.GS3945@suse.de>
On Llu, 2006-01-16 at 23:46 +0100, Jens Axboe wrote:
> > If you really need this enabled to be able to use suspend/resume at
> > all, you could add a line like:
> >
> > It's safe to say Y. If you say N, you might get serious disk
> > corruption when you suspend your machine.
>
> That's simply not true. If you say N (if you could), you could risk
> having a non-responsive disk after resume. However, it would have been
> synced a suspend time so you wont corrupt anything.
If you do not execute the ACPI taskfiles for the device and you are
doing an ACPI suspend you are in completely undefined space. Whether it
eats your disk or not is a question of probabilities only. Yes its
unlikely but you are in undefined space so "won't corrupt anything"
indicates an inappropriate level of certainty.
Fortunately it is better than the old PATA layer where as far as I can
tell if the BIOS resume restores the BIOS HPA setup you may actually end
up doing more damage by running ACPI taskfiles as we don't appear to
restore enough drive state.
Alan
next prev parent reply other threads:[~2006-01-16 22:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 6:42 Randy.Dunlap
2006-01-14 6:44 ` [PATCH 2/4] libata debugging support Randy.Dunlap
2006-01-14 6:45 ` [PATCH 3/4] SATA ACPI objects support Randy.Dunlap
2006-01-14 6:45 ` [PATCH 4/4] additional libata parameters Randy.Dunlap
2006-01-18 0:35 ` [PATCH 2/4] libata debugging support Jeff Garzik
2006-01-14 7:28 ` [PATCH 1/4] SATA ACPI build (applies to 2.6.16-git9) Sam Ravnborg
2006-01-14 7:30 ` Randy.Dunlap
2006-01-16 11:56 ` Erik Mouw
2006-01-16 14:07 ` Erik Mouw
2006-01-16 21:04 ` Adrian Bunk
2006-01-17 9:01 ` Erik Mouw
2006-01-17 11:27 ` Adrian Bunk
2006-01-16 22:46 ` Jens Axboe
2006-01-16 22:48 ` Randy.Dunlap
2006-01-16 23:00 ` Alan Cox [this message]
2006-01-16 23:10 ` Jens Axboe
2006-01-18 12:24 ` Pavel Machek
2006-01-17 9:09 ` Erik Mouw
2006-01-16 15:40 ` Randy.Dunlap
2006-01-16 12:31 ` Jens Axboe
2006-01-16 15:37 ` Randy.Dunlap
2006-01-16 15:44 ` Jens Axboe
2006-01-16 15:51 ` Alan Cox
2006-01-16 15:52 ` Jens Axboe
2006-01-16 15:58 ` Randy.Dunlap
2006-01-16 16:02 ` Jens Axboe
2006-01-16 16:08 ` Randy.Dunlap
2006-01-16 22:43 ` Jens Axboe
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=1137452436.15553.93.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=erik@harddisk-recovery.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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®