[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
https://lists.ubuntu.com/archives/kernel-team/2021-September/123898.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1892213
Title:
psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with
focal/groovy/hirsute/impish
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Bug description:
[Impact]
The expected to fail 'raw gso min size - 1' test in psock_snd.sh is
not failing as expected, and thus this test will fail with:
raw gso min size - 1 (expected to fail)
tx: 1524
rx: 1472
OK
This is because after commit 7c6d2ec ("net: be more gentle about silly
gso requests coming from user"), we relaxed the min gso_size check in
virtio_net_hdr_to_skb().
So when a packet which is smaller then the gso_size, GSO for this
packet will not be set, the packet will be send/recv successfully.
[Fix]
* cfba3fb68960b4 selftests/net: remove min gso test in packet_snd
This patch can be cherry-picked into all affected kernels.
I decided to skip those 5.8 variants, as the current cycle
(2021-09-06) might be the last cycle for them.
[Test]
Run this psock_snd.sh script, this test will no longer exist and the
script can proceed with the next test.
[Where problems could occur]
Removing this broken test should not have any negative impact to our
tests. We will need to update our hints later.
[Original Bug Report]
Testing failed on focal/linux 5.4.0-44.48:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz
psock_snd.sh output:
16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh
16:28:31 DEBUG| [stdout] # dgram
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # dgram bind
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw bind
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw qdisc bypass
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw vlan
16:28:31 DEBUG| [stdout] # tx: 146
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw vnet hdr
16:28:31 DEBUG| [stdout] # tx: 152
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw csum_off
16:28:31 DEBUG| [stdout] # tx: 152
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails)
16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
16:28:31 DEBUG| [stdout] # raw min size
16:28:31 DEBUG| [stdout] # tx: 42
16:28:31 DEBUG| [stdout] # rx: 0
16:28:31 DEBUG|
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
** Description changed:
[Impact]
- The expected to fail 'raw gso min size - 1' test in psock_snd.sh is always
failing with:
+ The expected to fail 'raw gso min size - 1' test in psock_snd.sh is
+ not failing as expected, and thus this test will fail with:
- raw gso min size - 1 (expected to fail)
- tx: 1524
- rx: 1472
- OK
+ raw gso min size - 1 (expected to fail)
+ tx: 1524
+ rx: 1472
+ OK
This is because after commit 7c6d2ec ("net: be more gentle about silly
- gso requests coming from user"), we relaxed the min gso_size check in
virtio_net_hdr_to_skb().
- So when a packet which is smaller then the gso_size,
- GSO for this packet will not be set, the packet will be
- send/recv successfully.
+ gso requests coming from user"), we relaxed the min gso_size check in
+ virtio_net_hdr_to_skb().
+
+ So when a packet which is smaller then the gso_size, GSO for this
+ packet will not be set, the packet will be send/recv successfully.
[Fix]
* cfba3fb68960b4 selftests/net: remove min gso test in packet_snd
This patch can be cherry-picked into all affected kernels.
- I will skip those 5.8 variants, as the current cycle (2021-09-06) might be
the last cycle for them.
+
+ I decided to skip those 5.8 variants, as the current cycle
+ (2021-09-06) might be the last cycle for them.
[Test]
- Run this psock_snd.sh script, this test will no longer exist and the script
can proceed to the next test.
+ Run this psock_snd.sh script, this test will no longer exist and the
+ script can proceed with the next test.
[Where problems could occur]
- Removing this broken test should not have any negative impact to our tests.
+ Removing this broken test should not have any negative impact to our
+ tests. We will need to update our hints later.
[Original Bug Report]
Testing failed on focal/linux 5.4.0-44.48:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz
psock_snd.sh output:
16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh
16:28:31 DEBUG| [stdout] # dgram
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # dgram bind
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw bind
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw qdisc bypass
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw vlan
16:28:31 DEBUG| [stdout] # tx: 146
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw vnet hdr
16:28:31 DEBUG| [stdout] # tx: 152
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw csum_off
16:28:31 DEBUG| [stdout] # tx: 152
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails)
16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
16:28:31 DEBUG| [stdout] # raw min size
16:28:31 DEBUG| [stdout] # tx: 42
16:28:31 DEBUG| [stdout] # rx: 0
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw mtu size
16:28:31 DEBUG| [stdout] # tx: 1514
16:28:31 DEBUG| [stdout] # rx: 1472
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails)
16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long
16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails)
16:28:31 DEBUG| [stdout] #
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
** Description changed:
[Impact]
The expected to fail 'raw gso min size - 1' test in psock_snd.sh is always
failing with:
raw gso min size - 1 (expected to fail)
tx: 1524
rx: 1472
OK
This is because after commit 7c6d2ec ("net: be more gentle about silly
gso requests coming from user"), we relaxed the min gso_size check in
virtio_net_hdr_to_skb().
So when a packet which is smaller then the gso_size,
GSO for this packet will not be set, the packet will be
send/recv successfully.
[Fix]
* cfba3fb68960b4 selftests/net: remove min gso test in packet_snd
- This patch can be cherry-picked into affected kernels.
+ This patch can be cherry-picked into all affected kernels.
+ I will skip those 5.8 variants, as the current cycle (2021-09-06) might be
the last cycle for them.
[Test]
Run this psock_snd.sh script, this test will no longer exist and the script
can proceed to the next test.
- [Impact]
+ [Where problems could occur]
+ Removing this broken test should not have any negative impact to our tests.
+
[Original Bug Report]
Testing failed on focal/linux 5.4.0-44.48:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz
psock_snd.sh output:
16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh
16:28:31 DEBUG| [stdout] # dgram
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # dgram bind
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw bind
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw qdisc bypass
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw vlan
16:28:31 DEBUG| [stdout] # tx: 146
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw vnet hdr
16:28:31 DEBUG| [stdout] # tx: 152
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw csum_off
16:28:31 DEBUG| [stdout] # tx: 152
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails)
16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
16:28:31 DEBUG| [stdout] # raw min size
16:28:31 DEBUG| [stdout] # tx: 42
16:28:31 DEBUG| [stdout] # rx: 0
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw mtu size
16:28:31 DEBUG| [stdout] # tx: 1514
16:28:31 DEBUG| [stdout] # rx: 1472
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails)
16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long
16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails)
16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long
16:28:32 DEBUG| [stdout] # dgram mtu size
16:28:32 DEBUG| [stdout] # tx: 1500
16:28:32 DEBUG| [stdout] # rx: 1472
16:28:32 DEBUG| [stdout] # OK
16:28:32 DEBUG| [stdout] #
16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails)
16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long
16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive)
16:28:32 DEBUG| [stdout] # tx: 14
16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable
16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL)
16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
16:28:32 DEBUG| [stdout] # raw gso min size
16:28:32 DEBUG|
[Kernel-packages] [Bug 1936708] Re: Wobbly graphics on built-in display since linux-image-5.11.0-22-generic
I filed a new SRU tracker here: LP: #1942972. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1936708 Title: Wobbly graphics on built-in display since linux- image-5.11.0-22-generic Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Wobbly graphics after a kernel update. [Fix] Older panels may require more bandwidth then advertised, so we need to use max params for them. [Test] Multiple users tested with positive result. [Where problems could occur] This patch reverts to the old behavior, which is to use max parameters, for older panels. If there's any new panel reports with older DP version, this might change the behavior on it. == Original Bug Report == Lenovo laptop with Intel + Nvidia graphics. Since booting from linux-image-5.11.0-22-generic, the built-in display is unusable, with wobbling horizontal stripes from the disk decryption prompt onwards: https://www.youtube.com/watch?v=LyRTuPzCe2I HDMI output works fine. If I boot from linux-image-5.11.0-18-generic instead, all is well. If I use Recovery mode with linux-image-5.11.0-22-generic and continue bootup, it's usable but there's no HDMI output. I think others may be having this issue too: https://askubuntu.com/questions/1351188/weird-graphical-glitches-appears-only-on-integrated-display-on-any-ubuntu-base# ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1598 F pulseaudio /dev/snd/controlC0: alex 1598 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 17 09:50:31 2021 InstallationDate: Installed on 2021-01-03 (194 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 80DU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-22 (55 days ago) dmi.bios.date: 08/18/2014 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y70-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y70-70 Touch dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:br1.49:efr1.49:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 80DU dmi.product.sku: LENOVO_MT_80DU_BU_idea_FM_Lenovo Y70-70 Touch dmi.product.version: Lenovo Y70-70 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942972] [NEW] Update fix for LP: #1936708
Public bug reported: [Impact] There's a new fix for LP: #1936708, and it's more reliable than the old approach. So replace it. [Fix] Use eDP as predicate to enable max params. [Test] Users confirmed the fix can resolve their issue. [Where problems could occur] This patch reverts to the old behavior, which is to use max parameters, for older panels. If there's any new panel reports with older eDP version, this might change the behavior on it. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: Confirmed ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Confirmed ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Hirsute) Status: New => Invalid -- 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/1942972 Title: Update fix for LP: #1936708 Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] There's a new fix for LP: #1936708, and it's more reliable than the old approach. So replace it. [Fix] Use eDP as predicate to enable max params. [Test] Users confirmed the fix can resolve their issue. [Where problems could occur] This patch reverts to the old behavior, which is to use max parameters, for older panels. If there's any new panel reports with older eDP version, this might change the behavior on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940610] Re: Fix mic noise on HP ProBook 445 G8
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1940610 Title: Fix mic noise on HP ProBook 445 G8 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] There's mic noise on HP ProBook 445 G8. [Fix] Limit mic boost to make the audio capture crystal clear. [Test] $ arecord -f dat test $ aplay test With the fix, the mic noise is gone. [Where problems could occur] If someone would like to let others hear the noise in Zoom, this will deprive of their pleasure. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936682] Re: Fix kernel panic caused by legacy devices on AMD platforms
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1936682 Title: Fix kernel panic caused by legacy devices on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] When a legacy device is only 32bit DMA capable and it's in the same IOMMU group with iommu_v2 capable devices, the device in question will be forced to use identity mapping and triggers kernel panic on DMA operation because it can't do 64bit DMA. [Fix] Keep swiotlb enabled so legacy devices can do 64bit DMA. This is also how Intel and ARM64 platforms deal with legacy devices. [Test] Boot an affected system. Kernel panic in Realtek WiFi driver's probe routine. After the patch is applied, the system can work normally. [Where problems could occur] The default swiotlb uses 64MB memory, so if the system doesn't have any legacy device, there are 64MB ram less for the system to use. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Hirsute)
Status: Confirmed => In Progress
** No longer affects: linux-oem-5.10 (Ubuntu Groovy)
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** No longer affects: linux-oem-5.14 (Ubuntu Groovy)
** No longer affects: linux-oem-5.13 (Ubuntu Groovy)
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Groovy)
Assignee: Po-Hsu Lin (cypressyew) => (unassigned)
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-oem-5.10 (Ubuntu Hirsute)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1892213
Title:
psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with
focal/groovy/hirsute/impish
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
New
Status in linux-oem-5.13 package in Ubuntu:
New
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Bug description:
[Impact]
The expected to fail 'raw gso min size - 1' test in psock_snd.sh is always
failing with:
raw gso min size - 1 (expected to fail)
tx: 1524
rx: 1472
OK
This is because after commit 7c6d2ec ("net: be more gentle about silly
gso requests coming from user"), we relaxed the min gso_size check in
virtio_net_hdr_to_skb().
So when a packet which is smaller then the gso_size,
GSO for this packet will not be set, the packet will be
send/recv successfully.
[Fix]
* cfba3fb68960b4 selftests/net: remove min gso test in packet_snd
This patch can be cherry-picked into affected kernels.
[Test]
Run this psock_snd.sh script, this test will no longer exist and the script
can proceed to the next test.
[Impact]
[Original Bug Report]
Testing failed on focal/linux 5.4.0-44.48:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz
psock_snd.sh output:
16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh
16:28:31 DEBUG| [stdout] # dgram
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # dgram bind
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw bind
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw qdisc bypass
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
[Kernel-packages] [Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
That's why the instructions in comment #29 say to install them together (in a single command): sudo dpkg -i linux*.deb -- 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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX
[Kernel-packages] [Bug 1933790] Re: Request to pull-in new HBA11 PCI-id from upstream
The previous branch in comment 4 is for impish, this branch is for focal. https://code.launchpad.net/~mreed8855/ubuntu/+source/hwdata/+git/hwdata/+ref/hba11_focal_pci_ids -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1933790 Title: Request to pull-in new HBA11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: HBA-11 is a shipping card supported since early Ubuntu 20.04 onwards, however a new form factor is being launched by which has a new subsystem-id. Request is to pull this pci-id to upcoming Ubuntu 20.04 builds. PCI-id details: 1000:00e6:1028:2175 External links: http://pci-ids.ucw.cz/read/PC/1000/00e6/10282175 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1933790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934428] Re: Request to pull-in new PERC11 PCI-id from upstream
This branch is for focal. The previous branch in comment #1 is for impish https://code.launchpad.net/~mreed8855/ubuntu/+source/hwdata/+git/hwdata/+ref/perc11_focal_pci_ids -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1934428 Title: Request to pull-in new PERC11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: 1000:10e2:1028:2171 PERC H750 Mini 1000:10e6:1028:2172 PERC H355 Adapter 1000:10e6:1028:2173 PERC H355 Front 1000:10e6:1028:2174 PERC H350 Mini 1000:10e2:1028:2176 PERC H750 Adapter 1000:10e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942830] Re: Fix sluggish r8169 by disaling ASPM L1.2
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942830 Title: Fix sluggish r8169 by disaling ASPM L1.2 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: [Impact] Realtek r8169 has abysmal network speed. [Fix] Disable ASPM L1.2 because the device takes a long time to exit from L1.2. [Test] Use `iperf` to test network speed. When ASPM L1.2 gets disabled, TX and RX and reach ~700Mbps and ~900Mbps respectively. [Where problems could occur] Disabling ASPM L1.2 can slightly increase power consumption. The CPU package C-State seems to be unaffected so the increase is rather minor. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942830/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/4.15.0.157.146)
All autopkgtests for the newly accepted linux-meta (4.15.0.157.146) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (s390x) linux/4.15.0-157.164 (ppc64el, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942952] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1942952 Title: Kernel Call Trace on Secure Boot Status in linux package in Ubuntu: Confirmed Bug description: Could the call traces in dmesg be related to UEFI secure boot? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 948 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Sep 7 21:05:54 2021 InstallationDate: Installed on 2021-09-06 (1 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M |__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic root=/dev/mapper/vgkubuntu-root ro ipv6.disable=1 elevator=deadline splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 15.63 dmi.bios.vendor: Insyde dmi.bios.version: F.63 dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 76.32 dmi.modalias: dmi:bvnInsyde:bvrF.63:bd03/25/2021:br15.63:efr76.32:svnHP:pn:pvr:sku:rvnHP:rn84B6:rvrKBCVersion76.32:cvnHP:ct10:cvrChassisVersion: dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942952] [NEW] Kernel Call Trace on Secure Boot
Public bug reported: Could the call traces in dmesg be related to UEFI secure boot? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 948 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Sep 7 21:05:54 2021 InstallationDate: Installed on 2021-09-06 (1 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M |__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic root=/dev/mapper/vgkubuntu-root ro ipv6.disable=1 elevator=deadline splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 15.63 dmi.bios.vendor: Insyde dmi.bios.version: F.63 dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 76.32 dmi.modalias: dmi:bvnInsyde:bvrF.63:bd03/25/2021:br15.63:efr76.32:svnHP:pn:pvr:sku:rvnHP:rn84B6:rvrKBCVersion76.32:cvnHP:ct10:cvrChassisVersion: dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1942952 Title: Kernel Call Trace on Secure Boot Status in linux package in Ubuntu: New Bug description: Could the call traces in dmesg be related to UEFI secure boot? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 948 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Sep 7 21:05:54 2021 InstallationDate: Installed on 2021-09-06 (1 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M |__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic root=/dev/mapper/vgkubuntu-root ro ipv6.disable=1 elevator=deadline splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 15.63 dmi.bios.vendor: Insyde dmi.bios.version: F.63 dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 76.32 dmi.modalias: dmi:bvnInsyde:bvrF.63:bd03/25/2021:br15.63:efr76.32:svnHP:pn:pvr:sku:rvnHP:rn84B6:rvrKBCVersion76.32:cvnHP:ct10:cvrChassisVersion: dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939205] Re: sound dummy output 21.04
laura@livingroom:~$ pulseaudio --kill && pulseaudio --start - --log-target=[file:~/pulseaudio.txt]file:~/pulseaudio.txt E: [pulseaudio] log.c: Invalid log target. E: [pulseaudio] cmdline.c: Invalid log target: use either 'syslog', 'journal', 'stderr' or 'auto' or a valid file name 'file:', 'newfile:'. E: [pulseaudio] main.c: Failed to parse command line. laura@livingroom:~$ pulseaudio --kill && pulseaudio --start - --log-target=[file:~/pulseaudio.txt]file:~/pulseaudio.txt E: [pulseaudio] log.c: Invalid log target. E: [pulseaudio] cmdline.c: Invalid log target: use either 'syslog', 'journal', 'stderr' or 'auto' or a valid file name 'file:', 'newfile:'. E: [pulseaudio] main.c: Failed to parse command line. laura@livingroom:~$ pulseaudio --kill && pulseaudio --start - --log-target=[file:~/pulseaudio.txt]file:~/pulseaudio.txt E: [pulseaudio] main.c: Failed to kill daemon: No such process laura@livingroom:~$ pulseaudio --kill && pulseaudio --start - --log-target=[file:~/pulseaudio.txt]file:~/pulseaudio.txt E: [pulseaudio] main.c: Failed to kill daemon: No such process laura@livingroom:~$ pulseaudio --kill && pulseaudio --start - --log-target=[file:~/pulseaudio.txt]file:~/pulseaudio.txt E: [pulseaudio] main.c: Failed to kill daemon: No such process laura@livingroom:~$ pulseaudio --kill && pulseaudio --start - --log-target=[file:~/pulseaudio.txt]file:~/pulseaudio.txt E: [pulseaudio] main.c: Failed to kill daemon: No such process laura@livingroom:~$ pulseaudio --kill && pulseaudio --start - --log-target=[file:~/pulseaudio.txt]file:~/pulseaudio.txt E: [pulseaudio] main.c: Failed to kill daemon: No such process -- 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/1939205 Title: sound dummy output 21.04 Status in linux package in Ubuntu: Confirmed Bug description: no more sound device /output since dist upgrade from 20.10 to 21.04 tried both official ubuntu kernel 5.11.0.26 and newer 5.13.8-051308-generic alsa log: http://alsa-project.org/db/?f=07dfaad1d5d30948449dc36f0caaf39c99145cce lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 apt-cache policy pkgname N: Unable to locate package pkgname ubuntu-bug linux: package not installed cat /proc/version_signature > version.log cat: /proc/version_signature: No such file or directory sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error be descriptive in helping as im a newbie to linux troubleshoot :) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2013-05-11 (3025 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) Package: linux (not installed) RebootRequiredPkgs: linux-image-5.11.0-31-generic linux-base Tags: hirsute Uname: Linux 5.13.9-051309-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to hirsute on 2021-07-19 (34 days ago) UserGroups: adm audio cdrom dip lpadmin netdev plugdev pulse pulse-access sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939205/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942944] [NEW] My touchpad(laptop) is not working....its not being deteted.....I: Bus=0019 Vendor=0000 Product=0001 Version=0000 N: Name="Power Button" P: Phys=PNP0C0C/button/in
Public bug reported: I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=2 20 0 0 1500f0210 3803078f900d401 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/LNXVIDEO:00/input/input5 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0011 Vendor=0002 Product=000e Version= N: Name="ETPS/2 Elantech Touchpad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input6 U: Uniq= H: Handlers=mouse0 event5 B: PROP=5 B: EV=b B: KEY=e420 1 0 0 0 0 B: ABS=66180001103 I: Bus=0003 Vendor=276d Product=1160 Version=0110 N: Name="YSTEK G Mouse" P: Phys=usb-:04:00.3-3/input0 S: Sysfs=/devices/pci:00/:00:08.1/:04:00.3/usb1/1-3/1-3:1.0/0003:276D:1160.0001/input/input7 U: Uniq= H: Handlers=mouse1 event6 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP Wireless hotkeys" P: Phys=hpq6001/input0 S: Sysfs=/devices/virtual/input/input8 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="ST LIS3LV02DL Accelerometer" P: Phys=lis3lv02d/input0 S: Sysfs=/devices/platform/lis3lv02d/input/input9 U: Uniq= H: Handlers=event8 js0 B: PROP=0 B: EV=9 B: ABS=7 I: Bus=0019 Vendor= Product= Version= N: Name="HP WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=33 B: KEY=40 0 10007 2102400 0 0 B: MSC=10 B: SW=20 I: Bus= Vendor= Product= Version= N: Name="HDA NVidia HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:01.1/:01:00.1/sound/card0/input11 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA NVidia HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:01.1/:01:00.1/sound/card0/input12 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA NVidia HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:01.1/:01:00.1/sound/card0/input13 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA NVidia HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:01.1/:01:00.1/sound/card0/input14 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.6/sound/card1/input15 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.6/sound/card1/input16 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0003 Vendor=13d3 Product=56c9 Version=1803 N: Name="HP TrueVision HD Camera: HP Tru" P: Phys=usb-:04:00.4-1/button S: Sysfs=/devices/pci:00/:00:08.1/:04:00.4/usb3/3-1/3-1:1.0/input/input17 U: Uniq= H: Handlers=kbd event16 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 thats all i can detect ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 05:44:04 2021 InstallationDate: Installed on 2021-09-07 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided
[Kernel-packages] [Bug 1928888] Re: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/192 Title: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19 Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz test_zz_cleanup_source_tree (__main__.ApparmorTestsuites) Cleanup downloaded source ... ok == FAIL: test_utils_testsuite (__main__.ApparmorTestsuites) Run utils (make check) -- Traceback (most recent call last): File "/tmp/autopkgtest.gBRfIs/build.V37/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py", line 1841, in test_utils_testsuite self.assertEqual(expected, rc, result + report) AssertionError: 0 != 2 : Got exit code 2, expected 0 ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db make: *** [Makefile:81: check_severity_db] Error 1 == FAIL: test_utils_testsuite3 (__main__.ApparmorTestsuites) Run utils (make check with python3) -- Traceback (most recent call last): File "/tmp/autopkgtest.gBRfIs/build.V37/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py", line 1862, in test_utils_testsuite3 self.assertEqual(expected, rc, result + report) AssertionError: 0 != 2 : Got exit code 2, expected 0 ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db make: *** [Makefile:81: check_severity_db] Error 1 -- Ran 58 tests in 1448.768s FAILED (failures=2) 23:36:54 INFO | END ERROR ubuntu_qrt_apparmor.test-apparmor.py ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1621035414localtime=May 14 23:36:54 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.4.0.85.89)
All autopkgtests for the newly accepted linux-meta (5.4.0.85.89) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (ppc64el, arm64, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
Hi Shengyao, According to Lenovo, the issue can be reproduced on a failed system in Windows environment. Would you please try? If you can see the same result, let's do debug in Windows environment. Please provide your system information for me to understand if it is vPro or non-vPro system. -- SoC Model: BIOS version: Windows version: Windows LAN driver version: ME FW version: -- If you can reproduce the issue in Windows, please follow steps below to collect logs. 1.) Boot to system to S0 2.) Unzip the folder 3.) Open Windows PowerShell as administrator in the folder of debug tool 4.) Run start_trace.bat e1d 0x 5.) Start to reproduce the issue 6. Run stop_trace.bat e1d 0x Rex ** Attachment added: "Intel-LAN-Trace-Tool.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927925/+attachment/5523584/+files/Intel-LAN-Trace-Tool.zip -- 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/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions:
[Kernel-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915
** Changed in: linux-firmware (Ubuntu) Milestone: None => focal-updates ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1939986 Title: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915 Status in initramfs-tools package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Dear all, I can see that the linux-firmware is missing firmware files, in Ubuntu 20.04.1 LTS, for initramfs, when it loads i915. Package: linux-firmware 1.187.15 It contains the following files, for the module i915: i915/tgl_dmc_ver2_04.bin 2019-09-13 installed i915/tgl_dmc_ver2_06.bin 2020-03-04 installed i915/tgl_dmc_ver2_08.bin 2020-08-13 installed i915/tgl_guc_35.2.0.bin 2019-11-06 installed i915/tgl_huc_7.0.12.bin 2020-03-04 installed i915/tgl_huc_7.0.3.bin2019-11-06 installed Package: linux-firmware MUST at least contain the following files, for the module i915: i915/tgl_huc_7.5.0.bin2020-08-13 i915: Add HuC firwmare v7.5.0 for TGL as the module asks for it, during 'update-initramfs', to avoid: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 But it COULD also contain : i915/tgl_dmc_ver2_12.bin 2021-07-28 i915: Add v2.12 DMC for TGL i915/tgl_guc_49.0.1.bin 2020-11-24 i915: Add GuC firmware v49.0.1 for all platforms i915/tgl_guc_62.0.0.bin 2021-06-29 firmware/i915/guc: Add GuC v62.0.0 for all platforms i915/tgl_huc_7.9.3.bin2021-06-29 firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1 Source: $ modprobe --show-depends --ignore-install i915 ... insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko $ modinfo -F firmware /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko ... i915/tgl_dmc_ver2_08.bin i915/tgl_guc_35.2.0.bin i915/tgl_huc_7.5.0.bin Actual result: $ sudo update-initramfs -u W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 Expected result: No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915 Info : INTEL Repository of firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.15 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1699 F pulseaudio /dev/snd/pcmC0D0p: chris 1699 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Aug 15 14:46:47 2021 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 InstallationDate: Installed on 2021-08-12 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.10.0-1038-oem N/A linux-backports-modules-5.10.0-1038-oem N/A linux-firmware 1.187.15 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2021 dmi.bios.release: 3.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.0.4 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.0.4:bd07/16/2021:br3.0:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1939986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928921] Re: LRMv5: switch primary version handling to kernel-versions data set
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! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1928921 Title: LRMv5: switch primary version handling to kernel-versions data set Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Released Bug description: Switch fetching dkms-versions data for these packages to the kernel- versions dataset. Currently the primary dkms-versions data is committed directly to the primary kernel packages. This allows this information to cascade reliably to all derivatives and their associated LRM packages. But once the primaries are closed it is increasingly hard to change this data. This makes performing an LRM-only respin very difficult as it differs in handling from a primary spin. We move the primary version dataset out of the kernel packages into a shared external "kernel-versions" dataset. Each package which needs this data then obtains the information it needs directly, with it committed locally to that package at update time. This renders preparation of am initial (-1) spin and a later LRM-only respin identicle. We simply update the shared dataset and perform a no-change rebuild (./update-versions) on them and they will automatically get the updated version information. We will want to update update-dkms-versions in all primary main packages, and introduce same into all LRM packages. As we already run update-dkms-versions in the primary main packages, and are introducing update-dkms-versions handling to update-versions in LRM this should not change kernel crank proceedure. The cycle proceedure will need a new step to update the shared kernel-versions dataset before cranking commences. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
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!
** Tags added: verification-needed-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/1932966
Title:
kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Confirmed
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
Our Bionic 4.15 kernel lacks of movups/movupd emulation support.
With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57 2021 -0700
x86: add movups/movupd sse testcases to emulator.c
Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
Signed-off-by: Jacob Xu
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini
It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
R8 =000a R9 =03f8 R10=000d
R11=
R12=e000 R13= R14=d000
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00c09300 DPL=0 DS [-WA]
CS =0008 00a09b00 DPL=0 CS64 [-RA]
SS =0010 00c09300 DPL=0 DS [-WA]
DS =0010 00c09300 DPL=0 DS [-WA]
FS =0010 00c09300 DPL=0 DS [-WA]
GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
LDT= 8200 DPL=0 LDT
TR =0080 0041207a 8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)
[Fix]
* 29916968c48691 kvm: Add emulation for movups/movupd
This patch can be cherry-picked into Bionic.
It can fix our test failure plus, as mentioned in the commit message,
emulation failures with openbsd as guest and with Windows 10 with
intel HD graphics pass through.
[Test]
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/
Run the emulator test from ubuntu_kvm_unit_tests, with this patch
applied it will pass without any issue:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
PASS: movups (read)
PASS: movups (write)
PASS: movupd (read)
PASS: movupd (write)
PASS: movups unaligned
PASS: movupd unaligned
PASS: unaligned movaps exception
PASS: movups unaligned crosspage
PASS: movups crosspage exception
PASS: movq (mmx, read)
PASS: movq (mmx, write)
PASS: movb $imm, 0(%rip)
PASS: shld (cl)
PASS: shrd (cl)
PASS: mov null, %ss
PASS: mov null, %ss (with ss.rpl != cpl)
PASS: Test ret/iret with a nullified segment
PASS: ltr
PASS: cmovnel
SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
PASS: push16
PASS: cross-page mmio read
PASS: cross-page mmio write
PASS: string_io_mmio
PASS: jump to non-canonical address
[Kernel-packages] [Bug 1940488] Re: dell300x: rsi wifi and bluetooth crash after suspend and resume
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! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-dell300x in Ubuntu. https://bugs.launchpad.net/bugs/1940488 Title: dell300x: rsi wifi and bluetooth crash after suspend and resume Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-dell300x package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-dell300x source package in Bionic: Fix Released Bug description: I tested the upstream stable kernel 4.19.191, also could reproduce this issue, and reported this testing result to stable mail list. [Impact] On the Dell300x machine, after system suspend and resume, the wifi and bluetooth can't work anymore. [Fix] Revert a patch which was applied to bionic kernel from stable update. [Test] Booting up with the patched kernel, run $sudo rtcwake -m freeze -s 10, then check dmesg to make sure there is crashing log, and run 'nmcli d wifi' and 'bluetoothctl, power on, scan on', all worked well. [Where problems could occur] After applying this SRU, the rsi wifi and bluetooth could have come change, like wifi and bluetooth can't work well after resume, but this possibility is very low, I already run '$sudo rtcwake -m freeze -s 10' for 50 times, the wifi and bluetooth still worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939915] Re: memory leaking when removing a profile
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!
** Tags added: verification-needed-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/1939915
Title:
memory leaking when removing a profile
Status in AppArmor:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
There's a memory leak in the kernel when removing a profile.
A simple reproducible example:
root@ubuntu:~# echo "profile foo {}" > profile
root@ubuntu:~# apparmor_parser profile
root@ubuntu:~# apparmor_parser -R profile
root@ubuntu:~# echo scan > /sys/kernel/debug/kmemleak
root@ubuntu:~# cat /sys/kernel/debug/kmemleak
unreferenced object 0x99bcf5128bb0 (size 16):
comm "apparmor_parser", pid 1318, jiffies 4295139856 (age 33.196s)
hex dump (first 16 bytes):
01 00 00 00 00 00 00 00 98 1f 01 fd bc 99 ff ff
backtrace:
[] kmem_cache_alloc_trace+0xd8/0x1e0
[<86ca7bd9>] aa_alloc_proxy+0x30/0x60
[<0e34f34c>] aa_alloc_profile+0xd4/0x100
[] unpack_profile+0x16f/0xe10
[<19033e2b>] aa_unpack+0x119/0x500
[] aa_replace_profiles+0x94/0xca0
[<1833f520>] policy_update+0x124/0x1e0
[<992f950e>] profile_load+0x7d/0xa0
[] __vfs_write+0x1b/0x40
[<4e709f5d>] vfs_write+0xb9/0x1a0
[<280db840>] SyS_write+0x5e/0xe0
[<14c5ab5d>] do_syscall_64+0x79/0x130
[] entry_SYSCALL_64_after_hwframe+0x41/0xa6
[<9d368497>] 0x
This issue was already fixed upstream 3622ad25d4d6 v5.8-rc1~102^2
It still needs to be applied on xenial, bionic and focal.
This issue could lead to a OOM and eventually DoS. We could see this
issue happening during a test in which snaps were disconnected and
reconnected, causing the leak every time the profile was removed.
Since it is a refcount issue, there could be a lot of memory involved
because the whole profile would be leaked.
Note that only privileged users can remove a profile.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1939915/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941829] Re: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
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! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941829 Title: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers
Retested with the latest kernels as of Sept 7, 2021. Now able to see that ubuntu-drivers now lists the 470-server driver as an available option. For both Focal and Hirsute, I first had to enable -proposed. For Bionic, it worked with the 4.15.0-156.163 kernel that was released this week. Tested combinations: Release Kernel Bionic 4.15.0-156.163 Focal 5.4.0-85.95 (from focal-proposed) Hirsute 5.11.0-35.37 (from hirsute-proposed) Tested each driver with a cuda workload and use of nvidia-smi to verify the driver functions as expected after install. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1939673 Title: Update the 470 and the 470-server NVIDIA drivers Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Bug description: Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.57.02 (470-server) == * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. == 470.63.01 (470) == * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942830] Re: Fix sluggish r8169 by disaling ASPM L1.2
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! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942830 Title: Fix sluggish r8169 by disaling ASPM L1.2 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: [Impact] Realtek r8169 has abysmal network speed. [Fix] Disable ASPM L1.2 because the device takes a long time to exit from L1.2. [Test] Use `iperf` to test network speed. When ASPM L1.2 gets disabled, TX and RX and reach ~700Mbps and ~900Mbps respectively. [Where problems could occur] Disabling ASPM L1.2 can slightly increase power consumption. The CPU package C-State seems to be unaffected so the increase is rather minor. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942830/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.11.0.35.37)
All autopkgtests for the newly accepted linux-meta (5.11.0.35.37) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: systemd/247.3-3ubuntu3.4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
I can confirm the same with proposed. On 9/7/21 3:40 PM, Will G wrote: > For the avoidance of doubt I've just booted up `5.11.0-35-generic` from > -proposed (after previously running Hui's build) and audio is working > fine on my 9710. > > ** Tags removed: hirsute verification-needed-hirsute > ** Tags added: verification-done-hirsute > -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909814] Re: Medion Notebook Keyboard not working
This bug was fixed in the package linux - 5.4.0-84.94 --- linux (5.4.0-84.94) focal; urgency=medium * focal/linux: 5.4.0-84.94 -proposed tracker (LP: #1941767) * Server boot failure after adding checks for ACPI IRQ override (LP: #1941657) - Revert "ACPI: resources: Add checks for ACPI IRQ override" linux (5.4.0-83.93) focal; urgency=medium * focal/linux: 5.4.0-83.93 -proposed tracker (LP: #1940159) * fails to launch linux L2 guests on AMD (LP: #1940134) // CVE-2021-3653 - KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl (CVE-2021-3653) * fails to launch linux L2 guests on AMD (LP: #1940134) - SAUCE: Revert "UBUNTU: SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl" linux (5.4.0-82.92) focal; urgency=medium * focal/linux: 5.4.0-82.92 -proposed tracker (LP: #1939799) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.08.16) * CVE-2021-3656 - SAUCE: KVM: nSVM: always intercept VMLOAD/VMSAVE when nested * CVE-2021-3653 - SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl * [regression] USB device is not detected during boot (LP: #1939638) - SAUCE: Revert "usb: core: reduce power-on-good delay time of root hub" * dev_forward_skb: do not scrub skb mark within the same name space (LP: #1935040) - dev_forward_skb: do not scrub skb mark within the same name space * XPS 9510 (TGL) Screen Brightness could not be changed (LP: #1933566) - SAUCE: drm/i915: Force DPCD backlight mode for Dell XPS 9510(TGL) * Acer Aspire 5 sound driver issues (LP: #1930188) - ALSA: hda/realtek: headphone and mic don't work on an Acer laptop * Sony Dualshock 4 usb dongle crashes the whole system (LP: #1935846) - HID: sony: Workaround for DS4 dongle hotplug kernel crash. * [21.10 FEAT] KVM: Provide a secure guest indication (LP: #1933173) - s390/uv: add prot virt guest/host indication files - s390/uv: fix prot virt host indication compilation * Skip rtcpie test in kselftests/timers if the default RTC device does not exist (LP: #1937991) - selftests: timers: rtcpie: skip test if default RTC device does not exist * Focal update: v5.4.133 upstream stable release (LP: #1938713) - drm/mxsfb: Don't select DRM_KMS_FB_HELPER - drm/zte: Don't select DRM_KMS_FB_HELPER - drm/amd/amdgpu/sriov disable all ip hw status by default - drm/vc4: fix argument ordering in vc4_crtc_get_margins() - net: pch_gbe: Use proper accessors to BE data in pch_ptp_match() - drm/amd/display: fix use_max_lb flag for 420 pixel formats - hugetlb: clear huge pte during flush function on mips platform - atm: iphase: fix possible use-after-free in ia_module_exit() - mISDN: fix possible use-after-free in HFC_cleanup() - atm: nicstar: Fix possible use-after-free in nicstar_cleanup() - net: Treat __napi_schedule_irqoff() as __napi_schedule() on PREEMPT_RT - drm/mediatek: Fix PM reference leak in mtk_crtc_ddp_hw_init() - reiserfs: add check for invalid 1st journal block - drm/virtio: Fix double free on probe failure - drm/sched: Avoid data corruptions - udf: Fix NULL pointer dereference in udf_symlink function - e100: handle eeprom as little endian - igb: handle vlan types with checker enabled - drm/bridge: cdns: Fix PM reference leak in cdns_dsi_transfer() - clk: renesas: r8a77995: Add ZA2 clock - clk: tegra: Ensure that PLLU configuration is applied properly - ipv6: use prandom_u32() for ID generation - RDMA/cxgb4: Fix missing error code in create_qp() - dm space maps: don't reset space map allocation cursor when committing - pinctrl: mcp23s08: fix race condition in irq handler - ice: set the value of global config lock timeout longer - virtio_net: Remove BUG() to avoid machine dead - net: bcmgenet: check return value after calling platform_get_resource() - net: mvpp2: check return value after calling platform_get_resource() - net: micrel: check return value after calling platform_get_resource() - drm/amd/display: Update scaling settings on modeset - drm/amd/display: Release MST resources on switch from MST to SST - drm/amd/display: Set DISPCLK_MAX_ERRDET_CYCLES to 7 - drm/amdkfd: use allowed domain for vmbo validation - fjes: check return value after calling platform_get_resource() - selinux: use __GFP_NOWARN with GFP_NOWAIT in the AVC - r8169: avoid link-up interrupt issue on RTL8106e if user enables ASPM - drm/amd/display: Verify Gamma & Degamma LUT sizes in amdgpu_dm_atomic_check - xfrm: Fix error reporting in xfrm_state_construct. - wlcore/wl12xx: Fix wl12xx get_mac error if device is in ELP - wl1251: Fix possible buffer overflow in wl1251_cmd_scan - cw1200: add missing MODULE_DEVICE_TABLE - bpf: Fix up register-based shifts in interpreter to silence KUBSAN -
[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync
** Attachment added: "screenlog.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1942935/+attachment/5523575/+files/screenlog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071] submit_bio_noacct+0x112/0x4f0 [921588.559075] submit_bio+0x51/0x1a0 [921588.559077] ? _cond_resched+0x19/0x30 [921588.559081] ? kmem_cache_alloc+0x38e/0x440 [921588.559084] ? ext4_init_io_end+0x1f/0x50 [921588.559088] ext4_io_submit+0x4d/0x60 [921588.559091] ext4_writepages+0x2c6/0xcd0 [921588.559094] ? __schedule+0x454/0x8a0 [921588.559097] ?
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
For the avoidance of doubt I've just booted up `5.11.0-35-generic` from -proposed (after previously running Hui's build) and audio is working fine on my 9710. ** Tags removed: hirsute verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
@hashratez right/official command (without adding any 3rd repository) is: sudo apt install --install-recommends linux-generic-hwe-20.04 on officialy supported HW is done automatically, on other you must manualy run for upgrade to latest HWE line, more info: https://wiki.ubuntu.com/Kernel/LTSEnablementStack @blueorange589 yes, about it is whole this bug report, newer that 5.11.15 "Ubuntu Mainline Kernel Builds" need libc >=2.33 for installing all packages... if you not need adding 3rd modules/drivers (nvidia, virtualbox, some unsupported wifi/lan card,...) then simple not install problematic one package: "linux-headers-._amd64.deb" and error is gone... -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942935] [NEW] kernel io hangs during mdcheck/resync
Public bug reported: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071] submit_bio_noacct+0x112/0x4f0 [921588.559075] submit_bio+0x51/0x1a0 [921588.559077] ? _cond_resched+0x19/0x30 [921588.559081] ? kmem_cache_alloc+0x38e/0x440 [921588.559084] ? ext4_init_io_end+0x1f/0x50 [921588.559088] ext4_io_submit+0x4d/0x60 [921588.559091] ext4_writepages+0x2c6/0xcd0 [921588.559094] ? __schedule+0x454/0x8a0 [921588.559097] ? hrtimer_start_range_ns+0x1aa/0x2f0 [921588.559100] ? timerqueue_del+0x24/0x50 [921588.559105] ? futex_wait+0x1ed/0x270 [921588.559109] do_writepages+0x43/0xd0 [921588.559112] ? do_writepages+0x43/0xd0 [921588.559115] ? futex_wake+0x7c/0x180 [921588.559118] __filemap_fdatawrite_range+0xcc/0x110 [921588.559123] file_write_and_wait_range+0x74/0xc0 [921588.559126] ext4_sync_file+0xf5/0x350 [921588.559129] vfs_fsync_range+0x49/0x80 [921588.559132] ? __fget_light+0x62/0x80 [921588.559136] do_fsync+0x3d/0x70 [921588.559139] __x64_sys_fsync+0x14/0x20 [921588.559142] do_syscall_64+0x38/0x90
[Kernel-packages] [Bug 1942932] [NEW] oob_net0 up but stops processing Rx packets
Public bug reported: SRU Justification: [Impact] * The oob_net0 interface, managed by the mlxbf_gige driver, will be up and enabled but can stop processing received packets if three specific conditions occur: 1) driver has received more than (N * RxRingSize) packets but less than (N+1 * RxRingSize) packets where N is an odd number. Note: the command "ethtool -g oob_net0" will display the current receive ring size, which currently defaults to 128. 2) the driver's interface was disabled via "ifconfig oob_net0 down" during the window described in #1. 3) the driver's interface is re-enabled via "ifconfig oob_net0 up" Without this fix, the driver needs to be unloaded and re-loaded to correct this condition. [Fix] * The fix is to ensure that the driver's "valid_polarity" field is cleared during the open() method so that it always matches the receive polarity used by hardware. [Test Case] * To test this fix, need to send in a specific number of packets to the "oob_net0" interface, then issue "ifconfig oob_net0 down" to disable the interface. A subsequent "ifconfig oob_net0 up" command will succesfully bring up the "oob_net0" interface and start the processing of received packets. [Regression Potential] * There is low risk of this fix causing any problems. [Other] * The mlxbf_gige driver will display v1.25 in modinfo after these changes. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1942932 Title: oob_net0 up but stops processing Rx packets Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] * The oob_net0 interface, managed by the mlxbf_gige driver, will be up and enabled but can stop processing received packets if three specific conditions occur: 1) driver has received more than (N * RxRingSize) packets but less than (N+1 * RxRingSize) packets where N is an odd number. Note: the command "ethtool -g oob_net0" will display the current receive ring size, which currently defaults to 128. 2) the driver's interface was disabled via "ifconfig oob_net0 down" during the window described in #1. 3) the driver's interface is re-enabled via "ifconfig oob_net0 up" Without this fix, the driver needs to be unloaded and re-loaded to correct this condition. [Fix] * The fix is to ensure that the driver's "valid_polarity" field is cleared during the open() method so that it always matches the receive polarity used by hardware. [Test Case] * To test this fix, need to send in a specific number of packets to the "oob_net0" interface, then issue "ifconfig oob_net0 down" to disable the interface. A subsequent "ifconfig oob_net0 up" command will succesfully bring up the "oob_net0" interface and start the processing of received packets. [Regression Potential] * There is low risk of this fix causing any problems. [Other] * The mlxbf_gige driver will display v1.25 in modinfo after these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
@hui your kernel works for me on my Dell XPS9710. Sound in and out. Thanks!! In other words, in response to the kernel bot: This patch solves the problem. If I knew how, I would change this to 'verification-done-hirsute' Thanks again! -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel
Hey Jo, Thanks for the debdiff! ... So, it looks like the 2 commits for dmesg/printk are actually LP#1921403 that you handled previously? For better tracking/documentation purposes, the right thing to do would be to keep these 2 patches associated with that bug (well, it requires an SRU template now, but you already have it on here.) Thus I added a Focal task there, and it can be properly referenced in the changelog. ... And the first commit, for uts_namespace.name should go into Hirsute too, right? I see it's not in the source package. Since we're adding it back to Focal, it should get into the later releases too. Adding a Hirsute task here. Could you please provide a debdiff for Hirsute as well? ... BTW, the debdiff has a `makedumpdife` typo on changelog (that was funny. :) And despite the patches being DEP3 tagged as 'upstream', at least one of them needs changes to apply (uts_namespace.name, hunk 5), so it should be tagged 'backport' (or just leave the first, optional field out.) ... And last but not least, since the patches are architecture independent, would you mind testing on the supported architectures? I know it seems overkill per the changes on these patches, but we're better safe than sorry, particularly on the kernel crash dump path. If some arch isn't available on canonistack, please see some old notes [1] that I used to get them running in QEMU to verify installer changes (s390x emulation was surprisingly fast, and arm64 worked well enough; I guess it should be ok to skip armhf, and of course, no more i386 on F/H.) Uh, on both kernels :/ But that should be the least of the suggested work steps, once the VM is already installed w/ the GA kernel. :) ... Thanks again! Mauricio [1] https://pastebin.ubuntu.com/p/YXBF9dFFp3/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1942784 Title: makedumpfile not properly working on focal with 5.11 kernel Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Hirsute: In Progress Bug description: [IMPACT] When running Focal with the hwe 5.11 kernel makedumpfile is not working as it should. Instead of compressing the dump makedumpfile falls back to cp. This can create problems on systems with very large RAM and result into exhausting all storage on the host. This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of 'uts_namespace.name' offset in VMCOREINFO). In addition the dmesg. is not created. This can be resolved with the following two commits : - commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer) - commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values) [TEST CASE] For testing a machine running focal with the 5.11 kernel is required. Then trigger a crash. On the console we can see that makedumpfile fails and `falls back to cp`. In /var/crash we can see that no dmesg file is created and instead of the dump file the uncompressed vmcoreinfo is created. [WHERE PROBLEMS COULD OCCUR] The 3 commits pulled into focal make makedumpfile compatible with the 5.11 kernel. Any regression potential would involve the crash dump not being created after a crash in case kdump is configured. [OTHER] Only Focal with 5.11 kernel is affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936295] Re: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate
It seems the maintainer has concerns on the patch, and there is no reply from the developer at the moment: https://patchwork.kernel.org/project/linux- input/patch/20210729010940.5752-1-phoe...@emc.com.tw/ -- 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/1936295 Title: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate the FW bug Status in linux package in Ubuntu: Confirmed Bug description: *Problem description:* On Lenovo Thinkpad T14s, X13, A475 (and probably more models) the Elantech Trackpoint firmware is defective. The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. Currently, the Trackpoint is barely usable and it's impossible to productively work using it. For a long while, Elantech has not yet put forward (nor confirmed) a firmware update. However, there is a Linux kernel patch mitigating the firmware bug. The kernel bugfix discards the wrongly reported packages by the Elantech hardware. This solves the problem for the user. *Solution:* Please apply existing kernel patch here. https://bugzilla.kernel.org/show_bug.cgi?id=209167 Bug entry in the Linux Kernel.org Bugzilla https://bugzilla.kernel.org/attachment.cgi?id=295733=diff Diff of bugfix *T14s and X13 are Ubuntu certified:* The Lenovo Thinkpad T14s and X13 are Ubuntu certified, but apparently this hardware issue has slipped the Ubuntu certification process! https://ubuntu.com/certified/202006-27978 and https://ubuntu.com/certified/202006-27979 *Further information:* https://forums.lenovo.com/t5/Fedora/T14s-AMD-Trackpoint-almost-unusable/m-p/5064952?page=1 Discussion on the bug in the Lenovo forum. E.g. see comment 18 by Lenovo employee MarkRHPearson *My System:* Lenovo Thinkpad T14s (AMD) 20ujs00k00 Ubuntu 21.04 and 20.04 see entries in kernel.org bugzilla for logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921403] Re: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels
** Changed in: makedumpfile (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: makedumpfile (Ubuntu Hirsute) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1921403 Title: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Hirsute: Fix Released Status in makedumpfile package in Debian: Fix Released Bug description: makedumpfile does not create the dmesg. in /var/crash. This happens only on 5.10+ kernel because 5.10 kernel introduces a new lockless ringbuffer. This issue has been addressed upstream with commits : [1] c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer) [2] 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values) [1] https://github.com/makedumpfile/makedumpfile/commit/c617ec63339222f3a44d73e36677a9acc8954ccd [2] https://github.com/makedumpfile/makedumpfile/commit/44b073b7ec467aee0d7de381d455b8ace1199184 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1921403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel
** Also affects: makedumpfile (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: makedumpfile (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: makedumpfile (Ubuntu Hirsute) Status: New => In Progress ** Changed in: makedumpfile (Ubuntu Hirsute) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Changed in: makedumpfile (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: makedumpfile (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1942784 Title: makedumpfile not properly working on focal with 5.11 kernel Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Hirsute: In Progress Bug description: [IMPACT] When running Focal with the hwe 5.11 kernel makedumpfile is not working as it should. Instead of compressing the dump makedumpfile falls back to cp. This can create problems on systems with very large RAM and result into exhausting all storage on the host. This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of 'uts_namespace.name' offset in VMCOREINFO). In addition the dmesg. is not created. This can be resolved with the following two commits : - commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer) - commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values) [TEST CASE] For testing a machine running focal with the 5.11 kernel is required. Then trigger a crash. On the console we can see that makedumpfile fails and `falls back to cp`. In /var/crash we can see that no dmesg file is created and instead of the dump file the uncompressed vmcoreinfo is created. [WHERE PROBLEMS COULD OCCUR] The 3 commits pulled into focal make makedumpfile compatible with the 5.11 kernel. Any regression potential would involve the crash dump not being created after a crash in case kdump is configured. [OTHER] Only Focal with 5.11 kernel is affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942931] [NEW] "ethtool -S oob_net0" does not report interrupt counts
Public bug reported: SRU Justification: [Impact] * The command "ethtool -S oob_net0" displays a set of statistics related to mlxbf_gige driver. This set of statistics does not include the driver's interrupt counts. [Fix] * The fix is to extend the statistics list supported by "ethtool -S" so that it includes MAC, receive packet, and LLU/PLU interrupt counts. [Test Case] * The command "ethtool -S oob_net0" should be executed before and after this fix to verify that three new fields are displayed: mac_intr_count rx_intr_count llu_plu_intr_count [Regression Potential] * There is low risk of this fix causing any problems. [Other] * n/a ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1942931 Title: "ethtool -S oob_net0" does not report interrupt counts Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] * The command "ethtool -S oob_net0" displays a set of statistics related to mlxbf_gige driver. This set of statistics does not include the driver's interrupt counts. [Fix] * The fix is to extend the statistics list supported by "ethtool -S" so that it includes MAC, receive packet, and LLU/PLU interrupt counts. [Test Case] * The command "ethtool -S oob_net0" should be executed before and after this fix to verify that three new fields are displayed: mac_intr_count rx_intr_count llu_plu_intr_count [Regression Potential] * There is low risk of this fix causing any problems. [Other] * n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921403] Re: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels
** Also affects: makedumpfile (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: makedumpfile (Ubuntu Focal) Status: New => In Progress ** Changed in: makedumpfile (Ubuntu Focal) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Tags added: sts-sponsor-mfo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1921403 Title: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Hirsute: Fix Released Status in makedumpfile package in Debian: Fix Released Bug description: makedumpfile does not create the dmesg. in /var/crash. This happens only on 5.10+ kernel because 5.10 kernel introduces a new lockless ringbuffer. This issue has been addressed upstream with commits : [1] c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer) [2] 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values) [1] https://github.com/makedumpfile/makedumpfile/commit/c617ec63339222f3a44d73e36677a9acc8954ccd [2] https://github.com/makedumpfile/makedumpfile/commit/44b073b7ec467aee0d7de381d455b8ace1199184 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1921403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.10 --- alsa-ucm-conf (1.2.2-1ubuntu0.10) focal; urgency=medium * d/p/0031-sof-soundwire-rt1316-DAC-L-and-R-is-replaced-by-DAC.patch The mixer name is changed in the codec driver rt1316-sdw.c, so need to handle the new mixer name. https://github.com/alsa-project/alsa-ucm-conf/pull/109 (LP: #1937980) * d/p/0032-sof-hda-dsp-Set-Capture-Switch-on-in-the-BootSequenc.patch The input volume of the external microphone is 0 by default for all machines with sof audio driver, that is because the capture switch is set to off by default, need to set it to on in the ucm. https://github.com/alsa-project/alsa-ucm-conf/pull/107 (LP: #1940788) -- Hui Wang Mon, 23 Aug 2021 11:00:48 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1937980 Title: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: [Impact] After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316. [Fix] Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. [Test] sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well. [Where problems will occur] The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940788] Re: [SRU] the input volume of external mic for sof driver is 0 by default
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.10 --- alsa-ucm-conf (1.2.2-1ubuntu0.10) focal; urgency=medium * d/p/0031-sof-soundwire-rt1316-DAC-L-and-R-is-replaced-by-DAC.patch The mixer name is changed in the codec driver rt1316-sdw.c, so need to handle the new mixer name. https://github.com/alsa-project/alsa-ucm-conf/pull/109 (LP: #1937980) * d/p/0032-sof-hda-dsp-Set-Capture-Switch-on-in-the-BootSequenc.patch The input volume of the external microphone is 0 by default for all machines with sof audio driver, that is because the capture switch is set to off by default, need to set it to on in the ucm. https://github.com/alsa-project/alsa-ucm-conf/pull/107 (LP: #1940788) -- Hui Wang Mon, 23 Aug 2021 11:00:48 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1940788 Title: [SRU] the input volume of external mic for sof driver is 0 by default Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: The change of this SRU has been squashed to https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980. [Impact] For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully. [Fix] Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume. [Test] sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully. [Where problems will occur] This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu1.3 --- alsa-ucm-conf (1.2.4-2ubuntu1.3) hirsute; urgency=medium * d/p/0005-sof-soundwire-rt1316-DAC-L-and-R-is-replaced-by-DAC.patch The mixer name is changed in the codec driver rt1316-sdw.c, so need to handle the new mixer name. https://github.com/alsa-project/alsa-ucm-conf/pull/109 (LP: #1937980) * d/p/0006-sof-hda-dsp-Set-Capture-Switch-on-in-the-BootSequenc.patch The input volume of the external microphone is 0 by default for all machines with sof audio driver, that is because the capture switch is set to off by default, need to set it to on in the ucm. https://github.com/alsa-project/alsa-ucm-conf/pull/107 (LP: #1940788) -- Hui Wang Mon, 23 Aug 2021 10:05:50 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1937980 Title: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: [Impact] After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316. [Fix] Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. [Test] sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well. [Where problems will occur] The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940788] Update Released
The verification of the Stable Release Update for alsa-ucm-conf has completed successfully and the package is now being 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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1940788 Title: [SRU] the input volume of external mic for sof driver is 0 by default Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: The change of this SRU has been squashed to https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980. [Impact] For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully. [Fix] Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume. [Test] sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully. [Where problems will occur] This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940788] Re: [SRU] the input volume of external mic for sof driver is 0 by default
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu1.3 --- alsa-ucm-conf (1.2.4-2ubuntu1.3) hirsute; urgency=medium * d/p/0005-sof-soundwire-rt1316-DAC-L-and-R-is-replaced-by-DAC.patch The mixer name is changed in the codec driver rt1316-sdw.c, so need to handle the new mixer name. https://github.com/alsa-project/alsa-ucm-conf/pull/109 (LP: #1937980) * d/p/0006-sof-hda-dsp-Set-Capture-Switch-on-in-the-BootSequenc.patch The input volume of the external microphone is 0 by default for all machines with sof audio driver, that is because the capture switch is set to off by default, need to set it to on in the ucm. https://github.com/alsa-project/alsa-ucm-conf/pull/107 (LP: #1940788) -- Hui Wang Mon, 23 Aug 2021 10:05:50 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1940788 Title: [SRU] the input volume of external mic for sof driver is 0 by default Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: The change of this SRU has been squashed to https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980. [Impact] For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully. [Fix] Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume. [Test] sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully. [Where problems will occur] This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937980] Update Released
The verification of the Stable Release Update for alsa-ucm-conf has completed successfully and the package is now being 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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1937980 Title: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: [Impact] After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316. [Fix] Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. [Test] sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well. [Where problems will occur] The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940204] Re: AMDGPU: Fix System hang after resume from suspend
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. 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! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1940204 Title: AMDGPU: Fix System hang after resume from suspend Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] With AMD-GPU and don't use it as a display output, After multiple Suspend, system would hang. [Fix] Disable BACO for polaris12 series. BACO allow the graphics cards on Linux to support S4 / hibernation support. [Test Case] 1. Must plug AMD GPU and don't use it as display output 2. Plug DP/HDMI on iGPU. 3. Suspend machine. 4. check if system hangs. [Where problems could occur] Disable BACO would cause higher power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. 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! ** Tags added: verification-needed-hirsute -- 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/1937897 Title: GPIO error logs in start and dmesg after update of kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] After upgrade kernel to 5.11.0-25 which introduce some ODM patches from AAEON, user encounters below errors [ 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 [Fix] AAEON provides a patch to check the BFPI version before loading the driver. Which fixes the issue introduced by Hirsute: 45a8bb8699cc UBUNTU: ODM: mfd: Add support for IO functions of AAEON devices Impish: 424945128781 UBUNTU: ODM: mfd: Add support for IO functions of AAEON devices [Test] Verified by AAEON. [Where problems could occur] It adds a check while probing the driver, should have no impact to normal user. = After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error to gpio: 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 On pc: description: Desktop Computer product: System Product Name (SKU) vendor: ASUS version: System Version serial: System Serial Number width: 64 bits capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32 configuration: boot=normal chassis=desktop family=To be filled by O.E.M. sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4 *-core description: Motherboard product: TUF GAMING B550M-PLUS (WI-FI) vendor: ASUSTeK COMPUTER INC. physical id: 0 version: Rev X.0x serial: 201176738701636 slot: Default string *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 2403 date: 06/16/2021 size: 64KiB capacity: 16MiB capabilities: pci apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936771] Re: disable “CONFIG_HISI_DMA” config for ubuntu version
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. 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! ** Tags added: verification-needed-hirsute -- 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/1936771 Title: disable “CONFIG_HISI_DMA” config for ubuntu version Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] Setup soft RAID5 on kunpeng920 machine and system will crash because of hisi_dma timeout. This issue can be reproduced with all Ubuntu kernel with hisi_dma. [Test Plan] Setup soft RAID5 and wait for few seconds. Kernel will crash. [Regression Risk] CONFIG_HISI_DMA only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] disable “CONFIG_HISI_DMA” config for ubuntu version [Steps to Reproduce] 1) 2) 3) [Actual Results] this module cause some error [Expected Results] ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1936771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. 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! ** Tags added: verification-needed-hirsute -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938999] Re: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. 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! ** Tags added: verification-needed-hirsute -- 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/1938999 Title: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock Status in linux package in Ubuntu: Confirmed Status in linux source package in Hirsute: Fix Committed Bug description: I have two external displays chained via Display port connected to the ThinkPad Thunderbolt 3 Dock. They are working with kernel 5.8.0-63 but not with the new 5.11.0-25 kernel. I could reproduce this behavior several times for both kernels, as follows: I booted up with disconnected dock, logged in, then I connected it, disconnected it, and connected it again. With the 5.11.0-25 kernel the external displays go black; the main screen turns off and on several times. Sometimes the main screen remains working, but UI is lagging. I'm attaching the logs. Two separate boots for each variant are marked 'a'/'b'. SRU Justifications: === [Impact] External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock [Fix] Some SKL systems DP output fails when AUX timeout of LTTPR detection. Disable the LTTPR detection until GLK to fix the link training. [Test] Verified on hardware, external DP work fine. Also tested on I+N GPU laptop and a iGPU only laptop, all displays with dock are good. [Where problems could occur] It may break output of external DP. This patch from 5.12-rc5, only Hirsute kernel is SRUed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939473] Re: mute/micmute LEDs no function on HP ProBook 650 G8
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. 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! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939473 Title: mute/micmute LEDs no function on HP ProBook 650 G8 Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Fix Committed Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook 650 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1939473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941669] Re: alsa: the soundwire audio doesn't work on the Dell TGL-H machines
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. 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! ** Tags added: verification-needed-hirsute -- 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/1941669 Title: alsa: the soundwire audio doesn't work on the Dell TGL-H machines Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Fix Committed Bug description: These 2 patches were merged to upstream kernel from v5.12, no need to send them to impish/oem-5.13/unstable kernels. And this patch is already in the oem-5.10 kernel, for focal kernel, since focal kernel doesn't support soundwire audio, these 2 patches are useless for focal kernel. [Impact] The Dell precision 5760 is a TGL-H machine, and it has soundwire audio design, when running the hirsute kernel, the audio driver fails to load sof-firmware, then the whole audio fails to initialize and fails to work. [Fix] Backport 2 patches, these will remove hardcoded firmware name and allow load firmware according to the firmware name defined by pciid [Test] Booting the patched kernel, check dmesg, there is no errors about loading audio sof-firmware, playsound to spk and headphone, all worked well, record sound from internal mic and external mic, all worked well. [Where problems could occur] The patch remove the hardcoded firmware for all TGL soundwire machines, this could make the TGL soundwire machines fail to load the sof-firmware then the whole audio fail to work. But this possibiliy is low, since we tested the patches on different TGL soundwire machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936998] Re: e1000e blocks the boot process when it tried to write checksum to its NVM
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. 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! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1936998 Title: e1000e blocks the boot process when it tried to write checksum to its NVM Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] While probing e1000e, it checks its NVM checksum, and write correct checksum back if the checksum is not correct. But for recent GBE update for security, its NVM could be written once for MAC address during production, so write checksum during driver probing is not allowed and would block the boot process. [Fix] Intel provides a fix for it. https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20210718041031.3619696-1-sasha.nef...@intel.com/ [Test] Verified on a Dell machine which has wrong NVM checksum. [Where problems could occur] From what Intel told us, the checksum isn't correct is not a big deal, we could ignore it and it won't lead to any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936682] Re: Fix kernel panic caused by legacy devices on AMD platforms
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. 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! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1936682 Title: Fix kernel panic caused by legacy devices on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] When a legacy device is only 32bit DMA capable and it's in the same IOMMU group with iommu_v2 capable devices, the device in question will be forced to use identity mapping and triggers kernel panic on DMA operation because it can't do 64bit DMA. [Fix] Keep swiotlb enabled so legacy devices can do 64bit DMA. This is also how Intel and ARM64 platforms deal with legacy devices. [Test] Boot an affected system. Kernel panic in Realtek WiFi driver's probe routine. After the patch is applied, the system can work normally. [Where problems could occur] The default swiotlb uses 64MB memory, so if the system doesn't have any legacy device, there are 64MB ram less for the system to use. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940610] Re: Fix mic noise on HP ProBook 445 G8
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. 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! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1940610 Title: Fix mic noise on HP ProBook 445 G8 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] There's mic noise on HP ProBook 445 G8. [Fix] Limit mic boost to make the audio capture crystal clear. [Test] $ arecord -f dat test $ aplay test With the fix, the mic noise is gone. [Where problems could occur] If someone would like to let others hear the noise in Zoom, this will deprive of their pleasure. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928921] Re: LRMv5: switch primary version handling to kernel-versions data set
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. 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! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1928921 Title: LRMv5: switch primary version handling to kernel-versions data set Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Released Bug description: Switch fetching dkms-versions data for these packages to the kernel- versions dataset. Currently the primary dkms-versions data is committed directly to the primary kernel packages. This allows this information to cascade reliably to all derivatives and their associated LRM packages. But once the primaries are closed it is increasingly hard to change this data. This makes performing an LRM-only respin very difficult as it differs in handling from a primary spin. We move the primary version dataset out of the kernel packages into a shared external "kernel-versions" dataset. Each package which needs this data then obtains the information it needs directly, with it committed locally to that package at update time. This renders preparation of am initial (-1) spin and a later LRM-only respin identicle. We simply update the shared dataset and perform a no-change rebuild (./update-versions) on them and they will automatically get the updated version information. We will want to update update-dkms-versions in all primary main packages, and introduce same into all LRM packages. As we already run update-dkms-versions in the primary main packages, and are introducing update-dkms-versions handling to update-versions in LRM this should not change kernel crank proceedure. The cycle proceedure will need a new step to update the shared kernel-versions dataset before cranking commences. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941829] Re: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
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- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. 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! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941829 Title: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940629] Re: Support Jasper Lake
This bug was fixed in the package thermald - 2.4.3-1ubuntu2 --- thermald (2.4.3-1ubuntu2) hirsute; urgency=medium * Support Jasper Lake. (LP: #1940629) - 0014-Added-Jasper-Lake-CPU-model.patch -- Andy Chi Fri, 20 Aug 2021 15:56:17 +0800 ** Changed in: thermald (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940629 Title: Support Jasper Lake Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Hirsute: Fix Released Status in thermald source package in Impish: Fix Released Bug description: [Impact] * Support thermald on Jasper Lake CPU. * [Test Plan] * Use a machine with a Jasper Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/309 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940629/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940629] Update Released
The verification of the Stable Release Update for thermald has completed successfully and the package is now being 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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940629 Title: Support Jasper Lake Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Hirsute: Fix Released Status in thermald source package in Impish: Fix Released Bug description: [Impact] * Support thermald on Jasper Lake CPU. * [Test Plan] * Use a machine with a Jasper Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/309 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940629/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940629] Re: Support Jasper Lake
This bug was fixed in the package thermald - 1.9.1-1ubuntu0.6 --- thermald (1.9.1-1ubuntu0.6) focal; urgency=medium [Andy Chi] * Support Jasper Lake. (LP: #1940629) - 0144-Added-Jasper-Lake-CPU-model.patch [Colin Ian King] * AlderLake CPU support (LP: #1942181) - 0015-Add-AlderLake-cpu-model.patch - 0016-Update-sysfs-paths-for-Alader-Lake.patch -- Colin King Mon, 31 Aug 2021 09:36:12 +0100 ** Changed in: thermald (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940629 Title: Support Jasper Lake Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Hirsute: Fix Released Status in thermald source package in Impish: Fix Released Bug description: [Impact] * Support thermald on Jasper Lake CPU. * [Test Plan] * Use a machine with a Jasper Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/309 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940629/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942181] Re: Add support for AlderLake CPUs
This bug was fixed in the package thermald - 1.9.1-1ubuntu0.6 --- thermald (1.9.1-1ubuntu0.6) focal; urgency=medium [Andy Chi] * Support Jasper Lake. (LP: #1940629) - 0144-Added-Jasper-Lake-CPU-model.patch [Colin Ian King] * AlderLake CPU support (LP: #1942181) - 0015-Add-AlderLake-cpu-model.patch - 0016-Update-sysfs-paths-for-Alader-Lake.patch -- Colin King Mon, 31 Aug 2021 09:36:12 +0100 ** Changed in: thermald (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1942181 Title: Add support for AlderLake CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Hirsute: New Status in thermald source package in Impish: Fix Released Bug description: [Impact] * Support thermald on AlderLake CPUs. [Test Plan] * Use a machine with a AlderLake CPUs * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware because the changes match on the CPU model ID. [Other Info] Supported added with: * https://github.com/intel/thermal_daemon/commit/ffb226c62d3bc052f47970be9802254e48799bf4 * https://github.com/intel/thermal_daemon/commit/d0c9e7fb5aea85b84841eba927feb8767765fda2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942181] Update Released
The verification of the Stable Release Update for thermald has completed successfully and the package is now being 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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1942181 Title: Add support for AlderLake CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Hirsute: New Status in thermald source package in Impish: Fix Released Bug description: [Impact] * Support thermald on AlderLake CPUs. [Test Plan] * Use a machine with a AlderLake CPUs * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware because the changes match on the CPU model ID. [Other Info] Supported added with: * https://github.com/intel/thermal_daemon/commit/ffb226c62d3bc052f47970be9802254e48799bf4 * https://github.com/intel/thermal_daemon/commit/d0c9e7fb5aea85b84841eba927feb8767765fda2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
Just a quick update to let you know that my local build is still working fine on all 5 test machines. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Committed Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
It's not in the commit log for -34: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/hirsute/log/?h=Ubuntu-5.11.0-34.36 It's in the log for the next kernel cycle -35: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/hirsute/log/?h=Ubuntu-5.11.0-35.37 -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942500] Re: invalid symbol # in scripts/module.lds
ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: bionic Uname: Linux 5.11.5-051105-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker input lpadmin plugdev sambashare sudo video _MarkForUpload: True ** Tags added: apport-collected -- 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/1942500 Title: invalid symbol # in scripts/module.lds Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04.5 LTS Release: 18.04 Kernel: 5.11.5-051105-generic Bug : Building External Wifi Drivers Fail , tried multiple drivers , Error generated , below. Resolution tried : copying module.lds.S to the running kernel, does not work !! Error : ld:scripts/module.lds:6: ignoring invalid character `#' in expression ld:scripts/module.lds:6: syntax error scripts/Makefile.modfinal:58: recipe for target '/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko' failed make[3]: *** [/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko] Error 1 scripts/Makefile.modpost:117: recipe for target '__modpost' failed make[2]: *** [__modpost] Error 2 Makefile:1710: recipe for target 'modules' failed make[1]: *** [modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.11.5-051105-generic' Makefile:2378: recipe for target 'modules' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942500] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1942500/+attachment/5523563/+files/ProcEnviron.txt -- 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/1942500 Title: invalid symbol # in scripts/module.lds Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04.5 LTS Release: 18.04 Kernel: 5.11.5-051105-generic Bug : Building External Wifi Drivers Fail , tried multiple drivers , Error generated , below. Resolution tried : copying module.lds.S to the running kernel, does not work !! Error : ld:scripts/module.lds:6: ignoring invalid character `#' in expression ld:scripts/module.lds:6: syntax error scripts/Makefile.modfinal:58: recipe for target '/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko' failed make[3]: *** [/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko] Error 1 scripts/Makefile.modpost:117: recipe for target '__modpost' failed make[2]: *** [__modpost] Error 2 Makefile:1710: recipe for target 'modules' failed make[1]: *** [modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.11.5-051105-generic' Makefile:2378: recipe for target 'modules' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942500] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1942500/+attachment/5523562/+files/ProcCpuinfoMinimal.txt -- 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/1942500 Title: invalid symbol # in scripts/module.lds Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04.5 LTS Release: 18.04 Kernel: 5.11.5-051105-generic Bug : Building External Wifi Drivers Fail , tried multiple drivers , Error generated , below. Resolution tried : copying module.lds.S to the running kernel, does not work !! Error : ld:scripts/module.lds:6: ignoring invalid character `#' in expression ld:scripts/module.lds:6: syntax error scripts/Makefile.modfinal:58: recipe for target '/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko' failed make[3]: *** [/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko] Error 1 scripts/Makefile.modpost:117: recipe for target '__modpost' failed make[2]: *** [__modpost] Error 2 Makefile:1710: recipe for target 'modules' failed make[1]: *** [modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.11.5-051105-generic' Makefile:2378: recipe for target 'modules' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942500] Re: invalid symbol # in scripts/module.lds
** 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/1942500 Title: invalid symbol # in scripts/module.lds Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04.5 LTS Release: 18.04 Kernel: 5.11.5-051105-generic Bug : Building External Wifi Drivers Fail , tried multiple drivers , Error generated , below. Resolution tried : copying module.lds.S to the running kernel, does not work !! Error : ld:scripts/module.lds:6: ignoring invalid character `#' in expression ld:scripts/module.lds:6: syntax error scripts/Makefile.modfinal:58: recipe for target '/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko' failed make[3]: *** [/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko] Error 1 scripts/Makefile.modpost:117: recipe for target '__modpost' failed make[2]: *** [__modpost] Error 2 Makefile:1710: recipe for target 'modules' failed make[1]: *** [modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.11.5-051105-generic' Makefile:2378: recipe for target 'modules' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928921] Re: LRMv5: switch primary version handling to kernel-versions data set
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! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1928921 Title: LRMv5: switch primary version handling to kernel-versions data set Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Released Bug description: Switch fetching dkms-versions data for these packages to the kernel- versions dataset. Currently the primary dkms-versions data is committed directly to the primary kernel packages. This allows this information to cascade reliably to all derivatives and their associated LRM packages. But once the primaries are closed it is increasingly hard to change this data. This makes performing an LRM-only respin very difficult as it differs in handling from a primary spin. We move the primary version dataset out of the kernel packages into a shared external "kernel-versions" dataset. Each package which needs this data then obtains the information it needs directly, with it committed locally to that package at update time. This renders preparation of am initial (-1) spin and a later LRM-only respin identicle. We simply update the shared dataset and perform a no-change rebuild (./update-versions) on them and they will automatically get the updated version information. We will want to update update-dkms-versions in all primary main packages, and introduce same into all LRM packages. As we already run update-dkms-versions in the primary main packages, and are introducing update-dkms-versions handling to update-versions in LRM this should not change kernel crank proceedure. The cycle proceedure will need a new step to update the shared kernel-versions dataset before cranking commences. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939618] Re: CryptoExpress EP11 cards are going offline
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!
** Tags added: verification-needed-focal
--
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/1939618
Title:
CryptoExpress EP11 cards are going offline
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification:
[Impact]
* With current focal kernels IBM Z CryptoExpress adapters in EP11 mode
go offline in case of unknown error indications from the hardware.
* This does not only lead to a software fallback, but can also lead to errors
and crashes,
if certain crypto operations are currently ongoing.
* A rework of the AP bus and zcrypt device driver, as it was done in
5.11, fixes the situation.
* From the below range of commits, the last 1/3 are the ones that fix the
issue mentioned here
and the others are pre-requisites to get the relevant ones applied.
* In theory the patch set could have been made smaller,
but with the cost that the code would be a mix between old and new, with
maybe some new code snippets,
hence it would divert from what's upstream accepted (in 5.11 and above),
the risk would increase,
increased effort to maintain and less test coverage.
[Fix]
* The SRU request was created as pull request,
so please pull f904c400c9c4^..f6d9ab1de03a (means starting at f904c400c9c4
{incl.} to head/f6d9ab1de03a {incl.})
from here: https://code.launchpad.net/~fheimes/+git/lp1939618
[Test Case]
* An Ubuntu Server 20.04 on IBM Z or LinuxONE installation is required,
with ideally three attached CryptoExpress adapters running in CCA, EP11 and
accelerator mode.
* Run stress test on these three CryptoExpress adapters.
* IBM has such stress tests and ran these based on a patched Ubuntu 20.04
kernel.
The tests come with a specially focus on error path tests,
since this patch set mainly focuses on doing a better error patch handling.
* Note: A a new config option for the zcrypt driver was introduced
that enables the possibility to inject erroneous messages.
* An application exists that generates such messages and thus tests
these error paths.
* Canonical's focus will mainly be on regression testing.
[Regression Potential]
* Like with all modification there is a certain risk of regressions,
especially with bigger patch sets.
* But the modifications here are limited to the s390x platform,
and there again largely to the s390x hardware crypto stack and driver
(CryptoExpress adapter) which is optional hardware.
(See the diff stat in the comment below.)
* The crypto-specific tools (located at the s390-tools package) may no longer
work with this patched driver.
But this got tested by IBM with the result that the changes are fully
backward compatible.
The 'older' s390 tools package (from focal) can just not show and control
the new (config state) feature,
but the functionality covered by the older s390 tools package is utterly
covered by this patch set.
* The core of this patch set went into the 5.11 kernel upstream,
hence is in hirsute (and has also been picked by other distros).
* Since this patch set is a rework of the AP bus and zcrypt driver code,
it may now show new errors that were never thrown before, like for or
example memory leaks.
However, this is not unique to this patch set, it the same for upstream,
Hirsute and Impish (and other distros).
* The patches are all upstream and all needed upstream commits could just be
cherry-picked,
hence no modifications were needed.
* So the commits were not only tested by IBM upfront,
but a patched focal master-next kernel is also available as PPA (see
comment below) for further testing.
* This patch set was also tested on 5.11, where two issues were found
that are already part of this set.
[Other]
* I iterated through all commits and found that that the latest ones got
upstream with 5.13,
hence Impish includes all commits needed and is not affected!
* Looks like all commits, expect three, are even upstream with 5.11,
but the missing three came in on top via upstream stable,
hence Hirsute master-next includes all commits needed too and is also
[Kernel-packages] [Bug 1939855] Re: [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands
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! ** Tags added: verification-needed-focal -- 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/1939855 Title: [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands Status in dellserver: Incomplete Status in focal package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in focal source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Impact] When we run the command, ethtool -d with Intel cards (ice driver), the kernel crashes because of the ice driver. The same works fine with HWE kernel (5.11). Here, we do not see any crash. [FIXES] ice: Fix bad register reads The "ethtool -d" handler reads registers in the ice_regs_dump_list array and returns read values back to the userspace. commitID: 1fba4a8a92706c89716449b1aab1b6879f438d34 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/ethernet/intel/ice?id=1fba4a8a92706c89716449b1aab1b6879f438d34 [TESTING] Install Focal on a system with an E810 network device. Ensure the network device has an IP address and has connectivity Run ethtool -d Expected result: Prints a register dump for the specified network device [REGRESSION RISK] The regression risk is low [OTHER INFO] I have added the fix, built the kernel and tested the fix. https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e810_ethtool_fix_next To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1939855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939915] Re: memory leaking when removing a profile
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!
** Tags added: verification-needed-focal
--
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/1939915
Title:
memory leaking when removing a profile
Status in AppArmor:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
There's a memory leak in the kernel when removing a profile.
A simple reproducible example:
root@ubuntu:~# echo "profile foo {}" > profile
root@ubuntu:~# apparmor_parser profile
root@ubuntu:~# apparmor_parser -R profile
root@ubuntu:~# echo scan > /sys/kernel/debug/kmemleak
root@ubuntu:~# cat /sys/kernel/debug/kmemleak
unreferenced object 0x99bcf5128bb0 (size 16):
comm "apparmor_parser", pid 1318, jiffies 4295139856 (age 33.196s)
hex dump (first 16 bytes):
01 00 00 00 00 00 00 00 98 1f 01 fd bc 99 ff ff
backtrace:
[] kmem_cache_alloc_trace+0xd8/0x1e0
[<86ca7bd9>] aa_alloc_proxy+0x30/0x60
[<0e34f34c>] aa_alloc_profile+0xd4/0x100
[] unpack_profile+0x16f/0xe10
[<19033e2b>] aa_unpack+0x119/0x500
[] aa_replace_profiles+0x94/0xca0
[<1833f520>] policy_update+0x124/0x1e0
[<992f950e>] profile_load+0x7d/0xa0
[] __vfs_write+0x1b/0x40
[<4e709f5d>] vfs_write+0xb9/0x1a0
[<280db840>] SyS_write+0x5e/0xe0
[<14c5ab5d>] do_syscall_64+0x79/0x130
[] entry_SYSCALL_64_after_hwframe+0x41/0xa6
[<9d368497>] 0x
This issue was already fixed upstream 3622ad25d4d6 v5.8-rc1~102^2
It still needs to be applied on xenial, bionic and focal.
This issue could lead to a OOM and eventually DoS. We could see this
issue happening during a test in which snaps were disconnected and
reconnected, causing the leak every time the profile was removed.
Since it is a refcount issue, there could be a lot of memory involved
because the whole profile would be leaked.
Note that only privileged users can remove a profile.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1939915/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936771] Re: disable “CONFIG_HISI_DMA” config for ubuntu version
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! ** Tags added: verification-needed-focal -- 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/1936771 Title: disable “CONFIG_HISI_DMA” config for ubuntu version Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] Setup soft RAID5 on kunpeng920 machine and system will crash because of hisi_dma timeout. This issue can be reproduced with all Ubuntu kernel with hisi_dma. [Test Plan] Setup soft RAID5 and wait for few seconds. Kernel will crash. [Regression Risk] CONFIG_HISI_DMA only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] disable “CONFIG_HISI_DMA” config for ubuntu version [Steps to Reproduce] 1) 2) 3) [Actual Results] this module cause some error [Expected Results] ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1936771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933248] Re: please drop virtualbox-guest-dkms virtualbox-guest-source
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! ** Tags added: verification-needed-focal -- 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/1933248 Title: please drop virtualbox-guest-dkms virtualbox-guest-source Status in linux package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in virtualbox source package in Focal: Invalid Status in virtualbox-hwe source package in Focal: Invalid Bug description: [Impact] * virtualbox guest modules have graduated into the upstream vanilla kernel, since at least v5.4 / Ubuntu 20.04 * These guest modules are no longer needed in dkms or source form, as they are always available from all kernel flavours, including when the packages are backported to Ubuntu 20.04. * Thus we should stop shipping them, and instead rely on the upstream ones. [Test Plan] * Boot virtualbox images * Check that guest-modules based integration still works. [Where problems could occur] * There might be differences between the linux kernel provided modules, guest userspace & host userspace tooling. If there are any differences, we would have to resolve the issues as needed to maintain backwards & forwards compatibility. [Other Info] * virtualbox guest modules fail to build from source with recent kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926142] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4
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! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1926142 Title: memfd from ubuntu_kernel_selftests failed to build on B-5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe-5.4 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe source package in Bionic: Invalid Status in linux-hwe-5.4 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-hwe source package in Focal: Invalid Status in linux-hwe-5.4 source package in Focal: Invalid Bug description: Test build on B-5.4 (5.4.0-73.82~18.04.1) failed with: error: ‘F_SEAL_FUTURE_WRITE’ undeclared Build log: $ sudo make TARGETS=memfd make --no-builtin-rules ARCH=x86 -C ../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd' gcc -D_FILE_OFFSET_BITS=64 -I../../../../include/uapi/ -I../../../../include/ -I../../../../usr/include/memfd_test.c common.o -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test memfd_test.c: In function ‘test_seal_future_write’: memfd_test.c:749:27: error: ‘F_SEAL_FUTURE_WRITE’ undeclared (first use in this function); did you mean ‘F_SEAL_WRITE’? mfd_assert_add_seals(fd, F_SEAL_FUTURE_WRITE); ^~~ F_SEAL_WRITE memfd_test.c:749:27: note: each undeclared identifier is reported only once for each function it appears in ../lib.mk:141: recipe for target '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test' failed make[1]: *** [/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test] Error 1 make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd' Makefile:143: recipe for target 'all' failed make: *** [all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1926142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941829] Re: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
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! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941829 Title: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
Same issue here on ubuntu 21.04, i was wondering why my power emptied overnight. ❯ sudo cat /sys/power/mem_sleep [s2idle] ❯ sudo dmesg | grep "suspend entry" [sudo] password for jeremy: [ 2739.515120] PM: suspend entry (s2idle) [22012.050938] PM: suspend entry (s2idle) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Hui Was the 5.11.0-34-generic release suppose to have the patch in it? Thanks Michael -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933173] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2021-09-07 11:34 EDT--- Fix released, landed in impish / 21.10, hence closing the bug. IBM BZ status:->CLOSED -- 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/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942908] Re: Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** No longer affects: linux (Ubuntu Impish) ** No longer affects: linux (Ubuntu Hirsute) ** No longer affects: linux (Ubuntu Focal) ** Also affects: s390-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: s390-tools-signed (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Changed in: s390-tools (Ubuntu) Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: s390-tools-signed (Ubuntu) Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- 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/1942908 Title: Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS Status in Ubuntu on IBM z Systems: New Status in s390-tools package in Ubuntu: New Status in s390-tools-signed package in Ubuntu: New Bug description: Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS Description: Fix of genprotimg allowing the tool to verify the validity of IBM Secure Execution host key documents. Without that, customers must verify the host key document by themselves,which is error prone and may impact security. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1942908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942908] [NEW] Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS
Public bug reported: Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS Description: Fix of genprotimg allowing the tool to verify the validity of IBM Secure Execution host key documents. Without that, customers must verify the host key document by themselves,which is error prone and may impact security. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-194437 severity-high targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-194437 severity-high targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- 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/1942908 Title: Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS Status in linux package in Ubuntu: New Bug description: Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS Description: Fix of genprotimg allowing the tool to verify the validity of IBM Secure Execution host key documents. Without that, customers must verify the host key document by themselves,which is error prone and may impact security. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942908] [NEW] Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS
You have been subscribed to a public bug: Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS Description: Fix of genprotimg allowing the tool to verify the validity of IBM Secure Execution host key documents. Without that, customers must verify the host key document by themselves,which is error prone and may impact security. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-194437 severity-high targetmilestone-inin2004 -- Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS https://bugs.launchpad.net/bugs/1942908 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909814] Re: Medion Notebook Keyboard not working
commit was reverted in Focal due to regression. Setting from fix released -> triaged ** Changed in: linux (Ubuntu Focal) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1909814 Title: Medion Notebook Keyboard not working Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942902] Re: Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split corruption"
** Tags added: bot-stop-nagging
--
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/1942902
Title:
Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split
corruption"
Status in linux package in Ubuntu:
Incomplete
Bug description:
In order to address https://bugs.launchpad.net/bugs/1933074 the following
SAUCE patch was introduced.
Colin Ian King (1):
UBUNTU: SAUCE: ext4: fix directory index node split corruption
fs/ext4/namei.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
Meanwhile the issue addressed by this patch was fixed upstream with
commit 877ba3f729fd ("ext4: fix potential htree corruption when
growing large_dir directories").
The upstream patch was already cherry-picked to hirsute with "upstream
stable patchset 2021-08-30" [1] commit ffcc845ec245) and focal with
"v5.4.140 upstream stable release" [2] (commit 93ad4c3f59c6).
[1] BugLink: https://bugs.launchpad.net/bugs/1942123
[2] BugLink: https://bugs.launchpad.net/bugs/1941798
Therefore the SAUCE patch is obsolete and can be either dropped or
reverted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942902/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942905] [NEW] nfs secure and kernel 5.11.0
Public bug reported: Since kernel update to 5.11.0-27, nfs is not mounted. I get "mount.nfs: access denied by server while mounting perso-env.univ- rennes1.fr:/homedir" error. If I start with kernel 5.8.0-40 or 5.8.0-55 nfs works fine. lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 Here is the log generated in syslog.log when I try to mount the nfs share : Sep 7 16:58:01 localhost kernel: [ 3421.211160] NFS: parsing nfs mount option 'source' Sep 7 16:58:01 localhost kernel: [ 3421.211169] NFS: parsing nfs mount option 'sec' Sep 7 16:58:01 localhost kernel: [ 3421.211170] NFS: parsing sec=krb5i option Sep 7 16:58:01 localhost kernel: [ 3421.211171] NFS: parsing nfs mount option 'rsize' Sep 7 16:58:01 localhost kernel: [ 3421.211173] NFS: parsing nfs mount option 'wsize' Sep 7 16:58:01 localhost kernel: [ 3421.211173] NFS: parsing nfs mount option 'vers' Sep 7 16:58:01 localhost kernel: [ 3421.211174] NFS: parsing nfs mount option 'addr' Sep 7 16:58:01 localhost kernel: [ 3421.211176] NFS: parsing nfs mount option 'clientaddr' Sep 7 16:58:01 localhost kernel: [ 3421.211178] NFS: MNTPATH: '/homedir' Sep 7 16:58:01 localhost kernel: [ 3421.211192] --> nfs4_try_get_tree() Sep 7 16:58:01 localhost kernel: [ 3421.211217] NFS: get client cookie (0xd9ee28bb/0xacddf283) Sep 7 16:58:01 localhost kernel: [ 3421.212538] nfs_callback_create_svc: service created Sep 7 16:58:01 localhost kernel: [ 3421.212540] NFS: create per-net callback data; net=f098 Sep 7 16:58:01 localhost kernel: [ 3421.212596] nfs_callback_up: service started Sep 7 16:58:01 localhost kernel: [ 3421.212597] NFS: nfs4_discover_server_trunking: testing 'perso-env.univ-rennes1.fr' Sep 7 16:58:01 localhost kernel: [ 3421.370800] NFS: nfs4_discover_server_trunking: status = -93 Sep 7 16:58:01 localhost kernel: [ 3421.370807] --> nfs4_proc_destroy_session Sep 7 16:58:01 localhost kernel: [ 3421.370817] nfs4_destroy_session Destroy backchannel for xprt b9884bbb Sep 7 16:58:01 localhost kernel: [ 3421.370822] NFS: destroy per-net callback data; net=f098 Sep 7 16:58:01 localhost kernel: [ 3421.370852] nfs_callback_down: service destroyed Sep 7 16:58:01 localhost kernel: [ 3421.370865] NFS: releasing client cookie (0xd9ee28bb/0xacddf283) Sep 7 16:58:01 localhost kernel: [ 3421.370886] NFS4: Couldn't follow remote path Sep 7 16:58:01 localhost kernel: [ 3421.370887] <-- nfs4_try_get_tree() = -93 [error] Sep 7 16:58:01 localhost kernel: [ 3421.370948] NFS: parsing nfs mount option 'source' Sep 7 16:58:01 localhost kernel: [ 3421.370951] NFS: parsing nfs mount option 'sec' Sep 7 16:58:01 localhost kernel: [ 3421.370952] NFS: parsing sec=krb5i option Sep 7 16:58:01 localhost kernel: [ 3421.370954] NFS: parsing nfs mount option 'rsize' Sep 7 16:58:01 localhost kernel: [ 3421.370956] NFS: parsing nfs mount option 'wsize' Sep 7 16:58:01 localhost kernel: [ 3421.370957] NFS: parsing nfs mount option 'vers' Sep 7 16:58:01 localhost kernel: [ 3421.370959] NFS: parsing nfs mount option 'addr' Sep 7 16:58:01 localhost kernel: [ 3421.370961] NFS: parsing nfs mount option 'clientaddr' Sep 7 16:58:01 localhost kernel: [ 3421.370963] NFS: MNTPATH: '/homedir' Sep 7 16:58:01 localhost kernel: [ 3421.370965] --> nfs4_try_get_tree() Sep 7 16:58:01 localhost kernel: [ 3421.370970] NFS: get client cookie (0x74a5c991/0xacddf283) Sep 7 16:58:01 localhost kernel: [ 3421.372032] nfs_callback_create_svc: service created Sep 7 16:58:01 localhost kernel: [ 3421.372034] NFS: create per-net callback data; net=f098 Sep 7 16:58:01 localhost kernel: [ 3421.372081] nfs_callback_up: service started Sep 7 16:58:01 localhost kernel: [ 3421.372083] NFS: nfs4_discover_server_trunking: testing 'perso-env.univ-rennes1.fr' Sep 7 16:58:01 localhost kernel: [ 3421.542850] --> nfs4_proc_create_session clp=74a5c991 session=28a54e79 Sep 7 16:58:01 localhost kernel: [ 3421.542858] nfs4_init_channel_attrs: Fore Channel : max_rqst_sz=1049620 max_resp_sz=1049480 max_ops=8 max_reqs=64 Sep 7 16:58:01 localhost kernel: [ 3421.542862] nfs4_init_channel_attrs: Back Channel : max_rqst_sz=4096 max_resp_sz=4096 max_resp_sz_cached=0 max_ops=2 max_reqs=16 Sep 7 16:58:01 localhost kernel: [ 3421.543599] --> nfs4_setup_session_slot_tables Sep 7 16:58:01 localhost kernel: [ 3421.543602] --> nfs4_realloc_slot_table: max_reqs=48, tbl->max_slots 0 Sep 7 16:58:01 localhost kernel: [ 3421.543610] nfs4_realloc_slot_table: tbl=f0cd7226 slots=580231a9 max_slots=48 Sep 7 16:58:01 localhost kernel: [ 3421.543613] <-- nfs4_realloc_slot_table: return 0 Sep 7 16:58:01 localhost kernel: [ 3421.543614] --> nfs4_realloc_slot_table: max_reqs=16, tbl->max_slots 0 Sep 7 16:58:01 localhost kernel: [ 3421.543617] nfs4_realloc_slot_table: tbl=0dfde2fa slots=baa5c9be max_slots=16 Sep
[Kernel-packages] [Bug 1933173] Re: [21.10 FEAT] KVM: Provide a secure guest indication
Since 5.13 already landed in impish: linux-generic | 5.13.0.14.25 | impish and the patches are also upstream with 5.13, I'll update the "affects impish" entry as Fix Released and with that the entire ticket is Fix Released. ** Changed in: linux (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- 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/1933173 Title: [21.10 FEAT] KVM: Provide a secure guest indication Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: SRU Justification: == [Impact] * It is difficult for customers to identify if a KVM guest on s390x runs in secure execution more or not. Hence several requests came up that asked about providing a better indication. * If the mode is not known, one may venture oneself into deceptive security. * Patches that allow a better indication via 'prot_virt_host' using the sysfs firmware interface were added to upstream kernel 5.13. * Secure execution was initially introduced in Ubuntu with focal / 20.04, hence this request to SRU. [Fix] * 37564ed834aca26993b77b9b2a0119ec1ba6e00c 37564ed834ac "s390/uv: add prot virt guest/host indication files" * df2e400e07ad53a582ee934ce8384479d5ddf48b df2e400e07ad "s390/uv: fix prot virt host indication compilation" [Test Case] * A z15 or LinuxONE III LPAR is needed that runs KVM in secure execution. * Have a look for the 'prot_virt_host' key at the sysfs firmware interface - '1' indicates that the ultravisor is active and that the guest is running protected (in secure execution mode). [Regression Potential] * The patch is s390x specific and modifies file arch/s390/kernel/uv.c only. * An entirely new new function 'uv_is_prot_virt_guest' was added and initialized and used in uv_info_init - hence the regression risk in existing code is rather small. * However, in case the initialization was done errornously the indication might be wrong, maybe showing that the system is not protected in the way it should be (wrong indication). * More general code deficiencies in these two functions will be largely indicated by the test compiles. * But the code was already tested based on kernel 5.13 - and for SRU- ing a cherry-pick of the patches was sufficient, hence the exact same code as in 5.13 is used. * Further tests of the SRU kernels (5.11 and 5.4) can be done based on the test kernel available from the PPA (see below). [Other] * Patches are upstream accepted with since 5.13-rc1. * Request was to add the patches to focal / 20.04. * To avoid potential regressions on upgrades, the patches need to be added to hirsute / 20.10, too. __ Provide an indication in the guest that it's running securely. Cannot replace a real attestation and doesn't really provide additional security (or could even create the false impression of security), but has been frequently requested by customers. Value: Usability, lower the effort to prepare and deploy secure workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942902] Missing required logs.
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 1942902
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.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1942902
Title:
Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split
corruption"
Status in linux package in Ubuntu:
Incomplete
Bug description:
In order to address https://bugs.launchpad.net/bugs/1933074 the following
SAUCE patch was introduced.
Colin Ian King (1):
UBUNTU: SAUCE: ext4: fix directory index node split corruption
fs/ext4/namei.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
Meanwhile the issue addressed by this patch was fixed upstream with
commit 877ba3f729fd ("ext4: fix potential htree corruption when
growing large_dir directories").
The upstream patch was already cherry-picked to hirsute with "upstream
stable patchset 2021-08-30" [1] commit ffcc845ec245) and focal with
"v5.4.140 upstream stable release" [2] (commit 93ad4c3f59c6).
[1] BugLink: https://bugs.launchpad.net/bugs/1942123
[2] BugLink: https://bugs.launchpad.net/bugs/1941798
Therefore the SAUCE patch is obsolete and can be either dropped or
reverted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942902/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936231] Re: Bionic update: upstream stable patchset 2021-07-14
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails to launch linux L2 guests on AMD (LP: #1940134) // CVE-2021-3653
- KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
(CVE-2021-3653)
* fails to launch linux L2 guests on AMD (LP: #1940134)
- SAUCE: Revert "UBUNTU: SAUCE: KVM: nSVM: avoid picking up unsupported bits
from L2 in int_ctl"
linux (4.15.0-155.162) bionic; urgency=medium
* bionic/linux: 4.15.0-155.162 -proposed tracker (LP: #1939833)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.08.16)
* CVE-2021-3656
- SAUCE: KVM: nSVM: always intercept VMLOAD/VMSAVE when nested
* CVE-2021-3653
- SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
* dev_forward_skb: do not scrub skb mark within the same name space
(LP: #1935040)
- dev_forward_skb: do not scrub skb mark within the same name space
* 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
(LP: #1890848)
- apparmor: fix ptrace read check
* Bionic update: upstream stable patchset 2021-08-03 (LP: #1938824)
- ALSA: usb-audio: fix rate on Ozone Z90 USB headset
- media: dvb-usb: fix wrong definition
- Input: usbtouchscreen - fix control-request directions
- net: can: ems_usb: fix use-after-free in ems_usb_disconnect()
- usb: gadget: eem: fix echo command packet response issue
- USB: cdc-acm: blacklist Heimann USB Appset device
- ntfs: fix validity check for file name attribute
- iov_iter_fault_in_readable() should do nothing in xarray case
- Input: joydev - prevent use of not validated data in JSIOCSBTNMAP ioctl
- ARM: dts: at91: sama5d4: fix pinctrl muxing
- btrfs: send: fix invalid path for unlink operations after parent
orphanization
- btrfs: clear defrag status of a root if starting transaction fails
- ext4: cleanup in-core orphan list if ext4_truncate() failed to get a
transaction handle
- ext4: fix kernel infoleak via ext4_extent_header
- ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
- ext4: remove check for zero nr_to_scan in ext4_es_scan()
- ext4: fix avefreec in find_group_orlov
- ext4: use ext4_grp_locked_error in mb_find_extent
- can: gw: synchronize rcu operations before removing gw job entry
- can: peak_pciefd: pucan_handle_status(): fix a potential starvation issue
in
TX path
- SUNRPC: Fix the batch tasks count wraparound.
- SUNRPC: Should wake up the privileged task firstly.
- s390/cio: dont call css_wait_for_slow_path() inside a lock
- rtc: stm32: Fix unbalanced clk_disable_unprepare() on probe error path
- iio: ltr501: mark register holding upper 8 bits of ALS_DATA{0,1} and
PS_DATA
as volatile, too
- iio: ltr501: ltr559: fix initialization of LTR501_ALS_CONTR
- iio: ltr501: ltr501_read_ps(): add missing endianness conversion
- serial: sh-sci: Stop dmaengine transfer in sci_stop_tx()
- serial_cs: Add Option International GSM-Ready 56K/ISDN modem
- serial_cs: remove wrong GLOBETROTTER.cis entry
- ath9k: Fix kernel NULL pointer dereference during ath_reset_internal()
- ssb: sdio: Don't overwrite const buffer if block_write fails
- rsi: Assign beacon rate settings to the correct rate_info descriptor field
- seq_buf: Make trace_seq_putmem_hex() support data longer than 8
- fuse: check connected before queueing on fpq->io
- spi: Make of_register_spi_device also set the fwnode
- spi: spi-loopback-test: Fix 'tx_buf' might be 'rx_buf'
- spi: spi-topcliff-pch: Fix potential double free in
pch_spi_process_messages()
- spi: omap-100k: Fix the length judgment problem
- crypto: nx - add missing MODULE_DEVICE_TABLE
- media: cpia2: fix memory leak in cpia2_usb_probe
- media: cobalt: fix race condition in setting HPD
- media: pvrusb2: fix warning in pvr2_i2c_core_done
- crypto: qat - check return code of qat_hal_rd_rel_reg()
- crypto: qat - remove unused macro in FW loader
- media: em28xx: Fix possible memory leak of em28xx struct
- media: v4l2-core: Avoid the dangling pointer in v4l2_fh_release
- media: bt8xx: Fix a missing check bug in bt878_probe
- media: st-hva: Fix potential NULL pointer dereferences
- media: dvd_usb: memory leak in cinergyt2_fe_attach
- mmc: via-sdmmc: add a check against NULL pointer dereference
- crypto: shash - avoid comparing pointers to exported functions under CFI
- media: dvb_net: avoid speculation from net slot
- media: siano: fix device register error path
- btrfs: fix error handling in __btrfs_update_delayed_inode
- btrfs: abort transaction if
[Kernel-packages] [Bug 1936960] Re: Bionic update: upstream stable patchset 2021-07-20
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails to launch linux L2 guests on AMD (LP: #1940134) // CVE-2021-3653
- KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
(CVE-2021-3653)
* fails to launch linux L2 guests on AMD (LP: #1940134)
- SAUCE: Revert "UBUNTU: SAUCE: KVM: nSVM: avoid picking up unsupported bits
from L2 in int_ctl"
linux (4.15.0-155.162) bionic; urgency=medium
* bionic/linux: 4.15.0-155.162 -proposed tracker (LP: #1939833)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.08.16)
* CVE-2021-3656
- SAUCE: KVM: nSVM: always intercept VMLOAD/VMSAVE when nested
* CVE-2021-3653
- SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
* dev_forward_skb: do not scrub skb mark within the same name space
(LP: #1935040)
- dev_forward_skb: do not scrub skb mark within the same name space
* 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
(LP: #1890848)
- apparmor: fix ptrace read check
* Bionic update: upstream stable patchset 2021-08-03 (LP: #1938824)
- ALSA: usb-audio: fix rate on Ozone Z90 USB headset
- media: dvb-usb: fix wrong definition
- Input: usbtouchscreen - fix control-request directions
- net: can: ems_usb: fix use-after-free in ems_usb_disconnect()
- usb: gadget: eem: fix echo command packet response issue
- USB: cdc-acm: blacklist Heimann USB Appset device
- ntfs: fix validity check for file name attribute
- iov_iter_fault_in_readable() should do nothing in xarray case
- Input: joydev - prevent use of not validated data in JSIOCSBTNMAP ioctl
- ARM: dts: at91: sama5d4: fix pinctrl muxing
- btrfs: send: fix invalid path for unlink operations after parent
orphanization
- btrfs: clear defrag status of a root if starting transaction fails
- ext4: cleanup in-core orphan list if ext4_truncate() failed to get a
transaction handle
- ext4: fix kernel infoleak via ext4_extent_header
- ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
- ext4: remove check for zero nr_to_scan in ext4_es_scan()
- ext4: fix avefreec in find_group_orlov
- ext4: use ext4_grp_locked_error in mb_find_extent
- can: gw: synchronize rcu operations before removing gw job entry
- can: peak_pciefd: pucan_handle_status(): fix a potential starvation issue
in
TX path
- SUNRPC: Fix the batch tasks count wraparound.
- SUNRPC: Should wake up the privileged task firstly.
- s390/cio: dont call css_wait_for_slow_path() inside a lock
- rtc: stm32: Fix unbalanced clk_disable_unprepare() on probe error path
- iio: ltr501: mark register holding upper 8 bits of ALS_DATA{0,1} and
PS_DATA
as volatile, too
- iio: ltr501: ltr559: fix initialization of LTR501_ALS_CONTR
- iio: ltr501: ltr501_read_ps(): add missing endianness conversion
- serial: sh-sci: Stop dmaengine transfer in sci_stop_tx()
- serial_cs: Add Option International GSM-Ready 56K/ISDN modem
- serial_cs: remove wrong GLOBETROTTER.cis entry
- ath9k: Fix kernel NULL pointer dereference during ath_reset_internal()
- ssb: sdio: Don't overwrite const buffer if block_write fails
- rsi: Assign beacon rate settings to the correct rate_info descriptor field
- seq_buf: Make trace_seq_putmem_hex() support data longer than 8
- fuse: check connected before queueing on fpq->io
- spi: Make of_register_spi_device also set the fwnode
- spi: spi-loopback-test: Fix 'tx_buf' might be 'rx_buf'
- spi: spi-topcliff-pch: Fix potential double free in
pch_spi_process_messages()
- spi: omap-100k: Fix the length judgment problem
- crypto: nx - add missing MODULE_DEVICE_TABLE
- media: cpia2: fix memory leak in cpia2_usb_probe
- media: cobalt: fix race condition in setting HPD
- media: pvrusb2: fix warning in pvr2_i2c_core_done
- crypto: qat - check return code of qat_hal_rd_rel_reg()
- crypto: qat - remove unused macro in FW loader
- media: em28xx: Fix possible memory leak of em28xx struct
- media: v4l2-core: Avoid the dangling pointer in v4l2_fh_release
- media: bt8xx: Fix a missing check bug in bt878_probe
- media: st-hva: Fix potential NULL pointer dereferences
- media: dvd_usb: memory leak in cinergyt2_fe_attach
- mmc: via-sdmmc: add a check against NULL pointer dereference
- crypto: shash - avoid comparing pointers to exported functions under CFI
- media: dvb_net: avoid speculation from net slot
- media: siano: fix device register error path
- btrfs: fix error handling in __btrfs_update_delayed_inode
- btrfs: abort transaction if
[Kernel-packages] [Bug 1882623] Re: VM enter into hung status after triggering a crash
This bug was fixed in the package linux-azure-4.15 - 4.15.0-1123.136
---
linux-azure-4.15 (4.15.0-1123.136) bionic; urgency=medium
* bionic/linux-azure-4.15: 4.15.0-1123.136 -proposed tracker (LP:
#1939816)
* VM enter into hung status after triggering a crash (LP: #1882623)
- Drivers: hv: vmbus: Implement Direct Mode for stimer0
[ Ubuntu: 4.15.0-156.163 ]
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails to launch linux L2 guests on AMD (LP: #1940134) // CVE-2021-3653
- KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
(CVE-2021-3653)
* fails to launch linux L2 guests on AMD (LP: #1940134)
- SAUCE: Revert "UBUNTU: SAUCE: KVM: nSVM: avoid picking up unsupported bits
from L2 in int_ctl"
[ Ubuntu: 4.15.0-155.162 ]
* bionic/linux: 4.15.0-155.162 -proposed tracker (LP: #1939833)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.08.16)
* CVE-2021-3656
- SAUCE: KVM: nSVM: always intercept VMLOAD/VMSAVE when nested
* CVE-2021-3653
- SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
* dev_forward_skb: do not scrub skb mark within the same name space
(LP: #1935040)
- dev_forward_skb: do not scrub skb mark within the same name space
* 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
(LP: #1890848)
- apparmor: fix ptrace read check
* Bionic update: upstream stable patchset 2021-08-03 (LP: #1938824)
- ALSA: usb-audio: fix rate on Ozone Z90 USB headset
- media: dvb-usb: fix wrong definition
- Input: usbtouchscreen - fix control-request directions
- net: can: ems_usb: fix use-after-free in ems_usb_disconnect()
- usb: gadget: eem: fix echo command packet response issue
- USB: cdc-acm: blacklist Heimann USB Appset device
- ntfs: fix validity check for file name attribute
- iov_iter_fault_in_readable() should do nothing in xarray case
- Input: joydev - prevent use of not validated data in JSIOCSBTNMAP ioctl
- ARM: dts: at91: sama5d4: fix pinctrl muxing
- btrfs: send: fix invalid path for unlink operations after parent
orphanization
- btrfs: clear defrag status of a root if starting transaction fails
- ext4: cleanup in-core orphan list if ext4_truncate() failed to get a
transaction handle
- ext4: fix kernel infoleak via ext4_extent_header
- ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
- ext4: remove check for zero nr_to_scan in ext4_es_scan()
- ext4: fix avefreec in find_group_orlov
- ext4: use ext4_grp_locked_error in mb_find_extent
- can: gw: synchronize rcu operations before removing gw job entry
- can: peak_pciefd: pucan_handle_status(): fix a potential starvation issue
in
TX path
- SUNRPC: Fix the batch tasks count wraparound.
- SUNRPC: Should wake up the privileged task firstly.
- s390/cio: dont call css_wait_for_slow_path() inside a lock
- rtc: stm32: Fix unbalanced clk_disable_unprepare() on probe error path
- iio: ltr501: mark register holding upper 8 bits of ALS_DATA{0,1} and
PS_DATA
as volatile, too
- iio: ltr501: ltr559: fix initialization of LTR501_ALS_CONTR
- iio: ltr501: ltr501_read_ps(): add missing endianness conversion
- serial: sh-sci: Stop dmaengine transfer in sci_stop_tx()
- serial_cs: Add Option International GSM-Ready 56K/ISDN modem
- serial_cs: remove wrong GLOBETROTTER.cis entry
- ath9k: Fix kernel NULL pointer dereference during ath_reset_internal()
- ssb: sdio: Don't overwrite const buffer if block_write fails
- rsi: Assign beacon rate settings to the correct rate_info descriptor field
- seq_buf: Make trace_seq_putmem_hex() support data longer than 8
- fuse: check connected before queueing on fpq->io
- spi: Make of_register_spi_device also set the fwnode
- spi: spi-loopback-test: Fix 'tx_buf' might be 'rx_buf'
- spi: spi-topcliff-pch: Fix potential double free in
pch_spi_process_messages()
- spi: omap-100k: Fix the length judgment problem
- crypto: nx - add missing MODULE_DEVICE_TABLE
- media: cpia2: fix memory leak in cpia2_usb_probe
- media: cobalt: fix race condition in setting HPD
- media: pvrusb2: fix warning in pvr2_i2c_core_done
- crypto: qat - check return code of qat_hal_rd_rel_reg()
- crypto: qat - remove unused macro in FW loader
- media: em28xx: Fix possible memory leak of em28xx struct
- media: v4l2-core: Avoid the dangling pointer in v4l2_fh_release
- media: bt8xx: Fix a missing check bug in bt878_probe
- media: st-hva: Fix potential NULL pointer dereferences
- media: dvd_usb: memory leak in cinergyt2_fe_attach
- mmc: via-sdmmc: add a check against NULL pointer dereference
- crypto: shash - avoid comparing
[Kernel-packages] [Bug 1935040] Re: dev_forward_skb: do not scrub skb mark within the same name space
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails to launch linux L2 guests on AMD (LP: #1940134) // CVE-2021-3653
- KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
(CVE-2021-3653)
* fails to launch linux L2 guests on AMD (LP: #1940134)
- SAUCE: Revert "UBUNTU: SAUCE: KVM: nSVM: avoid picking up unsupported bits
from L2 in int_ctl"
linux (4.15.0-155.162) bionic; urgency=medium
* bionic/linux: 4.15.0-155.162 -proposed tracker (LP: #1939833)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.08.16)
* CVE-2021-3656
- SAUCE: KVM: nSVM: always intercept VMLOAD/VMSAVE when nested
* CVE-2021-3653
- SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
* dev_forward_skb: do not scrub skb mark within the same name space
(LP: #1935040)
- dev_forward_skb: do not scrub skb mark within the same name space
* 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
(LP: #1890848)
- apparmor: fix ptrace read check
* Bionic update: upstream stable patchset 2021-08-03 (LP: #1938824)
- ALSA: usb-audio: fix rate on Ozone Z90 USB headset
- media: dvb-usb: fix wrong definition
- Input: usbtouchscreen - fix control-request directions
- net: can: ems_usb: fix use-after-free in ems_usb_disconnect()
- usb: gadget: eem: fix echo command packet response issue
- USB: cdc-acm: blacklist Heimann USB Appset device
- ntfs: fix validity check for file name attribute
- iov_iter_fault_in_readable() should do nothing in xarray case
- Input: joydev - prevent use of not validated data in JSIOCSBTNMAP ioctl
- ARM: dts: at91: sama5d4: fix pinctrl muxing
- btrfs: send: fix invalid path for unlink operations after parent
orphanization
- btrfs: clear defrag status of a root if starting transaction fails
- ext4: cleanup in-core orphan list if ext4_truncate() failed to get a
transaction handle
- ext4: fix kernel infoleak via ext4_extent_header
- ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
- ext4: remove check for zero nr_to_scan in ext4_es_scan()
- ext4: fix avefreec in find_group_orlov
- ext4: use ext4_grp_locked_error in mb_find_extent
- can: gw: synchronize rcu operations before removing gw job entry
- can: peak_pciefd: pucan_handle_status(): fix a potential starvation issue
in
TX path
- SUNRPC: Fix the batch tasks count wraparound.
- SUNRPC: Should wake up the privileged task firstly.
- s390/cio: dont call css_wait_for_slow_path() inside a lock
- rtc: stm32: Fix unbalanced clk_disable_unprepare() on probe error path
- iio: ltr501: mark register holding upper 8 bits of ALS_DATA{0,1} and
PS_DATA
as volatile, too
- iio: ltr501: ltr559: fix initialization of LTR501_ALS_CONTR
- iio: ltr501: ltr501_read_ps(): add missing endianness conversion
- serial: sh-sci: Stop dmaengine transfer in sci_stop_tx()
- serial_cs: Add Option International GSM-Ready 56K/ISDN modem
- serial_cs: remove wrong GLOBETROTTER.cis entry
- ath9k: Fix kernel NULL pointer dereference during ath_reset_internal()
- ssb: sdio: Don't overwrite const buffer if block_write fails
- rsi: Assign beacon rate settings to the correct rate_info descriptor field
- seq_buf: Make trace_seq_putmem_hex() support data longer than 8
- fuse: check connected before queueing on fpq->io
- spi: Make of_register_spi_device also set the fwnode
- spi: spi-loopback-test: Fix 'tx_buf' might be 'rx_buf'
- spi: spi-topcliff-pch: Fix potential double free in
pch_spi_process_messages()
- spi: omap-100k: Fix the length judgment problem
- crypto: nx - add missing MODULE_DEVICE_TABLE
- media: cpia2: fix memory leak in cpia2_usb_probe
- media: cobalt: fix race condition in setting HPD
- media: pvrusb2: fix warning in pvr2_i2c_core_done
- crypto: qat - check return code of qat_hal_rd_rel_reg()
- crypto: qat - remove unused macro in FW loader
- media: em28xx: Fix possible memory leak of em28xx struct
- media: v4l2-core: Avoid the dangling pointer in v4l2_fh_release
- media: bt8xx: Fix a missing check bug in bt878_probe
- media: st-hva: Fix potential NULL pointer dereferences
- media: dvd_usb: memory leak in cinergyt2_fe_attach
- mmc: via-sdmmc: add a check against NULL pointer dereference
- crypto: shash - avoid comparing pointers to exported functions under CFI
- media: dvb_net: avoid speculation from net slot
- media: siano: fix device register error path
- btrfs: fix error handling in __btrfs_update_delayed_inode
- btrfs: abort transaction if
[Kernel-packages] [Bug 1890848] Re: 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails to launch linux L2 guests on AMD (LP: #1940134) // CVE-2021-3653
- KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
(CVE-2021-3653)
* fails to launch linux L2 guests on AMD (LP: #1940134)
- SAUCE: Revert "UBUNTU: SAUCE: KVM: nSVM: avoid picking up unsupported bits
from L2 in int_ctl"
linux (4.15.0-155.162) bionic; urgency=medium
* bionic/linux: 4.15.0-155.162 -proposed tracker (LP: #1939833)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.08.16)
* CVE-2021-3656
- SAUCE: KVM: nSVM: always intercept VMLOAD/VMSAVE when nested
* CVE-2021-3653
- SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
* dev_forward_skb: do not scrub skb mark within the same name space
(LP: #1935040)
- dev_forward_skb: do not scrub skb mark within the same name space
* 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
(LP: #1890848)
- apparmor: fix ptrace read check
* Bionic update: upstream stable patchset 2021-08-03 (LP: #1938824)
- ALSA: usb-audio: fix rate on Ozone Z90 USB headset
- media: dvb-usb: fix wrong definition
- Input: usbtouchscreen - fix control-request directions
- net: can: ems_usb: fix use-after-free in ems_usb_disconnect()
- usb: gadget: eem: fix echo command packet response issue
- USB: cdc-acm: blacklist Heimann USB Appset device
- ntfs: fix validity check for file name attribute
- iov_iter_fault_in_readable() should do nothing in xarray case
- Input: joydev - prevent use of not validated data in JSIOCSBTNMAP ioctl
- ARM: dts: at91: sama5d4: fix pinctrl muxing
- btrfs: send: fix invalid path for unlink operations after parent
orphanization
- btrfs: clear defrag status of a root if starting transaction fails
- ext4: cleanup in-core orphan list if ext4_truncate() failed to get a
transaction handle
- ext4: fix kernel infoleak via ext4_extent_header
- ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
- ext4: remove check for zero nr_to_scan in ext4_es_scan()
- ext4: fix avefreec in find_group_orlov
- ext4: use ext4_grp_locked_error in mb_find_extent
- can: gw: synchronize rcu operations before removing gw job entry
- can: peak_pciefd: pucan_handle_status(): fix a potential starvation issue
in
TX path
- SUNRPC: Fix the batch tasks count wraparound.
- SUNRPC: Should wake up the privileged task firstly.
- s390/cio: dont call css_wait_for_slow_path() inside a lock
- rtc: stm32: Fix unbalanced clk_disable_unprepare() on probe error path
- iio: ltr501: mark register holding upper 8 bits of ALS_DATA{0,1} and
PS_DATA
as volatile, too
- iio: ltr501: ltr559: fix initialization of LTR501_ALS_CONTR
- iio: ltr501: ltr501_read_ps(): add missing endianness conversion
- serial: sh-sci: Stop dmaengine transfer in sci_stop_tx()
- serial_cs: Add Option International GSM-Ready 56K/ISDN modem
- serial_cs: remove wrong GLOBETROTTER.cis entry
- ath9k: Fix kernel NULL pointer dereference during ath_reset_internal()
- ssb: sdio: Don't overwrite const buffer if block_write fails
- rsi: Assign beacon rate settings to the correct rate_info descriptor field
- seq_buf: Make trace_seq_putmem_hex() support data longer than 8
- fuse: check connected before queueing on fpq->io
- spi: Make of_register_spi_device also set the fwnode
- spi: spi-loopback-test: Fix 'tx_buf' might be 'rx_buf'
- spi: spi-topcliff-pch: Fix potential double free in
pch_spi_process_messages()
- spi: omap-100k: Fix the length judgment problem
- crypto: nx - add missing MODULE_DEVICE_TABLE
- media: cpia2: fix memory leak in cpia2_usb_probe
- media: cobalt: fix race condition in setting HPD
- media: pvrusb2: fix warning in pvr2_i2c_core_done
- crypto: qat - check return code of qat_hal_rd_rel_reg()
- crypto: qat - remove unused macro in FW loader
- media: em28xx: Fix possible memory leak of em28xx struct
- media: v4l2-core: Avoid the dangling pointer in v4l2_fh_release
- media: bt8xx: Fix a missing check bug in bt878_probe
- media: st-hva: Fix potential NULL pointer dereferences
- media: dvd_usb: memory leak in cinergyt2_fe_attach
- mmc: via-sdmmc: add a check against NULL pointer dereference
- crypto: shash - avoid comparing pointers to exported functions under CFI
- media: dvb_net: avoid speculation from net slot
- media: siano: fix device register error path
- btrfs: fix error handling in __btrfs_update_delayed_inode
- btrfs: abort transaction if
[Kernel-packages] [Bug 1938824] Re: Bionic update: upstream stable patchset 2021-08-03
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails to launch linux L2 guests on AMD (LP: #1940134) // CVE-2021-3653
- KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
(CVE-2021-3653)
* fails to launch linux L2 guests on AMD (LP: #1940134)
- SAUCE: Revert "UBUNTU: SAUCE: KVM: nSVM: avoid picking up unsupported bits
from L2 in int_ctl"
linux (4.15.0-155.162) bionic; urgency=medium
* bionic/linux: 4.15.0-155.162 -proposed tracker (LP: #1939833)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.08.16)
* CVE-2021-3656
- SAUCE: KVM: nSVM: always intercept VMLOAD/VMSAVE when nested
* CVE-2021-3653
- SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
* dev_forward_skb: do not scrub skb mark within the same name space
(LP: #1935040)
- dev_forward_skb: do not scrub skb mark within the same name space
* 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
(LP: #1890848)
- apparmor: fix ptrace read check
* Bionic update: upstream stable patchset 2021-08-03 (LP: #1938824)
- ALSA: usb-audio: fix rate on Ozone Z90 USB headset
- media: dvb-usb: fix wrong definition
- Input: usbtouchscreen - fix control-request directions
- net: can: ems_usb: fix use-after-free in ems_usb_disconnect()
- usb: gadget: eem: fix echo command packet response issue
- USB: cdc-acm: blacklist Heimann USB Appset device
- ntfs: fix validity check for file name attribute
- iov_iter_fault_in_readable() should do nothing in xarray case
- Input: joydev - prevent use of not validated data in JSIOCSBTNMAP ioctl
- ARM: dts: at91: sama5d4: fix pinctrl muxing
- btrfs: send: fix invalid path for unlink operations after parent
orphanization
- btrfs: clear defrag status of a root if starting transaction fails
- ext4: cleanup in-core orphan list if ext4_truncate() failed to get a
transaction handle
- ext4: fix kernel infoleak via ext4_extent_header
- ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
- ext4: remove check for zero nr_to_scan in ext4_es_scan()
- ext4: fix avefreec in find_group_orlov
- ext4: use ext4_grp_locked_error in mb_find_extent
- can: gw: synchronize rcu operations before removing gw job entry
- can: peak_pciefd: pucan_handle_status(): fix a potential starvation issue
in
TX path
- SUNRPC: Fix the batch tasks count wraparound.
- SUNRPC: Should wake up the privileged task firstly.
- s390/cio: dont call css_wait_for_slow_path() inside a lock
- rtc: stm32: Fix unbalanced clk_disable_unprepare() on probe error path
- iio: ltr501: mark register holding upper 8 bits of ALS_DATA{0,1} and
PS_DATA
as volatile, too
- iio: ltr501: ltr559: fix initialization of LTR501_ALS_CONTR
- iio: ltr501: ltr501_read_ps(): add missing endianness conversion
- serial: sh-sci: Stop dmaengine transfer in sci_stop_tx()
- serial_cs: Add Option International GSM-Ready 56K/ISDN modem
- serial_cs: remove wrong GLOBETROTTER.cis entry
- ath9k: Fix kernel NULL pointer dereference during ath_reset_internal()
- ssb: sdio: Don't overwrite const buffer if block_write fails
- rsi: Assign beacon rate settings to the correct rate_info descriptor field
- seq_buf: Make trace_seq_putmem_hex() support data longer than 8
- fuse: check connected before queueing on fpq->io
- spi: Make of_register_spi_device also set the fwnode
- spi: spi-loopback-test: Fix 'tx_buf' might be 'rx_buf'
- spi: spi-topcliff-pch: Fix potential double free in
pch_spi_process_messages()
- spi: omap-100k: Fix the length judgment problem
- crypto: nx - add missing MODULE_DEVICE_TABLE
- media: cpia2: fix memory leak in cpia2_usb_probe
- media: cobalt: fix race condition in setting HPD
- media: pvrusb2: fix warning in pvr2_i2c_core_done
- crypto: qat - check return code of qat_hal_rd_rel_reg()
- crypto: qat - remove unused macro in FW loader
- media: em28xx: Fix possible memory leak of em28xx struct
- media: v4l2-core: Avoid the dangling pointer in v4l2_fh_release
- media: bt8xx: Fix a missing check bug in bt878_probe
- media: st-hva: Fix potential NULL pointer dereferences
- media: dvd_usb: memory leak in cinergyt2_fe_attach
- mmc: via-sdmmc: add a check against NULL pointer dereference
- crypto: shash - avoid comparing pointers to exported functions under CFI
- media: dvb_net: avoid speculation from net slot
- media: siano: fix device register error path
- btrfs: fix error handling in __btrfs_update_delayed_inode
- btrfs: abort transaction if
[Kernel-packages] [Bug 1942092] Re: linux-azure: main(): sched_setscheduler(): Operation not permitted
This bug was fixed in the package linux-azure-5.4 - 5.4.0-1058.60~18.04.1 --- linux-azure-5.4 (5.4.0-1058.60~18.04.1) bionic; urgency=medium * bionic/linux-azure-5.4: 5.4.0-1058.60~18.04.1 -proposed tracker (LP: #1942138) [ Ubuntu: 5.4.0-1058.60 ] * focal/linux-azure: 5.4.0-1058.60 -proposed tracker (LP: #1942117) * linux-azure: main(): sched_setscheduler(): Operation not permitted (LP: #1942092) - Revert "UBUNTU: [Config] azure: CONFIG_RT_GROUP_SCHED=y" * focal/linux: 5.4.0-84.94 -proposed tracker (LP: #1941767) * Server boot failure after adding checks for ACPI IRQ override (LP: #1941657) - Revert "ACPI: resources: Add checks for ACPI IRQ override" linux-azure-5.4 (5.4.0-1057.59~18.04.1) bionic; urgency=medium * bionic/linux-azure-5.4: 5.4.0-1057.59~18.04.1 -proposed tracker (LP: #1939774) [ Ubuntu: 5.4.0-1057.59 ] * focal/linux-azure: 5.4.0-1057.59 -proposed tracker (LP: #1939775) * Focal update: v5.4.129 upstream stable release (LP: #1936242) - [Config] enable CONFIG_SYSTEM_REVOCATION_LIST * linux-azure Enable CONFIG_RT_GROUP_SCHED (LP: #1939024) - [Config] azure: CONFIG_RT_GROUP_SCHED=y * Sync to SGX 1.33.2 (LP: #1936240) - SAUCE: ubuntu/sgx: backport fixes to 1.33 - SAUCE: ubuntu/sgx: missing synchronize_srcu call before cleanup - SAUCE: ubuntu/sgx: fix a synchronization issue for mmput - SAUCE: ubuntu/sgx: look for exported symbols in Makefile - SAUCE: ubuntu/sgx: hardening compiler options - SAUCE: ubuntu/sgx: Fix signed integer overflow on shift - SAUCE: ubuntu/sgx: move use space header - SAUCE: ubuntu/sgx: Version 1.33.2 * focal/linux: 5.4.0-83.93 -proposed tracker (LP: #1940159) * fails to launch linux L2 guests on AMD (LP: #1940134) // CVE-2021-3653 - KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl (CVE-2021-3653) * fails to launch linux L2 guests on AMD (LP: #1940134) - SAUCE: Revert "UBUNTU: SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl" * focal/linux: 5.4.0-82.92 -proposed tracker (LP: #1939799) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.08.16) * CVE-2021-3656 - SAUCE: KVM: nSVM: always intercept VMLOAD/VMSAVE when nested * CVE-2021-3653 - SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl * [regression] USB device is not detected during boot (LP: #1939638) - SAUCE: Revert "usb: core: reduce power-on-good delay time of root hub" * dev_forward_skb: do not scrub skb mark within the same name space (LP: #1935040) - dev_forward_skb: do not scrub skb mark within the same name space * XPS 9510 (TGL) Screen Brightness could not be changed (LP: #1933566) - SAUCE: drm/i915: Force DPCD backlight mode for Dell XPS 9510(TGL) * Acer Aspire 5 sound driver issues (LP: #1930188) - ALSA: hda/realtek: headphone and mic don't work on an Acer laptop * Sony Dualshock 4 usb dongle crashes the whole system (LP: #1935846) - HID: sony: Workaround for DS4 dongle hotplug kernel crash. * [21.10 FEAT] KVM: Provide a secure guest indication (LP: #1933173) - s390/uv: add prot virt guest/host indication files - s390/uv: fix prot virt host indication compilation * Skip rtcpie test in kselftests/timers if the default RTC device does not exist (LP: #1937991) - selftests: timers: rtcpie: skip test if default RTC device does not exist * Focal update: v5.4.133 upstream stable release (LP: #1938713) - drm/mxsfb: Don't select DRM_KMS_FB_HELPER - drm/zte: Don't select DRM_KMS_FB_HELPER - drm/amd/amdgpu/sriov disable all ip hw status by default - drm/vc4: fix argument ordering in vc4_crtc_get_margins() - net: pch_gbe: Use proper accessors to BE data in pch_ptp_match() - drm/amd/display: fix use_max_lb flag for 420 pixel formats - hugetlb: clear huge pte during flush function on mips platform - atm: iphase: fix possible use-after-free in ia_module_exit() - mISDN: fix possible use-after-free in HFC_cleanup() - atm: nicstar: Fix possible use-after-free in nicstar_cleanup() - net: Treat __napi_schedule_irqoff() as __napi_schedule() on PREEMPT_RT - drm/mediatek: Fix PM reference leak in mtk_crtc_ddp_hw_init() - reiserfs: add check for invalid 1st journal block - drm/virtio: Fix double free on probe failure - drm/sched: Avoid data corruptions - udf: Fix NULL pointer dereference in udf_symlink function - e100: handle eeprom as little endian - igb: handle vlan types with checker enabled - drm/bridge: cdns: Fix PM reference leak in cdns_dsi_transfer() - clk: renesas: r8a77995: Add ZA2 clock - clk: tegra: Ensure that PLLU configuration is applied properly - ipv6: use prandom_u32() for ID generation - RDMA/cxgb4: Fix missing error code in create_qp() - dm space maps: don't reset space map allocation cursor when committing -
[Kernel-packages] [Bug 1940488] Re: dell300x: rsi wifi and bluetooth crash after suspend and resume
This bug was fixed in the package linux-dell300x - 4.15.0-1027.32
---
linux-dell300x (4.15.0-1027.32) bionic; urgency=medium
* bionic/linux-dell300x: 4.15.0-1027.32 -proposed tracker (LP:
#1939817)
* dell300x: rsi wifi and bluetooth crash after suspend and resume
(LP: #1940488)
- Revert "rsi: Use resume_noirq for SDIO"
[ Ubuntu: 4.15.0-156.163 ]
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails to launch linux L2 guests on AMD (LP: #1940134) // CVE-2021-3653
- KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
(CVE-2021-3653)
* fails to launch linux L2 guests on AMD (LP: #1940134)
- SAUCE: Revert "UBUNTU: SAUCE: KVM: nSVM: avoid picking up unsupported bits
from L2 in int_ctl"
[ Ubuntu: 4.15.0-155.162 ]
* bionic/linux: 4.15.0-155.162 -proposed tracker (LP: #1939833)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.08.16)
* CVE-2021-3656
- SAUCE: KVM: nSVM: always intercept VMLOAD/VMSAVE when nested
* CVE-2021-3653
- SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
* dev_forward_skb: do not scrub skb mark within the same name space
(LP: #1935040)
- dev_forward_skb: do not scrub skb mark within the same name space
* 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
(LP: #1890848)
- apparmor: fix ptrace read check
* Bionic update: upstream stable patchset 2021-08-03 (LP: #1938824)
- ALSA: usb-audio: fix rate on Ozone Z90 USB headset
- media: dvb-usb: fix wrong definition
- Input: usbtouchscreen - fix control-request directions
- net: can: ems_usb: fix use-after-free in ems_usb_disconnect()
- usb: gadget: eem: fix echo command packet response issue
- USB: cdc-acm: blacklist Heimann USB Appset device
- ntfs: fix validity check for file name attribute
- iov_iter_fault_in_readable() should do nothing in xarray case
- Input: joydev - prevent use of not validated data in JSIOCSBTNMAP ioctl
- ARM: dts: at91: sama5d4: fix pinctrl muxing
- btrfs: send: fix invalid path for unlink operations after parent
orphanization
- btrfs: clear defrag status of a root if starting transaction fails
- ext4: cleanup in-core orphan list if ext4_truncate() failed to get a
transaction handle
- ext4: fix kernel infoleak via ext4_extent_header
- ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
- ext4: remove check for zero nr_to_scan in ext4_es_scan()
- ext4: fix avefreec in find_group_orlov
- ext4: use ext4_grp_locked_error in mb_find_extent
- can: gw: synchronize rcu operations before removing gw job entry
- can: peak_pciefd: pucan_handle_status(): fix a potential starvation issue
in
TX path
- SUNRPC: Fix the batch tasks count wraparound.
- SUNRPC: Should wake up the privileged task firstly.
- s390/cio: dont call css_wait_for_slow_path() inside a lock
- rtc: stm32: Fix unbalanced clk_disable_unprepare() on probe error path
- iio: ltr501: mark register holding upper 8 bits of ALS_DATA{0,1} and
PS_DATA
as volatile, too
- iio: ltr501: ltr559: fix initialization of LTR501_ALS_CONTR
- iio: ltr501: ltr501_read_ps(): add missing endianness conversion
- serial: sh-sci: Stop dmaengine transfer in sci_stop_tx()
- serial_cs: Add Option International GSM-Ready 56K/ISDN modem
- serial_cs: remove wrong GLOBETROTTER.cis entry
- ath9k: Fix kernel NULL pointer dereference during ath_reset_internal()
- ssb: sdio: Don't overwrite const buffer if block_write fails
- rsi: Assign beacon rate settings to the correct rate_info descriptor field
- seq_buf: Make trace_seq_putmem_hex() support data longer than 8
- fuse: check connected before queueing on fpq->io
- spi: Make of_register_spi_device also set the fwnode
- spi: spi-loopback-test: Fix 'tx_buf' might be 'rx_buf'
- spi: spi-topcliff-pch: Fix potential double free in
pch_spi_process_messages()
- spi: omap-100k: Fix the length judgment problem
- crypto: nx - add missing MODULE_DEVICE_TABLE
- media: cpia2: fix memory leak in cpia2_usb_probe
- media: cobalt: fix race condition in setting HPD
- media: pvrusb2: fix warning in pvr2_i2c_core_done
- crypto: qat - check return code of qat_hal_rd_rel_reg()
- crypto: qat - remove unused macro in FW loader
- media: em28xx: Fix possible memory leak of em28xx struct
- media: v4l2-core: Avoid the dangling pointer in v4l2_fh_release
- media: bt8xx: Fix a missing check bug in bt878_probe
- media: st-hva: Fix potential NULL pointer dereferences
- media: dvd_usb: memory leak in cinergyt2_fe_attach
- mmc: via-sdmmc: add a check against NULL pointer dereference
- crypto: shash - avoid comparing pointers to
[Kernel-packages] [Bug 1940134] Re: fails to launch linux L2 guests on AMD
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails to launch linux L2 guests on AMD (LP: #1940134) // CVE-2021-3653
- KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
(CVE-2021-3653)
* fails to launch linux L2 guests on AMD (LP: #1940134)
- SAUCE: Revert "UBUNTU: SAUCE: KVM: nSVM: avoid picking up unsupported bits
from L2 in int_ctl"
linux (4.15.0-155.162) bionic; urgency=medium
* bionic/linux: 4.15.0-155.162 -proposed tracker (LP: #1939833)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.08.16)
* CVE-2021-3656
- SAUCE: KVM: nSVM: always intercept VMLOAD/VMSAVE when nested
* CVE-2021-3653
- SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
* dev_forward_skb: do not scrub skb mark within the same name space
(LP: #1935040)
- dev_forward_skb: do not scrub skb mark within the same name space
* 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
(LP: #1890848)
- apparmor: fix ptrace read check
* Bionic update: upstream stable patchset 2021-08-03 (LP: #1938824)
- ALSA: usb-audio: fix rate on Ozone Z90 USB headset
- media: dvb-usb: fix wrong definition
- Input: usbtouchscreen - fix control-request directions
- net: can: ems_usb: fix use-after-free in ems_usb_disconnect()
- usb: gadget: eem: fix echo command packet response issue
- USB: cdc-acm: blacklist Heimann USB Appset device
- ntfs: fix validity check for file name attribute
- iov_iter_fault_in_readable() should do nothing in xarray case
- Input: joydev - prevent use of not validated data in JSIOCSBTNMAP ioctl
- ARM: dts: at91: sama5d4: fix pinctrl muxing
- btrfs: send: fix invalid path for unlink operations after parent
orphanization
- btrfs: clear defrag status of a root if starting transaction fails
- ext4: cleanup in-core orphan list if ext4_truncate() failed to get a
transaction handle
- ext4: fix kernel infoleak via ext4_extent_header
- ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
- ext4: remove check for zero nr_to_scan in ext4_es_scan()
- ext4: fix avefreec in find_group_orlov
- ext4: use ext4_grp_locked_error in mb_find_extent
- can: gw: synchronize rcu operations before removing gw job entry
- can: peak_pciefd: pucan_handle_status(): fix a potential starvation issue
in
TX path
- SUNRPC: Fix the batch tasks count wraparound.
- SUNRPC: Should wake up the privileged task firstly.
- s390/cio: dont call css_wait_for_slow_path() inside a lock
- rtc: stm32: Fix unbalanced clk_disable_unprepare() on probe error path
- iio: ltr501: mark register holding upper 8 bits of ALS_DATA{0,1} and
PS_DATA
as volatile, too
- iio: ltr501: ltr559: fix initialization of LTR501_ALS_CONTR
- iio: ltr501: ltr501_read_ps(): add missing endianness conversion
- serial: sh-sci: Stop dmaengine transfer in sci_stop_tx()
- serial_cs: Add Option International GSM-Ready 56K/ISDN modem
- serial_cs: remove wrong GLOBETROTTER.cis entry
- ath9k: Fix kernel NULL pointer dereference during ath_reset_internal()
- ssb: sdio: Don't overwrite const buffer if block_write fails
- rsi: Assign beacon rate settings to the correct rate_info descriptor field
- seq_buf: Make trace_seq_putmem_hex() support data longer than 8
- fuse: check connected before queueing on fpq->io
- spi: Make of_register_spi_device also set the fwnode
- spi: spi-loopback-test: Fix 'tx_buf' might be 'rx_buf'
- spi: spi-topcliff-pch: Fix potential double free in
pch_spi_process_messages()
- spi: omap-100k: Fix the length judgment problem
- crypto: nx - add missing MODULE_DEVICE_TABLE
- media: cpia2: fix memory leak in cpia2_usb_probe
- media: cobalt: fix race condition in setting HPD
- media: pvrusb2: fix warning in pvr2_i2c_core_done
- crypto: qat - check return code of qat_hal_rd_rel_reg()
- crypto: qat - remove unused macro in FW loader
- media: em28xx: Fix possible memory leak of em28xx struct
- media: v4l2-core: Avoid the dangling pointer in v4l2_fh_release
- media: bt8xx: Fix a missing check bug in bt878_probe
- media: st-hva: Fix potential NULL pointer dereferences
- media: dvd_usb: memory leak in cinergyt2_fe_attach
- mmc: via-sdmmc: add a check against NULL pointer dereference
- crypto: shash - avoid comparing pointers to exported functions under CFI
- media: dvb_net: avoid speculation from net slot
- media: siano: fix device register error path
- btrfs: fix error handling in __btrfs_update_delayed_inode
- btrfs: abort transaction if
