Yesterdays kernel/git/kvalo/ath.git failes with COMPEX WLE600VX

Kalle Valo kvalo at
Wed Nov 25 04:21:19 PST 2015

Joerg Pommnitz <pommnitz at> writes:

> Kalle, attached are dmesg logs from 3.18.24 and your git tree. The
> patch from your mail is _NOT_ yet applied.

Thanks. So the ath10k board is on slot 0000:05:00.0. In 4.3 log I saw
this warning:

[    0.488080] pci 0000:05:00.0: can't claim BAR 0 [mem
0xe8000000-0xe81fffff 64bit]: address conflict with PCI Bus 0000:01
[mem 0xe8000000-0xe85fffff]

Also the BAR configurations look different, 3.18 has:

[    0.596024] pci 0000:05:00.0: BAR 6: assigned [mem 0xe8200000-0xe820ffff pref]

but 4.3 has:

[    0.660123] pci 0000:05:00.0: BAR 0: assigned [mem 0x48400000-0x485fffff 64bit]
[    0.664037] pci 0000:05:00.0: BAR 6: assigned [mem 0x48290000-0x4829ffff pref]

The chances are that this has something to do with your problem. Also in
a private email[1] you mentioned that latest ath10k works with 3.18
kernel, right? This makes me suspect that this is a problem outside
ath10k, but I'm not a PCI bus expert so I'm not really sure.

I recommend that next you try other major kernel versions (3.19, 4.0,
4.1 and so on) and find out what release first introduced the
regression. Remember always to take full dmesg logs like you have done
now. And once you have that send a mail to proper lists asking for help,
for example at least linux-wireless and linux-pci. But please continue
to CC ath10k list also, it's interesting to know what is causing this.

And even better is that if you can run full bisect to find the offending
commit, but that takes a quite long time.

> BTW, patch gives an offset of 99 lines when applying to your git tree.
> Is this relative to a branch?

The patch was few weeks old, I haven't rebased it since so that's
normal. I just hope it applied to the change to the correct location.

[1] Please do not send private email, the discussions should happen on
the list.

Kalle Valo

More information about the ath10k mailing list