LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Karsten Wiese <fzu@wemgehoertderstaat.de>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.25-rc2 rcupreempt WARN after suspend to ram
Date: Sun, 24 Feb 2008 16:38:15 +0100 [thread overview]
Message-ID: <200802241638.15902.fzu@wemgehoertderstaat.de> (raw)
In-Reply-To: <200802231754.01681.fzu@wemgehoertderstaat.de>
Am Samstag, 23. Februar 2008 schrieb Karsten Wiese:
> Am Samstag, 23. Februar 2008 schrieb Paul E. McKenney:
> > On Sat, Feb 23, 2008 at 01:41:02PM +0100, Karsten Wiese wrote:
> > > Hi,
> > >
> > > This appeared in dmesg after
> > > $ echo core > /sys/power/pm_test
> > > followed by 3 cycles of
> > > $ echo mem > /sys/power/state
> > > . .config attached.
> > >
> > > dmesg excerpt (, full ~1MByte available):
> >
> > Does this tree have http://lkml.org/lkml/2008/1/29/208 applied?
>
> Yes. This tree was linus' git head as of yesterday or the day before.
Updated to git-head of today, same test and .config, different symptoms
like in this thread: http://lkml.org/lkml/2008/2/23/260
Later in this thread, Alan Cox said it looked like irq problems.
Maybe also the rcupreemt related WARN_ON I saw are caused by irq problems.
Thanks,
Karsten
next prev parent reply other threads:[~2008-02-24 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 12:41 Karsten Wiese
2008-02-23 15:52 ` Paul E. McKenney
2008-02-23 16:54 ` Karsten Wiese
2008-02-24 15:38 ` Karsten Wiese [this message]
[not found] ` <20080224182800.GA10194@linux.vnet.ibm.com>
2008-02-26 2:09 ` Karsten Wiese
2008-02-26 21:15 ` Karsten Wiese
2008-02-26 21:41 ` Rafael J. Wysocki
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=200802241638.15902.fzu@wemgehoertderstaat.de \
--to=fzu@wemgehoertderstaat.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--subject='Re: 2.6.25-rc2 rcupreempt WARN after suspend to ram' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).