tags 665493 patch
quit

As noted in the upstream bugzilla, the bug is fixed in kernel 3.6,
in commit dfb117b3e50c52c7b3416db4a4569224b8db80bb ,
"PCI: acpiphp: check whether _ADR evaluation succeeded".

Attached as a patch below. Applying this on top of 3.2.30 fixes the
problem indeed (and without the patch that still fails).
Would it be possible to apply this to the Debian kernel?

Thanks,

Jeroen Nijhof

On Sun, 2012-10-07 at 10:29 +0200, Jeroen Nijhof wrote:
> tags 665493 patch
> quit
>
> As noted in the upstream bugzilla, the bug is fixed in kernel 3.6,
> in commit dfb117b3e50c52c7b3416db4a4569224b8db80bb ,
> "PCI: acpiphp: check whether _ADR evaluation succeeded".
>
> Attached as a patch below. Applying this on top of 3.2.30 fixes the
> problem indeed (and without the patch that still fails).
> Would it be possible to apply this to the Debian kernel?

This is under review for inclusion in 3.2.31.

Ben.

--
Ben Hutchings
Who are all these weirdos? - David Bowie, about L-Space IRC channel #afp

I can confirm that the bug is fixed in kernel 3.6 and that applying the
patch provided by Jeroen in Message #71 ("PCI: acpiphp: check whether
_ADR evaluation succeeded") on top of 3.2.30 solves the problem.

Thanks!
Stefan.


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/1349707771.4421.6.camel@rosa