[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A4286F8.9020501@lwfinger.net>
Date: Wed, 24 Jun 2009 15:05:12 -0500
From: Larry Finger <Larry.Finger@...inger.net>
To: Gary Hade <garyhade@...ibm.com>
CC: Thomas Gleixner <tglx@...utronix.de>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Jaswinder Singh Rajput <jaswinder@...nel.org>,
LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
x86 maintainers <x86@...nel.org>, Len Brown <lenb@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Regression with commit f9cde5f in 2.6.30-gitX
Gary Hade wrote:
> On Wed, Jun 24, 2009 at 08:45:31PM +0200, Thomas Gleixner wrote:
>> Can we just bring the limit check back and increase the number for now
>> until folks come up with a better solution ?
>
> Another possible option is leaving in the limit check (still valid
> IMO for correct behavior of previous 'pci=use_crs') and reverting
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9e9f46c44e487af0a82eb61b624553e2f7118f5b
> until the better solution for the fixed size array issue is
> available.
Either increasing PCI_BUS_NUM_RESOURCES from 16 to 20 or 24 or
reverting f9cde5f will work for my system.
Larry
--
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/
Powered by blists - more mailing lists