From: Jouni Malinen <j@w1.fi>
To: "W. van den Akker" <listsrv@wilsoft.nl>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Still problems to get ath9k in accessmode. Kernel hangs
Date: Wed, 24 Dec 2008 12:07:41 +0200 [thread overview]
Message-ID: <20081224100741.GA30523@jm.kir.nu> (raw)
In-Reply-To: <200812241040.39056.listsrv@wilsoft.nl>
On Wed, Dec 24, 2008 at 10:40:38AM +0100, W. van den Akker wrote:
> I have tested with the latest kernel 2.6.27.10 and compat-wireless 22-12-2008.
> I have a dual core system (Intel(R) Pentium(R) 4 CPU 3.00GHz) and use hostapd
> 0.6.6.
I've never tested this with compat-wireless, but the wireless-testing
version seems to be working fine in my tests.
> I have build the kernel, compiled the compat-wireless and did a make install.
> Make unload didnt work because some drivers were in use (mac80211).
> First problem arises, a rmmod ath9k hangs the kernel. No message of what so
> ever in the log or to stdout.
Would you happen to have another host available for storing the logs? I
have been able to receive debug messages from most crashes with
netconsole (see Documentation/networking/netconsole.txt).
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2008-12-24 10:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 9:40 Still problems to get ath9k in accessmode. Kernel hangs W. van den Akker
2008-12-24 10:07 ` Jouni Malinen [this message]
2008-12-24 17:45 ` Luis R. Rodriguez
-- strict thread matches above, loose matches on Subject: below --
2009-01-01 13:44 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
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
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=20081224100741.GA30523@jm.kir.nu \
--to=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=listsrv@wilsoft.nl \
/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).