linux-kernel - Re: Regression: 2.6.34 boot fails on E5405 system, bisected: de08e2c26

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: <4C3D1942.1090207@gmail.com>
Date:	Tue, 13 Jul 2010 19:56:18 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Ben Greear <greearb@...delatech.com>
CC:	linux-kernel <linux-kernel@...r.kernel.org>,
	jbarnes@...tuousgeek.org, jacob.jun.pan@...el.com
Subject: Re: Regression:  2.6.34 boot fails on E5405 system, bisected:  de08e2c26

On 07/13/2010 07:17 PM, Ben Greear wrote:
> On 07/13/2010 05:36 PM, Ben Greear wrote:
>> We're seeing boot failures on multiple machines, running FC8 and
>> F11. I bisected on an FC8 32-bit system. Newer hardware works,
>> but these older ones do not.
>>
>> A console log of the hang is found later in this email.
>>
>> Please let me know if you would like any additional information,
>> and I will be happy to test patches.
>>
>> The same failure happens in 2.6.34.1, so the fix does not appear to
>> be in the stable tree yet.
>
>
> I added some printks to the offending code. It seems the problem
> is that the fixed_bar_cap method in arch/x86/pci/mrst.c loops forever:
>
> # Endless loop of this spewing to console...
>
> pcie_cap: 268435456Checking vendor..
> pos after shift: 256
> Before read..

Can you print out bus->number and devfn and look that up in lspci to 
find out which device it's hitting? It looks like there's a device with 
a PCI Express extended capability header that has a extended capability 
ID of 0000h and a next capability offset of 100h, which points to 
itself, causing the infinite loop. I'm guessing that if pcie_cap >> 20 
<= pos then it should give up and break out of the loop, since it means 
that the next capability pointer is invalidly pointing to the same or a 
previous entry..
--
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/