Stef Walter wrote:
> A short while ago (perhaps due to a change in traffic), every few hours,
> the wireless interface becomes unresponsive, and I started seeing
> thousands of lines like this in:
>
> ath0: ath_rx_proc: no mbuf!
> ath0: ath_rx_proc: no mbuf!
> ath0: ath_rx_
Lev Serebryakov wrote:
> Hello, Stef.
>
>> ath0: ath_rx_proc: no mbuf!
>
>> The mbufs are in fact all used up. I allocate more via
>> kern.ipc.nmbclusters, and see the same behavior.
> Same problem here on 7.2-STABLE, but incresaing kern.ipc.nmbclusters
> to
es unresponsive, and I started seeing
> thousands of lines like this in:
> ath0: ath_rx_proc: no mbuf!
> The mbufs are in fact all used up. I allocate more via
> kern.ipc.nmbclusters, and see the same behavior.
Same problem here on 7.2-STABLE, but incresaing kern.ipc.nmbclusters
to 65536
th_rx_proc: no mbuf!
ath0: ath_rx_proc: no mbuf!
ath0: ath_rx_proc: no mbuf!
ath0: ath_rx_proc: no mbuf!
ath0: ath_rx_proc: no mbuf!
Has anyone seen this problem? An mbuf leak? Or perhaps fixed something
like it in a later version of FreeBSD? Would upgrading the FreeBSD
version fix this? It
