From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 16:50:30 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86C7D16A41F for ; Fri, 6 Jan 2006 16:50:30 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EF6943D46 for ; Fri, 6 Jan 2006 16:50:30 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k06GoOo7036567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Jan 2006 08:50:25 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43BEA035.9030704@errno.com> Date: Fri, 06 Jan 2006 08:52:05 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051227) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <200601060340.35999.akbeech@gmail.com> <43BE7888.8060302@centtech.com> In-Reply-To: <43BE7888.8060302@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Beech Rintoul Subject: Re: /dev/ath log messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 16:50:30 -0000 Eric Anderson wrote: > Beech Rintoul wrote: > >> I have noticed that for about the past month or so I've been getting >> hundreds of the following every day in /var/log/messages: >> >> +ath0: link state changed to DOWN >> +ath0: link state changed to UP >> >> It doesn't seem to affect connectivity, but it's really annoying in >> the security report. Is there anything I can do to stop this? I'm >> running -CURRENT from yesterday. I have built Sam's new drivers, but >> this problem started long before that and was not affected by the >> upgrade. The lease on the AP I'm connecting to is good for 24 hours so >> I don't think that's an issue. I looked at the traffic with ethereal >> and everything looks normal. I'm getting sorely tempted to go back to >> isc-dhclient and see if this goes away, but I thought I would ask here >> first. >> >> >> > > I've noticed something recently too - my ath device frequently stops > working, and I get this in messages: > > Jan 6 06:19:48 neutrino kernel: ath0: link state changed to DOWN > Jan 6 06:20:35 neutrino kernel: ath0: device timeout > Jan 6 06:20:56 neutrino kernel: ath0: device timeout > Jan 6 06:21:06 neutrino kernel: ath0: device timeout > Jan 6 06:21:59 neutrino last message repeated 2 times > Jan 6 06:22:25 neutrino kernel: ath0: device timeout > Jan 6 06:23:03 neutrino kernel: ath0: link state changed to UP > Jan 6 06:41:35 neutrino kernel: ath0: link state changed to DOWN > Jan 6 06:42:03 neutrino kernel: Memory modified after free > 0xc5402000(2048) val=11600000 @ 0xc5402000 > Jan 6 06:42:04 neutrino kernel: ath0: link state changed to UP > Jan 6 06:42:08 neutrino kernel: ath0: device timeout > Jan 6 06:42:09 neutrino kernel: ath0: link state changed to DOWN > Jan 6 06:43:12 neutrino kernel: ath0: link state changed to UP > Jan 6 06:43:17 neutrino kernel: ath0: device timeout > Jan 6 06:43:17 neutrino kernel: ath0: link state changed to DOWN > Jan 6 06:43:33 neutrino kernel: ath0: device timeout > Jan 6 06:44:10 neutrino kernel: ath0: device timeout > [and so on] > > > I would say this started happening for me in the last 2 weeks. Device timeouts should not happen; it means the driver submitted a packet to the card and didn't get a tx complete interrupt back in 5 seconds. It's unclear if the "modified after free" msgs is related and w/o more diagnostic info it's really hard to say why you're seeing device timeouts. > > I'm running -current from Jan 4th. All kinds of system information is > here: > > http://googlebit.com/freebsd/ Most of the useful info is not there. No boot dmsg or indication of what your network config is. No indication of the hal version or the mac+phy revs. yada yada yada... Sam