linux-kernel - Re: Regression in ACPI in 2.6.31-rc5

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>] [day] [month] [year] [list]

Date:	Fri, 14 Aug 2009 20:36:01 +0100
From:	Ricardo Jorge da Fonseca Marques Ferreira <storm@...49152.net>
To:	Len Brown <lenb@...nel.org>
Cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: Regression in ACPI in 2.6.31-rc5

Resending with the lists CCed.

On Thursday 13 August 2009, you wrote:
> > I had two drivers stop working in 2.6.31 that were working fine in
> > 2.6.30. They are iwlagn and sky2. If i pass acpi=off to the kernel, they
> > work as expected.
>
> the bug report for this issue is here:
> http://bugzilla.kernel.org/show_bug.cgi?id=13940
>
> is it possible to bisect which commit between 2.6.30 and 2.6.31-rc5
> caused this regression?
>
> Please attach the dmesg from the working 2.6.30
> and the acpi=off 2.6.31 to the bug report so i can compare
> them to the failing 2.6.31

All dmesgs are attached. I also checked and 2.6.31-rc1 already has the bug. 
2.6.30.4 doesn't have the bug.

I'll have to look at some documentation on how to use git bisect. If you have 
some links, please send.

Thanks

View attachment "dmesg-working-2.6.31_acpi=off.log" of type "text/x-log" (55759 bytes)

View attachment "dmesg-not-working-2.6.31.log" of type "text/x-log" (64902 bytes)

View attachment "dmesg-working-2.6.30.log" of type "text/x-log" (63378 bytes)