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+icZUWqdPz5xFRYy6UMjN9QQNq61oJ=fP_KGOt5SH3o0DH62Q@mail.gmail.com>
Date:	Sat, 26 Jan 2013 13:05:53 +0100
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	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 12:10 PM, Sedat Dilek <sedat.dilek@...il.com> 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?
>
> Thanks!
>
> Regards,
> - Sedat -
>
> [1] http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=blob;f=kernel/watchdog.c;hb=refs/tags/next-20130125#l245

Just FYI:

Linux-Next (next-20130124) is also BROKEN on suspend here.

Latest GOOD is next-20130123... next-20130121 was also GOOD (I had
tested some days ago).

- 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/