From: "W. van den Akker" <listsrv@wilsoft.nl>
To: linux-wireless@vger.kernel.org
Cc: Jouni Malinen <j@w1.fi>
Subject: Re: Still problems to get ath9k in accessmode. Kernel hangs
Date: Tue, 6 Jan 2009 08:57:41 +0100 [thread overview]
Message-ID: <200901060857.41357.listsrv@wilsoft.nl> (raw)
In-Reply-To: <20090105094102.GA27836@jm.kir.nu>
On Monday 05 January 2009, you wrote:
> On Thu, Jan 01, 2009 at 02:44:20PM +0100, W. van den Akker wrote:
> > I have tested on the server with the latest wireless-testing the past
> > days (2.6.28-rc9-wl). The wireless-testing looks somewhat more stable
> > then the compat-wireless.
> >
> > I have also installed the netconsole module to watch any kernel prints.
> > After running hostapd (v0.6.6) from command line the AP is
> > up-and-running. Then if I connect with the laptop (tested it with kernel
> > .26 and .28 on the laptop) I get a connection and can start a browser en
> > explore the internet. If I start a second session (Kmail or second
> > browser) the
> > server hangs within a minute. Leaving again no trace on the console,
> > hostapd-log or netconsole.
>
> Just to make sure I understood this correctly.. Does this happen with
> just a single association station (your laptop)? What are you referring
> to with a "session"? Just another program using network (i.e., no new
> wireless associations, etc.)? As far as the ath9k driver is concerned,
> new applications (e.g., new TCP connection) should not really matter
> much.. If you have IEEE 802.11n enabled, could you please run a test
> with it disabled to make sure this is not related to frame aggregation?
>
> As far as getting any output from the system is concerned, the next step
> could be to see if NMI watchdog would be able to provide any help.
> Please take a look at Documentation/nmi_watchdog.txt in the kernel
> source code and see if you could use that on the AP to get some output
> when the system hangs (running without X on console to make sure you see
> the output).
Hi Jouni,
Yes you understood correctly. Only a laptop, start a browser then start Kmail
over the same wireless connection. Then it hangs. This is always
reproducable. There are also other sorts or hangups (for example when
starting hostapd, but that is not always reproducable when it happens).
I will try today the watchdog-suggestion. Hope that it will provide some help.
To be continued....
gr,
Willem
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
next prev parent reply other threads:[~2009-01-06 7:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 13:44 Still problems to get ath9k in accessmode. Kernel hangs W. van den Akker
2009-01-03 13:56 ` W. van den Akker
2009-01-05 9:41 ` Jouni Malinen
2009-01-06 7:57 ` W. van den Akker [this message]
2009-01-06 14:52 ` W. van den Akker
2009-01-06 20:32 ` W. van den Akker
2009-01-06 20:51 ` pat-lkml
2009-01-06 22:42 ` W. van den Akker
2009-01-07 15:42 ` W. van den Akker
2009-01-10 11:26 ` W. van den Akker
2009-01-10 19:50 ` pat-lkml
2009-01-12 7:47 ` W. van den Akker
-- strict thread matches above, loose matches on Subject: below --
2008-12-24 9:40 W. van den Akker
2008-12-24 10:07 ` Jouni Malinen
2008-12-24 17:45 ` Luis R. Rodriguez
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=200901060857.41357.listsrv@wilsoft.nl \
--to=listsrv@wilsoft.nl \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.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).