[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1162312126.5918.12.camel@Homer.simpson.net>
Date: Tue, 31 Oct 2006 17:28:46 +0100
From: Mike Galbraith <efault@....de>
To: Greg KH <gregkh@...e.de>
Cc: "Martin J. Bligh" <mbligh@...gle.com>,
Cornelia Huck <cornelia.huck@...ibm.com>,
Andy Whitcroft <apw@...dowen.org>,
Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
Steve Fox <drfickle@...ibm.com>
Subject: Re: 2.6.19-rc3-mm1 -- missing network adaptors
On Mon, 2006-10-30 at 23:22 -0800, Greg KH wrote:
> On Tue, Oct 31, 2006 at 08:09:54AM +0100, Mike Galbraith wrote:
> > > Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> > > all work just fine. Doesn't anyone read the Kconfig help entries for
> > > new kernel options?
> >
> > That's terminal here atm: kernel BUG at arch/i386/mm/pageattr.c:165!
> >
> > I did have it set, but had to disable it to not panic.
>
> I think there are two different issues here. That kernel config option
> should not be causing an oops in mm code.
>
> Can you bisect the different patches to see which one causes the
> problem?
I'm not bisecting, but I'm making progress anyway. Definitely seems to
be one of the driver-core-* patches. I'm applying things to 2.6.19-rc3
virgin group wise, and as soon as I applied those, wham.
With only [1] *acpi*, gregkh-driver*, and gregkk-pci* and all was well
(except it didn't cure my eth0 woes).
Still poking at it.
-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists