All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent ETIENNE <ve@vetienne.net>
To: Yinghai Lu <yinghai@kernel.org>
Cc: linux-kernel@vger.kernel.org, jbarnes@virtuousgeek.org
Subject: Re: Kernel 2.66.33-rC1 boot problem bisected to commit 99935a7a59eaca0292c1a5880e10bae03f4a5e3d
Date: Sat, 19 Dec 2009 23:06:29 +0100	[thread overview]
Message-ID: <200912192306.29636.ve@vetienne.net> (raw)
In-Reply-To: <4B2D4781.20907@kernel.org>

Le samedi 19 décembre 2009 22:37:05, Yinghai Lu a écrit :
> Vincent ETIENNE wrote:
> > I am experiencing boot problem with kernel 2.6.33-rc1.  Bisection points
> > to
> >
> 
> please check
> 
> Subject: [PATCH 1/7] x86/pci: intel ioh bus num reg accessing fix
> 
> it is above 0x100, so if mmconf is not enable, need to skip it
> 
> Reported-by: Jens Axboe <jens.axboe@oracle.com>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> 
> ---
>  arch/x86/pci/intel_bus.c |    4 ++++
>  1 file changed, 4 insertions(+)
> 
> Index: linux-2.6/arch/x86/pci/intel_bus.c
> ===================================================================
> --- linux-2.6.orig/arch/x86/pci/intel_bus.c
> +++ linux-2.6/arch/x86/pci/intel_bus.c
> @@ -49,6 +49,10 @@ static void __devinit pci_root_bus_res(s
>  	u64 mmioh_base, mmioh_end;
>  	int bus_base, bus_end;
> 
> +	/* some sys doesn't get mmconf enabled */
> +	if (dev->cfg_size < 0x200)
> +		return;
> +
>  	if (pci_root_num >= PCI_ROOT_NR) {
>  		printk(KERN_DEBUG "intel_bus.c: PCI_ROOT_NR is too small\n");
>  		return;
> 

It works : v2.6;33_rc1 + your patch booot sucessfully on my machine
Thanks a lot

		Vincent

      reply	other threads:[~2009-12-19 22:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-19 16:07 Kernel 2.66.33-rC1 boot problem bisected to commit 99935a7a59eaca0292c1a5880e10bae03f4a5e3d Vincent ETIENNE
2009-12-19 21:37 ` Yinghai Lu
2009-12-19 22:06   ` Vincent ETIENNE [this message]

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=200912192306.29636.ve@vetienne.net \
    --to=ve@vetienne.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yinghai@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 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.