Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)

Status changed to 'Confirmed' because the bug affects multiple users.

Is bluetooth working for you? I mean are you only reporting the log message, or is bluetooth also not working?

Hello Daniel,

> Is bluetooth working for you?

Yes, work for my

> I mean are you only reporting the log message, or is bluetooth also not working?

It sounds cut

Regards,
--
Cristian

Are you experiencing problems with bluetooth audio?

Confirmed this bug occurs with other bluetooth dongles too.

Still incomplete awaiting an answer to comment #5.

I suspect this log message is getting confused for bluetooth audio skipping, but I think those might be separate issues.

My problem was related to a faulty Bluetooth device. Sorry about the noise, please disregard. Thanks!

i can confirm this issue. bluetooth is working fine (keyboard & mouse).
however makes my console unusable since the message appears every couple of secs.

Confirm that issue too. Message is only printed when Bluetooth controller is discovering for devices.

confirming, imac 27 late 2013
Bluetooth: hci0: last event is not cmd complete (0x0f)

I'm also getting the same error: "Bluetooth: hci0: last event is not cmd complete (0x0f)"
The message always appears as Bluetooth audio starts to skip.

Also the device keeps disconnecting and reconnecting.
There is no message specific to when the device disconnects.
But every time the device reconnects it gets mapped with new input number:

Relevant exerpt:
"
[ +4,517247] input: 00:17:04:00:1F:AF as /devices/virtual/input/input22
[apr14 22:20] input: 00:17:04:00:1F:AF as /devices/virtual/input/input23
[apr14 22:22] input: 00:17:04:00:1F:AF as /devices/virtual/input/input24
[apr14 22:23] input: 00:17:04:00:1F:AF as /devices/virtual/input/input25
[ +27,459091] Bluetooth: hci0: last event is not cmd complete (0x0f)
[apr14 22:24] input: 00:17:04:00:1F:AF as /devices/virtual/input/input26
[ +4,048215] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ +16,005045] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ +16,315024] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ +15,891021] Bluetooth: hci0: last event is not cmd complete (0x0f)
[apr14 22:25] Bluetooth: hci0: last event is not cmd complete (0x0f)
[apr14 22:27] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ +9,471958] input: 00:17:04:00:1F:AF as /devices/virtual/input/input27
[ +6,452024] Bluetooth: hci0: last event is not cmd complete (0x0f)
"

I think this is related to suspend.

If I reboot my computer, and pair my headset, I get sound.

when I suspend my computer and try to turn on the bluetooth connection I get the error message dmesg.

Ubuntu 17.04 did not have this problem, but 17.10 and 18.04 has.

[27656.334177] usb 1-7: USB disconnect, device number 5
[27712.841243] usb 1-7: new full-speed USB device number 11 using xhci_hcd
[27712.990551] usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b
[27712.990556] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[27712.993366] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
[27712.994365] Bluetooth: hci0: Device revision is 16
[27712.994367] Bluetooth: hci0: Secure boot is enabled
[27712.994369] Bluetooth: hci0: OTP lock is enabled
[27712.994370] Bluetooth: hci0: API lock is enabled
[27712.994372] Bluetooth: hci0: Debug lock is disabled
[27712.994375] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[27712.994850] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
[27714.572396] Bluetooth: hci0: Waiting for firmware download to complete
[27714.572400] Bluetooth: hci0: Firmware loaded in 1543294 usecs
[27714.572517] Bluetooth: hci0: Waiting for device to boot
[27714.584421] Bluetooth: hci0: Device booted in 11674 usecs
[27714.584469] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-12-16.ddc
[27714.587439] Bluetooth: hci0: Applying Intel DDC parameters completed
[27719.936384] Bluetooth: hci0: last event is not cmd complete (0x0f)
[27735.811353] Bluetooth: hci0: last event is not cmd complete (0x0f)
[27751.680367] Bluetooth: hci0: last event is not cmd complete (0x0f)
[27766.592465] Bluetooth: hci0: advertising data len corrected
[27769.863398] Bluetooth: hci0: last event is not cmd complete (0x0f)

In my case I have the same issue
4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

If I type
 dmesg | grep -i bluetooth
I get:

[ 2.233539] usb 1-1.4: Product: DW375 Bluetooth Module
[ 35.812010] Bluetooth: Core ver 2.22
[ 35.812026] Bluetooth: HCI device and connection manager initialized
[ 35.812029] Bluetooth: HCI socket layer initialized
[ 35.812032] Bluetooth: L2CAP socket layer initialized
[ 35.812037] Bluetooth: SCO socket layer initialized
[ 36.487377] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 36.487378] Bluetooth: BNEP filters: protocol multicast
[ 36.487381] Bluetooth: BNEP socket layer initialized
[ 63.484470] Bluetooth: RFCOMM TTY layer initialized
[ 63.484478] Bluetooth: RFCOMM socket layer initialized
[ 63.484487] Bluetooth: RFCOMM ver 1.11
[ 460.003598] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 475.007411] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 490.005426] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 505.007211] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 520.003265] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 535.006019] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 550.002996] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 565.005810] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 580.006797] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 595.005627] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 610.005595] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 625.006373] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 640.005272] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 655.006210] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 670.007190] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 685.005978] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 700.003936] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 715.005885] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 730.002791] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 736.002704] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 751.005650] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 766.002556] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 781.005387] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 796.005311] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 811.003208] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 826.004147] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 841.001988] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 856.002863] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 871.006809] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 886.005745] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 901.005710] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 916.004466] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 931.006359] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 946.002300] Bluetooth: hci0: last event is not...

I recommend anyone who wishes to contribute to this bug do so in the upstream bug where the Bluetooth developers are: https://bugzilla.kernel.org/show_bug.cgi?id=198699

Hey, this is actually a 18.04 _show stopper_!

The Bluetooth devices of all 16.04->18.04 upgraded pc's (no matter which controller)
becomes completely unusable :-(

This is probably not a showstopper. You are confusing Bluetooth bugs for a probably harmless bluetooth log message. This but is about the latter.

If something is "completely unusable" then please log a new bug for that.

Confirm this issue too.

laptop : dell xps 15 9550
linux : 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
bluetooth device :
Device xxxxxxxxxxx (public)
 Name: Bluetooth Mouse M557
 Alias: Bluetooth Mouse M557
 Class: 0x00002580
 Icon: input-mouse
 Paired: no
 Trusted: yes
 Blocked: no
 Connected: no
 LegacyPairing: yes
 UUID: Service Discovery Serve.. (00001000-0000-1000-8000-00805f9b34fb)
 UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
 UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
 Modalias: usb:v046DpB010d1001
 RSSI: -36

May 16 09:35:55 joelin-XPS-15-9550 kernel: [ 124.383807] Bluetooth: hci0: last event is not cmd complete (0x0f)
May 16 09:35:57 joelin-XPS-15-9550 bluetoothd[1053]: Can't get HIDP connection info
May 16 09:35:57 joelin-XPS-15-9550 bluetoothd[1053]: connect error: Connection refused (111)
May 16 09:36:11 joelin-XPS-15-9550 kernel: [ 140.255753] Bluetooth: hci0: last event is not cmd complete (0x0f)

I've been running 18.04 on a MacBook Pro (early 2011) and my Bluetooth Ultrathin Touch Mouse worked just fine as did my touchpad for the past month or so.

Then last night I noticed that my touchpad didn't work but Bluetooth mouse did just fine. This morning there was a software update and now Bluetooth mouse bounces between connected and disconnected for a few seconds (about 30 or so) and then just settles on "Disconnected". While the mouse show's connected it doesn't work - the pointer doesn't move when moving the mouse and button clicks don't register either.

I've entered in dmesg | grep Blue and get the same:
"Bluetooth: hci0: last event is not cmd complete (0x0f)"

I can connect my mouse to my Mac OSX MacBook Pro (mid 2015) with no issue as well as to my Microsoft Surface, so I don't feel this is an issue with the mouse.

I also see that there are many devices I cannot pair to, e.g. my Bambo slate, it is discovered fine on my other pcs but just does not appear in the devices list as I make it discoverable and run

I from withing bluethootctl I start to search for a device, some of them show up some don't
my bluethooth hardware is:
Bus 001 Device 003: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
and the kernel keeps reporting the same error
[ 1116.036012] Bluetooth: hci0: last event is not cmd complete (0x0f)

over and over

This bug is not about Bluetooth failing. This bug is only about the kernel log message, which seems to happen even when everything is apparently working.

If you experience a failure of any sort then please log a new bug.

I have the same issue on the fresh install of Ubuntu 18.04

I can't make the headset microphone work and I see this in dmesg when I try to switch the profile from A2DP to HSP/HFP in settings. The profile isn't switching though.

Alexey, see comment #23.

I second comment #14 - that's what happens on my device, too.

I.e. - most of the time, after having suspended my computer, it will not connect to bluetooth and I have to reboot. So this bug _is_ about Bluetooth failing. At least until after a reboot. You could say, it's about "suspend" failing.

The message:

Bluetooth: hci0: last event is not cmd complete (0x0f)

occurs even on machines where Bluetooth is working properly.

So it would be most helpful if anyone is experiencing actual problems to report those in a separate bug.

I can confirm that I also get this message while using my bluetooth headphones. Bluetooth is working fine. This message makes my TTY console sessions completely unusable. For example when I'm editing a file using nano or vi the message is written on top of the file, wherever my cursor was.

In my case, it has nothing to do with suspend or sleep modes. I get the message after a full reboot as well. I'm using ubuntu 18.04.

Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) and I am unable to play anything via bluetooth. Speaker gets connected but can not play audio.

This bug is not related to playback failures. Please log a NEW bug for that by running:

  ubuntu-bug bluez

Hello,

I am creating a new report:
https://bugs.launchpad.net/bugs/1788383

Regards,
--
Cristian Aravena Romero (caravena)

Bug 1788383 is a duplicate of this one.

If you do log a new bug please describe a different issue to that described in this bug.

"So it would be most helpful if anyone is experiencing actual problems to report those in a separate bug."

@Daniel
You might want to reconsider if this is related to Bluetooth failures, at least the message is specifically linked to Bluetooth connection issues as seen in my tests.

See https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/comments/12

The logs show connection issues i have with Bluetooth, as described in https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/comments/11

I don't think so.

Because this error message happens all the time it's going to happen at the same time as other Bluetooth problems. So people will *think* it's related to those other problems because both occur concurrently in the log.

However because we already know this error message happens on healthy machines with no Bluetooth problems we believe that it's just a coincidence both issues happen concurrently, and that any actual problems should be reported as separate bugs.

Ok, you didn't actually read my log output and assume things. The log message disappears completely WHEN my Bluetooth starts working. The actual opposite of your argument. I.e., the message only appears when my machine is "unhealthy". The message does not occur concurrently at all.

Regardless, I can redo my test say 3 times before/after suspend/reboot/logout and if the same pattern occurs it is not a coincident for sure. The message will then be related to the issues (already) reported in several other bug reports.

The coder behind this message is arguing, from what i can surmise, that this is an error that is not handled, not that it is a superfluous debug statement as seen in statements above: https://www.spinics.net/lists/linux-bluetooth/msg75270.html

WRT comment #46: Installing brcm/BCM20702A1-0b05-180a.hcd from winterheart had no effect on this or any other Bluetooth anomalies I've observed except eliminating the "Direct firmware load" error.

WRT comment #51: in my environment this co-occurs with Bluetooth functioning "correctly", i.e. the only issue I see is this error message. (However, I am only using LE, not audio/BR/EDR.)

I suspect it may be related to mixing HCI-based and D-Bus-based bluetooth control within or across applications, or to an application not properly stopping discovery before it shuts down. Or both.

Issuing a "power off" "power on" sequence from bluetoothctl stops the error message. Getting from "unhealthy Bluetooth" to "working Bluetooth" may involve a power cycle, fixing multiple problems.

Everyone, if you would like this bug fixed then the most effective place to discuss it is directly with the Bluetooth/kernel developers here:

  https://bugzilla.kernel.org/show_bug.cgi?id=198699

Hello,
Has anybody checked Ubuntu 18.10?

Hello,
just installed Ubuntu 18.10 on a Lenovo E485 and got this error.

I confirm that too on Dell Precision 5530 (Intel Corporation Wireless-AC 9260) and Manjaro Cinnamon, Kernel 4.19.1
But it only occures if i have Bluetooth device discovery open and then only all 16s! So it must be related to that.
BT Headset is working anyway but sometimes interrupted but recovering.

I've just installed Blueberry on Arch Linux 4.18.17.a-1-hardened and I get this bug as well.
dmesg shows several 'not cmd complete' followed by an input remap. I have only ever seen the message pop up when the Blueberry device manager is open. Last format (read: last week) I used Blueman and did not have this issue so the fault may lie in Blueberry. Skipping still occurs without Blueberry open but no errors are logged.

...
[ 1544.104905] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1555.393338] input: 48:D6:D5:BB:12:02 as /devices/virtual/input/input54
...
[ 1663.107882] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1668.694434] input: 48:D6:D5:BB:12:02 as /devices/virtual/input/input55
... etc

Same issue on latest Manjaro and Intel 7260. Bluetooth is unusable cause of this.

I got a similar problem: many "Bluetooth: hci0: last event is not cmd complete (0x0f)" in dmesg and the sound from the bluetooth speaker is distorted (but connected).

The problem goes away as soon as I close the "bluetooth setting" windows: basically the issue arises only while the controller is searching for new devices.

$ tail -f /var/log/syslog
Dec 1 21:28:26 localhost kernel: [ 683.235091] Bluetooth: hci0: last event is not cmd complete (0x0f)

$ dmesg | grep -i bluetooth
[ 3.368473] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-13d3-3404.hcd failed with error -2
[ 3.368475] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-13d3-3404.hcd not found

I use the step to fix, now I can send file to my phone with bluetooth, and use AirPods :)

https://unix.stackexchange.com/questions/359979/broadcom-bcm4352-bluetooth-does-not-connect?answertab=votes#tab-top

my step:
$ cd /lib/firmware/brcm
$ sudo wget https://github.com/winterheart/broadcom-bt-firmware/raw/master/brcm/BCM20702A1-13d3-3404.hcd
$ sudo modprobe -r btusb
$ sudo modprobe btusb

I'm having the same issue on my Dell 7559 with Intel Dual Band Wireless-AC 8265 (Wi-Fi/BT combo) since forever (around two years ago). Mouse and keyboard works. However, I cannot connect my phone, headset or bluetooth speaker. I'm using 4.20.3-arch1-1-ARCH with Gnome Shell 3.30.2.

I addition to already mentioned error, these also come up:

Jan 18 17:08:09 juozas-laptop pulseaudio[1051]: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected
Jan 18 17:08:15 juozas-laptop pulseaudio[1051]: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected
Jan 18 17:08:20 juozas-laptop bluetoothd[615]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Jan 18 17:11:44 juozas-laptop kernel: Bluetooth: hci0: ACL packet for unknown connection handle 256
Jan 18 17:12:32 juozas-laptop bluetoothd[615]: A0:10:81:85:3B:B2: error updating services: Connection timed out (110)

As I suspected, the error:

  Bluetooth: hci0: last event is not cmd complete (0x0f)

is itself not a bug. The only bug is that the error was displayed when it shouldn't be. So if you have any actual Bluetooth bugs then they should probably be logged elsewhere. That is according to https://bugzilla.kernel.org/show_bug.cgi?id=198699#c24

It appears the "fix" to stop the error message appearing is in the mainline kernel 5.0 (AKA version 4.21) onward.

But again if you have any problems with the behaviour of Bluetooth then please open a new bug.

Why this have changed importance Medium->Low while it's the only method to further debug hardware/firmware problems on lot of platforms ?

> it's the only method to further debug hardware/firmware problems on lot of platforms

I don't know if that is true, but if the message is legitimately being used in debugging then it will keep appearing in future.

For more information see comment #73 above and comment 24 in the kernel bug:
https://bugzilla.kernel.org/show_bug.cgi?id=198699#c24

Specifically, instances of:

  hci0: last event is not cmd complete (0x0f)

are spurious so the message shouldn't be appearing at all. Because 0x0f == HCI_EV_CMD_STATUS. Just ignore the message. Future kernels won't show that message thanks to this fix from Intel:

  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1629db9c75342325868243d6bca5853017d91cf8

I have verified the fix is in Ubuntu 19.04 disco.

That commit fixes the issue for me.

^^^
Is that implying the fix is in proposed?

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

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!

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

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!

Hello Cristian and everyone involved,

The Bionic and Cosmic kernels containing a fix for this issue are now in -proposed. Could anyone please verify if they fix the issue as expected?

Thank you.

Hi all!

The Bionic and Cosmic kernels containing a fix for this issue are now in their "-proposed" repositories. Could someone please verify if they fix the issue you're experiencing?

For those reading that haven't done this before, here are instructions for enabling and using the "-proposed" repository: https://wiki.ubuntu.com/Testing/EnableProposed

Thank you!

This bug was fixed in the package linux - 4.18.0-18.19

---------------
linux (4.18.0-18.19) cosmic; urgency=medium

  * linux: 4.18.0-18.19 -proposed tracker (LP: #1822796)

  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts
    - [Packaging] resync retpoline extraction

  * 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes
    triggers system hang on i386 (LP: #1812845)
    - btrfs: raid56: properly unmap parity page in finish_parity_scrub()

  * [SRU][B/C/OEM]IOMMU: add kernel dma protection (LP: #1820153)
    - ACPI / property: Allow multiple property compatible _DSD entries
    - PCI / ACPI: Identify untrusted PCI devices
    - iommu/vt-d: Force IOMMU on for platform opt in hint
    - iommu/vt-d: Do not enable ATS for untrusted devices
    - thunderbolt: Export IOMMU based DMA protection support to userspace
    - iommu/vt-d: Disable ATS support on untrusted devices

  * Huawei Hi1822 NIC has poor performance (LP: #1820187)
    - net-next: hinic: fix a problem in free_tx_poll()
    - hinic: remove ndo_poll_controller
    - net-next/hinic: add checksum offload and TSO support
    - hinic: Fix l4_type parameter in hinic_task_set_tunnel_l4
    - net-next/hinic:replace multiply and division operators
    - net-next/hinic:add rx checksum offload for HiNIC
    - net-next/hinic:fix a bug in set mac address
    - net-next/hinic: fix a bug in rx data flow
    - net: hinic: fix null pointer dereference on pointer hwdev
    - hinic: optmize rx refill buffer mechanism
    - net-next/hinic:add shutdown callback
    - net-next/hinic: replace disable_irq_nosync/enable_irq

  * [CONFIG] please enable highdpi font FONT_TER16x32 (LP: #1819881)
    - Fonts: New Terminus large console font
    - [Config]: enable highdpi Terminus 16x32 font support

  * [19.04 FEAT] qeth: Enhanced link speed - kernel part (LP: #1814892)
    - s390/qeth: report 25Gbit link speed

  * Avoid potential memory corruption on HiSilicon SoCs (LP: #1819546)
    - iommu/arm-smmu-v3: Avoid memory corruption from Hisilicon MSI payloads

  * CVE-2017-5715
    - x86/speculation: Apply IBPB more strictly to avoid cross-process data leak
    - x86/speculation: Propagate information about RSB filling mitigation to sysfs
    - x86/speculation: Add RETPOLINE_AMD support to the inline asm CALL_NOSPEC
      variant
    - x86/retpoline: Make CONFIG_RETPOLINE depend on compiler support
    - x86/retpoline: Remove minimal retpoline support
    - x86/speculation: Update the TIF_SSBD comment
    - x86/speculation: Clean up spectre_v2_parse_cmdline()
    - x86/speculation: Remove unnecessary ret variable in cpu_show_common()
    - x86/speculation: Move STIPB/IBPB string conditionals out of
      cpu_show_common()
    - x86/speculation: Disable STIBP when enhanced IBRS is in use
    - x86/speculation: Rename SSBD update functions
    - x86/speculation: Reorganize speculation control MSRs update
    - sched/smt: Make sched_smt_present track topology
    - x86/Kconfig: Select SCHED_SMT if SMP enabled
    - sched/smt: Expose sched_smt_present static key
    - x86/speculation: Rework SMT state change
    - x86/l1tf: Show actual SMT state
    - x86/speculation: R...

This bug was fixed in the package linux - 4.15.0-48.51

---------------
linux (4.15.0-48.51) bionic; urgency=medium

  * linux: 4.15.0-48.51 -proposed tracker (LP: #1822820)

  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts
    - [Packaging] resync retpoline extraction

  * 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes
    triggers system hang on i386 (LP: #1812845)
    - btrfs: raid56: properly unmap parity page in finish_parity_scrub()

  * [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats
    (LP: #1719545)
    - cpupower : Fix header name to read idle state name

  * [amdgpu] screen corruption when using touchpad (LP: #1818617)
    - drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3)
    - drm/amdgpu: Free VGA stolen memory as soon as possible.

  * [SRU][B/C/OEM]IOMMU: add kernel dma protection (LP: #1820153)
    - ACPICA: AML parser: attempt to continue loading table after error
    - ACPI / property: Allow multiple property compatible _DSD entries
    - PCI / ACPI: Identify untrusted PCI devices
    - iommu/vt-d: Force IOMMU on for platform opt in hint
    - iommu/vt-d: Do not enable ATS for untrusted devices
    - thunderbolt: Export IOMMU based DMA protection support to userspace
    - iommu/vt-d: Disable ATS support on untrusted devices

  * Add basic support to NVLink2 passthrough (LP: #1819989)
    - powerpc/powernv/npu: Do not try invalidating 32bit table when 64bit table is
      enabled
    - powerpc/powernv: call OPAL_QUIESCE before OPAL_SIGNAL_SYSTEM_RESET
    - powerpc/powernv: Export opal_check_token symbol
    - powerpc/powernv: Make possible for user to force a full ipl cec reboot
    - powerpc/powernv/idoa: Remove unnecessary pcidev from pci_dn
    - powerpc/powernv: Move npu struct from pnv_phb to pci_controller
    - powerpc/powernv/npu: Move OPAL calls away from context manipulation
    - powerpc/pseries/iommu: Use memory@ nodes in max RAM address calculation
    - powerpc/pseries/npu: Enable platform support
    - powerpc/pseries: Remove IOMMU API support for non-LPAR systems
    - powerpc/powernv/npu: Check mmio_atsd array bounds when populating
    - powerpc/powernv/npu: Fault user page into the hypervisor's pagetable

  * Huawei Hi1822 NIC has poor performance (LP: #1820187)
    - net-next: hinic: fix a problem in free_tx_poll()
    - hinic: remove ndo_poll_controller
    - net-next/hinic: add checksum offload and TSO support
    - hinic: Fix l4_type parameter in hinic_task_set_tunnel_l4
    - net-next/hinic:replace multiply and division operators
    - net-next/hinic:add rx checksum offload for HiNIC
    - net-next/hinic:fix a bug in set mac address
    - net-next/hinic: fix a bug in rx data flow
    - net: hinic: fix null pointer dereference on pointer hwdev
    - hinic: optmize rx refill buffer mechanism
    - net-next/hinic:add shutdown callback
    - net-next/hinic: replace disable_irq_nosync/enable_irq

  * [CONFIG] please enable highdpi font FONT_TER16x32 (LP: #1819881)
    - Fonts: New Terminus large console font
    - [Config]: enable highdpi Terminus 16x32 font support

  * [19.04 FEAT] qeth: Enhanced link...