Date: Tue, 1 Aug 2006 03:19:53 GMT From: Huidae Cho <id4you@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: i386/101135: iwi goes up and down Message-ID: <200608010319.k713JrGh028467@www.freebsd.org> Resent-Message-ID: <200608010320.k713KD21044708@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 101135 >Category: i386 >Synopsis: iwi goes up and down >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Aug 01 03:20:12 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Huidae Cho >Release: kern.osreldate: 601103 (6.1-STABLE July 31, 2006) >Organization: >Environment: FreeBSD localhost 6.1-STABLE FreeBSD 6.1-STABLE #0: Mon Jul 31 20:46:04 CDT 2006 geni@localhost:/usr/obj/usr/src/sys/GENI i386 >Description: I've updated to today's (July 31, 2006) 6.1-STABLE to use /usr/ports/net/iwi-firmware-kmod because iwi(4) with /usr/ports/net/iwi-firmware freezes the system so often. After build/installing kernel, everything looked fine, but I found iwi(4) does not work at all. Looking into /var/log/messages, iwi(4) driver goes up and down every about 5 seconds. It makes the driver unusable. I added firmware(9) and iwi(4) into the kernel and compiled a recent version of iwi-firmware-kmod port. My previous environment was 6.1-STABLE of the last month. Do I have to rebuild vpnc and "world" to make dhclient work with the new firmware framework? $ pciconf -lv iwi0@pci2:11:0: class=0x028000 card=0x27518086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class = network $ tail -f /var/log/messages Jul 31 21:35:04 localhost kernel: iwi0: link state changed to UP Jul 31 21:35:04 localhost vpnc[784]: routing loop to 165.91.140.250 Jul 31 21:35:04 localhost dhclient: New IP Address (iwi0): 10.32.19.182 Jul 31 21:35:04 localhost dhclient: New Subnet Mask (iwi0): 255.255.255.0 Jul 31 21:35:04 localhost dhclient: New Broadcast Address (iwi0): 10.32.19.255 Jul 31 21:35:04 localhost dhclient: New Routers (iwi0): 10.32.19.1 Jul 31 21:35:05 localhost vpnc[784]: routing loop to 165.91.140.250 Jul 31 21:35:06 localhost last message repeated 6 times Jul 31 21:35:06 localhost kernel: iwi0: link state changed to DOWN Jul 31 21:35:06 localhost vpnc[784]: routing loop to 165.91.140.250 Jul 31 21:35:07 localhost last message repeated 4 times Jul 31 21:35:08 localhost kernel: iwi0: link state changed to UP Jul 31 21:35:08 localhost dhclient: New IP Address (iwi0): 10.32.19.182 Jul 31 21:35:08 localhost dhclient: New Subnet Mask (iwi0): 255.255.255.0 Jul 31 21:35:08 localhost dhclient: New Broadcast Address (iwi0): 10.32.19.255 Jul 31 21:35:08 localhost dhclient: New Routers (iwi0): 10.32.19.1 Jul 31 21:35:08 localhost vpnc[784]: routing loop to 165.91.140.250 Jul 31 21:35:10 localhost last message repeated 5 times Jul 31 21:35:10 localhost kernel: iwi0: link state changed to DOWN Jul 31 21:35:11 localhost kernel: iwi0: link state changed to UP Jul 31 21:35:12 localhost dhclient: New IP Address (iwi0): 10.32.19.182 Jul 31 21:35:12 localhost dhclient: New Subnet Mask (iwi0): 255.255.255.0 Jul 31 21:35:12 localhost dhclient: New Broadcast Address (iwi0): 10.32.19.255 Jul 31 21:35:12 localhost dhclient: New Routers (iwi0): 10.32.19.1 Jul 31 21:35:12 localhost vpnc[784]: routing loop to 165.91.140.250 Jul 31 21:35:14 localhost last message repeated 6 times >How-To-Repeat: 1. Build kernel with firmware(9) and iwi(4) built-in (6.1-STABLE, July 31, 2006) 2. Use vpnc to connect to the network 3. tail -f /var/log/messages >Fix: No idea >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200608010319.k713JrGh028467>