public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Gary Hade <garyhade@us.ibm.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jesse Barnes <jbarnes@virtuousgeek.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 11:52:50 -0500	[thread overview]
Message-ID: <4A4259E2.8090006@lwfinger.net> (raw)
In-Reply-To: <20090624161306.GC7239@us.ibm.com>

Gary Hade wrote:

> I think the resource array needs to be larger.  Can you try
> the below patch?
> 
> Gary
> 
> --- linux-2.6.30-rc8/include/linux/pci.h.ORIG	2009-06-24 09:03:41.000000000 -0700
> +++ linux-2.6.30-rc8/include/linux/pci.h	2009-06-24 09:06:50.000000000 -0700
> @@ -319,7 +319,7 @@ static inline void pci_add_saved_cap(str
>  }
>  
>  #ifndef PCI_BUS_NUM_RESOURCES
> -#define PCI_BUS_NUM_RESOURCES	16
> +#define PCI_BUS_NUM_RESOURCES	20
>  #endif
>  
>  #define PCI_REGION_FLAG_MASK	0x0fU	/* These bits of resource flags tell us the PCI region flags */

As noted, I had already tested and posted that increasing
PCI_BUS_NUM_RESOURCES from 16 to 24 "solves" the problem as does
increasing it to 20, but I wonder if that isn't just papering over the
bug, which will reoccur when there is a machine with even a more
complicated PCI bus structure even more complicated than mine. Of
course, increasing it to something as large as 64 might delay the
problem "forever".

Larry



  parent reply	other threads:[~2009-06-24 16:52 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
2009-06-24 23:44                                       ` Linus Torvalds
2009-06-24 19:28             ` Gary Hade
2009-06-24 16:52           ` Larry Finger [this message]
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=4A4259E2.8090006@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 \
    /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