linux-kernel - Re: Regression in 2.6.28-rc and 2.6.27-stable

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: <200811270002.29537.rjw@sisk.pl>
Date:	Thu, 27 Nov 2008 00:02:29 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Stefan Richter <stefanr@...6.in-berlin.de>,
	Fabio Comolli <fabio.comolli@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jay Fenlason <fenlason@...hat.com>
Subject: Re: Regression in 2.6.28-rc and 2.6.27-stable - hibernate related

On Wednesday, 26 of November 2008, Stefan Richter wrote:
> 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.

Actually, yes, Fabio, you can try to revert all of the "ACPI: EC:" commits
applied after 2.6.27.4 and retest.

Thanks,
Rafael
--
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/