All of lore.kernel.org
 help / color / mirror / Atom feed
From: Barry Green <barry@lemonpi.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] still same problem
Date: Sun, 04 Jan 2009 12:53:01 +1100	[thread overview]
Message-ID: <4960167D.2030905@lemonpi.net> (raw)
In-Reply-To: <49601028.9030201@gmail.com>

Hi Dimitri,

I"m getting a similar problem to you, in that my computer is hanging 
shortly after loading ath9k and trying to set up a wireless connection. 
I've logged a bug report here:

http://bugzilla.kernel.org/show_bug.cgi?id=12110

but unfortunately, there hasn't been any progress or feedback on my 
comments since the 6th December.  I'm willing to test, but I need some 
guidance on exactly how to get some useful debugging information.

Barry.

Dmitri Seletski wrote:
> Hi guys.
> After quite some time has passed since my last message, i have pulled 
> wireless drivers from web site several times, still same problem,  
> refresh of drivers didn't seem to affect the problem at all.
> I am lost, since you don't  seem to take it seriously, but it hangs 
> machine! Can someone give me an advice what I can do in order to help 
> you to troubleshoot the issue?
> I am not a programmer, but looks like a memory leak somewhere. If you 
> give clear understandable instructions - I am glad to follow them!
> Regards
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> 

  reply	other threads:[~2009-01-04  1:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-04  1:26 [ath9k-devel] still same problem Dmitri Seletski
2009-01-04  1:53 ` Barry Green [this message]
2009-01-04  3:34   ` Luis R. Rodriguez
2009-01-04  9:58     ` Jens Ott - Opteamax
2009-01-05 16:09       ` Luis R. Rodriguez
2009-01-17 23:55       ` W. van den Akker
2009-01-18  1:41         ` Jens Ott - Opteamax
2009-01-18  9:14           ` W. van den Akker
2009-01-18  5:17         ` Dmitri Seletski
2009-01-18  9:34           ` W. van den Akker
2009-01-18 15:16             ` Luis R. Rodriguez
2009-01-19  8:35               ` W. van den Akker
2009-01-19 22:31               ` W. van den Akker
2009-01-20 17:48                 ` Luis R. Rodriguez
2009-01-20 18:32                   ` W. van den Akker
2009-01-20 22:22                   ` W. van den Akker
2009-01-20 23:08                     ` Chris Kennedy
2009-01-21  7:54                       ` W. van den Akker
2009-01-21 10:11                         ` W. van den Akker
2009-01-21 12:35                           ` Jouni Malinen
2009-01-21 17:01                             ` [ath9k-devel] [PATCH] " Chris Kennedy
2009-01-21 21:05                               ` W. van den Akker
2009-01-27  9:30                                 ` W. van den Akker
2009-01-27 21:47                                   ` Chris Kennedy
2009-01-21 17:15                             ` [ath9k-devel] " W. van den Akker
2009-01-21 10:17                         ` W. van den Akker
2009-01-04 10:33 ` W. van den Akker
2009-01-04 10:47   ` W. van den Akker

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=4960167D.2030905@lemonpi.net \
    --to=barry@lemonpi.net \
    --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.