linux-kernel - Re: linux-next: Tree for Jan 25 (BROKEN suspend)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+icZUX=XdAJjWwx8P_y31JGW3GC+tdWuFhv2Ym-0OELGWGbDQ@mail.gmail.com>
Date:	Sat, 26 Jan 2013 16:05:53 +0100
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Linux PM List <linux-pm@...ts.linux-foundation.org>,
	Linux ACPI <linux-acpi@...r.kernel.org>,
	Sasha Levin <sasha.levin@...cle.com>
Subject: Re: linux-next: Tree for Jan 25 (BROKEN suspend)

On Sat, Jan 26, 2013 at 3:33 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
> On Sat, Jan 26, 2013 at 2:24 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
>> On Sat, Jan 26, 2013 at 2:25 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
>>> On Saturday, January 26, 2013 12:10:32 PM Sedat Dilek wrote:
>>>> On Fri, Jan 25, 2013 at 6:26 AM, Stephen Rothwell <sfr@...b.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?
>>>
>>
>> That sounds like a good idea as I just reverted "cpu-hotplug,
>> memory-hotplug: try offlining the node when hotremoving a cpu" [1]
>> from akpm tree.
>> Building... 1st with revert than trying pm-next only.
>>
>
> Your pm-next tree is fine here.
>
> commit 0b9d032a2bf0a0224ef446f3d6048fdd8a5b8280
> "Merge branch 'pm-cpufreq-next' into linux-next linux-next"
>
> Furthermore, the culprit is not between akpm-master and akpm-current
> as I have seen cpu/mem hotplug and pm changes there.
>
> Hmm, maybe bisecting would have been faster than hunting on suspicious commits.
>
> - Sedat -
>
>> - Sedat -
>>
>> [1] http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=154cb61f36690edef68beb5fd9dc0a5027f9dbd9
>>
>>> Rafael
>>>
>>>
>>> --
>>> I speak only for myself.
>>> Rafael J. Wysocki, Intel Open Source Technology Center.

I merged on top of my Linux-v3.8-rc5 GIT branch...

Sedat Dilek (8):
      mei: Fix some more kernel-doc typos in hw-me.c
      kbuild: deb-pkg: Try to determine distribution
      kbuild: deb-pkg: Bump year in debian/copyright file
      kbuild: deb-pkg: Update git repository URL in debian/copyright file
      Merge tag 'next-20130124' of
git://git.kernel.org/.../next/linux-next into Linux-Next-v20130124
      Merge branch 'deb-pkg-fixes' into 3.8.0-rc5-next20130124-1-pmnext-generic
      Merge branch 'Linux-Next-v20130124' into
3.8.0-rc5-next20130124-1-pmnext-generic
      Merge branch 'pm-next' into 3.8.0-rc5-next20130124-1-pmnext-generic

...and this f-u-s the machine as well.
So, the culprit seems not to get from your PM stuff.

Anyway, this does not help me... but hope it's good news for you, Rafael :-)!

- Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/