thanks.

please look at 197147 and try to provide the data as required there.
Please note the privacy notice.

Thanks.

Created attachment 260551 [details]
Encrypted dmesg part

Created attachment 260553 [details]
Encrypted FW dump

Thank you, Emmanuel. I've dumped FW and provided relevant part of dmesg. I've created them in such way:
1) stopped wifi, rmmod all modules
2) modprobe iwlwifi
3) connected to WiFi
4) tried to connect both BT devices
5) dumped both FW and dmesg
Should I provide FW dump from FW 27?

the dump should be automatic and that is much better because we can be sure that the right events have been caught in the buffer.
In the firmware from the other bug, I added a trigger to dump the data automatically upon WiFi connection.

please make sure you run with the firmware attached in https://bugzilla.kernel.org/show_bug.cgi?id=197147#c15

I'm attaching new dump and dmesg. I'm not sure if FW dump could help, as dumping is happening before BT connection, but here it is :)

Created attachment 260555 [details]
Encrypted dmesg

Created attachment 260557 [details]
Encrypted FW dump

Oh, and this dump have been created using FW from https://bugzilla.kernel.org/show_bug.cgi?id=197147#c15

Can you connect BT if WiFi is not connected yet?

tried this few times, but no luck with FW 31. Maybe I should rfkill this interface...

Ok - if so, I'll forward your latest dump to the Coex experts.

thanks.

I've unloaded iwlwifi/iwlmvm/btusb/btintel, then reloaded btusb - and my mouse connects!

after I've loaded iwlwifi again - mouse stopped working. So, for me wifi wins over BT every time

Ok. I'll let you know if we can need more data.

Thanks.

OK, thank you!

Can you please try the -34.ucode?
We've published it recently.

Thanks.

(Forgot to say: you'd better use our backport driver or 4.14-rc8 + the fix included in https://bugzilla.kernel.org/show_bug.cgi?id=197591)

Nope, don't work with FW version 34.0.1 and patch applied on 4.14.0

Gnome Bluetooth even cannot start scan mode, and in dmesg there are such messages:
bluetoothd[980]: Failed to set mode: Busy (0x0a)

There were such messages on 31 as well, it looks like.

Created attachment 260645 [details]
Core31 firmware with debug enabled

Hi,

Can you please try the following flow:

1) connect BT
2) connect WiFi

At this point, the firmware will automatically create a dump. This is the dump we need.

Please take the time to read the privacy notice:
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#privacy_aspects

Thank you.

Created attachment 260649 [details]
Fix candidate

Hi,

our firmware team has found a problem and here is a fix candidate.
Please try.

Thank you.

Emmanuel, no, unfortunately, it doesn't fix my problem. FW is:
iwlwifi 0000:04:00.0: loaded firmware version 31.622545.1 op_mode iwlmvm
md5 is 5aa8ea53b6807b4f366507fbf3204f9f (just to be sure that I'm using right FW)
Tested on 4.14.0

Should I perform steps from #22?

Oh, and I've tried two cases - reboot my laptop (it is connecting to WiFi automatically), try to connect my BT LE mouse. Second try, I've unloaded iwlwifi/iwlmvm/btusb/btintel, loaded iwlwifi, waited connection to Internet, and tried to connect my mouse. Both tries - mouse cannot connect to laptop.

Attaching both dmesg and FW dump

Created attachment 260659 [details]
Encrypted FW dump

Created attachment 260661 [details]
Encrypted dmesg

FW dump is useless here since I haven't configured the FW to send the right data.
Will do in a bit.

BTW - you have triggered the dumps manually, right?
The firwmare shouldn't have dumped data automatically.

Oh - I can see that the dump was automatic...
Seems like you haven't used the right firmware. You were using 34.ucode instead of 31.ucode.
At least for the repro you sent to me in comments 27/28

31.622545.1 seems right though.

Attachment 260645 [details] from #22 is 34.0.1 - it's called iwlwifi-8000C-34.ucode, md5sum  1b900b688de269c6156d3e8986744ffd - this is automatic dump is for

Tried 31.622545.1 the same way - mouse worked even with module loaded from the boot, but stopped working after connecting to WiFi. No debug logs for it...

Created attachment 260663 [details]
Fix candidate with debug logs

Great. Here is the same fix candidate with debug configured.
Please use that one.
It'll trigger a dump one second after you connect and hopefully this will bring data that the firmware team will be able to analyze.

Thanks!

Created attachment 260667 [details]
Encrypted dmesg (31)

Created attachment 260669 [details]
Encrypted FW dump (31)

Hope this helps! Same behavior as on 34

Data sent to the firmware team.

Thanks.

Created attachment 260893 [details]
New BT firmware

Here is a pre-release of the new firmware for BT.
Please copy the files to /lib/firmware/intel/

You'll need a hard power off / on cycle.

After boot,  run btmon in 1 terminal and in the other terminal give the command hcitool cmd 3f 05 in root permission.
After giving the hcitool cmd 3f 05 the btmon log will show the version information.

Please provide the btmon log.

Let us know if things feel better.

Note: this includes BT firmware for 8260 and 8265.

Emmanuel,
Thank you a lot! This new firmware is definitely makes difference - at least my mouse is now working. Here is a output of hcitool:
 HCI Command: Intel Read Version (0x3f|0x0005) plen 0     #67 [hci0] 41.308459
> HCI Event: Command Complete (0x0e) plen 13               #68 [hci0] 41.405398
      Intel Read Version (0x3f|0x0005) ncmd 1
        Status: Success (0x00)
        Hardware platform: 0x37
        Hardware variant: 0x0b
        Hardware revision: 1.2
        Firmware variant: 0x23
        Firmware revision: 0.0
        Firmware build: 176-45.2017
        Firmware patch: 0

My iwlwifi firmware now is 31.622545.1

Checked with 34.0.1 as well - and it works!

Will check another device tomorrow. Thanks a lot!

Closing for now. Please reopen if needed.