Date: Thu, 24 Dec 2009 15:47:38 -0800 From: Kurt Buff <kurt.buff@gmail.com> To: freebsd-net@freebsd.org Subject: Re: 8.0R, AMD64 and wpi is giving me major grief Message-ID: <a9f4a3860912241547y5fd833b8pdc3486db594527d5@mail.gmail.com> In-Reply-To: <3a142e750912200524i3618bf49v6a54ee797667c921@mail.gmail.com> References: <a9f4a3860912141921p59f52970j5044438b238cfcb1@mail.gmail.com> <a9f4a3860912161558p424f87b3t23315c8a4583f88e@mail.gmail.com> <3a142e750912200524i3618bf49v6a54ee797667c921@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 20, 2009 at 05:24, Paul B Mahol <onemda@gmail.com> wrote:
> On 12/17/09, Kurt Buff <kurt.buff@gmail.com> wrote:
>> Anyone?
>>
>> BTW - I dual-boot this with XP, and don't have any issues with
>> wireless when running that. Also works flawlessly when running wired,
>> over em0.
>>
>> I've just done a BIOS update - I'll be trying that out tomorrow, and
>> will update this with results.
>>
>> Kurt
>>
>> On Mon, Dec 14, 2009 at 19:21, Kurt Buff <kurt.buff@gmail.com> wrote:
>>> All,
>>>
>>> I've got a Lenovo t61 with 4gbytes RAM that is giving me fits.
>>>
>>> It's got a 3945abg chip in it, and it's getting really flaky. I can
>>> boot it up, and work at the console for a while, and that seems to
>>> work OK, usually.
>>>
>>> However, today, when I start up my gui (xfce4), wireless just dies on
>>> me. For a week before, it would usually run for a while (sometimes
>>> days) before dying on me and requiring a reboot.
>>>
>>> Below is a snippet of /var/log/messages - Does this mean anything to
>>> anyone? Is there anything I can do to recover once this happens?
>>>
>>> Thanks,
>>>
>>> Kurt
>>>
>>> Dec 14 07:16:43 grimsqueaker kernel: wlan0: Ethernet address:
>>> 00:1f:3c:4d:e2:55
>>> Dec 14 07:16:43 grimsqueaker kernel: wpi0: timeout resetting Tx ring 1
>>> Dec 14 07:16:43 grimsqueaker kernel: wpi0: timeout resetting Tx ring 3
>>> Dec 14 07:16:43 grimsqueaker kernel: wpi0: timeout resetting Tx ring 4
>>> Dec 14 07:16:43 grimsqueaker kernel: microcode alive notification
>>> version 10e02 alive 1
>>> Dec 14 07:16:43 grimsqueaker kernel: microcode alive notification
>>> version 10e02 alive 1
>>> Dec 14 07:16:43 grimsqueaker kernel: wpi_newstate: INIT -> SCAN flags 0x0
>>> Dec 14 07:16:45 grimsqueaker wpa_supplicant[381]: CTRL-EVENT-SCAN-RESULTS
>>> Dec 14 07:16:45 grimsqueaker wpa_supplicant[381]: Trying to associate
>>> with 00:23:69:82:b2:bf (SSID='5705NE197th' freq=2462 MHz)
>>> Dec 14 07:16:45 grimsqueaker kernel: wpi_newstate: SCAN -> AUTH flags 0x0
>>> Dec 14 07:16:45 grimsqueaker kernel: config chan 11 flags 8005 cck f ofdm
>>> 15
>>> Dec 14 07:16:45 grimsqueaker kernel: wpi_newstate: AUTH -> ASSOC flags 0x0
>>> Dec 14 07:16:45 grimsqueaker kernel:
>>> Dec 14 07:16:45 grimsqueaker wpa_supplicant[381]: Associated with
>>> 00:23:69:82:b2:bf
>>> Dec 14 07:16:45 grimsqueaker kernel: wpi_newstate: ASSOC -> RUN flags 0x0
>>> Dec 14 07:16:45 grimsqueaker kernel: config chan 11 flags 8035
>>> Dec 14 07:16:45 grimsqueaker kernel: wlan0: link state changed to UP
>>> Dec 14 07:16:45 grimsqueaker kernel: wpi0: need multicast update callback
>>> Dec 14 07:16:46 grimsqueaker wpa_supplicant[381]: WPA: Key negotiation
>>> completed with 00:23:69:82:b2:bf [PTK=CCMP GTK=CCMP]
>>> Dec 14 07:16:46 grimsqueaker wpa_supplicant[381]: CTRL-EVENT-CONNECTED
>>> - Connection to 00:23:69:82:b2:bf completed (auth) [id=0 id_str=]
>>> Dec 14 07:16:53 grimsqueaker dhclient: New IP Address (wlan0):
>>> 192.168.151.104
>>> Dec 14 07:16:53 grimsqueaker kernel: wpi0: need multicast update callback
>>> Dec 14 07:16:53 grimsqueaker kernel: wpi0: need multicast update callback
>>> Dec 14 07:16:53 grimsqueaker dhclient: New Subnet Mask (wlan0):
>>> 255.255.255.0
>>> Dec 14 07:16:53 grimsqueaker dhclient: New Broadcast Address (wlan0):
>>> 192.168.151.255
>>> Dec 14 07:16:53 grimsqueaker dhclient: New Routers (wlan0): 192.168.151.1
>>> Dec 14 07:17:56 grimsqueaker kernel: drm0: <Intel i965GM> on vgapci0
>>> Dec 14 07:17:56 grimsqueaker kernel: info: [drm] MSI enabled 1 message(s)
>>> Dec 14 07:17:56 grimsqueaker kernel: vgapci0: child drm0 requested
>>> pci_enable_busmaster
>>> Dec 14 07:17:56 grimsqueaker kernel: info: [drm] AGP at 0xe0000000 256MB
>>> Dec 14 07:17:56 grimsqueaker kernel: info: [drm] Initialized i915 1.6.0
>>> 20080730
>>> Dec 14 07:17:57 grimsqueaker kernel: drm0: [ITHREAD]
>>> Dec 14 07:18:24 grimsqueaker kernel: pid 1424 (xfce4-panel), uid 1001:
>>> exited on signal 11 (core dumped)
>>> Dec 14 07:25:43 grimsqueaker wpa_supplicant[381]: WPA: Group rekeying
>>> completed with 00:23:69:82:b2:bf [GTK=CCMP]
>>> Dec 14 07:48:38 grimsqueaker kernel: wpi0: device timeout
>>> Dec 14 07:48:39 grimsqueaker kernel: wpi0: could not set power mode
>>>
>
> Enable all wpi debug messages?
>
> --
> Paul B Mahol
So, I su'ed to root after a clean reboot, before entering xfce4,
entered the command
sysctl debug.wpi=-2
and the console started spewing incredible amounts of messages.
Typing blind, I exited su, started xfce4 as my account, and the
console was still spewing, and now it works. I have also exited,
rebooted clean again, and it still works.
BTW - I should mention that I updated to STABLE a few days ago, though
that didn't help at all - I was experiencing the same issues:
# uname -a
FreeBSD grimsqueaker.pigfarm.org 8.0-STABLE FreeBSD 8.0-STABLE #0: Fri
Dec 18 18:26:33 PST 2009
root@grimsqueaker.pigfarm.org:/usr/obj/usr/src/sys/GENERIC amd64
I'll work with whomever to see if we can replicate and diagnose the problem.
Kurt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a9f4a3860912241547y5fd833b8pdc3486db594527d5>