From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Errors in dmesg on latest cero
Date: Tue, 18 Jun 2013 15:35:50 +0200 [thread overview]
Message-ID: <87ppvjmthl.fsf@toke.dk> (raw)
In-Reply-To: <87txkvmwad.fsf@toke.dk> ("Toke =?utf-8?Q?H=C3=B8iland-J?= =?utf-8?Q?=C3=B8rgensen=22's?= message of "Tue, 18 Jun 2013 14:35:22 +0200")
[-- Attachment #1: Type: text/plain, Size: 2123 bytes --]
Toke Høiland-Jørgensen <toke@toke.dk> writes:
> 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!
Something is definitely dodgy with the wireless. I can only see the
different networks intermittently, and when I try to connect, I get this
in the logs:
Jun 18 15:31:33 guardian daemon.notice hostapd: sw10: STA 00:21:5c:51:c1:ad IEEE 802.11: did not acknowledge authentication response
Jun 18 15:31:33 guardian daemon.info hostapd: sw10: STA 00:21:5c:51:c1:ad IEEE 802.11: associated (aid 1)
Jun 18 15:31:34 guardian daemon.info hostapd: sw10: STA 00:21:5c:51:c1:ad RADIUS: starting accounting session 51BE2E3B-00000000
Jun 18 15:31:34 guardian daemon.info hostapd: sw10: STA 00:21:5c:51:c1:ad WPA: pairwise key handshake completed (RSN)
Jun 18 15:31:37 guardian daemon.info dnsmasq-dhcp[2782]: DHCPDISCOVER(sw10) 00:21:5c:51:c1:ad
Jun 18 15:31:37 guardian daemon.info dnsmasq-dhcp[2782]: DHCPOFFER(sw10) 10.42.3.101 00:21:5c:51:c1:ad
Jun 18 15:31:37 guardian daemon.info dnsmasq-dhcp[2782]: DHCPREQUEST(sw10) 10.42.3.101 00:21:5c:51:c1:ad
Jun 18 15:31:37 guardian daemon.info dnsmasq-dhcp[2782]: DHCPACK(sw10) 10.42.3.101 00:21:5c:51:c1:ad alrua-laptop
Jun 18 15:31:37 guardian daemon.info dnsmasq-dhcp[2782]: RTR-ADVERT(sw10) xxxx.xxxx.xxxx:4::
Jun 18 15:31:44 guardian daemon.notice hostapd: sw10: STA 00:21:5c:51:c1:ad IEEE 802.11: did not acknowledge authentication response
Jun 18 15:31:44 guardian daemon.notice hostapd: sw10: STA 00:21:5c:51:c1:ad IEEE 802.11: did not acknowledge authentication response
On a second try it succeeds, however I still can't connect to the 2.4ghz
net...
-Toke
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-06-18 13:35 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 [this message]
2013-06-18 16:50 ` Dave Taht
2013-06-19 8:17 ` Toke Høiland-Jørgensen
2013-06-18 17:07 ` Dave Taht
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=87ppvjmthl.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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