Re: 2.6.18-rc1-git4 and 2.6.18-rc1-mm1 OOM's on boot

[Andy Whitcroft <apw@shadowen.org>]

Andrew Morton wrote:
> On Fri, 14 Jul 2006 09:00:36 +0100
> Andy Whitcroft <apw@shadowen.org> wrote:
> 
>>> Yep, I've run this with badari's fix as a set across the whole family. I 
>>> did all dbenchall runs for now as this example is showing on that and 
>>> badari's is triggered same.  If there is any measure of success there 
>>> I'll throw in the externals too.
>> General goodness from this one.  Except where we're getting issues with 
>> the e1000's.  That seems to be fixed up by backing out some driver changes.
>>
>> All moot, as -mm2 is showing similar goodness.
> 
> Is -mm2's e1000 OK?

Whilst calling it the e1000 problem (that was how it was originally 
reported) I should say that this was related to the sysfs change in the 
following patches:

     gregkh-driver-network-class_device-to-device.patch
     gregkh-driver-class_device_rename-remove.patch

I have two boxes under test which were failing on -mm1 similar to teh 
following (from userland):

     eth-id-00:02:55:d3:37:4a            No interface found

Both are booting -mm2 fine.

I can only see two outstanding issues.  An IDE lost interrupt issue on a 
blade we have under test which I believe benh is looking at, and what 
looks like an s390 tool chain issue which I am told is being looked at.

-apw