lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 8 Aug 2007 14:27:00 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Robert Hancock <hancockr@...w.ca>
Cc:	Henrique de Moraes Holschuh <hmh@....eng.br>,
	Tejun Heo <htejun@...il.com>,
	Michael Sedkowski <sedmich@...il.com>,
	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org,
	linux-acpi@...r.kernel.org
Subject: Re: Disk spin down issue on shut down/suspend to disk

On Wednesday, 8 August 2007 02:23, Robert Hancock wrote:
> Henrique de Moraes Holschuh wrote:
> > On Tue, 07 Aug 2007, Tejun Heo wrote:
> >> Henrique de Moraes Holschuh wrote:
> >>> On Tue, 07 Aug 2007, Tejun Heo wrote:
> >>>> Michael Sedkowski wrote:
> >>>>>> Hmmm... If the problem only shows up on nx6325, it might be that ACPI is
> >>>>>> pulling unnecessary stunt.  Please apply the attached patch and report
> >>>>>> when the disk spins down and up.
> >>>>> Disk spins down on "Pre-shutdown prepare" and then goes up and down on
> >>>>> "Power down".
> >>>> Oh... crap, so acpi wants to sync cache on shutdown.  I wonder whether
> >>>> it spins down the disk correctly.  Does emergency unload count increase
> >>>> after each power down?  Also, please post the result of 'dmidecode'.
> >>> You know, this actually make a lot of sense, and one can't even complain
> >>> about firmware that pulls that off.
> >> Well, I'm complaining.  I think the problem here is that it isn't clear
> >> which one is who's responsibility.  There's a Korean saying which
> > 
> > The BIOS *has* to do it when in DOS mode, the HD manuals are very very clear
> > about it.  Doing it through ACPI ATA objects is at least non-broken as far
> > as these things go, as one knows when to do it directly ("non-ACPI mode"),
> > and one doesn't talk to the disk directly.
> > 
> >> approximately translates into "if you have too many boatmen on a ship,
> >> it goes to mountain".  We also have a bunch of Toshiba laptops which
> > 
> > Yeah, that's a problem.  But we can avoid it if we start snooping what ACPI
> > is asking us to deliver to the disks, which IMO is an extremely good idea
> > anyway.
> 
> Problem is I don't think we can do this. As far as I can tell, on my 
> Compaq at least, it's not being done through ACPI AML in the DSDT, like 
> in the _PTS function (which the kernel executes and can snoop), but when 
> we actually do the power-off we write a value to a magic ACPI register. 
> That likely triggers the BIOS to take control in SMM mode and access the 
> controller directly before triggering the power off, which we have no 
> control or knowledge of.

Yes, this also is my observation.

Greetings,
Rafael


-- 
"Premature optimization is the root of all evil." - Donald Knuth
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ