[NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all

Problem also occurs in Ubuntu 19.10 and Ubuntu 18.04

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 1875199

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.

That is because there is no available output device on your machine, please plug sth into the lineout jack, and choose the lineout from gnome-sound-setting, then it will not show dummy audio.

Hi Hui,

Thank you for reviewing my bug report so quickly.

When I gathered the original information in my bug report, standard analog stereo speakers were connected to the host system's 3.5mm analog audio output jack.

The first test tone played by the bug report generator was heard via these speakers, however the second test tone was not. The test tone was the first and only time I have had successful audio output while using Ubuntu on this system.

I do not know if it helps, but prior to installing Ubuntu I had Windows 10 installed and the audio output worked properly with the same external speakers. This would appear to confirm that host system hardware and external speakers are working properly.

The problem only occurs when trying to use any version of Ubuntu (18.04, 19.10 and 20.20)

Please let me know if I can provide any additional information or logs to investigate the problem further, and thank you for your help!

I have uploaded a video that shows the problem in more detail, and shows what happens during the audio tests when using the Ubuntu Audio Bug reporting tool:

https://youtu.be/gJNpK3Mgw2U

Please let me know if I can provide any additional information, and thank you in advance for the help.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Ran the 'apport-collect 1875199' command as requested by Ubuntu Kernel Bot to provide additional information. Also added link to video that shows the behavior in comment #6.

Gentle bump to raise visibility. In more information is needed please let me know.
In the interim I tested the behavior with Linux Mint 19.3, and audio output works correctly when using that distribution.

Thank you!

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc6/

Testing with the the 5.7.0-050700rc6-generic kernel does not change the behavior. Sound output does not work, and the 'Dummy Output' remains in the Sound section within the Settings application.

When testing the system with Linux Mint 19.3 with kernel version 5.3.0-51 #44-18.04.2-Ubuntu sound works properly.

Please let me know if I should provide new logs or any other additional information to help troubleshoot the problem.

Thank you again for your help!

@Robert,

you can't find the external speaker from UI, that is because even you physically plugged the speaker to the lineout audio jack, but in the pulseaudio, the audio jack is not available (not plug anything)
analog-output-lineout: Line Out (priority 9000, latency offset 0 usec, available: no)
   properties:

If you plug out and plug in again, does the available change yes? If not, it is the audio jack detection problem on the kernel driver.

Can this be the same PA regression?
Please test this PPA:
https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

@Hui,

Thank you for looking deeper into the problem, and for your explanation.

I tried disconnecting and reconnecting the speaker to the audio output jack as you suggested, however it did not change the behavior. The 'Dummy Output' remains, and no sound is heard.

@Kai, I added the PPA you linked to, applied the updates, and rebooted my system. Unfortunately, this did not change the behavior. The 'Dummy Output' remains, and no sound is heard.

Please let me know if I can provide any addition information or fresh logs files from my system, as I am happy to do so.

Thank you both again for your help!

Gentle bump to raise visibility. In more information is needed please let me know.

Thank you!

Does your system have Windows installed? I guess we need to dump the codec pin from Windows to move forward.

The system does not have Windows installed at present, however I am happy to install Windows 10 if it helps the investigation.

If you can please just provide instructions for what you would like to me do from within Windows I will do my best to provide the information promptly.

* Just a quick reminder, when using Linux Mint 19.3 on the system the audio output works properly. I have Ubuntu 20.04 and Linux Mint 19.3 setup as a dual-boot, so if any useful information can be gathered from Linux Mint 19.3 I would be happy to provide it *

Thanks again for all of your help!

Great! That means it's a regression, let's do a kernel bisection.

First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the working version you found)
$ git bisect bad $(the non-working version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If it still have the same issue,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the offending commit.

I attempted the process you describe, however I cannot find any kernel version which allows for the audio output to work within Ubuntu 20.04.

To reiterate, when testing the system with Linux Mint 19.3 with kernel version 5.3.0-51 #44-18.04.2-Ubuntu sound works properly.

I used these instructions --> https://wiki.ubuntu.com/Kernel/MainlineBuilds to install these kernel versions from --> http://kernel.ubuntu.com/~kernel-ppa/mainline/ :

4.20.17
5.0.21
5.1.21
5.2.21
5.3
5.3.1
5.3.2
5.3.2
5.3.4
5.3.5
5.3.6
5.3.7
5.3.8
5.3.9
5.3.18
5.4.45
5.5.19
5.6.17
5.7
5.7.1

None of these kernel versions allowed for the audio output device within the system to be detected from within Ubuntu 20.04. Only the 'dummy' audio output shows within settings.

The system is dual-booting Ubuntu 20.04 and Linux Mint 19.3. When I reboot into Linux Mint 19.3, the audio output is recognized and works properly.

Please let me know if I can provide more information from either the Ubuntu installation or Linux Mint installation to help troubleshoot the problem and I will be happy to do so. I can also erase the boot drive and reinstall Windows 10 if that helps.

Thanks again for all of your help!

Can you please attach dmesg under 5.3.0-51?

While the system is booted into Linux Mint 19.3 (with audio working properly), the kernel version is reported as:

Linux NUC8CCHK 5.3.0-53-generic #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

(I think the kernel version may have been updated slightly as a result of an automatic update)

The dmesg log file from the system booting under Linux Mint 19.3 with that kernel is attached.

Thank you for your continued assistance!

Gentle bump to raise visibility. If more information is needed, please let me know.

Thank you!

Ok, it doesn't seem to be a kernel bug then.

Please upgrade the system and retest, the pulse audio is too old:
Package: pulseaudio 1:13.99.1-1ubuntu3

There are several important fix for Pulseaudio in 1:13.99.1-1ubuntu3.3.

Updated the system as requested:

||/ Name Version Architecture Description
+++-==============-====================-============-=================================
ii pulseaudio 1:13.99.1-1ubuntu3.3 amd64 PulseAudio sound server

Unfortunately, the problem remains.
Audio output does not work, only the 'Dummy Output' device is detected.

Please let me know if I can provide any additional information, and thank you as always for your help!

Can you please attach "pactl list" under both Ubuntu and Mint?

Attaching files as requested...

Please let me know if I can provide any additional information, and thank you as always for your help!

Gentle bump to raise visibility. In more information is needed please let me know.

Thank you!

Yea there's no available profile from PulseAudio. Does remove saved config help? i.e.
$ rm -r ~/.config/pulse/

Ran command as requested, no change in behavior.
Audio output device not detected, only 'Dummy Output' is present in Sound Settings

Rebooted system after change, and tested again. No change in behavior.
Audio output device not detected, only 'Dummy Output' is present in Sound Settings

Please let me know if I can provide any additional information, and thank you as always for the help!

Hmm, it does seems to be a PulseAudio regression.

Can you please test 20.04 based Mint?

@Robert,

the PA in the ubuntu is 13.99 while the PA in the min is 11.1. It is because PA introduced a commit after 11.1, BTW, if you plug sth in the line-out port, what will happen?

@Kai-Heng,

I tested the behavior of Linux Mint 20 via a Live USB stick and the audio output did NOT work. The only audio device detected is a 'Dummy Output' device. This behavior matches that of Ubuntu 20.04.

To put that another way, there appears to have been a regression in behavior between Linux Mint 19.3 and Linux Mint 20. Audio does work with Linux Mint 19.3. Audio does not work in Linux Mint 20.

@Hui,

You ask, "...if you plug sth in the line-out port, what will happen?"

I am afraid I am not quite sure what you are asking me to do. Could you please provide some additional detail?

Just a reminder, at every point during my testing standard analog speakers have been powered on and connected to the host system's 3.5mm audio output jack. To put that another way, I am testing with a 'real' hardware setup.

Please let me know if I can provide any additional information, and thank you both as always for the help!

Would it be possible to test upstream PulseAudio? I am not sure if there's any easy way to test it under Ubuntu though...

@Kai-Heng,

I am happy to do whatever is necessary to help isolate the cause of the problem.

If you are able to provide instructions for what you would like me to try, I will do my best to ensure they are followed precisely.

There is no real data on the system, so I happy to allow you to remote access to the system if that would be helpful.

Thank you as always for the help!

Pulseaudio introduced this commit, this commit introduce your issue.

0d50e787f86b385bf33aeb53b16ca40543f1db63

    alsa-card: improve the profile availability logic

    When a new card shows up (during pulseaudio startup or hotplugged),
    pulseaudio needs to pick the initial profile for the card. Unavailable
    profiles shouldn't be picked, but module-alsa-card sometimes marked
    unavailable profiles as available, causing bad initial profile choices.

    This patch changes module-alsa-card so that it marks all profiles
    unavailable whose all output ports or all input ports are unavailable.
    Previously only those profiles were marked as unavailable whose all
    ports were unavailable. For example, if a profile contains one sink and
    one source, and the sink is unavailable and the source is available,
    previously such profile was marked as available, but now it's marked as
    unavailable.

    BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=102902

@Robert,

I don't know if it is a regression or not, if there is nothing to be plugged in the 3.5mm audio jack, the output shows dummy output, if you plug sth into the 3.5mm audio jack, does the output change to lineout/headphone?

The log you posted in the #42 shows:
analog-output-lineout: Line Out (priority: 9000, latency offset: 0 usec, not available)
   Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo

I want your to pug sth in that lineout audio jack (3.5mm audio jack) and make it to be "available" instead of "not available"

BTW, I already reported to the pulseaudio community for that commit since that commit introduced some issues different from this one, but no feedback yet.
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/927

@Hui,

Thank you for your efforts here, they are much appreciated.

You ask,"...if you plug sth into the 3.5mm audio jack, does the output change to lineout/headphone?"

I am afraid I am not sure what 'sth' means when you say, '...plug sth into the 3.5mm audio jack...'

Does 'sth' refer to stereo headphones? (as opposed to stereo speakers)

Apologies in advance if the question is in any way redundant, however I just want to make sure I understand your wishes correctly and not make any incorrect assumptions.

Just to reiterate and to be clear, at every point during my testing standard analog speakers have been powered on and connected to the host system's 3.5mm audio output jack.

To put that another way, I am testing with a 'real' hardware setup.

This is documented in the demonstration video I made about the problem --> https://youtu.be/gJNpK3Mgw2U

Assuming for the moment that my understanding as described is correct, I tested again in the following manner:

1. Simple stereo headphones connected to the 3.5mm analog audio output port of the host.
2. Ran 'pactl list' command.
3. Relevant snippet from the tool output is identical to what is seen in the previous log (and what you describe):

analog-output-lineout: Line Out (priority: 9000, latency offset: 0 usec, not available)
   Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo

4. Disconnected stereo headphones from host system.
5. Connected stereo analog speakers to the 3.5mm analog audio output port of the host.
6. Ran 'pactl list' command again.
7. Relevant snippet from the tool output is identical as before:

analog-output-lineout: Line Out (priority: 9000, latency offset: 0 usec, not available)
   Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo

8. In both cases despite having an audio output device connected to the host, the entry in the log file output is still listed as 'not available'

Please let me know if I can provide any additional information, and thank you as always for the help!

Gentle bump to raise visibility. If more information is needed, please let me know.

Thank you!

Ok, I guess we need override a pin for it. I am checking the device spec, and it says the jack is "Speaker/Headset Jack", but icon indicates it only support outputs. Does it support mic?

Also, you can use "hdajackretask" to see if overriding some pins helps.

@Kai-Heng,

Apologies for the delay in my reply...

I tested to the best of my ability using the Audacity audio application in both Linux Mint 19.3 (where audio output works) and Ubuntu 20.04 (where audio output does not work) and it appears that audio input via microphones is not supported.

I tested with a standard microphone as well as with a combination headset with an integrated microphone.

Based on the block diagram on page 35 (printed page 27) of the technical specifications for the unit --> https://www.intel.com/content/dam/support/us/en/documents/mini-pcs/NUC8CCH_TechProdSpec.pdf it appears that the audio port is only a line out jack.

I attempted to use the "hdajackretask" application you mention, however when attempting to do so I receive an error message 'Device or resource busy' when I attempt to apply the override. I have attached a screenshot of the specific error.

Please let me know if I can provide any additional information, and thank you as always for the help!

Please test the kernel here:
https://people.canonical.com/~khfeng/lp1875199/

@Kai-Heng,

Short version - Audio output is now working properly using the test kernel you provided. However, I am not quite sure if I did the update correctly.

More detail:
------------

- I downloaded all of the kernel *.deb files you provided and tried installing them all using this command:

sudo dpkg -i *.deb

When I did so, all but one of the packages installed properly. I have provided the full text of the error in the attached file 'installation_error.txt'

Despite this error, I rebooted the system to see what would happen.

Upon rebooting, the system provides this output from running 'uname -a':

Linux NUC8CCHK 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

I make mention only because I am unsure if I did anything incorrectly, so I wanted to make you aware.

That said, now when I access the 'Sound' settings, I now see a 'Line-out Built-in Audio' option under 'Output Device'. Prior to this the only option was a 'Dummy Output'.

I can now successfully test the audio output from within the 'Sound' settings application (and I hear the female voice appropriately on both the right and left channel), and audio output works properly when playing back a YouTube video via Firefox.

In short, things are now working as expected. Despite this, I am unsure if I performed the update properly, and as a result I am unsure if I inadvertently tainted the results in any way.

May I ask what you changed in the test kernel you provided?

May I provide any updated files from my system for your review?

Thank you as always for your help!

I had this problem on nuc10i7fnb
it worked when I disabled jack sensing by using hdajackretask as @kaihengfeng suggested.

I had to use "Install boot override" cause when I tried "Apply now" I got error : "Device or resource busy"

Kamil Sztuke,
Can you please file a new bug? Thanks.

The installation error should be harmless. Those kernels can be removed safely.

https://lkml.org/lkml/2020/8/7/140

@Kai-Heng,

Thank you very much for your efforts here. I just wanted to provide a quick update...

Short version - I have been able to repeat the positive result using the updated kernel you provide on a fresh install of Ubuntu 20.04.1 (the recent point release).

More detail -

Since Ubuntu 20.04.1 was just released, I decided to completely erase the system once again and install Ubuntu 20.04.1 from the latest .ISO

I performed the installation and then applied all of the software updates (there were not very many, which I understand is to be expected).

While in this 'fresh' state, the audio output did not work (which again was expected).

I followed the same procedure as I did before (as described in comment #60 --> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/comments/60) to install the updated kernel you provided in comment #59 --> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/comments/59

When I did so, as happened before all but one of the packages installed properly. I have provided the full text of the error in the attached file 'installation_log_ver2.txt'

Despite this error, I rebooted the system.

Upon rebooting, the system provides this output from running 'uname -a':

Linux NUC8CCHK 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

I make mention once again only because I am unsure if I did anything incorrectly, so I wanted to make you aware.

That said, I did experience the same positive result in that audio output now works properly.

Now when I access the 'Sound' settings, I now see a 'Line-out Built-in Audio' option under 'Output Device'. Prior to this the only option was a 'Dummy Output'.

I can now successfully test the audio output from within the 'Sound' settings application (and I hear the female voice appropriately on both the right and left channel), and audio output works properly when playing back a YouTube video via Firefox.

In summation, I was able to repeat the positive result using your updated kernel on a fresh install of Ubuntu 20.04.1 and audio output on this system works as expected.

Despite this, I wanted to make you aware of the error I received during the installation on the off chance that would be of interest.

I would like to thank you again for all of your help throughout the process, it is very much appreciated.

Please let me know if I can provide any additional information regarding this issue and I will be happy to do so.

The error is because the testing kernel version is clashed with the install kernel version. I should've bumped the version number...

Anyway, everything is good now, the patch is upstreamed and we just need to wait until the patch lands to Ubuntu kernel.

@Kai-Heng,

Thank you for the explanation of the error, and thank you once again for your help throughout the process it is very much appreciated.

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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

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 was fixed in the package linux - 5.8.0-19.20

---------------
linux (5.8.0-19.20) groovy; urgency=medium

  * groovy/linux: 5.8.0-19.20 -proposed tracker (LP: #1895120)

  * Please switch default, hwe, oem kernel flavours governor to
    CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that advanced userspace
    utilities such as game-mode can be later used to rev-up to to performance,
    or rev-down to powersave. (LP: #1885730)
    - [Config] Set the default CPU governor to ONDEMAND

  * Packaging resync (LP: #1786013)
    - update dkms package versions
    - [Packaging] update variants

  * [WD19TB] external DP failed with DRM error message (LP: #1886165)
    - drm/i915/tgl+: Use the correct DP_TP_* register instances in MST encoders
    - drm/i915/tgl+: Fix TBT DPLL fractional divider for 38.4MHz ref clock

  * Groovy update: v5.8.8 upstream stable release (LP: #1895097)
    - hwmon: (pmbus/isl68137) remove READ_TEMPERATURE_1 telemetry for RAA228228
    - HID: quirks: Always poll three more Lenovo PixArt mice
    - drm/msm/dpu: Fix reservation failures in modeset
    - drm/msm/dpu: Fix scale params in plane validation
    - drm/msm/dpu: fix unitialized variable error
    - tty: serial: qcom_geni_serial: Drop __init from qcom_geni_console_setup
    - drm/msm: add shutdown support for display platform_driver
    - hwmon: (applesmc) check status earlier.
    - nvmet: Disable keep-alive timer when kato is cleared to 0h
    - drm/msm: enable vblank during atomic commits
    - habanalabs: unmap PCI bars upon iATU failure
    - habanalabs: validate packet id during CB parse
    - habanalabs: set clock gating according to mask
    - habanalabs: proper handling of alloc size in coresight
    - habanalabs: set max power according to card type
    - habanalabs: validate FW file size
    - habanalabs: check correct vmalloc return code
    - drm/msm/a6xx: fix gmu start on newer firmware
    - gfs2: add some much needed cleanup for log flushes that fail
    - hv_utils: return error if host timesysnc update is stale
    - hv_utils: drain the timesync packets on onchannelcallback
    - ceph: don't allow setlease on cephfs
    - i2c: iproc: Fix shifting 31 bits
    - drm/omap: fix incorrect lock state
    - irqchip/ingenic: Leave parent IRQ unmasked on suspend
    - cpuidle: Fixup IRQ state
    - nbd: restore default timeout when setting it to zero
    - s390: don't trace preemption in percpu macros
    - drm/amd/display: should check error using DC_OK
    - drm/amd/display: Reject overlay plane configurations in multi-display
      scenarios
    - drivers: gpu: amd: Initialize amdgpu_dm_backlight_caps object to 0 in
      amdgpu_dm_update_backlight_caps
    - drm/amd/display: Revert HDCP disable sequence change
    - drm/amd/display: Fix passive dongle mistaken as active dongle in EDID
      emulation
    - drm/amd/display: Keep current gain when ABM disable immediately
    - drm/amd/display: Retry AUX write when fail occurs
    - drm/amd/display: Fix memleak in amdgpu_dm_mode_config_init
    - xen/xenbus: Fix granting of vmalloc'd memory
    - fsldma: fix very broken 32-bit ppc ioread64 functionality
    - dmaengine: of-dma: Fix of_dma_router_xla...

I can confirm that when using the updated 'proposed' kernel (version 5.4.0-49-generic) that audio output works properly on my Intel NUC8CCHK test system.

Thank you to everyone that helped identify and fix this issue, your efforts are much appreciated.

I am trying to follow the directions in the automated comment #68 --> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/comments/68 however I am unsure of how to change the status of this issue to properly confirm the fix. If anyone else could provide some additional guidance (or change the status for me) that would be much appreciated.

Thank you!

I found the proper area to update the tags (it was not obvious, at least to me) and have changed it to 'verification-done-focal' as requested.

If anyone else can verify this has been done correctly, that would be much appreciated (I would hate to see this change reverted).

Thank you!

This bug was fixed in the package linux - 5.4.0-51.56

---------------
linux (5.4.0-51.56) focal; urgency=medium

  * Packaging resync (LP: #1786013)
    - update dkms package versions

linux (5.4.0-50.55) focal; urgency=medium

  * CVE-2020-16119
    - SAUCE: dccp: avoid double free of ccid on child socket

  * CVE-2020-16120
    - Revert "UBUNTU: SAUCE: overlayfs: ensure mounter privileges when reading
      directories"
    - ovl: pass correct flags for opening real directory
    - ovl: switch to mounter creds in readdir
    - ovl: verify permissions in ovl_path_open()
    - ovl: call secutiry hook in ovl_real_ioctl()
    - ovl: check permission to open real file

linux (5.4.0-49.53) focal; urgency=medium

  * focal/linux: 5.4.0-49.53 -proposed tracker (LP: #1896007)

  * Comet Lake PCH-H RAID not support on Ubuntu20.04 (LP: #1892288)
    - ahci: Add Intel Comet Lake PCH-H PCI ID

  * Novalink (mkvterm command failure) (LP: #1892546)
    - tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()

  * Oops and hang when starting LVM snapshots on 5.4.0-47 (LP: #1894780)
    - SAUCE: Revert "mm: memcg/slab: fix memory leak at non-root kmem_cache
      destroy"

  * Intel x710 LOMs do not work on Focal (LP: #1893956)
    - i40e: Fix LED blinking flow for X710T*L devices
    - i40e: enable X710 support

  * Add/Backport EPYC-v3 and EPYC-Rome CPU model (LP: #1887490)
    - kvm: svm: Update svm_xsaves_supported

  * Fix non-working NVMe after S3 (LP: #1895718)
    - SAUCE: PCI: Enable ACS quirk on CML root port

  * Focal update: v5.4.65 upstream stable release (LP: #1895881)
    - ipv4: Silence suspicious RCU usage warning
    - ipv6: Fix sysctl max for fib_multipath_hash_policy
    - netlabel: fix problems with mapping removal
    - net: usb: dm9601: Add USB ID of Keenetic Plus DSL
    - sctp: not disable bh in the whole sctp_get_port_local()
    - taprio: Fix using wrong queues in gate mask
    - tipc: fix shutdown() of connectionless socket
    - net: disable netpoll on fresh napis
    - Linux 5.4.65

  * Focal update: v5.4.64 upstream stable release (LP: #1895880)
    - HID: quirks: Always poll three more Lenovo PixArt mice
    - drm/msm/dpu: Fix scale params in plane validation
    - tty: serial: qcom_geni_serial: Drop __init from qcom_geni_console_setup
    - drm/msm: add shutdown support for display platform_driver
    - hwmon: (applesmc) check status earlier.
    - nvmet: Disable keep-alive timer when kato is cleared to 0h
    - drm/msm: enable vblank during atomic commits
    - habanalabs: validate FW file size
    - habanalabs: check correct vmalloc return code
    - drm/msm/a6xx: fix gmu start on newer firmware
    - ceph: don't allow setlease on cephfs
    - drm/omap: fix incorrect lock state
    - cpuidle: Fixup IRQ state
    - nbd: restore default timeout when setting it to zero
    - s390: don't trace preemption in percpu macros
    - drm/amd/display: Reject overlay plane configurations in multi-display
      scenarios
    - drivers: gpu: amd: Initialize amdgpu_dm_backlight_caps object to 0 in
      amdgpu_dm_update_backlight_caps
    - drm/amd/display: Retry AUX write when fail occurs
    - drm/amd/display: Fix memleak in amdg...