I've got a real problem here. NetworkManager is making my system lockup
immediately as I start the service. I had previously switched to using legacy
configuration for my network devices (two wired, one unused wireless) on this
desktop machine. I tried to return to NM config but this lockup is making it
impossible to test/workaround, and the machine must be hard-reset each time (a
plus is I'm giving my luks ext4 filesystem a good lashing, it recovers the
journal each time).
I've got kernel debuginfo installed, but absolutely nothing gets printed to
terminal after NetworkManager starts (I get the new root terminal prompt, then
the cursor stops blinking and thats it...). I have NM turned off by chkconfig
and am manually requesting start after its fully booted.
I filed this in bz as .
I have the configuration scripts setup like this:
-> cat /etc/sysconfig/network-scripts/ifcfg-eth0
# ADMtek NC100 Network Everywhere Fast Ethernet 10/100
$-> cat /etc/sysconfig/network-scripts/ifcfg-eth1
# 3Com Corporation 3c905C-TX/TX-M [Tornado]
The tulip (network everwhere) card is turned off for NM because I know it has an
ifup/ifdown bug  which causes a kernel stacktrace but never hard-locks the
system like this by itself. Even with that not NM controlled the system locks
up. I can use that device with legacy config but it sometimes causes the oops.
Any clues where to attack this one? If I leave service network running, and
just ifup eth0 or ifup eth1 the network works just fine. If I stop network, and
then start NM I get a deadlocked kernel (same if I leave network running and
I've tried getting NM started up without any configs in place and same thing
Andrew Farris <lordmorgul(a)gmail.com> www.lordmorgul.net
gpg 0x8300BF29 fingerprint 071D FFE0 4CBC 13FC 7DEB 5BD5 5F89 8E1B 8300 BF29
revoked key 0xC99B1DF3 no longer used
No one now has, and no one will ever again get, the big picture. - Daniel Geer