On Sun, Dec 11, 2005 at 02:36:57PM -0500, Lee Revell wrote:
> 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 <[email protected]> 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?
No, the code works just fine if built as a module. Just building into
the kernel is when problems happen at init time.
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]