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>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Regression: 2.6.34 boot fails on E5405 system, bisected: de08e2c26
Date: Wed, 14 Jul 2010 11:22:43 -0700 [thread overview]
Message-ID: <4C3E0073.7070302@candelatech.com> (raw)
In-Reply-To: <43F901BD926A4E43B106BF17856F0755EA8EEA18@orsmsx508.amr.corp.intel.com>
On 07/14/2010 11:19 AM, Pan, Jacob jun wrote:
>> -----Original Message-----
>> From: Ben Greear [mailto:greearb@candelatech.com]
>> Sent: Wednesday, July 14, 2010 10:07 AM
>> To: Pan, Jacob jun
>> Cc: Robert Hancock; linux-kernel; jbarnes@virtuousgeek.org
>> Subject: Re: Regression: 2.6.34 boot fails on E5405 system, bisected:
>> de08e2c26
>>
>> 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.
>>
>> That patch is already in 2.6.34.y (with slight white-space
>> change it seems: space before<).
>>
>> I just posted a patch to lkml that fixes the problem for me,
>> based on a suggestion by Robert Hancock.
>>
>> I think this or something similar should to go 2.6.34.y stable
>> as well.
>>
>
>
> I have not seen the patch yet, but there is no guarantee that
> capabilities are always laid out in ascending address. So I think
> we cannot bail out when
> pcie_cap>> 20<= pos
>
> If that is some bug in the config space, can we fix it with some quirks?
No idea, but if it's on this one motherboard/device, I imagine it's somewhere
else as well.
Is there at least a maximum number of capabilities that can exist so that
you can limit the loop by that?
Thanks,
Ben
>
> Thanks,
>
> Jacob
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-07-14 18:22 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
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 [this message]
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=4C3E0073.7070302@candelatech.com \
--to=greearb@candelatech.com \
--cc=hancockrwd@gmail.com \
--cc=hpa@zytor.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