Experiences with ath(4)
sam at errno.com
Mon Jul 7 16:43:31 PDT 2003
>> Ok, I've investigated this further. The strange thing is: whenever the
>> connections to the outside drop, I can ping and connect to any host in my
>> LAN (10.0.0.0/24), but I _cannot_ ping 10.0.0.138 from the WLAN client,
>> which is the inside interface of the ADSL router and thus the default
>> route. I can't explain why. "ifconfig ath0 down && ifconfig ath0 up"
>> solves this lock-up. Could this be a driver bug?
> Another update:
> Jul 5 22:38:39 korben kernel: ath0: device timeout
> Jul 5 22:38:40 korben kernel: ath_hal_wait: timeout on reg 0x8:
> 0xffffffff & 0x00000004 != 0x00000000
> Jul 5 22:38:40 korben kernel: ieee80211_new_state: RUN -> INIT
> Jul 5 22:38:40 korben kernel: ath0: unable to reset hardware; hal status
> 3 Jul 5 22:39:02 korben kernel: ath0: unable to reset hardware; hal
> status 3
> Then the card is dead. According to the manpage, "this should not happen"
Never seen this sort of thing except when yanking a card while the driver
was in the middle of talking to the hardware. Some more context would be
> If I pull it out and plug it back in, I get:
> Jul 5 22:39:46 korben kernel: ath0: detached
> Jul 5 22:39:57 korben kernel: ath0: <Atheros 5212> mem
> 0x20000000-0x2000ffff irq 11 at device 0.0 on cardbus1
> Jul 5 22:40:54 korben kernel: ath0: failed to allocate descriptors: 12
> Jul 5 22:40:54 korben kernel: device_probe_and_attach: ath0 attach
> returned 12
> Jul 5 22:40:54 korben kernel: cbb1: CardBus card activation failed
Looks like memory didn't get free'd up when you yanked the card as
reinserting should've found at least the same memory that was there before.
More information about the freebsd-current