Package: kernel-image-2.6.11-1-686 Version: 2.6.11-5 Severity: normal I was experimenting with ifupdown's mapping feature to autodetect the network my laptop is connected currently before bringing the interface up, and have found the following problem:
Invoking "mii-tool eth0" before the first "ifconfig eth0 up" run causes the system to freeze (HW reset required). It also seems that if I skip the "mii-tool eth0" on bootup, it freezes later when starting up exim4, although I did not investigate that exim4 case. Stracing mii-tool revealed that the system freezes during the ioctl call: socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3 ioctl(3, SIOCGMIIREG, the call never returns. However bringing the interface up before, makes mii-tool run OK. Also bringing it up and down again makes mii-tool run OK. It looks like something gets initialized in the kernel only on ifconfig up, and running mii-tool before that makes the system go into some kind of infinite loop. I'm using Broadcom 4400 10/100BaseT NIC on HP/Compaq nx6110 I'll submit a dmesg and othe stuff as a followup once I get this laptop online. (I'm submitting this bug from a different machine). Marcin -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-k7 Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]