From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Errors in dmesg on latest cero
Date: Tue, 18 Jun 2013 10:07:26 -0700 [thread overview]
Message-ID: <CAA93jw4nL-Hg+7WVO58E2HfzmQGWhsHXk3ZD5QcXLoqxrOua4Q@mail.gmail.com> (raw)
In-Reply-To: <87txkvmwad.fsf@toke.dk>
grumble. An ubnt box running something close to 3.8.13-7
[33398.253906] ath: phy0: Failed to stop TX DMA, queues=0x004!
[33398.269531] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024
AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[33398.281250] ath: phy0: Could not stop RX, we could be confusing the
DMA engine when we start RX up
[35734.441406] ath: phy0: Failed to stop TX DMA, queues=0x006!
[35734.460937] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024
AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[35734.468750] ath: phy0: Could not stop RX, we could be confusing the
DMA engine when we start RX up
[50427.460937] ath: phy0: Failed to stop TX DMA, queues=0x004!
On Tue, Jun 18, 2013 at 5:35 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> I'm getting some weird errors in dmesg on my latest cero(-based) build:
>
> [75667.492187] ath: phy0: Failed to stop TX DMA, queues=0x004!
> [75667.574218] ath: phy0: Failed to stop TX DMA, queues=0x004!
> [75667.660156] ath: phy0: Failed to stop TX DMA, queues=0x004!
> [75667.742187] ath: phy0: Failed to stop TX DMA, queues=0x004!
> [75667.828125] ath: phy0: Failed to stop TX DMA, queues=0x004!
> [78593.152343] ath: phy0: Failed to stop TX DMA, queues=0x004!
> [78600.367187] ath: phy0: Failed to stop TX DMA, queues=0x004!
>
> and some IPv6 checksum failures:
>
> [127948.988281] ICMPv6 checksum failed [xxxx:xxxx:xxxx:0015:0000:0000:0000:0001 > xxxx:xxxx:xxxx:0015:0000:0000:0000:0002]
>
> The addresses are the 6in4 tunnel endpoints.
>
> I've also seen babeld lose connectivity (restarting it helped).
>
>
> Anything I can do about these, or are they just noise?
>
> -Toke
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
prev parent reply other threads:[~2013-06-18 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 12:35 Toke Høiland-Jørgensen
2013-06-18 13:35 ` Toke Høiland-Jørgensen
2013-06-18 16:50 ` Dave Taht
2013-06-19 8:17 ` Toke Høiland-Jørgensen
2013-06-18 17:07 ` Dave Taht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4nL-Hg+7WVO58E2HfzmQGWhsHXk3ZD5QcXLoqxrOua4Q@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=toke@toke.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox