From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 14:03:11 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 BD0EF16A420 for ; Fri, 6 Jan 2006 14:03:11 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43D6143D48 for ; Fri, 6 Jan 2006 14:03:09 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k06E38E8078927; Fri, 6 Jan 2006 08:03:08 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <43BE7888.8060302@centtech.com> Date: Fri, 06 Jan 2006 08:02:48 -0600 From: Eric Anderson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060104) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Beech Rintoul References: <200601060340.35999.akbeech@gmail.com> In-Reply-To: <200601060340.35999.akbeech@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1233/Fri Jan 6 06:31:08 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org 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 14:03:11 -0000 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. I'm running -current from Jan 4th. All kinds of system information is here: http://googlebit.com/freebsd/ Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------