Redpine: BLE scanning for nearby beacons per second is too low and result high loss rate.

[Amitkumar Karwar]

SRU Justification

Impact: BLE scanning for nearby beacons per second is too low and result high loss rate.

Fix: Updated firmware.

Test Case: Test on affected hardware using instructions below.

Regression Potential: Limited to specific hardware.

---

Steps to replicate the issue:

1. Power on the BT device, then change the terminal by "Ctil+F1" or open another putty to ssh SUT.
2.Use command below to discover BLE device.
$ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan --duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
3. log as attachment.

This bug is for tracking purposes only, do not triage.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1753439

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

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 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4

[Amitkumar Karwar (amitkarwar)]

SRU Justification
=================

[Impact]
Less beacons were found in BLE scanning with RS9113 chipset.

[Fix]
BLE Scanning is happening for less scan window, which is causing this issue. Scan window value is adjusted (increase)dynamically in firmware when there is no activity on WiFi/BT. Along with this fix i firmware, we have added deep sleep feature in driver. Driver will put chip in sleep state when there is not activity.

[Test Case]
Conducted tests to confirm BLE scanning results are improved with the driver and firmware changes. Also, ran suspend resume s3, s4 and s5 stress tests to ensure it passed with newly added sleep changes

[Shrirang Bagul (shrirang-bagul)]

This firmware is required for in Bionic as well to support Dell Edge 300X devices in 18.04.

[Stefan Bader (smb)]

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 'verification-needed-xenial' to 'verification-failed-xenial'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 4.4.0-119.143

---------------
linux (4.4.0-119.143) xenial; urgency=medium

  * linux: 4.4.0-119.143 -proposed tracker (LP: #1760327)

  * Dell XPS 13 9360 bluetooth scan can not detect any device (LP: #1759821)
    - Revert "Bluetooth: btusb: fix QCA Rome suspend/resume"

linux (4.4.0-118.142) xenial; urgency=medium

  * linux: 4.4.0-118.142 -proposed tracker (LP: #1759607)

  * Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (Trusty) (LP: #1758869)
    - x86/microcode/AMD: Do not load when running on a hypervisor

  * CVE-2018-8043
    - net: phy: mdio-bcm-unimac: fix potential NULL dereference in
      unimac_mdio_probe()

linux (4.4.0-117.141) xenial; urgency=medium

  * linux: 4.4.0-117.141 -proposed tracker (LP: #1755208)

  * Xenial update to 4.4.114 stable release (LP: #1754592)
    - x86/asm/32: Make sync_core() handle missing CPUID on all 32-bit kernels
    - usbip: prevent vhci_hcd driver from leaking a socket pointer address
    - usbip: Fix implicit fallthrough warning
    - usbip: Fix potential format overflow in userspace tools
    - x86/microcode/intel: Fix BDW late-loading revision check
    - x86/retpoline: Fill RSB on context switch for affected CPUs
    - sched/deadline: Use the revised wakeup rule for suspending constrained dl
      tasks
    - can: af_can: can_rcv(): replace WARN_ONCE by pr_warn_once
    - can: af_can: canfd_rcv(): replace WARN_ONCE by pr_warn_once
    - PM / sleep: declare __tracedata symbols as char[] rather than char
    - time: Avoid undefined behaviour in ktime_add_safe()
    - timers: Plug locking race vs. timer migration
    - Prevent timer value 0 for MWAITX
    - drivers: base: cacheinfo: fix x86 with CONFIG_OF enabled
    - drivers: base: cacheinfo: fix boot error message when acpi is enabled
    - PCI: layerscape: Add "fsl,ls2085a-pcie" compatible ID
    - PCI: layerscape: Fix MSG TLP drop setting
    - mmc: sdhci-of-esdhc: add/remove some quirks according to vendor version
    - fs/select: add vmalloc fallback for select(2)
    - hwpoison, memcg: forcibly uncharge LRU pages
    - cma: fix calculation of aligned offset
    - mm, page_alloc: fix potential false positive in __zone_watermark_ok
    - ipc: msg, make msgrcv work with LONG_MIN
    - x86/ioapic: Fix incorrect pointers in ioapic_setup_resources()
    - ACPI / processor: Avoid reserving IO regions too early
    - ACPI / scan: Prefer devices without _HID/_CID for _ADR matching
    - ACPICA: Namespace: fix operand cache leak
    - netfilter: x_tables: speed up jump target validation
    - netfilter: arp_tables: fix invoking 32bit "iptable -P INPUT ACCEPT" failed
      in 64bit kernel
    - netfilter: nf_dup_ipv6: set again FLOWI_FLAG_KNOWN_NH at flowi6_flags
    - netfilter: nf_ct_expect: remove the redundant slash when policy name is
      empty
    - netfilter: nfnetlink_queue: reject verdict request from different portid
    - netfilter: restart search if moved to other chain
    - netfilter: nf_conntrack_sip: extend request line validation
    - netfilter: use fwmark_reflect in nf_send_reset
    - ext2: Don't clear SGID when inheriting ACLs
    - reiserfs: fix race in prealloc discard
    - re...

[Seth Forshee (sforshee)]

@Shrirang - we have neither the firmware in linux-firmware nor the driver in the kernel for bionic. We cannot apply fixes for things which do not exist.

[Łukasz Zemczak (sil2100)]

Hello Amitkumar, or anyone else affected,

Accepted linux-firmware into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/1.157.18 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Brian Murray (brian-murray)]

Could you please provide some information about how you verified the fix for xenial?

[Shrirang Bagul (shrirang-bagul)]

The verification was done by Redpine, ODM and one of the Beta customers.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-firmware - 1.157.18

---------------
linux-firmware (1.157.18) xenial; urgency=medium

  * Redpine: BLE scanning for nearby beacons per second is too low and result
    high loss rate (LP: #1753439)
    - UBUNTU: linux-firmware: update firmware images for Redpine 9113 chipset

  * Redpine: BLE radio lost issue (LP: #1757443)
    - UBUNTU: linux-firmware: update firmware images for Redpine 9113 chipset

  * Update firmware for 18.04 hwe kernel (LP: #1763823)
    - linux-firmware: liquidio: update firmware to v1.4.2
    - linux-firmware: liquidio: update firmware to v1.5.1
    - linux-firmware: liquidio: update firmware to v1.6.0
    - firmware: tegra: Add VIC firmware
    - linux-firmware: liquidio: update firmware to v1.6.1
    - rtlwifi: rtl8822be: Add firmware for new driver/device
    - linux-firmware/i915: Add Geminilake DMC version 1.04
    - iwlwifi: add new firmware version 34 for 8000C and 8265
    - linux-firmware: liquidio: update firmware to v1.7.0
    - iwlwifi: add firmware version 34 for new 9000 series
    - amdgpu: add new CP firmware for polaris chips
    - Mellanox: Add new mlxsw_spectrum firmware 13.1530.152
    - brcm: introduce firmware for bcm43430 revision 0
    - amdgpu: add firmware for Raven
    - brcm: add CYW4373 firmwares and Cypress license file
    - amdgpu: update vcn firmware for raven
    - Revert "UBUNTU: Remove obsolete bnx2 firmware"
    - Revert "UBUNTU: Remove duplicate bnx2 firmware"
    - Revert "UBUNTU: Remove obsolete bnx2 firmware"
    - Revert "UBUNTU: Remove obsolete bnx2 firmware"
    - UBUNTU: update nic-firmware.lst for 18.04 hwe kernel

  * Update Qualcomm QCA6174-HMC (DW1820) to comply with CE-RED (Radio
    Emissions Directive) (LP: #1752044)
    - ath10k: QCA6174 hw3.0: update firmware-6.bin to WLAN.RM.4.4.1-00079-QCARMSWPZ-1
    - ath10k: QCA6174 hw3.0: update board-2.bin

 -- Seth Forshee <email address hidden> Tue, 24 Apr 2018 10:58:13 -0500

[Chris Halse Rogers (raof)]

The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.