From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: 2.6.25-rc2 regression - hang on suspend
Date: Fri, 22 Feb 2008 16:56:28 +0100 [thread overview]
Message-ID: <200802221656.28546.rjw@sisk.pl> (raw)
In-Reply-To: <1203663628.8422.2.camel@localhost>
On Friday, 22 of February 2008, Soeren Sonnenburg wrote:
> On Fri, 2008-02-22 at 00:06 +0100, Rafael J. Wysocki wrote:
> > On Thursday, 21 of February 2008, Soeren Sonnenburg wrote:
> > > On Thu, 2008-02-21 at 01:31 +0100, Rafael J. Wysocki wrote:
> > > > On Wednesday, 20 of February 2008, Soeren Sonnenburg wrote:
> > > > > On Wed, 2008-02-20 at 00:50 +0100, Rafael J. Wysocki wrote:
> [...]
> > > Using echo none >/sys/power/pm_test and then
> > > echo mem >/sys/power/state I see it hang on ata1 errors again. Waiting
> > > about 10-30 seconds it progresses further and finally arrives at
> > >
> > > CPU0 attaching NULL sched-domain
> > > CPU1 attaching NULL sched-domain
> > >
> > > then hangs.
> >
> > Please see if compiling the kernel with CONFIG_SMP unset makes suspend
> > work.
>
> *Argh*, this bug is not behaving nicely :( Whatever happened,
> git-current now suspends correctly with and without CONFIG_SMP and all
> may CONFIG_PREEMPT_RCU=y and CONFIG_CLASSIC_RCU=y attempts. Also no sata
> errors anymore.
>
> However it is not reliably waking up (at least when all of the above
> except CLASSIC_RCU is on). Sometimes the display remains black on the
> console, but X still works and sometimes it hangs completely on resume.
I have created the Bugzilla entry at http://bugzilla.kernel.org/show_bug.cgi?id=10065
for this issue. Please add yourself to the CC list in there and update it with
any new findings.
> Also when compiling these many kernels via make -j4 I noted that I could
> hardly move the mouse / use the keyboard, but saw random jumps and
> key-repetitions...
This last bit is most likely a scheduler issue. Do you have CONFIG_GROUP_SCHED
set by chance? If you do, please try to unset it and see if that helps.
Thanks,
Rafael
next prev parent reply other threads:[~2008-02-22 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 11:59 Soeren Sonnenburg
2008-02-19 13:12 ` Tino Keitel
2008-02-19 21:06 ` Rafael J. Wysocki
2008-02-19 21:59 ` Soeren Sonnenburg
2008-02-19 23:50 ` Rafael J. Wysocki
2008-02-20 6:01 ` Soeren Sonnenburg
2008-02-21 0:31 ` Rafael J. Wysocki
2008-02-21 10:04 ` Soeren Sonnenburg
2008-02-21 23:06 ` Rafael J. Wysocki
2008-02-22 7:00 ` Soeren Sonnenburg
2008-02-22 15:56 ` Rafael J. Wysocki [this message]
2008-02-23 7:38 ` Soeren Sonnenburg
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=200802221656.28546.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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®