note: previously I've added this info as a comment to ticket #576, but as mrenzmann suggested this should be a separate ticket:
I've got a new model of D-Link AirPremier? AG DWL-AG660 (cardbus) and unfortunatelly have some issues in monitor mode. After some time (from 20 min up to 1 hour) in monitor mode (dumping a net traffic with airodump-ng) the card stops receiving frames/packets. LEDS blink as usual but the card do not see any traffic. After (un)plugging the card back everything works fine for some time. There is no sign of any problems in the log (I use ath_debug=1 option for ath_pci). I have only one ath interface.
I use snapshot madwifi-ng r1763 (with aircrack-ng patch 1756 and fixes from tickets #617 and #946) on Linux 2.6.17.14 (dmesg):
ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath_rate_sample: 1.2 (svn r1763)
ath_pci: 0.9.4.5 (svn r1763)
The card have "H/W Ver.:B3 F/W Ver.:2.20" data on the sticker. lspci tells:
lspci -nn -v -s 03:00.0
03:00.0 Ethernet controller [0200]: Atheros Communications, Inc. AR5006X 802.11abg NIC [168c:001b] (rev 01)
Subsystem: D-Link System Inc D-Link AirPremier AG DWL-AG660 Wireless Cardbus Adapter [1186:3a19]
Flags: bus master, medium devsel, latency 168, IRQ 185
Memory at 32000000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
With the same drivers/Linux version the older D-Link AG650 (Cardbus) and D-Link G520 (PCI) work fine.
Last night I've done some net dumping with athdebug 0xffffffff, and for single sniffed channel I havent noticed any problems, for over 6 hours, later I did over 1 hour channel hopping net monitoring w/o problems, and later after 30 minutes of sniffing card moved to a deaf mode. I'm going to attach athdebug logs from the point of time.
With athdebug 0xffffffff the card still dumps some (but less) network information to logs, but airodump-ng shows nothing.
Is this HAL/too new hardware - related problem? In several days I should be able to test some more AG660 (the same model).