linux-kernel - Re: [PATCH 2.6.34-rcX] Do not expect PCI devices to return zeroes in PCIe space

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]

Date:	Fri, 14 May 2010 13:51:13 -0700
From:	Petr Vandrovec <petr@...drovec.name>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	Jacob Pan <jacob.jun.pan@...el.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>, dcovelli@...are.com
Subject: Re: [PATCH 2.6.34-rcX] Do not expect PCI devices to return zeroes in 
	PCIe space

On Fri, May 14, 2010 at 11:37 AM, H. Peter Anvin <hpa@...or.com> wrote:
> On 04/30/2010 07:54 PM, Petr Vandrovec wrote:
>> Hello,
>>   openSUSE11.3 32bit kernels hang when installed to the VMware's VMs because Moorestown
>> fixed capabilities detection code enters endless loop on Intel's AGP bridges (with
>> device ID=7191).  See https://bugzilla.kernel.org/show_bug.cgi?id=15888 for additional
>> details.  arch/x86/pci/mrst.c was introduced after 2.6.33, so only 2.6.34-rcX are
>> affected.
>>                               Thanks,
>>                                       Petr Vandrovec

> Could you check if this patch fixes your problem, and if so let me know
> as soon as possible?
>
> Sorry for the delay.

Thanks for the fix.  Yes, it fixes hang too, and seems much nicer..

Petr
--
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/