Re: sysutils/hal causes ath device timeout

Hi Lars,
Hi List,


On 20/01/2008, Lars Engels <lme_at_freebsd.org> wrote:
> Hi all,
>
[...]
> The hal daemon causes a timeout of my ath-driven Netgear WAG511 PC-Card.
> As soon as hald is started, the wireless connection is lost and I get
> this kernel message:
> ath0: device timeout
> ath0: ath_reset: unable to reset hardware; hal status 3230239248
>
Same here: Card is an D-Link DWl-G650
Jan 19 22:24:28 fairy kernel: ath0: <Atheros 5212> mem
0x88000000-0x8800ffff irq 16 at device 0.0 on cardbus0
Jan 19 22:24:28 fairy kernel: ath0: Ethernet address: 00:19:5b:3a:82:be
Jan 19 22:24:28 fairy kernel: ath0: mac 7.9 phy 4.5 radio 5.6

dhclient is able to receive and set the IP address, but that's all.

The message appear to be the same, too:

Jan 20 23:26:26 fairy kernel: ath0: device timeout
Jan 20 23:26:26 fairy kernel: ath0: ath_reset: unable to reset
hardware; hal status 3232504036


> When I eject the card then, the machine reboots.

The reason for the panic seems to be:

Jan 20 23:27:59 fairy savecore: reboot after panic:
resource_list_release: resource entry is not busy

>
> Environment:
>
> FreeBSD 8.0-CURRENT #0: Mon Jan 14 22:37:27 CET 2008
> lars_at_maggie.bsd-geek.de:/usr/obj/usr/src/sys/MAGGIE  i386
>
For me this is:
FreeBSD fairy.alashan.de 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Sun
Jan 20 18:41:12 UTC 2008     zoot_at_fairy:/usr/obj/usr/src/sys/GENERIC
i386

I guess I'll rebuilt all ports now, just to make sure that everything
is fine. Maybe the problem goes away with a newly built hal.

Christian