From: "Tuncer Ayaz" <tuncer.ayaz@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.22 libata spindown
Date: Fri, 1 Jun 2007 22:14:51 +0200 [thread overview]
Message-ID: <4ac8254d0706011314g5468f02m3cf5a5281bd30018@mail.gmail.com> (raw)
I'm still seeing the libata warning that disks were not spun down
properly on the following two setups and am wondering whether I need
a new shutdown binary or the changeset mentioned below is not meant
to fix what I'm triggering by halt'ing.
If it's not a bug I will try to update my shutdown utility and if
that does not work I promise not to bother lkml about a problem
caused by my userland. If it is a bug I hope it will be of interest
for 2.6.22 bug tracking.
Setup 1:
SATA 1 Disks
AMD64 3200+
nVidia nForce 3 250 (Ultra?)
Debian i386 Unstable
Setup 2:
SATA 2 disks
Core 2 Duo E6600
Intel 975X
Debian x86_64 Unstable
Just to be clear what warning I'm talking about:
DISK MIGHT NOT BE SPUN DOWN PROPERLY. UPDATE SHUTDOWN UTILITY
For more info, visit http://linux-ata.org/shutdown.html
The following is from the reply I got from Michal Piotrowski while
I was trying to find out what happened to the regression report:
MICHAL>>
I guess you meant this
Subject : libata crash on halt
References : http://marc.info/?l=linux-ide&m=117899827710565&w=2
Submitter : Andrew Morton <akpm@linux-foundation.org>
Caused-By : Tejun Heo <htejun@gmail.com>
commit 920a4b1038e442700a1cfac77ea7e20bd615a2c3
Status : problem is being debugged
This bug was fixed by
commit da071b42f73dabbd0daf7ea4c3ff157d53b00648
Author: Tejun Heo <htejun@gmail.com>
Date: Mon May 14 17:26:18 2007 +0200
libata: fix shutdown warning message printing
Unlocking ap->lock and ssleeping don't work because SCSI commands can
be issued from completion path without context. Reimplement delayed
completion by allowing translation functions to override
qc->scsidone(), storing the original completion function to
scmd->scsi_done() and overriding qc->scsidone() with a function which
schedules delayed invocation of scmd->scsi_done().
This isn't pretty at all but all the ugly parts are thankfully
contained in the stop translation path where the compat feature is
implemented.
Signed-off-by: Tejun Heo <htejun@gmail.com>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
> [ 715.196000] ata3.00: DISK MIGHT NOT BE SPUN DOWN PROPERLY. UPDATE
> SHUTDOWN UTILITY
> [ 715.196000] ata3.00: For more info, visit http://linux-ata.org/
> shutdown.html
^^^^
If you think about this, please send a bug report. IMHO it's ABI breakage.
<<MICHAL
next reply other threads:[~2007-06-01 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 20:14 Tuncer Ayaz [this message]
2007-06-01 20:39 ` Jeff Garzik
2007-06-01 20:55 ` Tuncer Ayaz
2007-06-02 3:23 ` Henrique de Moraes Holschuh
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=4ac8254d0706011314g5468f02m3cf5a5281bd30018@mail.gmail.com \
--to=tuncer.ayaz@gmail.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
all inboxes | Powered by JetHome®