From: Mihai Moldovan <ionic@ionic.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] received PCI FATAL interrupt
Date: Tue, 07 Apr 2009 20:53:23 +0200 [thread overview]
Message-ID: <49DBA123.7070600@ionic.de> (raw)
Hello guys,
today I have updated to Kernel 2.6.29.1 using compat-wireless
(yesterday's snapshot) and got those messages in my kernel log ring buffer:
[ 72.952758] ath9k: received PCI FATAL interrupt
[ 77.087480] ath9k: received PCI FATAL interrupt
[ 86.072429] ath9k: received PCI FATAL interrupt
[ 86.074685] ath9k: received PCI FATAL interrupt
[ 89.203901] ath9k: received PCI FATAL interrupt
[ 89.448506] ath9k: received PCI FATAL interrupt
[ 94.713862] ath9k: received PCI FATAL interrupt
[ 94.869953] ath9k: received PCI FATAL interrupt
[ 102.265172] ath9k: received PCI FATAL interrupt
[ 102.281810] ath9k: received PCI FATAL interrupt
[ 102.342217] ath9k: received PCI FATAL interrupt
[ 102.347172] ath9k: received PCI FATAL interrupt
[ 102.646480] ath9k: received PCI FATAL interrupt
I don't know where they are coming from, but I suspect those error
messages to be related to my other problems as well.
I own two Atheros cards, a PCI one (04:00.0 Network controller: Atheros
Communications Inc. AR5416 802.11abgn Wireless PCI Adapter (rev 01)) and
a PCIe one (02:00.0 Network controller: Atheros Communications Inc.
AR5418 802.11abgn Wireless PCI Express Adapter (rev 01)) - both
connected to the same PC.
As already stated, OS is Linux 2.6.29.1 with compat-wireless-2009-04-06.
Both cards (and another ethernet card) are bridged together into br0
(this piece of information is of no real importance, though.)
wlan0 and wlan1 are set up to work via hostapd into MASTER mode. (WPA1
enabled, CCMP/PSK.)
They operate on two separate, non-overlapping channels with the same ESSID.
Most of the time, everything is working fine, it seems that either ath9k
or hostapd can't handle high traffic for a long time. This particularly
means, that streaming video is impossible, because the wireless
connection will eventually go down after a few minutes. Even more
interesting in this context is, that re-starting hostapd on the router
helps solving this problem, at least temporarly.
Another interesting effect is that the signal quality seen by my ipw2200
card goes up and down, that is, is unsteady when generating high network
traffic via WLAN. This can't be normal!
This all is particularly bad, because I would like to use this box as my
wireless LAN router... but currently this is more like wireless cheese
with a few lucky packets. :(
I'm open to any kind of helping rants.
Best regards,
Mihai Moldovan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 898 bytes
Desc: OpenPGP digital signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090407/9416fed9/attachment.pgp
next reply other threads:[~2009-04-07 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 18:53 Mihai Moldovan [this message]
2009-04-07 19:04 ` [ath9k-devel] received PCI FATAL interrupt Jason Tackaberry
2009-04-07 19:44 ` Mihai Moldovan
2009-05-15 0:57 ` Mihai Moldovan
2009-05-15 1:47 ` 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=49DBA123.7070600@ionic.de \
--to=ionic@ionic.de \
--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.