[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This bug was fixed in the package linux - 5.0.0-21.22 --- linux (5.0.0-21.22) disco; urgency=medium * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc -

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This bug was fixed in the package linux - 5.0.0-21.22 --- linux (5.0.0-21.22) disco; urgency=medium * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc -

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This bug was fixed in the package linux - 4.15.0-55.60 --- linux (4.15.0-55.60) bionic; urgency=medium * linux: 4.15.0-55.60 -proposed tracker (LP: #1834954) * Request backport of ceph commits into bionic (LP: #1834235) - ceph: use atomic_t for ceph_inode_info::i_shared_gen

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This bug was fixed in the package linux-oem - 4.15.0-1045.50 --- linux-oem (4.15.0-1045.50) bionic; urgency=medium * linux-oem: 4.15.0-1045.50 -proposed tracker (LP: #1833962) [ Ubuntu: 4.15.0-54.58 ] * linux: 4.15.0-54.58 -proposed tracker (LP: #1833987) * Remote denial of

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This bug was fixed in the package linux-oem - 4.15.0-1045.50 --- linux-oem (4.15.0-1045.50) bionic; urgency=medium * linux-oem: 4.15.0-1045.50 -proposed tracker (LP: #1833962) [ Ubuntu: 4.15.0-54.58 ] * linux: 4.15.0-54.58 -proposed tracker (LP: #1833987) * Remote denial of

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

** Tags removed: verification-needed-cosmic verification-needed-disco ** Tags added: verification-done-cosmic verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu.

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

I tested 4.15.0-55-generic and after multiple times turning the computer on and off, both Bluetooth and Wireless network were working correctly all the times. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Cosmic)

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp:

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp:

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp:

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu)

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

** Description changed: - Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. - This caused, on prior versions, a kernel panic at boot. With Bionic, the - system boots but is unable to use wireless network. On dmesg there are - messages like: + === SRU Justification === +

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

I shutdown and turned on the computer using this kernel four times and in none the problem happened. With the default Bionic kernel the failure on boot would have happened twice. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Please try if this kernel works. May need to reboot twice because the fix is in shutdown path. https://people.canonical.com/~khfeng/lp1757218-bionic/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This kernel did not work. On boot, the same messages that appeared with the other problematic kernels appear and the boot freezes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Bionic kernel with the delay quirk: https://people.canonical.com/~khfeng/lp1757218-bionic/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Ok, using btusb.autosuspend=0 with this kernel version worked. I tested to turn the notebook off and on 5 times and all times both Bluetooth and Wireless worked. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Forgot to mention you should test it with btusb.autosuspend=0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This kernel version works, but I don't understand why testing a 4.17 version would be relevant on this case, as the first kernel fixed is 4.16-rc5 and, according to the checkout we've done before, the first good commit should be: commit 1fdb926974695d3dbc05a429bafa266fdd16510e Author: Hans de

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Added a delay init quirk, let's see if this kernel works: https://people.canonical.com/~khfeng/lp1757218/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

The issues happens only on cold boot. In a pattern of: Work -> Don't work -> Work If the cold boot is successful, all reboots work. If the cold boot failed, all reboots fail. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Sorry for the late reply for this issue. Does this issue also happen to cold boot? AFAICT, it only happens to reboot, right? We probably need to reset the device before reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Unfortunately, this kernel still has the same issue. The parameter btusb.enable_autosuspend is decisive to define if the fixed kernels will work. Disabling it ("btusb.enable_autosuspend=0") makes the fixed kernels act like the broken ones. However, setting it in broken kernels

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Please try the kernel here: https://people.canonical.com/~khfeng/lp1757218/ It adds your device to btusb_needs_reset_resume_table[]. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This file is one with the failed boot, unfortunately the kernel panic message don't appear. Unlike the other file with the failure I uploaded before, on this one the boot failed. I was helped on #ubuntu+1 on how to add netconsole to initramfs, so I was able to obtain the first 7 seconds of the

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

** Attachment added: "dmesg_ok.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5119845/+files/dmesg_ok.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Many tries were required until I could obtain a useful log. As it can be seen in the kernel command line, I had to add many debug options to obtain this. ** Attachment added: "dmesg_falha.txt"

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Can you attach dmesg with "btusb.enable_autosuspend=0", and another dmesg without the parameter? I am guessing that ath10k and btusb can't get probed at the same time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This is funny, but the option btusb.enable_autosuspend=0 make the bug happen on v4.16-rc7. I'm seeing a pattern that, when I change the kernel version or a grub option, I can't just turn on and off the notebook twice (as it triggers normally), but thrice. So, every time I change a configuration I

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

The bug is still the same. What happened was that the system froze at a different message in that particular try. Journalctl from a successful initialization showing the most common point of failure: systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight...

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Because the commit you bisected has been included since 4.15.12, which you said the issue is not fixed (comment #10). That particular commit will be included in next Bionic kernel update. So I guess now the bug is "waiting for /dev/disk"? -- You received this bug notification because you are a

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

No, using this parameter when using the kernel v4.16-rc7 do not cause the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Do you have this issue when using v4.16-rc7 with kernel parameter "btusb.enable_autosuspend=0"? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This is comparing the 4.15.0-13 kernel with the mainline kernel. ** Attachment added: "diff_415_416rc7.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5092728/+files/diff_415_416rc7.txt -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

The only thing I can think that is wrong is the configuration file of the kernels. They have some significant differences regarding Bluetooth. ** Attachment added: "diff_415_416rc2+.txt"

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This is insane. I have reset that bisect and tried again using "fixed" and "broken" instead of "new" and "old" and, again, the bisect had the following: 1fdb926974695d3dbc05a429bafa266fdd16510e is the first fixed commit commit 1fdb926974695d3dbc05a429bafa266fdd16510e Author: Hans de Goede

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Don't mark this as fixed yet, it has just happened in a different way: it progressed further on boot until it froze at the a message like waiting for /dev/disk. I, sincerely, don't know what to do now. This has never happened the kernels starting from 4.16.0-rc5. I have uploaded the bisect log.

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

No problem. Does this somehow (magically) also fix the ethernet r8169 for you? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

The kernel was updated today to version 4.15.0-13 and the commit "Bluetooth: btusb: Use DMI matching for QCA reset_resume quirking" was added. I have tested the notebook and now it is no longer failing to boot or booting without wireless and bluetooth. The problem is fixed to me. Thank you. --

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Finally, after 10 kernels built, I've obtained the result. Here is the output: 1fdb926974695d3dbc05a429bafa266fdd16510e is the first new commit commit 1fdb926974695d3dbc05a429bafa266fdd16510e Author: Hans de Goede Date: Tue Feb 20 09:06:18 2018 +0100 Bluetooth: btusb:

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

It's hard to say which commit(s) fixes the issue, so the fastest way is to bisect locally. You can still follow the steps [1], but instead of "bad good", use "old new": $ git bisect start $ git bisect old v4.16-rc4 $ git bisect new v4.16-rc5 $ make localmodconfig $ make -j`nproc` deb-pkg Install

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

The first kernel fixed is 4.16-rc5. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu:

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Can you find the first v4.16-rc* that fixes this issue? We need to backport the fix to Bionic's kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

With kernel version 4.15.12 the the problem is not fixed. It has the same behavior as 4.15.0-12. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Does it also get fixed by latest upstream stable kernel? http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.12/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This is not happening with the kernel 4.16-rc6, so I added the tag kernel-fixed-upstream. I can no longer boot with the 4.15.0-12 kernel successfully when the error happens, it just freeze and I wait until the HD stops to shutdown it by keeping the power button pressed. I was lucky the system was

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Looks like the ath10k_pci device drops off the PCI bus completely. I guess you can't find the device in `lspci` when this happens. Does the device re-appear if you rescan the PCI bus? i.e. `# echo 1 > /sys/bus/pci/rescan`. -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This is the dmesg from when it failed yesterday. ** Attachment added: "dmesg_falhou_mas_ligou.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5085831/+files/dmesg_falhou_mas_ligou.txt -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

usb 1-7 is the Bluetooth of the wireless module. Can you attach the dmesg when this issue happens? I'd like to see what ath10k_pci complains. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

The behavior appears to be much better with the kernel version 4.16-rc6. However, I think this is not 100% solved, as the following error is still (but now rarely) happening when disconnecting from a network: [ 5934.740004] ath10k_pci :02:00.0: failed to install key for vdev 0 peer

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16