Re: 2.5.70-bk+ broken networking

[Arnaldo Carvalho de Melo <acme@conectiva.com.br>]

Em Wed, Jun 04, 2003 at 11:33:49PM -0300, Arnaldo C. Melo escreveu:
> Em Wed, Jun 04, 2003 at 06:56:52PM -0700, Andrew Morton escreveu:
> > 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.
> 
> Strange as I'm using 2.5.70-latest-bk as of 30 minutes ago, i.e. uptodate with
> Linus + my network patches. Thing is related to nfs, please nfs loading at

Ouch, it should have been "please disable nfs loading..."

> boot time and try again, worked for me, don't know what is wrong with nfs
> loading tho (haven't checked at all, just disabled loading of the nfs
> server) :-(