All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitri Seletski <drjoms@gmail.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: Fri, 19 Dec 2008 00:01:00 +0000	[thread overview]
Message-ID: <494AE43C.4030805@gmail.com> (raw)

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

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
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dmesg2340+27.txt
Url: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20081219/ae7b637b/attachment-0001.txt 

             reply	other threads:[~2008-12-19  0:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19  0:01 Dmitri Seletski [this message]
2008-12-18 16:09 ` [ath9k-devel] ath9k atomic failure (i am so cool to use words i don't understand) Luis R. Rodriguez
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=494AE43C.4030805@gmail.com \
    --to=drjoms@gmail.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.