From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "Starikovskiy, Alexey Y" <alexey.y.starikovskiy@intel.com>
Cc: linux-acpi@vger.kernel.org, "Brown, Len" <len.brown@intel.com>
Subject: Re: Bad libata resume behaviour due to ACPICA change (in acpi-test)
Date: Thu, 8 Feb 2007 13:30:25 -0200 [thread overview]
Message-ID: <20070208153025.GA466@khazad-dum.debian.net> (raw)
In-Reply-To: <B41635854730A14CA71C92B36EC22AAC803F9D@mssmsx411>
On Mon, 05 Feb 2007, Starikovskiy, Alexey Y wrote:
> I cannot reproduce your problem with T43 here on linux-acpi-test with
> defconfig (relevant ACPI modules were tried both dynamic and static).
> Resume time is about 4-6 seconds, not 20-40 as you mention.
> Could you please send your .config and try defconfig on your machine?
Sorry for the delay on doing the tests. 2.6.20+acpi-test defconfig does NOT
do ACPI S3, so I had to use defconfig with SMP turned off (that was the only
change). Are you sure you tried linux-acpi-test in 2.6.20 defconfig without
any changes?
gcc is Debian 3.4.6-5. I am avoiding 4.1.1 because of the reports of it
miscompiling the kernel sometimes.
The bug changed behaviour a little in defconfig. Now, I get the "Restarting
tasks ... done" right away after the line that used to hang (SCSI device
sda: write cache...", and THEN it hangs for about 20s.
In my default T43 kernel, I get "Restarting tasks ... done" *before* the
(SCSI device sda: write cache..." line.
So the hang is still there, it is still 100% reproducible here, but I am not
sure it has much to do with libata. It might have something to do with
whatever happens after "Restarting tasks ... done", and libata resume just
happens to be running in another thread at that time and outputs its stuff
through printk.
Any ideas on how to debug this further?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2007-02-08 15:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-03 0:41 Bad libata resume behaviour due to ACPICA change (in acpi-test) Henrique de Moraes Holschuh
2007-02-05 18:51 ` Starikovskiy, Alexey Y
2007-02-05 23:59 ` Henrique de Moraes Holschuh
2007-02-06 12:17 ` Starikovskiy, Alexey Y
2007-02-06 13:39 ` T43 BIOS and AHCI Henrique de Moraes Holschuh
2007-02-06 14:02 ` Alexey Starikovskiy
2007-02-08 15:30 ` Henrique de Moraes Holschuh [this message]
2007-02-08 17:50 ` Bad libata resume behaviour due to ACPICA change (in acpi-test) Alexey Starikovskiy
2007-02-08 18:20 ` Starikovskiy, Alexey Y
2007-02-09 3:02 ` Henrique de Moraes Holschuh
2007-02-09 6:31 ` Starikovskiy, Alexey Y
2007-02-09 2:59 ` Henrique de Moraes Holschuh
2007-02-09 15:10 ` Alexey Starikovskiy
2007-02-09 18:58 ` 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=20070208153025.GA466@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=alexey.y.starikovskiy@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@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