LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   shutdown hang during eth0 shutdown (https://www.linuxquestions.org/questions/linux-networking-3/shutdown-hang-during-eth0-shutdown-103488/)

kurtisw 10-13-2003 02:11 PM

shutdown hang during eth0 shutdown
 
Hi,

I'm having trouble shutting down, in that every time I am connected to a network with DHCP, the shutdown hangs while shutting down eth0. When I reboot, I am chided for an unclean shutdown. The hang also occurs if I do an ifdown or network stop.

I'm running RedHat 8.0 with kernel 2.4.20-20.8 on a Dell Inspiron 8000. My network card is a D-Link DFE-690TXD; no errors in the logs during startup. The card works just fine otherwise.

I don't have the option of using a static IP address without some major bureaucratic hurdle-jumping.

Thanks!

Dalma 10-29-2003 04:26 PM

I'm having the same problem on a Toshiba A10 laptop. The only hint I have is that while I was adding the NIC settings a message came up once that said something like... "Can not find alias e100"

My problem began after seeing this message.

inode100 10-29-2003 04:33 PM

any errors in /var/log/messages at the time of the shutdown - hang ?

any errors when you do the ifdown ?

inode

Dalma 10-30-2003 12:28 PM

There are no updates to messages during normal shutdown as error logging is turned off just before the hang. I will try the ifdown manually and see if anything is logged.

ifdown eth0 hangs and nothing is logged in messages.

inode100 10-30-2003 02:27 PM

hmm, what about in the kernel log ?

musrum 10-30-2003 02:49 PM

One common reason for a hang when shuting down a nic is if the driver is a module and your distro is configured to unload the module when shuting down.

I don't use RedHat so I can't help directly, but this might point a RedHat type in the right direction.

One way to test this is to execute:

rmmod <module>

Where <module> is replaced by the name of your module as in

rmmod e1000

If that is the problem, one workaround is to build the driver into the kernel, rather than as a module


All times are GMT -5. The time now is 04:00 AM.