[Fwd: Re: [OpenWrt] #11862: ath: Failed to stop TX DMA, queues=0x004]
Oha, es geschehen noch Zeichen und Wunder. -- xmpp bjo@schafweide.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Das Ende ist nah!11!!! :D Am 2. Juli 2015 13:54:59 MESZ, schrieb Bjoern Franke <bjo@nord-west.org>:
Oha, es geschehen noch Zeichen und Wunder.
-- xmpp bjo@schafweide.org
------------------------------------------------------------------------
Von: OpenWrt <openwrt-devel@lists.openwrt.org> CC: openwrt-tickets@lists.openwrt.org Gesendet: Thu Jul 02 13:46:15 MESZ 2015 Betreff: Re: [OpenWrt] #11862: ath: Failed to stop TX DMA, queues=0x004
#11862: ath: Failed to stop TX DMA, queues=0x004 ------------------------------+----------------------------------- Reporter: igor@… | Owner: nbd Type: defect | Status: closed Priority: response-needed | Milestone: Barrier Breaker 14.07 Component: kernel | Version: Trunk Resolution: fixed | Keywords: ------------------------------+----------------------------------- Changes (by nbd):
* status: assigned => closed * resolution: => fixed
Comment:
fixed in r46158, r46159
-- Ticket URL: <https://dev.openwrt.org/ticket/11862#comment:332> OpenWrt <http://openwrt.org> Opensource Wireless Router Technology
------------------------------------------------------------------------
_______________________________________________ Dev mailing list Dev@lists.ffnw.de https://lists.ffnw.de/mailman/listinfo/dev -----BEGIN PGP SIGNATURE----- Version: APG v1.1.1
iG0EAREKAC0FAlWVKtkmHENsZW1lbnMgSm9obiA8Y2xlbWVuc0BmcmVpZnVuay1v bC5kZT4ACgkQZgdHbA22lqM/qQCgyQV3T491ygDdyiOVQqacYDbWq+4AoPM9uS2b NN69I9ABVLRYWF6Oy4rr =a256 -----END PGP SIGNATURE-----
Am Donnerstag, den 02.07.2015, 14:13 +0200 schrieb Clemens John:
Das Ende ist nah!11!!! :D
Es gab dazu noch einen Kommentar: " A long time ago, ath9k had issues during reset where the DMA engine would stay active and could potentially corrupt memory. To debug those issues, the driver would print warnings whenever they occur. Nowadays, these issues are gone and the primary cause of these messages is if the MAC is stuck during reset or busy processing a long transmission. This is fairly harmless, yet these messages continue to worry users. To reduce the number of bogus bug reports, turn these messages into debug messages and count their occurence in the "reset" debugfs file." vg -- xmpp bjo@schafweide.org
participants (3)
-
Bjoern Franke -
Clemens John -
Jan-Tarek Butt