From: "Rafael J. Wysocki" <rjw@sisk•pl>
To: sedat.dilek@gmail•com
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Linux PM List <linux-pm@lists•linux-foundation.org>,
Linux ACPI <linux-acpi@vger•kernel.org>,
Sasha Levin <sasha.levin@oracle•com>
Subject: Re: linux-next: Tree for Jan 25 (BROKEN suspend)
Date: Sat, 26 Jan 2013 14:25:47 +0100 [thread overview]
Message-ID: <1378199.89Y5N0mHyy@vostro.rjw.lan> (raw)
In-Reply-To: <CA+icZUW6LBSjpqK-eQUAt7R=kXCPRjFoi=z1UijaajrVAj=fEg@mail.gmail.com>
On Saturday, January 26, 2013 12:10:32 PM Sedat Dilek wrote:
> On Fri, Jan 25, 2013 at 6:26 AM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> > Hi all,
> >
> > Changes since 20130124:
> >
> > New trees: ipsec and ipsec-next
> >
> > The powerpc tree still had a build failure.
> >
> > The sound-asoc tree still had its build failure so I used the version from
> > next-20130122.
> >
> > The akpm tree lost its build failure and several patches that turned up
> > elsewhere.
> >
> > ----------------------------------------------------------------------------
> >
>
> Unfortunately, on suspend or running the pm_test/freezer leads here to
> a frozen machine - hard reset.
>
> I see 4-5 pages of call-traces but dunno how to log them in such a f-u-ed state.
> Any hints welcome!
>
> As I saw catched with my left eye on one call-trace sth. with...
>
> kernel/watchdog.c (line #245, watchdog_overflow_callback)
>
> ... I tried to revert the last two commits from Sascha (see -3 patch,
> but no success.
>
> The same with reverting all cpu-freq changes since v3.8-rc4 (see -4
> patch) after seeing some suspicious lines on the screen.
>
> Can someone confirm that suspend is BROKEN for him/her before doing
> eventually a bisect?
Can you please test the linux-next branch of the linux-pm.git tree alone?
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-01-26 13:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 11:10 linux-next: Tree for Jan 25 (BROKEN suspend) Sedat Dilek
2013-01-26 12:05 ` Sedat Dilek
2013-01-26 13:25 ` Rafael J. Wysocki [this message]
2013-01-26 13:24 ` Sedat Dilek
2013-01-26 14:33 ` Sedat Dilek
2013-01-26 15:05 ` Sedat Dilek
2013-01-26 18:27 ` Sedat Dilek
2013-01-26 21:49 ` Rafael J. Wysocki
2013-01-27 13:01 ` Sedat Dilek
2013-01-28 19:28 ` Tejun Heo
2013-01-28 22:06 ` Sedat Dilek
2013-01-28 22:08 ` Tejun Heo
2013-01-28 22:18 ` Sedat Dilek
2013-01-28 22:30 ` James Hogan
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=1378199.89Y5N0mHyy@vostro.rjw.lan \
--to=rjw@sisk$(echo .)pl \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-pm@lists$(echo .)linux-foundation.org \
--cc=sasha.levin@oracle$(echo .)com \
--cc=sedat.dilek@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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