Date: Sun, 13 Sep 2009 18:16:09 -0700 From: Kurt Buff <kurt.buff@gmail.com> To: freebsd-questions@freebsd.org Subject: wpi0 went away, though a reboot cures it. Message-ID: <a9f4a3860909131816r700c1e11w722e121bcbc4fb65@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Today, after leaving my Lenovo T61 on overnight to do some compiles, I lost my wireless. I tried a few other things that what I've listed below, but none of it worked. This is a dual boot machine - I also run Windows XP, and don't have any issues with wireless on that OS. Any clues would be appreciated. # uname -a FreeBSD grimsqueaker.pigfarm.org 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 07:18:07 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 First, in /var/log/messages, I found the following: Sep 13 15:09:23 grimsqueaker kernel: wpi0: device timeout Sep 13 15:09:23 grimsqueaker kernel: wpi0: link state changed to DOWN Sep 13 15:09:24 grimsqueaker kernel: wpi0: could not set power mode Sep 13 15:09:24 grimsqueaker kernel: wpi0: device config failed So I tried stopping and starting netif: # /etc/rc.d/netif stop Stopping network:wpa_supplicant not running? (check /var/run/wpa_supplicant/wpi0.pid). lo0 em0 wpi0 fwe0 fwip0. # /etc/rc.d/netif start em0: no link .............. giving up Starting wpa_supplicant. wpi0: no link .............. giving up lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4> ether 00:1c:25:80:db:87 media: Ethernet autoselect status: no carrier wpi0: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether 00:1f:3c:4d:e2:55 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 11 (2462 Mhz 11g) authmode WPA1+WPA2/802.11i privacy ON deftxkey UNDEF txpower 50 bmiss 7 scanvalid 60 protmode CTS roaming MANUAL Then, I let the compile get as far as it could, and rebooted. While rebooting, I noticed this on the console, and found these traces in /var/log/messages: Sep 13 16:05:44 grimsqueaker kernel: interrupt storm detected on "irq16:"; throttling interrupt source Sep 13 16:05:48 grimsqueaker last message repeated 4 times Sep 13 16:05:49 grimsqueaker syslogd: exiting on signal 15 Sep 13 16:07:38 grimsqueaker syslogd: kernel boot file is /boot/kernel/kernel Sep 13 16:07:38 grimsqueaker kernel: interrupt storm detected on "irq16:"; throttling interrupt source Sep 13 16:07:38 grimsqueaker kernel: interrupt storm detected on "irq16:"; throttling interrupt source Sep 13 16:07:38 grimsqueaker kernel: Waiting (max 60 seconds) for system process `vnlru' to stop...done Sep 13 16:07:38 grimsqueaker kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...interrupt storm detected on "irq16:"; throttling interrupt source Sep 13 16:07:38 grimsqueaker kernel: done Sep 13 16:07:38 grimsqueaker kernel: Waiting (max 60 seconds) for system process `syncer' to stop...interrupt storm detected on "irq16:"; throttling interrupt source Sep 13 16:07:38 grimsqueaker kernel: Sep 13 16:07:38 grimsqueaker kernel: Syncing disks, vnodes remaining...0 interrupt storm detected on "irq16:"; throttling interrupt source Sep 13 16:07:38 grimsqueaker kernel: 0 done Sep 13 16:07:38 grimsqueaker kernel: All buffers synced. Sep 13 16:07:38 grimsqueaker kernel: Uptime: 6h53m12s Sep 13 16:07:38 grimsqueaker kernel: interrupt storm detected on "irq16:"; throttling interrupt source Thanks, Kurt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a9f4a3860909131816r700c1e11w722e121bcbc4fb65>