From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753415Ab1IUM3V (ORCPT ); Wed, 21 Sep 2011 08:29:21 -0400 Received: from cantor2.suse.de ([195.135.220.15]:46006 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751492Ab1IUM3U (ORCPT ); Wed, 21 Sep 2011 08:29:20 -0400 Date: Wed, 21 Sep 2011 14:29:19 +0200 Message-ID: From: Takashi Iwai To: =?UTF-8?B?w4lyaWM=?= Brunet Cc: linux-kernel@vger.kernel.org Subject: Re: Regression between 2.6.35 and 2.6.38 (freeze at resume) In-Reply-To: <201109202206.35705.Eric.Brunet@lps.ens.fr> References: <201109170935.17777.Eric.Brunet@lps.ens.fr> <201109202206.35705.Eric.Brunet@lps.ens.fr> User-Agent: Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.7 Emacs/23.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Tue, 20 Sep 2011 22:06:35 +0200, Éric Brunet wrote: > > I reported a bug three days ago about my computer occasionaly not waking up > (see below) and I have since compiled several kernels to see when the bug > arrived. > > Till now, I have seen the bug trigger on a vanilla 2.6.39-rc3. (Only once, in > about ten suspend/resume) and I haven't seen it trigger in 2.6.38 nor 2.6.39- > rc1. I am now running 2.6.39-rc1 to see if the bug will eventualy trigger or > not. > > The WARNING with call trace on the fedora kernel that I reported in my > previous message (see below) also happened in the vanilla kernel in exactly > the same way. After that initial WARNING, I had four more WARNINGS and one BUG > in rapid succession, and one final BUG 14 seconds later. > > I'd like to know what I can do to help nail this annoying bug. I am not sure > if I can git bisect it; it is hard to tell offhand if a kernel is good; it may > resume correctly many times before crashing. Did you try the recent 3.1-rc? There have been a few commits relevant with battery module and PM after 3.0, and I guess this will be the fix for your case, too. Takashi