Re: 2.5.70-bk+ broken networking

[Andrew Morton <akpm@digeo.com>]

Andrew Morton <akpm@digeo.com> wrote:
>
> Stephen Hemminger wrote:
> > 
> > Test machine running 2.5.70-bk latest can't boot because eth2 won't
> > come up.  The same machine and configuration successfully brings up
> > all the devices and runs on 2.5.70.
> 
> kjournald is stuck waiting for IO to complete against some buffer
> during transaction commit.
> 
> I'd be suspecting block layer or device drivers.  What device driver
> is handling your /var/log?

I take that back.

Your sysrq-T woke up syslogd which did a synchronous write which poked
kjournald.  You happened to catch it in mid-commit.  So that's all normal
and sane.

Something is up with netdevice initialisation.  My eth0 (e100) is in a
strange half-there state and won't come up.  Reverting the post-2.5.70 e100
changes does not help.  It's something which went into the tree today I
think.