Re: Regression in 2.6.28-rc and 2.6.27-stable - hibernate related

From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Fabio Comolli <fabio.comolli@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jay Fenlason <fenlason@redhat.com>
Subject: Re: Regression in 2.6.28-rc and 2.6.27-stable - hibernate related
Date: Wed, 26 Nov 2008 21:07:29 +0100	[thread overview]
Message-ID: <492DAC81.4020803@s5r6.in-berlin.de> (raw)
In-Reply-To: <b637ec0b0811261145q3c7af010l1db0480d13b41715@mail.gmail.com>

Fabio Comolli wrote:
> Ok, I reproduced the bug with 2.6.27.7 without firewire. So the
> firewire stack is innocent after all.

That's great news for me at least.  ;-)

> FWIW, it happened after the resume, as soon as I plugged the AC
> adapter. The system became unresponsive for at least two minutes and
> then "resurrected" as nothing happened. Nothing in the logs and the
> dmesg is clean.
> 
> I ran out of ideas. I'm trying 2.6.27.4, the kernel then never showed
> the problem.

The 2.6.27.5 changelog shows a bunch of ACPI changes.  They may not be
responsible, but in my uninformed opinion these are the changes to look
at more closely.  Since plain bisection did not work well for you, maybe
you should ask the maintainers involved in the ACPI patches for a
priority list of patches to unapply for long-term tests.

Also look at the diffstat whether there were changes to drivers which
you use.

Furthermore, maybe the few scheduler changes may play a role.  But I
don't understand what they do, so I may be completely off.

http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.27.5
http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv2.6%2Fincr%2Fpatch-2.6.27.4-5.bz2
-- 
Stefan Richter
-=====-==--- =-== ==-=-
http://arcgraph.de/sr/