linux-kernel - Re: Regression between 2.6.35 and 2.6.38 (freeze at resume)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20110923093704.GB8971@lps.ens.fr>
Date:	Fri, 23 Sep 2011 11:37:04 +0200
From:	Éric Brunet <Eric.Brunet@....ens.fr>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Regression between 2.6.35 and 2.6.38 (freeze at resume)


Dans son message du jeudi 22/09/11 à  7:32, Takashi Iwai a écrit:
> 
> As mentioned, the series of patches were added first in 3.1-rc.
> 3.0.x have no these commits.
> 
3.1-rc6 crashed on me this morning at resume time. Unfortunately, nothing
appeared in the logs so I cannot be 100% sure it is the same bug as has
been hitting me since circa 2.6.38, but it looks the same.

What should I do now ? Run 3.1-rc7 and hope for the best ? Go on with
3.1-rc6 and hope that I'll get a crash with information in the logs so as
to make sure it is indeed the same bug ? Or go back to 2.6.38 to try to
pinpoint the first problematic kernel and (hopefully) the change that
introduced the problem ?

Thanks,

	Éric Brunet
--
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/