From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Sune_M=F8lgaard?= Date: Thu, 01 Mar 2012 20:05:45 +0100 Subject: [ath9k-devel] "Failed to stop Tx DMA" and "Could not stop RX" with AR9485 In-Reply-To: <4F4FB6D6.9040606@candelatech.com> References: <4F4E9A36.2080809@lacto.se> <20120301144642.13047.qmail@stuge.se> <4F4FB6D6.9040606@candelatech.com> Message-ID: <4F4FC889.1030400@molgaard.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Ben Greear wrote: > On 03/01/2012 07:04 AM, Mohammed Shafi wrote: >>> Work with someone who has hardware clue and just fix the problem. >> >> completely agree, we got to fix it. >> > > There are folks with machines that can reproduce this very easily. > > Maybe offer to rent their system for some short time to > see if you can reproduce it in your lab? > > I tried just getting their NICs and putting them in my own > systems, but though I could occassionally get the error to print (maybe once > every 2 days under full load) nothing locked up. It must be exacerbated by some > interaction with other system components and/or the environment... > > Thanks, > Ben > Sending my server anywhere would be inconvenient, but I could, perhaps, be persuaded to let 1, trustworthy, individual get an account and sudo rights on it. In my case, the problem doesn't lock the machine, but, of course, halts the wlan connection in question... Best, Sune -- It is my supposition that the Universe in not only queerer than we imagine, is queerer than we CAN imagine. - J. B. S. Haldane