public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Greg KH <greg@kroah.com>
Cc: Ashutosh Naik <ashutosh.naik@gmail.com>,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [BUG] Early Kernel Panic with 2.6.15-rc5
Date: Sun, 11 Dec 2005 14:36:57 -0500	[thread overview]
Message-ID: <1134329818.6019.27.camel@mindpipe> (raw)
In-Reply-To: <20051211192057.GB11450@kroah.com>

On Sun, 2005-12-11 at 11:20 -0800, Greg KH wrote:
> On Sun, Dec 11, 2005 at 12:19:39PM +0530, Ashutosh Naik wrote:
> > On 12/11/05, Greg KH <greg@kroah.com> wrote:
> > > On Sun, Dec 11, 2005 at 11:56:08AM +0530, Ashutosh Naik wrote:
> > > > CONFIG_HOTPLUG_PCI_PCIE=y
> > >
> > > Change this to "m" or "n" and the oops should go away.  It's a known
> > > problem that is being worked on, but will probably take a while to get
> > > done.
> > >
> > > Do you really have a pci express hotplug controller on this machine?
> > 
> > Yeh, the Oops went away when I did  CONFIG_HOTPLUG_PCI_PCIE=n.
> > 
> > If its a known bug and will take a while to get done, maybe the
> > feature should not be included in 2.6.15 ( if it is not fixed until
> > then). Because a release kernel should theoretically never break. What
> > say?
> 
> As no distro will build their kernel with that option=y, and it is now
> documented in the archives that there's an error there, I don't want to
> really rip out all of those files :)
> 
> Hm, wonder if we can just force the option to be either N or M.  I don't
> see an easy way to do that in the config system, anyone else know how?

Um, isn't this what BROKEN is for?

Lee


  reply	other threads:[~2005-12-11 19:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-11  6:11 [BUG] Early Kernel Panic with 2.6.15-rc5 Ashutosh Naik
2005-12-11  6:26 ` Ashutosh Naik
2005-12-11  6:35   ` Greg KH
2005-12-11  6:49     ` Ashutosh Naik
2005-12-11 19:20       ` Greg KH
2005-12-11 19:36         ` Lee Revell [this message]
2005-12-11 19:42           ` Greg KH
2005-12-11 21:06         ` Adrian Bunk
2005-12-11  6:34 ` Andrew Morton
2005-12-11 17:55   ` Randy.Dunlap
2005-12-14 22:47     ` Rajesh Shah
2005-12-22  9:34       ` Ashutosh Naik

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=1134329818.6019.27.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=akpm@osdl.org \
    --cc=ashutosh.naik@gmail.com \
    --cc=greg@kroah.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