From: "Sune Mølgaard" <sune@molgaard.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Failed to stop TX DMA
Date: Fri, 27 Jan 2012 12:47:34 +0100 [thread overview]
Message-ID: <4F228ED6.2070102@molgaard.org> (raw)
In-Reply-To: <4F1DB019.3040206@candelatech.com>
Ben Greear wrote:
> On 01/23/2012 05:18 AM, Paul Farrow wrote:
>> Hi Ben
>>
>> Thanks for replying and offering to try it on your machine. Perhaps the trick is the 64 bit kernel (3.1.9-1.fc16.x86_64.debug)
>> - not sure. I have attached hostapd.conf and lspci for your information.
>
> Can you try my kernel first?
>
> http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.0.dev.y/.git;a=summary
>
>
> You see the problem when you test either with your Android or Macbook,
> or just some specific combination?
>
> Thanks,
> Ben
>
I seem to be hit by this as well. My machine is rather old, and I'm
quite busy today, but I will start a build now and test it later.
What did you want to know when it's running?
Best regards,
Sune M?lgaard
next prev parent reply other threads:[~2012-01-27 11:47 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 1:19 [ath9k-devel] Failed to stop TX DMA Paul Farrow
2011-12-29 4:07 ` Adrian Chadd
2011-12-29 14:10 ` Paul Farrow
2011-12-29 20:34 ` Adrian Chadd
2011-12-29 20:58 ` Paul Farrow
2011-12-29 22:31 ` Paul Farrow
2011-12-30 6:23 ` Mohammed Shafi
2012-01-03 1:44 ` Paul Farrow
[not found] ` <2ef536609cbee9c771dc3ebdf7e79bb1@www.thefabfarrows.com>
2012-01-05 6:46 ` Mohammed Shafi
2012-01-05 12:58 ` Paul Farrow
2012-01-20 3:36 ` Paul Farrow
2012-01-20 3:50 ` Peter Stuge
2012-01-20 13:17 ` Paul Farrow
2012-01-20 5:30 ` Ben Greear
2012-01-20 13:25 ` Paul Farrow
2012-01-20 17:03 ` Ben Greear
2012-01-20 20:09 ` Adrian Chadd
2012-01-20 20:13 ` Ben Greear
2012-01-23 13:18 ` Paul Farrow
[not found] ` <CAD2nsn0JP4GJQna_YeCPXgPW-Z6EYW18oWKgt_tW9ti2J+cT9A@mail.gmail.com>
2012-01-23 13:57 ` Paul Farrow
2012-01-23 14:01 ` Peter Stuge
2012-01-23 14:07 ` Paul Farrow
2012-01-23 14:29 ` Peter Stuge
2012-01-23 14:39 ` Paul Farrow
2012-01-23 19:08 ` Ben Greear
2012-01-23 19:46 ` Paul Farrow
2012-01-23 20:57 ` Paul Farrow
2012-01-24 0:40 ` Ben Greear
2012-01-24 13:04 ` Paul Farrow
2012-01-24 17:26 ` Ben Greear
2012-01-25 13:20 ` Paul Farrow
2012-01-26 1:22 ` Paul Farrow
2012-01-26 3:14 ` Ben Greear
2012-01-26 12:58 ` Paul Farrow
2012-01-27 11:47 ` Sune Mølgaard [this message]
2012-01-27 17:04 ` Ben Greear
2012-01-27 18:30 ` Sune Mølgaard
2012-01-27 19:20 ` Ben Greear
2012-01-27 20:05 ` Adrian Chadd
2012-01-27 21:37 ` Ben Greear
2012-01-28 9:39 ` Sune Mølgaard
2012-01-28 16:49 ` Paul Farrow
2012-01-30 17:45 ` Ben Greear
2012-01-30 18:22 ` Paul Farrow
2012-02-03 21:26 ` Ben Greear
2012-02-05 12:01 ` Paul Farrow
2012-02-06 17:47 ` Ben Greear
2012-03-16 13:30 ` Paul Farrow
2012-03-16 15:35 ` Adrian Chadd
2012-03-16 16:08 ` Ben Greear
2012-03-16 17:12 ` Paul Farrow
2012-03-16 18:50 ` Adrian Chadd
2012-02-04 12:43 ` [ath9k-devel] (no subject) Mieszko Ślusarczyk
2012-02-06 17:51 ` Ben Greear
2012-02-06 17:55 ` [ath9k-devel] Failed to stop TX DMA Mieszko Ślusarczyk
[not found] ` <4F3016CC.3030003@candelatech.com>
2012-02-06 18:09 ` Mieszko Ślusarczyk
2012-02-06 23:11 ` [ath9k-devel] (no subject) Sune Mølgaard
2012-01-20 14:05 ` [ath9k-devel] Failed to stop TX DMA Mohammed Shafi
2012-01-20 14:17 ` Paul Farrow
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F228ED6.2070102@molgaard.org \
--to=sune@molgaard.org \
--cc=ath9k-devel@lists.ath9k.org \
/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;
as well as URLs for NNTP newsgroup(s).