Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 May 2005 16:53:28 -0700
From:      Sam Leffler <sam@errno.com>
To:        dandee@volny.cz
Cc:        freebsd-current@freebsd.org, 'Emil Mikulic' <emil@cs.rmit.edu.au>
Subject:   Re: ath0 goes down periodically
Message-ID:  <42911B78.8080301@errno.com>
In-Reply-To: <20050522181904.7202B4E70E@pipa.profix.cz>
References:  <20050522181904.7202B4E70E@pipa.profix.cz>

next in thread | previous in thread | raw e-mail | index | archive | help
Daniel Dvorak wrote:
> On Thursday I reported my problem with atheros and no response.
> Now we see it is common problem.

Not sure why you think your problem is related to this one.

> 
> I used ath_rate_onoe, ath_rate_amrr and now last I am testing
> ath_rate_sample, and yet no "kernel: ath0: device timeout" message turns up
> in /var/log/messages since last reboot after recompilation kornel with
> sample rate.
> 
> But U use sample rate and have the same messages.
> So choise of ath_rate does not have a influence on timeout.
> Last panic was connection to mbuf.
> 
> My box went to panic state due to Atheros for many times, my friend advised
> me to use this:
> lsd# sysctl kern.ipc.maxsockbuf
> kern.ipc.maxsockbuf: 2097152

Don't recall you had a panic; if so please post the strack trace.

	Sam



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42911B78.8080301>