Hi,
This is basically a repost from a bug-report I sent to linux-net 2 weeks
ago. I did not receive any reaction and the problem still remains
(did several kernel upgrades since then).
I have a problem with one of my routers not configuring eth0 after a reboot
since I've switched to Linux 2.2.* (from 2.0.36). The system is now
running Linux 2.2.5-ac4.
Debugging the network config scripts showed that it was this problem:
+ ifconfig eth0 130.161.38.165 netmask 255.255.240.0 broadcast 130.161.47.255
SIOCSIFFLAGS: Resource temporarily unavailable
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
My "solution" is to do *exactly the same* ifconfig command after the first
one fails. Then it succeeds ! Sometimes the first one *is* successful.
I have another router with the same setup that does never have this problem.
So it seems that there is some kind of timing problem that makes
the SIOCSIFFLAGS control fail temporarily.
Is this a known problem ?
A friend suggested that it might have something to do with the Ethernet
driver (3c503). For example probing/registering the interrupt line or
something like that. Sounds unlikely to me.
My setup:
---------
- standard Red Hat 5.2 (completely up-to-date, with all 2.2 updates
from Red Hat)
- Cyrix DX2 66, 16 MB RAM
- 3c503 Ethernet card
- 2 PPP lines (but the problem shows *before* PPP is started !)
- 2.2.5-ac4 kernel built with gcc-2.7.2.3 (on RH 5.2, 2.2.5-ac2)
- all drivers built into the kernel: no modules or kerneld !
- system has always functioned flawlessly with Linux 2.0.x
Red Hat details:
----------------
I have added an extra "./ifup eth0 boot" to /etc/rc.d/init.d/network in
the "start)" section just before the "touch /var/lock/subsys/network"
This results in exactly the same ifconfig command as the one that
just failed.
Greetings,
Rob van Nieuwkerk
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
