All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k atomic failure (i am so cool to use words	i don't understand)
Date: Thu, 18 Dec 2008 08:09:54 -0800	[thread overview]
Message-ID: <20081218160954.GD465@tesla> (raw)
In-Reply-To: <494AE43C.4030805@gmail.com>

On Thu, Dec 18, 2008 at 04:01:00PM -0800, Dmitri Seletski wrote:
> Hello boys and girls.
> Tried yesterdays package provided by Luis.
> 
> 
> in order to catch kernel error message i have written little script that
> is basically loop that writes dmesg info onto my flash memory card.
> several times tried it - not one time successful...
> 
> script is below by the way.
> 
> 
> ////////////////////////////////////////////////////////////////////////////////////////////////////////
> 
> while [ "1" != "0" ]
> 
> do
> 
> savepath=/media/disk/fcron/dmesg$(date +%H%M+%S).txt
> 
> echo $savepath
> 
> dmesg >> $savepath

You shouldn' tdo this in a loop, if anything first rmmod ath9k, then dump the first
dmesg -c to /dev/null/; then modprobe ath9k and start appending to the file using
dmesg -c 

> sync
> 
> done
> 
> 
> ///////////////////////////////////////////////////////////////////////////////////////////////////////
> 
> it takes roughly  0.6 second to update file on flash drive.
> 
> Bad news, out of 3 times - no error message has being caught in dmesg...
> last dmesg output is attached to this email. in any of cases raising
> elephants didn't help.
> 
> What i have noticed - if i run two "ping -A ROUTER" in parallel, than
> condition comes earlier. It seems to me, that using "several streams" at
> the same time, be it tcp traffic or icm - computer hangs quicker.
> Let me know if you want me to try anything else.
> 
> I am trying to be good, so Santa will spare my sinful soul and do me a
> Christmas present :-)
> 
> Dmitri

> [  170.981448] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [  215.004494] wlan0: direct probe to AP 00:1e:58:b4:f6:83 try 1
> [  215.007989] wlan0 direct probe responded
> [  215.007995] wlan0: authenticate with AP 00:1e:58:b4:f6:83
> [  215.010413] wlan0: authenticated
> [  215.010418] wlan0: associate with AP 00:1e:58:b4:f6:83
> [  215.019408] wlan0: RX AssocResp from 00:1e:58:b4:f6:83 (capab=0x421 status=0 aid=1)
> [  215.019413] wlan0: associated
> [  215.028226] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready


Unfortunately as you noted this provides no help to us to help debug the issue you are
seeing. What kernel are you using? Please provide the output of:

modprobe -l mac80211
modprobe -l cfg80211
modprobe -l ath9k

Did you disable Network Manager and wpa_supplicant before starting? Are you using
encryption or no encryption? If so what encryption are you using? Is it an 11n AP? If
so do you have HT enabled? If so is it HT20 or HT40?

  Luis

  reply	other threads:[~2008-12-18 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19  0:01 [ath9k-devel] ath9k atomic failure (i am so cool to use words i don't understand) Dmitri Seletski
2008-12-18 16:09 ` Luis R. Rodriguez [this message]
2008-12-19  0:31   ` Dmitri Seletski

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=20081218160954.GD465@tesla \
    --to=lrodriguez@atheros.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.