public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]PCI Express Port Bus Driver
Date: Mon, 20 Dec 2004 10:24:16 -0800	[thread overview]
Message-ID: <20041220182416.GA20951@kroah.com> (raw)
In-Reply-To: <C7AB9DA4D0B1F344BF2489FA165E5024074749A1@orsmsx404.amr.corp.intel.com>

On Mon, Dec 20, 2004 at 10:15:30AM -0800, Nguyen, Tom L wrote:
> Friday, December 17, 2004 4:06 PM, Greg KH wrote: 
> > Hm, I get a oops message at boot time, on a non-pci express box, with
> > PCI_GOMMCONFIG enabled and your patch.  Something down in the ACPI
> > subsystem. 
> >
> > Have you tested this kind of configuration?
> With PCI_GOMMCONFIG enabled and PCIE Port Bus driver included, I got
> kernel 
> panic at boot time on a non-pci express box. Similar to your case, I 
> observed something down in the ACPI subsystem. I tested the other case 
> where the kernel is built with PCI_GOMMCONFIG and without PCIE Port 
> Bus driver being included, same kernel panic occurred at boot time. I
> tested 
> another case where the kernel is built with PCI_GOANY and with PCIE Port
> 
> Bus driver being included, the kernel boots fine. Based on these test
> results, 
> it seems that PCI_GOMMCONFIG, not PCIE Port Bus driver, is a root cause 
> of kernel panic.
> 
> > I'll hold off on applying the patch for now due to this :)
> It seems that it is ok to apply the patch for now. What do you think?

I think you might want to either get the PCI_GOANY code to work with the
pci express driver, or fix up the PCI_GOMMCONFIG case in the acpi code,
as no distro will ever enable PCI_GOMMCONFIG in the current case :)

Sound ok?

thanks,

greg k-h

  reply	other threads:[~2004-12-20 18:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-20 18:15 [PATCH]PCI Express Port Bus Driver Nguyen, Tom L
2004-12-20 18:24 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-23  1:23 long
2005-01-11 23:39 ` [PATCH]PCI " Greg KH
2004-12-21 21:02 Nguyen, Tom L
2004-12-21 19:46 Nguyen, Tom L
2004-12-21 19:56 ` Greg KH
2004-12-21 19:21 long
2004-12-21 18:57 ` [PATCH]PCI " Christoph Hellwig
2004-12-20 23:00 Nguyen, Tom L
2004-12-18  0:44 Nguyen, Tom L
2004-12-18  0:37 Nguyen, Tom L
2004-12-16  0:06 Nguyen, Tom L
2004-12-18  0:05 ` Greg KH
2004-12-18  5:49   ` Tim Hockin
2004-12-15 22:27 long
2004-12-15 21:37 ` Greg KH
2004-12-18  0:05 ` Greg KH

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=20041220182416.GA20951@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom.l.nguyen@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox