[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#311820: marked as done (ioctl(fd, SIOCGMIIPHY,...) causes hard freeze before first ifconfig up)

Your message dated Fri, 5 May 2006 19:17:49 +0100
with message-id <20060505181749.GA11079@kufelek>
and subject line Bug#311820: ioctl(fd, SIOCGMIIPHY,...) causes hard freeze before first ifconfig up
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
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)

--- End Message ---
--- Begin Message --- 
Version: 2.6.16-10

On Thu, Apr 27, 2006 at 11:12:24PM -0700, Jurij Smakov wrote:
> I'd appreciate if you could test it and close the bug if it works.

Checked, it does not hang any more, just returns an error.

Marcin
-- 
Marcin Owsiany <porridge@debian.org>             http://marcin.owsiany.pl/
GnuPG: 1024D/60F41216  FE67 DA2D 0ACA FC5E 3F75  D6F6 3A0D 8AA0 60F4 1216

--- End Message ---
Reply to: