public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gary Hade <garyhade@us.ibm.com>
To: Gary Hade <garyhade@us.ibm.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
	"GARCIA DE SORIA LUCENA,
	JUAN JESUS" <juanj.g_soria@grupobbva.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Regression: Boot hang sizing transparent PCI-to-PCI bridge since after 2.6.25-r7.
Date: Tue, 11 Nov 2008 15:15:31 -0800	[thread overview]
Message-ID: <20081111231531.GB7072@us.ibm.com> (raw)
In-Reply-To: <20081110175815.GA7650@us.ibm.com>

On Mon, Nov 10, 2008 at 09:58:16AM -0800, Gary Hade wrote:
> On Mon, Nov 10, 2008 at 11:14:11AM +0100, Jiri Slaby wrote:
> > On 11/10/2008 10:12 AM, GARCIA DE SORIA LUCENA, JUAN JESUS wrote:
> > > Hello.
> > > 
> > > Time ago I bisected a commit that was making my OKI Anima 3300 laptop
> > > hang during boot.
> > 
> > Doesn't pci=norom help in your case? There was a patch which tried to resolve
> > this issue in a different manner, but it was reverted too. This boot parameter
> > was introduced as a replacement IIRC.
> 
> As the unfortunate author of both of the reverted patches and author
> of the pci=norom patch I can confirm that Jiri is correct.  The issues
> that the patches addressed (with some unintended side effects caused
> by the reverted attempts) were PCI resource allocation failures observed
> during PCI hotplug.  We were not seeing or trying to address boot-time
> PCI resource allocation failures or hangs.

Correction.  We were not trying to address boot-time hangs but I
believe we may have been trying to address expansion ROM related
PCI resource allocation failures that we were seeing during boot
with certain PCI cards.  However, I doubt that this is relevent
to your problem.  The transparent bridge sizing removal change is
probably a red herring.

Gary

-- 
Gary Hade
System x Enablement
IBM Linux Technology Center
503-578-4503  IBM T/L: 775-4503
garyhade@us.ibm.com
http://www.ibm.com/linux/ltc

  parent reply	other threads:[~2008-11-11 23:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10  9:12 Regression: Boot hang sizing transparent PCI-to-PCI bridge since after 2.6.25-r7 GARCIA DE SORIA LUCENA, JUAN JESUS
2008-11-10 10:14 ` Jiri Slaby
2008-11-10 17:58   ` Gary Hade
2008-11-11 11:21     ` Regression: Boot hang sizing transparent PCI-to-PCI bridgesince " GARCIA DE SORIA LUCENA, JUAN JESUS
2008-11-11 11:33       ` Jiri Slaby
2008-11-11 11:43         ` Regression: Boot hang sizing transparent PCI-to-PCI bridgesinceafter 2.6.25-r7 GARCIA DE SORIA LUCENA, JUAN JESUS
2008-11-11 21:30           ` Gary Hade
2008-11-11 23:15     ` Gary Hade [this message]
2008-11-12  8:50       ` Regression: Boot hang sizing transparent PCI-to-PCI bridgesince after 2.6.25-r7 GARCIA DE SORIA LUCENA, JUAN JESUS
2008-11-12 22:11         ` Gary Hade

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=20081111231531.GB7072@us.ibm.com \
    --to=garyhade@us.ibm.com \
    --cc=jirislaby@gmail.com \
    --cc=juanj.g_soria@grupobbva.com \
    --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