From: Ben Greear <greearb@candelatech.com>
To: "Pan, Jacob jun" <jacob.jun.pan@intel.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"jbarnes@virtuousgeek.org" <jbarnes@virtuousgeek.org>
Subject: Re: Regression: 2.6.34 boot fails on E5405 system, bisected: de08e2c26
Date: Wed, 14 Jul 2010 09:09:44 -0700 [thread overview]
Message-ID: <4C3DE148.9020509@candelatech.com> (raw)
In-Reply-To: <43F901BD926A4E43B106BF17856F0755EA8EE7E2@orsmsx508.amr.corp.intel.com>
On 07/14/2010 08:36 AM, Pan, Jacob jun wrote:
> what is the config size of 10.1?
> ls -l /sys/bus/pci/devices/0000:00:10.1/config
>
> if that is 256, it might be related to this patch.
>
>> From e9b1d5d0ff4d3ae86050dc4c91b3147361c7af9e Mon Sep 17 00:00:00 2001
> From: H. Peter Anvin<hpa@linux.intel.com>
> Date: Fri, 14 May 2010 13:55:57 -0700
> Subject: [PATCH] x86, mrst: Don't blindly access extended config space
>
> Do not blindly access extended configuration space unless we actively
> know we're on a Moorestown platform. The fixed-size BAR capability
> lives in the extended configuration space, and thus is not applicable
> if the configuration space isn't appropriately sized.
>
> This fixes booting certain VMware configurations with CONFIG_MRST=y.
>
> Moorestown will add a fake PCI-X 266 capability to advertise the
> presence of extended configuration space.
I'll try this in a bit, but shouldn't we also check for no-progress in
that while loop and bail out in that case? No reason to hang on
boot just because the bios or whatever is busted?
Thanks,
Ben
>
> Reported-and-tested-by: Petr Vandrovec<petr@vandrovec.name>
> Signed-off-by: H. Peter Anvin<hpa@linux.intel.com>
> Acked-by: Jacob Pan<jacob.jun.pan@intel.com>
> Acked-by: Jesse Barnes<jbarnes@virtuousgeek.org>
> LKML-Reference:<AANLkTiltKUa3TrKR1M51eGw8FLNoQJSLT0k0_K5X3-OJ@mail.gmail.com>
> ---
> arch/x86/pci/mrst.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/pci/mrst.c b/arch/x86/pci/mrst.c
> index 8bf2fcb..1cdc02c 100644
> --- a/arch/x86/pci/mrst.c
> +++ b/arch/x86/pci/mrst.c
> @@ -247,6 +247,10 @@ static void __devinit pci_fixed_bar_fixup(struct pci_dev *dev)
> u32 size;
> int i;
>
> + /* Must have extended configuration space */
> + if (dev->cfg_size< PCIE_CAP_OFFSET + 4)
> + return;
> +
> /* Fixup the BAR sizes for fixed BAR devices and make them unmoveable */
> offset = fixed_bar_cap(dev->bus, dev->devfn);
> if (!offset || PCI_DEVFN(2, 0) == dev->devfn ||
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-07-14 16:09 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
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 [this message]
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=4C3DE148.9020509@candelatech.com \
--to=greearb@candelatech.com \
--cc=hancockrwd@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox