I have a computer running fedora core 6 and did some automatic yum
updating a week ago and now my eth0 interface says:

SIOCSIFFLAGS: Resource temporarily unavailable

When I try to bring it up. I can use another interface, but want to
understand and correct the eth0 problem.

In googling this, I see some mention of this might be an interrupt
problem. I do know that /var/log/messages tells me that eth0 (an Intel,
using the e100 driver) is set to IRQ22. I also can see with a car
/proc/interrupts that IRQ22 shows no activity.

What sort of things can cause this and how can I troubleshoot it?

Charles

On Sun, 07 Jan 2007, in the Usenet newsgroup comp.os.linux.setup, in article
<Ezdoh.29788$hI.7995@newssvr11.news.prodigy.net> , datax wrote:

>I have a computer running fedora core 6 and did some automatic yum
>updating a week ago and now my eth0 interface says:
>
>SIOCSIFFLAGS: Resource temporarily unavailable

which is saying that the interface isn't up. We could start by asking
how you are trying to configure this? Static? DHCP? Look at the contents
of /etc/sysconfig/network-scripts/ifcfg-eth0

>When I try to bring it up. I can use another interface, but want to
>understand and correct the eth0 problem.

/sbin/ifconfig -a

>In googling this, I see some mention of this might be an interrupt
>problem. I do know that /var/log/messages tells me that eth0 (an Intel,
>using the e100 driver) is set to IRQ22. I also can see with a car
>/proc/interrupts that IRQ22 shows no activity.

Does the count remain at zero? Does ifconfig show the interface? Do you
see the MAC address of the device? How about in /var/log/messages?

>What sort of things can cause this and how can I troubleshoot it?

Not enough details

Old guy