From: Pavel Machek <pavel@ucw.cz>
To: Alexey Fisher <bug-track@fisher-privat.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
David Brownell <dbrownell@users.sourceforge.net>,
Ingo Molnar <mingo@elte.hu>, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: PM: resume devices took 9.176 seconds
Date: Sat, 18 Jul 2009 13:49:14 +0200 [thread overview]
Message-ID: <20090718114913.GF1433@ucw.cz> (raw)
In-Reply-To: <4A52247B.4040204@fisher-privat.net>
On Mon 2009-07-06 18:21:15, Alexey Fisher wrote:
> Hallo all,
> it testing a lot git tree especially suspend and resume. With my new
> Intel DG45ID board i get always this trace:
>
> ============================================
> [ 176.763922] PM: resume devices took 9.176 seconds
> [ 176.763924] ------------[ cut here ]------------
> [ 176.763930] WARNING: at kernel/power/suspend_test.c:52
> suspend_test_finish+0x7c/0x80()
>
> this is related with the commit:
> commit 77437fd4e61f87cc94d9314baa5cbf50e3ccdf54
> Author: David Brownell <dbrownell@users.sourceforge.net>
> Date: Wed Jul 23 21:28:33 2008 -0700
>
> probobly it's depend on this message:
> [ 173.076075] ata1: link is slow to respond, please be patient (ready=0)
>
> so it's looks normal for this board and harddrive. I think it should be
> some way to change default TEST_SUSPEND_SECONDS by .config or
> kernel-parameter. I changed default settings to 10 in
> kernel/power/suspend_test.c but this is not the way it should be done.
I'm not sure if that's normal. Does it also delay on boot?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-07-18 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 16:21 PM: resume devices took 9.176 seconds Alexey Fisher
2009-07-18 11:49 ` Pavel Machek [this message]
2009-07-18 13:46 ` Alexey Fisher
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=20090718114913.GF1433@ucw.cz \
--to=pavel@ucw.cz \
--cc=bug-track@fisher-privat.net \
--cc=dbrownell@users.sourceforge.net \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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