by I posted about this issue a couple of months (or so) back, and have now
had very inconclusive PMR going with IBM about this... and it STILL BUGS
ME ...
I've seen this problem on _three_ machines, on one it went away after a
while for no apparent reason (in other words, it may come back ?) but
the problem remains on two machines. One box is an F50 and the two
other are golden oldies (7013 - 530), so it seems that architecture is
not an issue here.
Following an upgrade on from 4.3.1 to 4.3.2 on the F50 and fresh
(overwrite) installs of 4.3.2 on the 530's the network interfaces don't
come up after boot unless you manually (now inserted into the startup
scripts) issue the appropriate ifconfig <if> up.
The problem is _ONLY_ manifest when two interfaces are configured.
I.e. remove either interface from the config and everything is fine.
Has anybody else seen this problem ?