All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	jbarnes@virtuousgeek.org, jacob.jun.pan@intel.com
Subject: Re: Regression:  2.6.34 boot fails on E5405 system, bisected:  de08e2c26
Date: Tue, 13 Jul 2010 19:56:18 -0600	[thread overview]
Message-ID: <4C3D1942.1090207@gmail.com> (raw)
In-Reply-To: <4C3D101E.5010605@candelatech.com>

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..

  reply	other threads:[~2010-07-14  1:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14  0:36 Regression: 2.6.34 boot fails on E5405 system, bisected: de08e2c26 Ben Greear
2010-07-14  1:17 ` Ben Greear
2010-07-14  1:56   ` Robert Hancock [this message]
2010-07-14  2:22     ` Ben Greear
2010-07-14  3:29       ` Robert Hancock
2010-07-14 14:14         ` Ben Greear
2010-07-14 15:36           ` Pan, Jacob jun
2010-07-14 16:09             ` Ben Greear
2010-07-14 16:11             ` Ben Greear
2010-07-14 17:06             ` Ben Greear
2010-07-14 18:19               ` Pan, Jacob jun
2010-07-14 18:22                 ` Ben Greear
2010-07-14 18:47                   ` H. Peter Anvin
2010-07-14 18:25                 ` H. Peter Anvin
2010-07-14 18:35           ` H. Peter Anvin
2010-07-14 18:41             ` Ben Greear
2010-07-14  2:19   ` Jesse Barnes
2010-07-14  2:24     ` Ben Greear
2010-07-14 18:52     ` H. Peter Anvin
2010-07-14 18:59       ` Jesse Barnes
2010-07-14 19:01         ` Pan, Jacob jun
2010-07-14 19:55           ` H. Peter Anvin
2010-07-15 16:38             ` Ben Greear
2010-07-16 17:33               ` Pan, Jacob jun
2010-07-16 18:28                 ` H. Peter Anvin
2010-07-14 19:03         ` H. Peter Anvin
2010-07-14 19:27       ` Ben Greear

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C3D1942.1090207@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=greearb@candelatech.com \
    --cc=jacob.jun.pan@intel.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.