ath problems on 7.0 with ThinkPad X61s

[Dan Langille]

Kevin Oberman wrote:
>> Date: Fri, 21 Mar 2008 13:10:39 -0400
>> From: Dan Langille <dan at langille.org>
>> Sender: owner-freebsd-mobile at freebsd.org
>>
>> Dan Langille wrote:
>>> Folks:
>>>
>>> The ThinkPad X61s has arrived. It has 7.0-RELEASE installed on it.
>>>
>>> ifconfig ath0 <== never returns to the command line:
>>>
>>> from dmesg:
>>>
>>> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
>>>
>>> ath0: <Atheros 5212> mem 0xf7f00000-0xf7f0ffff irq 17 at device 0.0 on pci3
>>> ath0: [ITHREAD]
>>> ath0: using obsoleted if_watchdog interface
>>> ath0: Ethernet address: 00:1f:3a:08:xx:xx <== dunno why, but I masked those
>>> ath0: mac 10.3 phy 6.1 radio 10.2
>>>
>>>
>>> ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>>>         ether 00:1f:3a:08:xx:xx
>>>         inet 0.0.0.16 netmask 0xff000000 broadcast 0.255.255.255
>>>         media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
>>>         status: no carrier
>>>         ssid "" channel 165 (5825 Mhz 11a)
>>>         authmode OPEN privacy OFF txpower 0 scanvalid 32767 bgscan
>>>         bgscanintvl 300 bgscanidle 250 roam:rssi11a 4.5 roam:rate11a 12 
>>> burst
>>>
>>>
>>>
>>> # uname -a
>>> FreeBSD laptop.unixathome.org 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun 
>>> Feb 24 10:35:36 UTC 2008     
>>> root at driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
>> Oh, and this:
>>
>> ath0 at pci0:3:0:0:        class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01 hdr=0x00
>>      vendor     = 'Atheros Communications Inc.'
>>      device     = 'AR5212 Atheros AR5212 802.11abg wireless'
>>      class      = network
>>      subclass   = ethernet
> 
> Same card works fine for me and several others.
> 
> Are you running GENERIC or is it your own?

GENERIC.

> Clearly the ifconfig in the startup script works fine, so the issue is
> why does the ifconfig you enter manually fail?

Agreed.

> What state is the process in while it's hung? (top(1) or CTRL-T will
> provide this.) Can it be interrupted by a signal (CTRL-C), kill, or 'kill
> -9'?

sbwait.

Yes, it can be control c'd, no problem here.  ifconfig is not frozen. It
just never comes back.

> There was really not much information in your message with which to
> guess what might be happening. 

If I knew what to say, I would.  :)

Thank you.

-- 
Dan Langille

BSDCan - The Technical BSD Conference : http://www.bsdcan.org/
PGCon  - The PostgreSQL Conference:     http://www.pgcon.org/