All of lore.kernel.org
 help / color / mirror / Atom feed
From: W. van den Akker <listsrv@wilsoft.nl>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] still same problem
Date: Sun, 4 Jan 2009 11:33:11 +0100	[thread overview]
Message-ID: <200901041133.11779.listsrv@wilsoft.nl> (raw)
In-Reply-To: <49601028.9030201@gmail.com>

On Sunday 04 January 2009, 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

I am facing the same problems. Kernel hangups without any oops or log-trace.
Sometimes it freezes directly after hostapd (0.6.6) is loading. But once 
running hostapd I can connect with one station to the AP (AR5416). A second
station can be added but sometimes it causes a hangup.

For what I can see the problems may also have to do with the total number of
sessions to the AP or the number of sessions setup in a short time.

If I for example start my notebook and connect to the AP all is (mostly) ok.
I can start a browser. But if I start Kmail with 6 mailboxes it hangs within a 
second.

I am desperate looking for a solution.....


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

  parent reply	other threads:[~2009-01-04 10:33 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
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 [this message]
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=200901041133.11779.listsrv@wilsoft.nl \
    --to=listsrv@wilsoft.nl \
    --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.