Shut down hangs when network connected
 

Hello,
I am running mandrake 10.1 Community edition on a vprmatrix 220a5 laptop. I am experiencing a problem I have experienced with several distros running the 2.6.x kernel. When I try to shut down or reboot, the system hangs and I have to hard reset. However, if I boot the system with the network cable disconnected, it shuts down/reboots cleanly.
The last message displayed when shutting down isn't consistent. And I never experienced this problem running Redhat 9.0.
What can I do to diagnose and solve this problem? Has anyone experienced this before, and how can it be solved!

Thank you.

can you see where it stop's if you halt the box from the console? have you dhcp enabled?

sl mritch.

When I reboot from console, I normally type "reboot" or "shutdown -r" and it turns off the computer in the same manner as when I shut down from KDE. The last message that's displayed isn't consistant each time. And I do have DHCP enabled, as I need it for internet connectivity (I'm on a college campus).

Thank you,

try bringing your ethernet card down and ther try shutting down..

#ifconfig eth0 down

#shutdown -r

u could write a simple bash script

#! /bin/bash
`ifconfig eth0 down`
`shutdown -r`

something like the above..


.. put it in ur path .. and call the script..

I tried that, but my system hanged (hung?) when I tried to turn off the network. So it appears that the system hangs when I attempted to deactivate the network...any suggestions?

Thanks!

maybe a prob with your network card. what does dmesg say about it?
another:
try the way UsualTuxpect suggested and reconfigure the network with
ifconfig ethX 0.0.0.0 before.

sl mritch.

thats really wierd...

try killing the dhclient running on ur system..


#ps -ael | grep dhclient

[SAMPLE OUTPUT]
1 S 0 910 1 0 75 0 - 475 0 ? 00:00:00 dhclient

1) #kill -9 910 [ie. the process-id of dhclient]

2) #ifconfig eth0 down

3) #shutdown -r

post back as to how it went....

Best of luck...

I successfully killed the dhclient, but again, when I attempted the ifconfig ..., the system hung and because totally unresponsive.

Any ideas?

does it happen with a 2.4 kernel or just with 2.6?
please post type of your network card & what dirvers u use.
have you iptables set up on that box?
sound quite weired to me...

sl mritch.

I never had any problem with this in the 2.4 kernel (I was running Redhat 9), however, I have had this problem in *every* 2.6 distro I've used.

Harddrake is telling me this information about my network adaptor:

Identification
Vendor: ‎National Semi

Description: ‎DP83810 10/100 Ethernet

Media class: ‎NETWORK_ETHERNET

Connection
Bus: ‎PCI

Bus PCI #: ‎0

PCI device #: ‎18

PCI function #: ‎0

Vendor ID: ‎4107

Device ID: ‎32

Sub vendor ID: ‎5421

Sub device ID: ‎8705

Misc
Module: ‎natsemi

In terms of iptables, I'm not sure if I have any set up. i don't remember doing so.

Thank you.

well, do a lspci -vv for the network-card. this will give more info. also post nfo 'bout your irq allocation (cat /proc/interrupts) or post the whole lspic output. i assume you have acpi enabled, so try booting with acpi=off. maybe it's related to powermanagement, but i'm guessing now.
have you googled on that issue. sometimes you're lucky and somebody had the same troubles before.

iptables -L -v will give you a list of active firewall rules.

sl mritch.

Here's the output of the lspci:
And everything else. eth2 is the network card in question. eth1 is my wireless card. I can kill eth1 with no problem.
I have tried booting with ACPI off, with no success, as well as noapic and nolapic.
The command "iptables" returned a "command not found"

Thanks for any help.

so it's related to the 2.6.? kernel. what sub version(s)?

i suggest to look for similar problems at www.tux.org/lkml/ , the kernel mailing list. mybe post there, but the list is somewhat crowded, so don't be sure to get an answer:-(
to you need 2.6 for any reasons? if not i'd keep using 2.4 for now.

if it's a module, see if there are options for it with "modinfo xxx".

can't think of what's wrong here.

sl mricth.