On Sat, Jan 26, 2013 at 12:10 PM, Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > On Fri, Jan 25, 2013 at 6:26 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> 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-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
