From: "W. van den Akker" <listsrv@wilsoft.nl>
To: linux-wireless@vger.kernel.org
Subject: Re: Still problems to get ath9k in accessmode. Kernel hangs
Date: Wed, 7 Jan 2009 16:42:04 +0100 [thread overview]
Message-ID: <200901071642.04310.listsrv@wilsoft.nl> (raw)
In-Reply-To: <200901062342.22935.listsrv@wilsoft.nl>
On Tuesday 06 January 2009, you wrote:
> On Tuesday 06 January 2009 21:51:09 you wrote:
> > W. van den Akker wrote:
> > --- Snip ---
> >
> > >> However, after starting a internet session and Kmail session the
> > >> server hangs again without any output. Does the NMI-handler not
> > >> process per CPU? So if one CPU hangs, the other would still proceed?
> > >>
> > >> I have no 802.11n enabled, nor X.
> > >>
> > >> This means I think the system halted hard 'hlt-instruction'
> > >>
> > >> Any further suggestion? I am little bit hopeless now. I have placed
> > >> the PCI card into another slot, no result.
> > >
> > > Some additional information:
> > > I have booted the server at approx 16:00. Hostapd was started at
> > > boot-time. After 5 hours without any connection from any computers the
> > > server hangs.
> >
> > Just as a data point, I'm running master mode with ath9k on 64bit with
> > multiple clients and have no problems. Perhaps it's hardware version
> > related? Here's the info for my system:
> >
> > kernel: 2.6.28-gentoo
> > compat-wireless-2.6: cedd75beb269e2b559a5174ee628ebd01f63a4040
> > wireless-testing: fd1dae5fbc7a260b0ddfab7d4939a766a82ef3f3
> > hostapd: 2c04820d80b5c489576cb735c3be8f026a035a5b
> >
> > I have 80211n enabled for my device with this config:
> >
> > ht_capab=[HT40-][SHORT-GI-40][DSSS_CCK-40]
> >
> > my device:
> >
> > Network controller: Atheros Communications, Inc. AR5416 802.11a/b/g/n
> > Wireless PCI Adapter (rev 01)
> >
> > phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81:
> > mem=0xffffc20000060000, irq=17
> >
> > Currently I'm using my ps3, axim, laptop, and a netbook at the same
> > time, and have no disconnects. Any additional testing I could do that
> > might help you out, or more information I could provide you?
>
> My system:
> kernel: 2.6.28-rc9-wl (wireless testing): 2.6.28-rc9-1-686-wl #1 SMP Fri
> Jan 2 19:38:20 CET 2009 i686 GNU/Linux
> hostapd: 0.6.6
> Have no 80211n enabled
> Processor Intel(R) Pentium(R) 4 CPU 3.00GHz 1024 KB
>
> my device:
> 04:08.0 Network controller: Atheros Communications Inc. AR5416 802.11abgn
> Wireless PCI Adapter (rev 01)
> Subsystem: Linksys Device 0061
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+
> Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 168, Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 21
> Region 0: Memory at d0310000 (32-bit, non-prefetchable) [size=64K]
> Capabilities: [40] #80 [0000]
> Kernel driver in use: ath9k
> Kernel modules: ath9k
>
> System hangsup depending on the number of devices or cennections are
> opened: - only hostapd (no devices connected). system hangs after approx 5
> hours. (ifconfig shows wlan0 up)
> - only a laptop with a browsing session, system did nog hang after a few
> hours.
> - only a laptop with a browsing session and kmail, system hangs directly.
> No logging to console. Nmi watchdog enabled...
I have tested today with the latest wireless testing 2.6.28-wl and tested with
WPA and without WPA. It didnt make any difference.
I am getting pretty hopeless now. Because nothing seems to work or give any
progress.
This is the hostapd log:
mgmt::auth
authentication: STA=00:1d:e0:48:a0:a3 auth_alg=0 auth_transaction=1
status_code=0 wep=0
New STA
wlan0: STA 00:1d:e0:48:a0:a3 IEEE 802.11: authentication OK (open system)
wlan0: STA 00:1d:e0:48:a0:a3 MLME:
MLME-AUTHENTICATE.indication(00:1d:e0:48:a0:a3, OPEN_SYSTEM)
wlan0: STA 00:1d:e0:48:a0:a3 MLME: MLME-DELETEKEYS.request(00:1d:e0:48:a0:a3)
authentication reply: STA=00:1d:e0:48:a0:a3 auth_alg=0 auth_transaction=2
resp=0 (IE len=0)
MGMT (TX callback) ACK
mgmt::auth cb
wlan0: STA 00:1d:e0:48:a0:a3 IEEE 802.11: authenticated
MGMT
mgmt::auth
authentication: STA=00:1d:e0:48:a0:a3 auth_alg=0 auth_transaction=1
status_code=0 wep=0
wlan0: STA 00:1d:e0:48:a0:a3 IEEE 802.11: authentication OK (open system)
wlan0: STA 00:1d:e0:48:a0:a3 MLME:
MLME-AUTHENTICATE.indication(00:1d:e0:48:a0:a3, OPEN_SYSTEM)
wlan0: STA 00:1d:e0:48:a0:a3 MLME: MLME-DELETEKEYS.request(00:1d:e0:48:a0:a3)
authentication reply: STA=00:1d:e0:48:a0:a3 auth_alg=0 auth_transaction=2
resp=0 (IE len=0)
MGMT
mgmt::assoc_req
association request: STA=00:1d:e0:48:a0:a3 capab_info=0x421 listen_interval=10
new AID 1
wlan0: STA 00:1d:e0:48:a0:a3 IEEE 802.11: association OK (aid 1)
MGMT (TX callback) ACK
mgmt::auth cb
wlan0: STA 00:1d:e0:48:a0:a3 IEEE 802.11: authenticated
MGMT (TX callback) ACK
mgmt::assoc_resp cb
wlan0: STA 00:1d:e0:48:a0:a3 IEEE 802.11: associated (aid 1)
wlan0: STA 00:1d:e0:48:a0:a3 MLME:
MLME-ASSOCIATE.indication(00:1d:e0:48:a0:a3)
wlan0: STA 00:1d:e0:48:a0:a3 MLME: MLME-DELETEKEYS.request(00:1d:e0:48:a0:a3)
wlan0: STA 00:1d:e0:48:a0:a3 RADIUS: starting accounting session
4964CA2A-00000000
DATA
.......
DATA
STA 00:01:db:08:6b:5a sent probe request for our SSID
STA 00:01:db:08:6b:5a sent probe request for our SSID
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT (TX callback) ACK
mgmt::proberesp cb
DATA
DATA
DATA
STA 00:01:db:08:6b:5a sent probe request for our SSID
STA 00:01:db:08:6b:5a sent probe request for our SSID
STA 00:01:db:08:6b:5a sent probe request for our SSID
MGMT (TX callback) ACK
mgmt::proberesp cb
STA 00:01:db:08:6b:5a sent probe request for our SSID
STA 00:01:db:08:6b:5a sent probe request for our SSID
STA 00:01:db:08:6b:5a sent probe request for our SSID
STA 00:01:db:08:6b:5a sent probe request for our SSID
MGMT (TX callback) ACK
mgmt::proberesp cb
STA 00:01:db:08:6b:5a sent probe request for our SSID
STA 00:01:db:08:6b:5a sent probe request for our SSID
STA 00:01:db:08:6b:5a sent probe request for our SSID
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT (TX callback) ACK
mgmt::proberesp cb
STA 00:01:db:08:6b:5a sent probe request for our SSID
STA 00:01:db:08:6b:5a sent probe request for our SSID
MGMT (TX callback) fail
mgmt::proberesp cb
MGMT (TX callback) fail
mgmt::proberesp cb
DATA
DATA
DATA
DATA
DATA
DATA
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
MGMT (TX callback) fail
mgmt::proberesp cb
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
MGMT (TX callback) fail
mgmt::proberesp cb
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
MGMT (TX callback) ACK
mgmt::proberesp cb
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
MGMT (TX callback) ACK
mgmt::proberesp cb
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
MGMT (TX callback) ACK
mgmt::proberesp cb
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
MGMT (TX callback) ACK
mgmt::proberesp cb
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
MGMT (TX callback) ACK
mgmt::proberesp cb
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT (TX callback) ACK
mgmt::proberesp cb
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
MGMT (TX callback) ACK
mgmt::proberesp cb
STA 00:01:db:08:6b:5a sent probe request for broadcast SSID
MGMT (TX callback) fail
mgmt::proberesp cb
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT (TX callback) fail
mgmt::proberesp cb
DATA
....
DATA
STA 00:1d:e0:48:a0:a3 sent probe request for our SSID
MGMT (TX callback) ACK
mgmt::proberesp cb
MGMT
mgmt::auth
authentication: STA=00:1d:e0:48:a0:a3 auth_alg=0 auth_transaction=1
status_code=0 wep=0
wlan0: STA 00:1d:e0:48:a0:a3 IEEE 802.11: authentication OK (open system)
wlan0: STA 00:1d:e0:48:a0:a3 MLME:
MLME-AUTHENTICATE.indication(00:1d:e0:48:a0:a3, OPEN_SYSTEM)
wlan0: STA 00:1d:e0:48:a0:a3 MLME: MLME-DELETEKEYS.request(00:1d:e0:48:a0:a3)
authentication reply: STA=00:1d:e0:48:a0:a3 auth_alg=0 auth_transaction=2
resp=0 (IE len=0)
MGMT (TX callback) ACK
mgmt::auth cb
wlan0: STA 00:1d:e0:48:a0:a3 IEEE 802.11: authenticated
MGMT
mgmt::reassoc_req
reassociation request: STA=00:1d:e0:48:a0:a3 capab_info=0x421
listen_interval=10 current_ap=00:18:39:19:7f:87
old AID 1
wlan0: STA 00:1d:e0:48:a0:a3 IEEE 802.11: association OK (aid 1)
MGMT (TX callback) ACK
mgmt::reassoc_resp cb
wlan0: STA 00:1d:e0:48:a0:a3 IEEE 802.11: associated (aid 1)
wlan0: STA 00:1d:e0:48:a0:a3 MLME:
MLME-REASSOCIATE.indication(00:1d:e0:48:a0:a3)
wlan0: STA 00:1d:e0:48:a0:a3 MLME: MLME-DELETEKEYS.request(00:1d:e0:48:a0:a3)
wlan0: STA 00:1d:e0:48:a0:a3 RADIUS: starting accounting session
4964CA2A-00000001
DATA
DATA
DATA
------------------->> hang
--
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-07 15:42 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
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 [this message]
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=200901071642.04310.listsrv@wilsoft.nl \
--to=listsrv@wilsoft.nl \
--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).