Re: sysutils/hal causes ath device timeout

2 msg	cnclose() doesn't actually call TTY's close rou...
1 msg	HEADS UP! : sf(4)
1 msg	Only 64 MB memory recognized - HP xw4550
1 msg	'Bad address' with smbfs inside a jail

sysutils/hal causes ath device timeout
\ Lars Engels (20 Jan 2008)
. \ Christian Walther (20 Jan 2008)
. . \ Wes Morgan (23 Jan 2008)

16 msg	page fault panic in scioctl and console-kit-daemon
2 msg	patch for review: ATI SB600 SATA AHCI
8 msg	Taking screenshots during install
9 msg	[RFC] SysV SHM on 64-bit platforms
2 msg	Processes stuck in vmo_de state
3 msg	Still having ServerWorks HT1000 drive problems
2 msg	make delete-old whine: Malformed conditional ($...
3 msg	SIGABRT on `cvs login`
3 msg	Strange /dev/tty behaviour on 7.0-PRELEASE
4 msg	BSD cflow available
4 msg	Reading and Writing to Block from di_spare
1 msg	xorg core dumped with multi-display setting
5 msg	7.0 RC1 amd64 -- no boot with 3ware 9650-2 port
1 msg	unkillable multithreaded stopped process
6 msg	Question on security..

Subject:	Re: sysutils/hal causes ath device timeout
Group:	Freebsd-current
From:	Wes Morgan
Date:	23 Jan 2008

On Sun, 20 Jan 2008, Christian Walther wrote:

> Hi Lars,
> Hi List,
>
>
> On 20/01/2008, Lars Engels <lme> 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:/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@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.

I can say ditto. I ran across this when playing with KDE4, and I am pretty
sure that rebuilding hal won't fix it. I rebuilt *everything* from the
ground up, multiple times, still had it.

_______________________________________________
freebsd-current mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe"