From: Larry Finger <Larry.Finger@lwfinger.net>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Gary Hade <garyhade@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Jaswinder Singh Rajput <jaswinder@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
x86 maintainers <x86@kernel.org>, Len Brown <lenb@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Regression with commit f9cde5f in 2.6.30-gitX
Date: Wed, 24 Jun 2009 18:33:16 -0500 [thread overview]
Message-ID: <4A42B7BC.2000402@lwfinger.net> (raw)
In-Reply-To: <86802c440906241553j11c84adm45ef6e6e8f1fe10e@mail.gmail.com>
Yinghai Lu wrote:
> On Wed, Jun 24, 2009 at 3:11 PM, Yinghai Lu<yhlu.kernel@gmail.com> wrote:
>> On Wed, Jun 24, 2009 at 3:04 PM, Larry Finger<Larry.Finger@lwfinger.net> wrote:
>>> Yinghai Lu wrote:
>>> node 0 link 0: mmio [a0000, bffff]
>>> node 0 link 0: mmio [c0000000, dfffffff]
>>> node 0 link 0: mmio [e0000000, efffffff]
>>> node 0 link 0: mmio [f0000000, fe0bffff]
>>> bus: [00,ff] on node 0 link 0
>>> bus: 00 index 0 io port: [0, ffff]
>>> bus: 00 index 1 mmio: [a0000, bffff]
>>> bus: 00 index 2 mmio: [c0000000, fcffffffff]
>> that is read from pci config.
>>
>> and only one HT chain is there. so there is no point to use _CRS for them.
>>
>> please let me check if we could could have patch to deselect that.
>>
>
> please try the attached patches.
>
> applying sequence:
> fix_crs.patch
> use_pci_crs_early.patch
>
> only_one.patch
>From what I read in Linus's mails, it may be a moot point; however, my
system boots with these 3, and only these 3, patches applied.
I didn't see any of the new printk's in the dmesg output.
Larry
next prev parent reply other threads:[~2009-06-24 23:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 1:33 Regression with commit f9cde5f in 2.6.30-gitX Larry Finger
2009-06-24 5:31 ` Larry Finger
2009-06-24 12:16 ` Jaswinder Singh Rajput
2009-06-24 12:22 ` Ingo Molnar
2009-06-24 12:30 ` Jaswinder Singh Rajput
2009-06-24 14:46 ` Gary Hade
2009-06-24 14:21 ` Larry Finger
2009-06-24 15:16 ` Ingo Molnar
2009-06-24 15:19 ` Thomas Gleixner
2009-06-24 15:42 ` Larry Finger
2009-06-24 15:57 ` Jaswinder Singh Rajput
2009-06-24 16:13 ` Gary Hade
2009-06-24 16:33 ` Jaswinder Singh Rajput
2009-06-24 16:44 ` Jesse Barnes
2009-06-24 17:55 ` Gary Hade
2009-06-24 18:28 ` Jesse Barnes
2009-06-24 18:45 ` Thomas Gleixner
2009-06-24 19:48 ` Gary Hade
2009-06-24 20:05 ` Larry Finger
2009-06-24 21:24 ` Gary Hade
2009-06-24 22:12 ` Gary Hade
2009-06-24 21:32 ` Yinghai Lu
2009-06-24 21:42 ` Larry Finger
2009-06-24 21:44 ` Yinghai Lu
2009-06-24 22:04 ` Larry Finger
2009-06-24 22:11 ` Yinghai Lu
2009-06-24 22:53 ` Yinghai Lu
2009-06-24 23:33 ` Larry Finger [this message]
2009-06-24 23:44 ` Linus Torvalds
2009-06-24 19:28 ` Gary Hade
2009-06-24 16:52 ` Larry Finger
2009-06-24 14:51 ` Thomas Gleixner
2009-06-24 15:55 ` Jaswinder Singh Rajput
2009-06-24 16:17 ` Thomas Gleixner
2009-06-24 15:56 ` Gary Hade
2009-06-24 16:15 ` Jaswinder Singh Rajput
2009-06-24 16:33 ` Gary Hade
2009-06-24 16:25 ` Jesse Barnes
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=4A42B7BC.2000402@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=garyhade@us.ibm.com \
--cc=jaswinder@kernel.org \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=yhlu.kernel@gmail.com \
/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.