Thanks.
I do really have in kernel
options ATH_DEBUG
options ATH_DIAGAPI
and I've got D-Link WiFi card with Atheros chip
ath0 at pci0:3:0:0: class=0x028000 card=0x3a7e1186 chip=0x0030168c
rev=0x01 hdr=0x00
vendor = 'Atheros Communications Inc.'
device = 'AR9300 Wireless LAN adaptor'
class = network
bar [10] = type Memory, range 64, base 0xf7ee0000, size 131072,
enabled
cap 01[40] = powerspec 3 supports D0 D1 D3 current D0
cap 05[50] = MSI supports 4 messages, 64 bit, vector masks
cap 10[70] = PCI-Express 2 endpoint max data 128(128) link x1(x1)
speed 2.5(2.5) ASPM disabled(L0s/L1)
ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected
ecap 0002[140] = VC 1 max VC0
ecap 0003[300] = Serial 1 0000000000000000
If you say that's nothing bad than OK. I just get a little worried 'cos
I
never expieirnced this debug output for at least 2 years of using this
card. Probably last kernel/system update to 1001510 r280164 stable bring
this up.
2015-04-24 9:32 GMT+03:00 Victor Balada Diaz <victor at bsdes.net>:
> On Sun, Apr 12, 2015 at 12:11:42PM +0300, Michael BlackHeart wrote:
> > In a log
> >
> > Apr 11 10:10:23 diablo kernel: Seq: 17600 swtry: 0 ADDBAW?: 1 DOBAW?:
1
>
> [ lots of trimmed log entries ]
>
> >
> > First time I see this and do not know what is it and how to handle it.
> > There's no kernel debug symbols.
> >
>
> Do you have ATH_DEBUG enabled in your kernel? This seems to be printed
> by an Atheros card[1] where the driver is compiled with debug support.
> As this seems to be debugging information, I don't think there is
anything
> you need to do with it.
>
> [1]: http://fxr.watson.org/fxr/source/dev/ath/if_ath_debug.c#L161
>
--
amd_miek
Think different.
Just superior.