[Kernel-packages] [Bug 2044657] Re: zfs block cloning file system corruption
** Patch added: "Patch from OpenZFS master branch" https://github.com/openzfs/zfs/commit/30d581121bb122c90959658e7b28b1672d342897.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.2 package in Ubuntu: New Status in linux-hwe-6.5 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+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 2044657] Re: zfs block cloning file system corruption
** Patch added: "Patch for OpenZFS 2.1" https://github.com/openzfs/zfs/commit/e49b10f57c770a03217e6537252c90550aadb538.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.2 package in Ubuntu: New Status in linux-hwe-6.5 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+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 2044657] Re: zfs block cloning file system corruption
Apparently the bug was not in block cloning, it was just exacerbated by it. The issue affects older versions of ZFS as well, including 2.1.x. That is why the upstream OpenZFS project has backported the patch to 2.1.x (Chad linked the PR above). Thus, linux-hwe-6.2 is affected. ** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.2 package in Ubuntu: New Status in linux-hwe-6.5 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+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 1828380] Re: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes failed on D i386
Kernel EOL and we don't have this issue recorded in our hint database. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** 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/1828380 Title: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes failed on D i386 Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Won't Fix Bug description: Test failed with: btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43 Test log: * Command: BINDIR=/home/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes /home /ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes/ubuntu_btrfs_kerne l_fixes.sh /home/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes/fi xes/f88ba6a2a44ee98e8d59654463dc157bb6d13c43.sh 2>&1 Exit status: 1 Duration: 11.0287649632 stdout: Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 fix f88ba6a2a44ee98e8d59654463dc157bb6d13c43 Btrfs: skip submitting barrier for missing device I got an error on v3.13: BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO failure (errors while submitting device barriers.) how to reproduce: > mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2 > wipefs -a /dev/sdf2 > mount -o degraded /dev/sdf1 /mnt > btrfs balance start -f -sconvert=single -mconvert=single -dconvert=single /mnt The reason of the error is that barrier_all_devices() failed to submit barrier to the missing device. However it is clear that we cannot do anything on missing device, and also it is not necessary to care chunks on the missing device. This patch stops sending/waiting barrier if device is missing. btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43 FAIL: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 (ret=1) Syslog: kernel: [ 1531.598180] Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 kernel: [ 1531.822544] BTRFS: device fsid 28683721-4c7a-4922-a753-e61ca95c0726 devid 1 transid 5 /dev/loop2 kernel: [ 1531.917840] BTRFS: device fsid 28683721-4c7a-4922-a753-e61ca95c0726 devid 2 transid 5 /dev/loop3 kernel: [ 1532.314274] BTRFS info (device loop2): allowing degraded mounts kernel: [ 1532.314276] BTRFS info (device loop2): disk space caching is enabled kernel: [ 1532.314277] BTRFS info (device loop2): has skinny extents kernel: [ 1532.314278] BTRFS info (device loop2): flagging fs with big metadata feature kernel: [ 1532.315442] BTRFS warning (device loop2): devid 2 uuid b6fe3a66-6a6d-42fe-9b57-5373a2f8d014 is missing kernel: [ 1532.315882] BTRFS info (device loop2): checking UUID tree kernel: [ 1532.319154] BTRFS error (device loop2): balance: invalid convert data profile single systemd[965]: tmp-mnt\x2df88ba6a2a44ee98e8d59654463dc157bb6d13c43.mount: Succeeded. systemd[1]: tmp-mnt\x2df88ba6a2a44ee98e8d59654463dc157bb6d13c43.mount: Succeeded. kernel: [ 1532.524774] Test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 returned 0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:31 seq crw-rw 1 root audio 116, 33 May 9 09:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Thu May 9 09:33:18 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Error: [Errno 2] No such
[Kernel-packages] [Bug 1845858] Re: pmtu.sh in net from ubuntu_kernel_selftests failed on B-hwe-edge 5.3
Kernel EOL and we don't have this issue recorded in our hint database. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Eoan) Status: New => Won't Fix ** Changed in: linux-hwe (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe (Ubuntu Eoan) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1845858 Title: pmtu.sh in net from ubuntu_kernel_selftests failed on B-hwe-edge 5.3 Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in linux source package in Disco: Won't Fix Status in linux-hwe source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-hwe source package in Eoan: Won't Fix Bug description: Issue found on B-hwe 5.3 amd64, test failed with: # TEST: ipv6: list and flush cached exceptions [FAIL] Complete test log: # selftests: net: pmtu.sh # TEST: ipv4: PMTU exceptions [ OK ] # TEST: ipv6: PMTU exceptions [ OK ] # vxlan4 not supported # TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] # vxlan4 not supported # TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] # TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] # TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] # geneve4 not supported # TEST: IPv4 over geneve4: PMTU exceptions [SKIP] # geneve4 not supported # TEST: IPv6 over geneve4: PMTU exceptions [SKIP] # TEST: IPv4 over geneve6: PMTU exceptions [ OK ] # TEST: IPv6 over geneve6: PMTU exceptions [ OK ] # TEST: IPv4 over fou4: PMTU exceptions [ OK ] # TEST: IPv6 over fou4: PMTU exceptions [ OK ] # TEST: IPv4 over fou6: PMTU exceptions [ OK ] # TEST: IPv6 over fou6: PMTU exceptions [ OK ] # TEST: IPv4 over gue4: PMTU exceptions [ OK ] # TEST: IPv6 over gue4: PMTU exceptions [ OK ] # TEST: IPv4 over gue6: PMTU exceptions [ OK ] # TEST: IPv6 over gue6: PMTU exceptions [ OK ] # TEST: vti6: PMTU exceptions [ OK ] # TEST: vti4: PMTU exceptions [ OK ] # TEST: vti4: default MTU assignment [ OK ] # TEST: vti6: default MTU assignment [ OK ] # TEST: vti4: MTU setting on link creation [ OK ] # TEST: vti6: MTU setting on link creation [ OK ] # TEST: vti6: MTU changes on link changes [ OK ] # vxlan4 not supported # TEST: ipv4: cleanup of cached exceptions [SKIP] # TEST: ipv6: cleanup of cached exceptions [ OK ] # TEST: ipv4: list and flush cached exceptions [ OK ] # TEST: ipv6: list and flush cached exceptions [FAIL] # can't list cached exceptions not ok 16 selftests: net: pmtu.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845858/+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 1827845] Re: ubuntu_bpf_jit report result in D on s390x is a bit confusing
Kernel EOL and we don't have this issue recorded in our hint database. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- 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/1827845 Title: ubuntu_bpf_jit report result in D on s390x is a bit confusing Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: The only failure is the test_bpf module load failure, and there are 378 tests (0-377) But the result shows "Summary: 377 PASSED, 1 FAILED" Module test_bpf load failure [ 873.481738] test_bpf: #0 TAX jited:1 36 34 35 PASS [ 873.481888] test_bpf: #1 TXA jited:1 17 17 17 PASS [ 873.481960] test_bpf: #2 ADD_SUB_MUL_K jited:1 18 PASS [ 873.481997] test_bpf: #3 DIV_MOD_KX jited:1 35 PASS [ 873.482054] test_bpf: #4 AND_OR_LSH_K jited:1 16 16 PASS [ 873.482106] test_bpf: #5 LD_IMM_0 jited:1 16 PASS [ 873.482141] test_bpf: #6 LD_IND jited:1 48 47 47 PASS [ 873.482305] test_bpf: #7 LD_ABS jited:1 49 49 49 PASS [ 873.482472] test_bpf: #8 LD_ABS_LL jited:1 72 72 PASS [ 873.482637] test_bpf: #9 LD_IND_LL jited:1 49 49 49 PASS [ 873.482804] test_bpf: #10 LD_ABS_NET jited:1 71 71 PASS [ 873.482966] test_bpf: #11 LD_IND_NET jited:1 48 48 48 PASS [ 873.483132] test_bpf: #12 LD_PKTTYPE jited:1 18 18 PASS [ 873.483189] test_bpf: #13 LD_MARK jited:1 18 18 PASS [ 873.483242] test_bpf: #14 LD_RXHASH jited:1 18 18 PASS [ 873.483295] test_bpf: #15 LD_QUEUE jited:1 18 18 PASS [ 873.483347] test_bpf: #16 LD_PROTOCOL jited:1 20 20 PASS [ 873.483410] test_bpf: #17 LD_VLAN_TAG jited:1 18 18 PASS [ 873.483463] test_bpf: #18 LD_VLAN_TAG_PRESENT jited:1 17 17 PASS [ 873.483515] test_bpf: #19 LD_IFINDEX jited:1 17 17 PASS [ 873.483567] test_bpf: #20 LD_HATYPE jited:1 17 17 PASS [ 873.483618] test_bpf: #21 LD_CPU jited:1 52 52 PASS [ 873.483742] test_bpf: #22 LD_NLATTR jited:1 34 44 PASS [ 873.483839] test_bpf: #23 LD_NLATTR_NEST jited:1 155 236 PASS [ 873.484254] test_bpf: #24 LD_PAYLOAD_OFF jited:1 295 325 PASS [ 873.484894] test_bpf: #25 LD_ANC_XOR jited:1 16 16 PASS [ 873.484945] test_bpf: #26 SPILL_FILL jited:1 20 20 20 PASS [ 873.485026] test_bpf: #27 JEQ jited:1 47 18 18 PASS [ 873.485131] test_bpf: #28 JGT jited:1 47 18 18 PASS [ 873.485236] test_bpf: #29 JGE (jt 0), test 1 jited:1 46 18 18 PASS [ 873.485339] test_bpf: #30 JGE (jt 0), test 2 jited:1 18 18 18 PASS [ 873.485414] test_bpf: #31 JGE jited:1 34 35 35 PASS [ 873.485540] test_bpf: #32 JSET jited:1 37 36 39 PASS [ 873.485678] test_bpf: #33 tcpdump port 22 jited:1 47 52 57 PASS [ 873.485871] test_bpf: #34 tcpdump complex jited:1 47 50 74 PASS [ 873.486082] test_bpf: #35 RET_A jited:1 16 16 PASS [ 873.486132] test_bpf: #36 INT: ADD trivial jited:1 16 PASS [ 873.486165] test_bpf: #37 INT: MUL_X jited:1 16 PASS [ 873.486197] test_bpf: #38 INT: MUL_X2 jited:1 17 PASS [ 873.486230] test_bpf: #39 INT: MUL32_X jited:1 17 PASS [ 873.486263] test_bpf: #40 INT: ADD 64-bit jited:1 36 PASS [ 873.486331] test_bpf: #41 INT: ADD 32-bit jited:1 50 PASS [ 873.486411] test_bpf: #42 INT: SUB jited:1 33 PASS [ 873.486472] test_bpf: #43 INT: XOR jited:1 22 PASS [ 873.486516] test_bpf: #44 INT: MUL jited:1 71 PASS [ 873.486609] test_bpf: #45 MOV REG64 jited:1 19 PASS [ 873.486647] test_bpf: #46 MOV REG32 jited:1 19 PASS [ 873.486685] test_bpf: #47 LD IMM64 jited:1 20 PASS [ 873.486725] test_bpf: #48 INT: ALU MIX jited:1 24 PASS [ 873.486788] test_bpf: #49 INT: shifts by register jited:1 19 PASS [ 873.486827] test_bpf: #50 check: missing ret PASS [ 873.486834] test_bpf: #51 check: div_k_0 PASS [ 873.486840] test_bpf: #52 check: unknown insn PASS [ 873.486846] test_bpf: #53 check: out of range spill/fill PASS [ 873.486851] test_bpf: #54 JUMPS + HOLES jited:1 21 PASS [ 873.486964] test_bpf: #55 check: RET X PASS [ 873.486970] test_bpf: #56 check: LDX + RET X PASS [ 873.486976] test_bpf: #57 M[]: alt STX + LDX jited:1 57 PASS [ 873.487065] test_bpf: #58 M[]: full STX + full LDX jited:1 27 PASS [ 873.487122] test_bpf: #59 check: SKF_AD_MAX PASS [ 873.487128] test_bpf: #60 LD [SKF_AD_OFF-1] jited:1 48 PASS [ 873.487196] test_bpf: #61 load 64-bit immediate jited:1 17 PASS [ 873.487231] test_bpf: #62 ALU_MOV_X: dst = 2 jited:1 16 PASS [ 873.487265] test_bpf: #63 ALU_MOV_X: dst = 4294967295 jited:1 16 PASS [ 873.487298] test_bpf: #64 ALU64_MOV_X: dst = 2 jited:1 16 PASS [ 873.487331] test_bpf: #65 ALU64_MOV_X: dst = 4294967295 jited:1 16 PASS [ 873.487364] test_bpf: #66 ALU_MOV_K: dst = 2 jited:1 16 PASS [ 873.487397] test_bpf: #67 ALU_MOV_K: dst = 4294967295 jited:1 16 PASS [ 873.487430] test_bpf: #68 ALU_MOV_K:
[Kernel-packages] [Bug 1837365] Re: ubuntu_kvm_smoke_test failed on Intel KVM node with D-KVM kernel
Kernel EOL and we don't have this issue recorded in our hint database.
Closing this bug.
** Changed in: ubuntu-kernel-tests
Status: New => Won't Fix
** Changed in: linux-kvm (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1837365
Title:
ubuntu_kvm_smoke_test failed on Intel KVM node with D-KVM kernel
Status in ubuntu-kernel-tests:
Won't Fix
Status in linux-kvm package in Ubuntu:
Won't Fix
Bug description:
The KVM can be started in our KVM node (zeppo) with the D-KVM kernel.
But it looks like that we can't run it on the Intel Cloud KVM nodes
(automation-vm8)
Test failed with:
+ uvt-kvm wait bjf-test --insecure --ssh-private-key-file
/home/ubuntu/.ssh/id_rsa
uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:67:78:dc.
++ uvt-kvm ip bjf-test
uvt-kvm: error: no IP address found for libvirt machine 'bjf-test'.
sudo -u ubuntu /home/ubuntu/autotest/client/tests/ubuntu_kvm_smoke_test
/the-test amd64
Exit status: 1
Duration: 354.469812155
stdout:
INFO: /dev/kvm exists
KVM acceleration can be used
Generating public/private rsa key pair.
Your identification has been saved in /home/ubuntu/.ssh/id_rsa.
Your public key has been saved in /home/ubuntu/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:hXBMvlRcr+MMJACF2ymdbkl+gxISLagx0ZUSlOYR/+E ubuntu@automation-vm8
The key's randomart image is:
+---[RSA 2048]+
|.=+*o=+oo |
|+ O.+ =.o. . |
|.= =.+.o= o . |
|. o +o*o = . |
| . *EoS . o |
| . * o + . |
| o . . o |
| |
| |
+[SHA256]-+
** ERROR: The codename returned from lsb_release -c was ( ) and we were
expecting 'disco'
stderr:
+ SUT=bjf-test
+ SSH_KEY=/home/ubuntu/.ssh/id_rsa
+ SSH_OPTIONS='-o StrictHostKeyChecking=no -o
UserKnownHostsFile=/dev/null -o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
++ lsb_release -c
++ awk '{print$2}'
+ DISTRO=disco
+ ARCHITECTURE=amd64
+ '[' -z amd64 ']'
+ kvm-ok
+ '[' 0 '!=' 0 ']'
+ '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
+ ssh-keygen -f /home/ubuntu/.ssh/id_rsa -t rsa -N ''
+ '[' amd64 = ppc64el ']'
++ grep -P 'disco.*amd64'
++ uvt-simplestreams-libvirt query
+ image=
+ '[' -z '' ']'
+ uvt-simplestreams-libvirt sync --source
http://cloud-images.ubuntu.com/daily release=disco arch=amd64
+ uvt-kvm create bjf-test release=disco arch=amd64
+ uvt-kvm wait bjf-test --insecure --ssh-private-key-file
/home/ubuntu/.ssh/id_rsa
uvt-kvm: error: timed out waiting for dnsmasq lease for
52:54:00:67:78:dc.
++ uvt-kvm ip bjf-test
uvt-kvm: error: no IP address found for libvirt machine 'bjf-test'.
+ ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa ubuntu@ uname -a
+++ uvt-kvm ip bjf-test
++ cut '-d ' -f 2
uvt-kvm: error: no IP address found for libvirt machine 'bjf-test'.
++ ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa ubuntu@ lsb_release -c
+ RESULT=
+ '[' '' '!=' disco ']'
+ echo '** ERROR: The codename returned from lsb_release -c was (' ')
and we were expecting '\''disco'\'''
+ exit 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837365/+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 1930100] Re: selftests/net/bpf - Failure in building bpf program on G/RISC-V (kernel 5.8)
Kernel EOL and we don't have this issue recorded in our hint database. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Won't Fix -- 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/1930100 Title: selftests/net/bpf - Failure in building bpf program on G/RISC-V (kernel 5.8) Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Groovy: Won't Fix Bug description: I found the following failure in G/RISC-V, cycle sru-20210510 : 21:07:11 ERROR| [stderr] progs/test_vmlinux.c:24:18: error: use of undeclared identifier '__NR_nanosleep' 21:07:11 ERROR| [stderr] if (args->id != __NR_nanosleep) 21:07:11 ERROR| [stderr] ^ [...] 21:07:11 ERROR| [stderr] progs/test_vmlinux.c:60:12: error: use of undeclared identifier '__NR_nanosleep' 21:07:11 ERROR| [stderr] if (id != __NR_nanosleep) 21:07:11 ERROR| [stderr] ^ 21:07:11 ERROR| [stderr] progs/test_vmlinux.c:63:15: warning: implicit declaration of function 'PT_REGS_PARM1_CORE' is invalid in C99 [-Wimplicit-function-declaration] 21:07:11 ERROR| [stderr] ts = (void *)PT_REGS_PARM1_CORE(regs); 21:07:11 ERROR| [stderr] ^ [...] /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_tracing.h:298:29: note: expanded from macro '___bpf_concat' 21:07:12 ERROR| [stderr] #define ___bpf_concat(a, b) a ## b 21:07:12 ERROR| [stderr] ^ 21:07:12 ERROR| [stderr] :28:1: note: expanded from here 21:07:12 ERROR| [stderr] ___bpf_kprobe_args3 21:07:12 ERROR| [stderr] ^ 21:07:12 ERROR| [stderr] /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_tracing.h:359:29: note: expanded from macro '___bpf_kprobe_args3' 21:07:12 ERROR| [stderr] ___bpf_kprobe_args2(args), (void *)PT_REGS_PARM3(ctx) 21:07:12 ERROR| [stderr] ^~ 21:07:12 ERROR| [stderr] 10 warnings and 3 errors generated. 21:07:12 ERROR| [stderr] llc: error: llc: :1:1: error: expected top-level entity 21:07:12 ERROR| [stderr] BPF obj compilation failed 21:07:12 ERROR| [stderr] ^ 21:07:12 ERROR| [stderr] make[1]: *** [Makefile:376: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/test_vmlinux.o] Error 1 21:07:12 ERROR| [stderr] make: *** [Makefile:159: all] Error 2 21:07:12 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py", line 239, in run_once utils.system(cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=2, Command returned non-zero exit status * Command: make -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= KDIR=/usr/src/linux-headers-5.8.0-26-generic Exit status: 2 See more on the attachment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1930100/+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 2041006] Re: WARNING CPU: 2 PID: 3763 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_hwseq.c:1197 dcn32_calculate_dccg_k1_k2_values
The error going into sleep as well as the error coming out of sleep are now gone with the latest linux-hwe-6.2 update.Thank you. uname -a Linux Tardis-2 6.2.0-37-generic #38~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 2 18:01:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux I'm seeing this error now once going into sleep and once coming out no spam in the log. Other than an longer than normal delayed blanking of the screen no apparent issues with it. IE not seeing any of the issues reported in the bug report below. 11/28/23 10:35 PM kernel [drm:dcn20_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc! I found this bug report so it's already fixed in the future can upload the latest kernel log if needed. https://gitlab.freedesktop.org/drm/amd/-/issues/2581 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2581 https://gitlab.freedesktop.org/drm/amd/-/issues/2581 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2041006 Title: WARNING CPU: 2 PID: 3763 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_hwseq.c:1197 dcn32_calculate_dccg_k1_k2_values Status in linux package in Ubuntu: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux-hwe-6.2 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-hwe-6.2 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-hwe-6.2 source package in Noble: Invalid Bug description: darkfoss@Tardis-2:~$ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 Clean install just apt-get update and apt-get dist-upgrade During the installation process when intramfs is run the following error is being generated: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module amdgpu darkfoss@Tardis-2:~$ apt-cache policy linux-firmware linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.21 Candidate: 20220329.git681281e4-0ubuntu3.21 Version table: *** 20220329.git681281e4-0ubuntu3.21 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 20220329.git681281e4-0ubuntu3.14 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 20220329.git681281e4-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages All of the above do not work even though the driver is installed correctly. The above error prevents radeonsi from loading. The good news is when I installed Both 23.04 and 23.10 they had 1 working firmware each they are: From Lunar Lobster 20230323.gitbcdcfbcf-0ubuntu1.2 security (main) 2023-07-06 Publishing details Created on 2023-07-06 by Andy Whitcroft Published on 2023-07-06 Changelog linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) lunar; urgency=medium * rtl8761b usb bluetooth doesn't work following reboot until unplug/replug (LP: #1968604) - rtl_bt: Update RTL8761B BT UART firmware to 0x9DC6_D922 - rtl_bt: Update RTL8761B BT USB firmware to 0xDFC6_D922 -- Juerg Haefliger Mon, 05 Jun 2023 09:22:50 +0200 Available diffs diff from 20230323.gitbcdcfbcf-0ubuntu1.1 to 20230323.gitbcdcfbcf-0ubuntu1.2 (653 bytes) Builds [FULLYBUILT] amd64 Built packages linux-firmware Firmware for Linux kernel drivers Package files linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2.debian.tar.xz (3.4 MiB) linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2.dsc (2.0 KiB) linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2_all.deb (268.0 MiB) linux-firmware_20230323.gitbcdcfbcf.orig.tar.xz (254.0 MiB) From The Mantic Minotaur (current stable release) 20230919.git3672ccab-0ubuntu2.1 release (main) 2023-10-09 Publishing details Created on 2023-10-09 by Ubuntu Archive Auto-Sync Published on 2023-10-09 Changelog linux-firmware (20230919.git3672ccab-0ubuntu2.1) mantic; urgency=medium * /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 (LP: #2038546) - [Packaging] config: Don't exclude cypress fw link targets -- Juerg Haefliger Mon, 09 Oct 2023 16:16:20 +0200 Available diffs diff from 20230919.git3672ccab-0ubuntu2 to 20230919.git3672ccab-0ubuntu2.1 (992 bytes) Builds [FULLYBUILT] amd64
[Kernel-packages] [Bug 2045106] [NEW] package linux-intel-iotg-tools-common 5.15.0-1043.49 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf
Public bug reported: package linux-intel-iotg-tools-common 5.15.0-1043.49 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf- archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1/perf- buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf-daemon.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz usr/share/man/man1/perf-dlfilter.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-inject.1.gz usr/share/man/man1/perf-intel-pt.1.gz usr/share/man/man1/perf- iostat.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script- perl.1.gz usr/share/man/man1/perf-script-python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf-version.1.gz usr/share/man/man1/perf.1.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-89.99 ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-intel-iotg-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Nov 29 10:49:50 2023 DpkgTerminalLog: Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1045.51_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1045.51) over (5.15.0-1043.49) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1045.51_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-89.99 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-89.99 InstallationDate: Installed on 2023-10-28 (31 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, unpackaged RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-intel-iotg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2045106 Title: package linux-intel-iotg-tools-common 5.15.0-1043.49 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf- archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1/perf-buildid-cache.1.gz usr/share/man/man1/perf- buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf- daemon.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf- diff.1.gz usr/share/man/man1/perf-dlfilter.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf- ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf- inject.1.gz usr/share/man/man1/perf-intel-pt.1.gz usr/share/man/man1/perf-iostat.1.gz usr/share/man/man1/perf- kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf- script-python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf- top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf- version.1.gz usr/share/man/man1/perf.1.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-89.99 Status in linux-intel-iotg package in Ubuntu: New Bug description: package linux-intel-iotg-tools-common 5.15.0-1043.49 [modified: usr/share/man/man1/perf-annotate.1.gz
[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal
** Tags removed: verification-needed-focal-linux ** Tags added: verification-done-focal-linux -- 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/2043197 Title: USB bus error after upgrading to proposed kernel on lunar, jammy and focal Status in linux package in Ubuntu: Triaged Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: == SRU Justification == [Impact] USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel. [Fix] Use logarithmic encoding for the bMaxPacketSize0 value. [Test] With the patch applied, SuperSpeed devices can be enumerated across several reboots. [Where problems could occur] The switch case for Wireless USB (not USB WiFi dongle) was removed by the fix. I am not aware of the existence of any Wireless USB device. But if they do exist, this patch may the packet size encoding on them. == Original Bug Report == [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 16.0 dmi.bios.vendor: HP dmi.bios.version: S12 Ver. 02.16.00 dmi.board.name: 8810 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.23 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA: dmi.product.family: 103C_53307F HP ProOne dmi.product.name:
[Kernel-packages] [Bug 2025987] Re: 5.15.0-76: Qemu live migration regression due to PKRU leakage
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/2025987 Title: 5.15.0-76: Qemu live migration regression due to PKRU leakage Status in linux package in Ubuntu: Expired Status in qemu package in Ubuntu: Expired Bug description: I am trying to live migrate Qemu VMs between Amd Zen3 to Zen2 servers. What we expect: VMs continue to run after live-migrate What happened: VMs instantly get stuck after migration with 100% CPU usage. All Nodes are running Ubuntu 22.04. We have tested Kernel releases back to 5.15.0-70. Nodes running Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 : Zen2 -> Zen3 migration: OK Zen3 -> Zen2 migration: OK Nodes running Ubuntu 5.15.0-76.83-generic 5.15.99 : Zen2 -> Zen3 migration: OK Zen3 -> Zen2 migration: NOT OK Mixed Kernel versions: Zen2 5.15.0-76.83-generic -> Zen3 5.19.0-43.44~22.04.1-generic -> OK Zen3 5.19.0-43.44~22.04.1-generic -> Zen2 5.15.0-76.83-generic -> OK Zen2 5.19.0-43.44~22.04.1-generic -> Zen3 5.15.0-76.83-generic -> OK Zen3 5.15.0-76.83-generic -> Zen2 5.19.0-43.44~22.04.1-generic -> NOT OK We've tested it with fresh started and with live-migrated VMs, getting same results. Its probably related to KVM: SVM: fix tsc scaling cache logic https://linux.googlesource.com/linux/kernel/git/torvalds/linux/+/11d39e8cc43e1c6737af19ca9372e590061b5ad2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025987/+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 2025987] Re: 5.15.0-76: Qemu live migration regression due to PKRU leakage
[Expired for qemu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qemu (Ubuntu) Status: Incomplete => Expired -- 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/2025987 Title: 5.15.0-76: Qemu live migration regression due to PKRU leakage Status in linux package in Ubuntu: Expired Status in qemu package in Ubuntu: Expired Bug description: I am trying to live migrate Qemu VMs between Amd Zen3 to Zen2 servers. What we expect: VMs continue to run after live-migrate What happened: VMs instantly get stuck after migration with 100% CPU usage. All Nodes are running Ubuntu 22.04. We have tested Kernel releases back to 5.15.0-70. Nodes running Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 : Zen2 -> Zen3 migration: OK Zen3 -> Zen2 migration: OK Nodes running Ubuntu 5.15.0-76.83-generic 5.15.99 : Zen2 -> Zen3 migration: OK Zen3 -> Zen2 migration: NOT OK Mixed Kernel versions: Zen2 5.15.0-76.83-generic -> Zen3 5.19.0-43.44~22.04.1-generic -> OK Zen3 5.19.0-43.44~22.04.1-generic -> Zen2 5.15.0-76.83-generic -> OK Zen2 5.19.0-43.44~22.04.1-generic -> Zen3 5.15.0-76.83-generic -> OK Zen3 5.15.0-76.83-generic -> Zen2 5.19.0-43.44~22.04.1-generic -> NOT OK We've tested it with fresh started and with live-migrated VMs, getting same results. Its probably related to KVM: SVM: fix tsc scaling cache logic https://linux.googlesource.com/linux/kernel/git/torvalds/linux/+/11d39e8cc43e1c6737af19ca9372e590061b5ad2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025987/+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 2043786] Re: RTL8111EPP: Fix the network lost after resume with DASH
verified on 1 device with RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10EC:8168] ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043786 Title: RTL8111EPP: Fix the network lost after resume with DASH Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] On the system installed RTL8111EPP with DASH, unable to get the network back upon system resume [Fix] handle DASH during system suspend and resume. [Test] Vendor tested on hardware, the ethernet is OK after resume. [Where problems could occur] It may break r8169 driver. No SRU for Jammy 5.15 kernel due to too many commits are needed to backport to support DASH. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043786/+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 2031412] Re: Support mipi camera on Intel Meteor Lake platform
@Andreas, is there a problem in ipu6-drivers? ivsc-driver is in -proposed, but ipu6-drivers is not. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in ipu6-drivers source package in Mantic: In Progress Status in ivsc-driver source package in Mantic: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: Fix Released Status in ivsc-driver source package in Noble: Fix Released Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. Need both firmware and driver change to probe the hardware correctly. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are in v6.6 already, and IPU6 ISYS is under upstream review. More
[Kernel-packages] [Bug 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
This affects me as well. All though this seems to be working apt policy zfs-dkms zfs-dkms: Installed: 2.2.0-0ubuntu3 Candidate: 2.2.0-0ubuntu3 Version table: 2.2.1-0ubuntu1 100 100 http://archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 http://archive.ubuntu.com/ubuntu noble-proposed/universe i386 Packages *** 2.2.0-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu noble/universe i386 Packages 100 /var/lib/dpkg/status Please also follow the Link Mike provided -- 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/2044969 Title: Upstream bug: ZFS feature@block_cloning causes data corruption Status in zfs-linux package in Ubuntu: Confirmed Bug description: Noble DAILY ISO 2023.11.27 & Current Mantic Installers. some copied files are corrupted (chunks replaced by zeros) ISSUE #15526 RE:https://github.com/openzfs/zfs/issues/15526 zpool feature@block_cloning came out with version 2.2.0 of zfs-linux, this is not the root of that bug, but exacerbates the underlying bug. The bug was reported, and version 2.2.1 was released with that feature turned off by default, so that would be a problem out of the gate. There is a patch out which got approved, merged and built tonight that, after testing, seems to correct that: dnode_is_dirty: check dnode and its data for dirtiness #15571 https://github.com/openzfs/zfs/pull/15571 Unfortunately, Mantic was released with version 2.2.0. Current DEV Noble also has 2.2.0. This feature in the default ZFS install scripts for both Mantic and Noble, with the current default, In bpool, feature@block_cloning is disable, but for rpool, the same feature is enabled, so "at risk". This feature is set at pool creation time. You cannot set this feature to disable without destroying the pool and recreating it fresh. Have good backups, via rsync. cp is affected, but not rsync. Version 2.2.1 has this feature disabled by default. It was released Nov 21, 2023. I am proposing that the patched build from tonight get pushed through for Mantic when it hits from upstream... And possibly pushing 2.2.1 through for Noble, where we can thoroughly test it in this current DEV Cycle. Also, this was filed because of Security as it relates to data integrity concerns: CVE-2023-49298 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-49298 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: zfsutils-linux 2.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 27 19:58:32 2023 InstallationDate: Installed on 2023-11-23 (4 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969/+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 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal
** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- 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/2043197 Title: USB bus error after upgrading to proposed kernel on lunar, jammy and focal Status in linux package in Ubuntu: Triaged Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: == SRU Justification == [Impact] USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel. [Fix] Use logarithmic encoding for the bMaxPacketSize0 value. [Test] With the patch applied, SuperSpeed devices can be enumerated across several reboots. [Where problems could occur] The switch case for Wireless USB (not USB WiFi dongle) was removed by the fix. I am not aware of the existence of any Wireless USB device. But if they do exist, this patch may the packet size encoding on them. == Original Bug Report == [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 16.0 dmi.bios.vendor: HP dmi.bios.version: S12 Ver. 02.16.00 dmi.board.name: 8810 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.23 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA: dmi.product.family: 103C_53307F HP ProOne dmi.product.name: HP
[Kernel-packages] [Bug 2038998] Re: [amdgpu] Screen corruption, distorted geometry and misplaced triangles
The corruption also feels like something is broken with mid command
buffer preemption so please try this kernel parameter:
amdgpu.mcbp=0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038998
Title:
[amdgpu] Screen corruption, distorted geometry and misplaced triangles
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 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.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
More people, please try comment #16.
Please also ensure you don't have any unsupported extensions installed.
Wobbly Windows comes to mind, but you can remove them all by running:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again.
** Summary changed:
- [amdgpu] Screen artifacts/UI oddities on Wayland
+ [amdgpu] Screen corruption, distorted geometry and misplaced triangles
--
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/2038998
Title:
[amdgpu] Screen corruption, distorted geometry and misplaced triangles
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 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.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- 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/2044969 Title: Upstream bug: ZFS feature@block_cloning causes data corruption Status in zfs-linux package in Ubuntu: Confirmed Bug description: Noble DAILY ISO 2023.11.27 & Current Mantic Installers. some copied files are corrupted (chunks replaced by zeros) ISSUE #15526 RE:https://github.com/openzfs/zfs/issues/15526 zpool feature@block_cloning came out with version 2.2.0 of zfs-linux, this is not the root of that bug, but exacerbates the underlying bug. The bug was reported, and version 2.2.1 was released with that feature turned off by default, so that would be a problem out of the gate. There is a patch out which got approved, merged and built tonight that, after testing, seems to correct that: dnode_is_dirty: check dnode and its data for dirtiness #15571 https://github.com/openzfs/zfs/pull/15571 Unfortunately, Mantic was released with version 2.2.0. Current DEV Noble also has 2.2.0. This feature in the default ZFS install scripts for both Mantic and Noble, with the current default, In bpool, feature@block_cloning is disable, but for rpool, the same feature is enabled, so "at risk". This feature is set at pool creation time. You cannot set this feature to disable without destroying the pool and recreating it fresh. Have good backups, via rsync. cp is affected, but not rsync. Version 2.2.1 has this feature disabled by default. It was released Nov 21, 2023. I am proposing that the patched build from tonight get pushed through for Mantic when it hits from upstream... And possibly pushing 2.2.1 through for Noble, where we can thoroughly test it in this current DEV Cycle. Also, this was filed because of Security as it relates to data integrity concerns: CVE-2023-49298 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-49298 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: zfsutils-linux 2.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 27 19:58:32 2023 InstallationDate: Installed on 2023-11-23 (4 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969/+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 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
** Information type changed from Private Security to Public Security ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-49298 -- 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/2044969 Title: Upstream bug: ZFS feature@block_cloning causes data corruption Status in zfs-linux package in Ubuntu: New Bug description: Noble DAILY ISO 2023.11.27 & Current Mantic Installers. some copied files are corrupted (chunks replaced by zeros) ISSUE #15526 RE:https://github.com/openzfs/zfs/issues/15526 zpool feature@block_cloning came out with version 2.2.0 of zfs-linux, this is not the root of that bug, but exacerbates the underlying bug. The bug was reported, and version 2.2.1 was released with that feature turned off by default, so that would be a problem out of the gate. There is a patch out which got approved, merged and built tonight that, after testing, seems to correct that: dnode_is_dirty: check dnode and its data for dirtiness #15571 https://github.com/openzfs/zfs/pull/15571 Unfortunately, Mantic was released with version 2.2.0. Current DEV Noble also has 2.2.0. This feature in the default ZFS install scripts for both Mantic and Noble, with the current default, In bpool, feature@block_cloning is disable, but for rpool, the same feature is enabled, so "at risk". This feature is set at pool creation time. You cannot set this feature to disable without destroying the pool and recreating it fresh. Have good backups, via rsync. cp is affected, but not rsync. Version 2.2.1 has this feature disabled by default. It was released Nov 21, 2023. I am proposing that the patched build from tonight get pushed through for Mantic when it hits from upstream... And possibly pushing 2.2.1 through for Noble, where we can thoroughly test it in this current DEV Cycle. Also, this was filed because of Security as it relates to data integrity concerns: CVE-2023-49298 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-49298 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: zfsutils-linux 2.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 27 19:58:32 2023 InstallationDate: Installed on 2023-11-23 (4 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969/+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 2044657] Re: zfs block cloning file system corruption
I'm not sure why linux-hwe-6.2 is marked as affected. hwe-6.2 use 2.1.9 based zfs-linux and will not be upgraded to use 2.2.0 series. ** Package changed: linux-hwe-6.2 (Ubuntu) => linux-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.5 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2044657/+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 2044657] Re: zfs block cloning file system corruption
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Confirmed -- 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/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.5 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2044657/+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 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)
This bug was fixed in the package initramfs-tools - 0.142ubuntu15.1 --- initramfs-tools (0.142ubuntu15.1) mantic; urgency=medium * Install intel_lpss_pci and spi_pxa2xx_platform kernel modules for keyboard on MacBook Pro 2017 (LP: #2042710) * Install surface_aggregator_registry for keyboard on Surface Laptop 4 (LP: #2007050) -- Benjamin Drung Tue, 14 Nov 2023 20:02:42 +0100 ** Changed in: initramfs-tools (Ubuntu Mantic) 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/2007050 Title: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password) Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in initramfs-tools source package in Mantic: Fix Released Status in linux source package in Mantic: Invalid Bug description: [ Impact ] With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. [ Test Plan ] The -generic kernel and probably all kernel flavors contain the needed driver (on amd64). On mantic systems, you can verify the current initrd doesn't contain these modules by decompressing the initramfs and listing its files: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'surface_aggregator_registry\|intel-lpss-pci' After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up the kernel modules: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'surface_aggregator_registry\|intel-lpss-pci' usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst usr/lib/modules/6.5.0-10-generic/kernel/drivers/platform/surface/surface_aggregator_registry.ko.zst Test case on Microsoft Surface Laptop 4: Remove all previous workarounds. Install the fixed initramfs-tools version. Then the keyboard should work during boot to enter the passphrase. [ Where problems could occur ] This is making the initramfs slightly bigger. In my testing, both added were 11,868 bytes in total (or 0.01 % on a 102 MB initramfs). [ Apport report ] ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3
[Kernel-packages] [Bug 2007050] Update Released
The verification of the Stable Release Update for initramfs-tools 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 linux in Ubuntu. https://bugs.launchpad.net/bugs/2007050 Title: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password) Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in initramfs-tools source package in Mantic: Fix Committed Status in linux source package in Mantic: Invalid Bug description: [ Impact ] With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. [ Test Plan ] The -generic kernel and probably all kernel flavors contain the needed driver (on amd64). On mantic systems, you can verify the current initrd doesn't contain these modules by decompressing the initramfs and listing its files: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'surface_aggregator_registry\|intel-lpss-pci' After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up the kernel modules: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'surface_aggregator_registry\|intel-lpss-pci' usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst usr/lib/modules/6.5.0-10-generic/kernel/drivers/platform/surface/surface_aggregator_registry.ko.zst Test case on Microsoft Surface Laptop 4: Remove all previous workarounds. Install the fixed initramfs-tools version. Then the keyboard should work during boot to enter the passphrase. [ Where problems could occur ] This is making the initramfs slightly bigger. In my testing, both added were 11,868 bytes in total (or 0.01 % on a 102 MB initramfs). [ Apport report ] ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3
[Kernel-packages] [Bug 2040181] Re: upgrade zfs-linux to 2.2.0 final
** Tags removed: verification-done verification-done-mantic ** Tags added: verification-needed verification-needed-mantic -- 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/2040181 Title: upgrade zfs-linux to 2.2.0 final Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Mantic: Fix Committed Status in zfs-linux source package in Noble: Fix Released Bug description: [ Impact ] * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal to update to final * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional cherrypicks, or kernel team created fixes that got contributed & accepted upstream. At the time this was the only way to get zfs working with v6.5 kernels and also drop the need for shiftfs (due to zfs impovements). Since us shipping this package, upstream has identified and fixed multiple small bugfixes in the subsequent RC and the final releases, including one bug fix that can lead to potential data loss. * The 2.2.0 release branch was frozen for a long time already, and outstanding number of commits of fixes that Mantic does not have is less than 30 small patches. * Proposal to upgrade our build to 2.2.0 final, pick up all the regression fixes, and drop all the cherrypicked patches that enable v6.5 support. This will give us the best kernel driver to support in the runnup to next Ubuntu LTS. [ Test Plan ] * autopkgtest pass * kernel regression zfs testsuite pass * zsys integration test pass * LXD support retested [ Where problems could occur ] * LXD snap in edge shipped zfs tooling of RC5 version until 16th October when they upgraded to 2.2.0 final, there are no kernel- userspace incompatiblities between RC & final, but we should explicitly test this. [ Other Info ] * Upstream is alerting us to the potential data loss and requesting upgrade to 2.2.0-rc5 or better. [ Abbriviated changes being introduced ] $ git log --oneline 4a104ac047..95785196f2 -- cmd/ lib/ module/os/linux/ | grep -v compat 810fc49a3e Ensure we call fput when cloning fails due to different devices. a80e1f1c90 zvol: Temporally disable blk-mq 33d7c2d165 import: require force when cachefile hostid doesn't match on-disk 8015e2ea66 Add '-u' - nomount flag for zfs set c53bc3837c Improve the handling of sharesmb,sharenfs properties e9dc31c74e Update the behavior of mountpoint property 608741d062 Report ashift of L2ARC devices in zdb 0ce1b2ca19 Invoke zdb by guid to avoid import errors 0aabd6b482 ZIL: Avoid dbuf_read() in ztest_get_data() a199cac6cd status: report pool suspension state under failmode=continue 729507d309 Fix occasional rsend test crashes 3af63683fe cmd: add 'help' subcommand to zpool and zfs 9aa1a2878e Fix incorrect expected error in ztest f7a07d76ee Retire z_nr_znodes 54c6fbd378 zed: Allow autoreplace and fault LEDs for removed vdevs 32949f2560 Relax error reporting in zpool import and zpool split 63159e5bda checkstyle: fix action failures e99e684b33 zed: update zed.d/statechange-slot_off.sh d19304ffee zed: Add zedlet to power off slot when drive is faulted 92f095a903 copy_file_range: fix fallback when source create on same txg 895cb689d3 zfs_clone_range should return a descriptive error codes 6bdc7259d1 libzfs: sendrecv: send_progress_thread: handle SIGINFO/SIGUSR1 df8c9f351d ZIL: Second attempt to reduce scope of zl_issuer_lock. 0ae7bfc0a4 zpool_vdev_remove() should handle EALREADY error return bd1eab16eb linux: zfs: ctldir: set [amc]time to snapshot's creation property c47f0f4417 linux/copy_file_range: properly request a fallback copy on Linux <5.3 12f2b1f65e zdb: include cloned blocks in block statistics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2040181/+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 2043059] Re: Installation errors out when installing in a chroot
Thanks, Dann, This dpkg-divert won't work unless we first remove the package this "clashes" with (nvidia-crashdump had already diverted this file). Not sure if this is really much better than just removing kdump-tools (and dependencies) and then reinstalling them later. We're still looking into removing the `unshare --mount-proc`. Perhaps this would be a better long term solution. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2043059 Title: Installation errors out when installing in a chroot Status in linux-nvidia package in Ubuntu: New Bug description: Processing triggers for linux-image-5.15.0-1040-nvidia (5.15.0-1040.40) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.15.0-1040-nvidia ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.15.0-1040-nvidia cryptsetup: WARNING: Couldn't determine root device W: Couldn't identify type of root file system for fsck hook cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory /etc/kernel/postinst.d/kdump-tools: kdump-tools: Generating /var/lib/kdump/initrd.img-5.15.0-1040-nvidia mkinitramfs: failed to determine device for / mkinitramfs: workaround is MODULES=most, check: grep -r MODULES /var/lib/kdump/initramfs-tools Error please report bug on initramfs-tools Include the output of 'mount' and 'cat /proc/mounts' update-initramfs: failed for /var/lib/kdump/initrd.img-5.15.0-1040-nvidia with 1. run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1 dpkg: error processing package linux-image-5.15.0-1040-nvidia (--configure): installed linux-image-5.15.0-1040-nvidia package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-5.15.0-1040-nvidia E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2043059/+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-gcp/5.4.0.1120.122)
All autopkgtests for the newly accepted linux-meta-gcp (5.4.0.1120.122) for focal have finished running. The following regressions have been reported in tests triggered by the package: r8168/8.048.00-1ubuntu0.20.04.2 (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-gcp [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: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix 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: Won't Fix 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: Won't Fix 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 packaging 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 2045080] [NEW] apply nvidia igx patches for Oct 19 - Nov 28 2023
Public bug reported: Patches for IGX. These are intended for releases that come after the r36.2 DP release. ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2045080 Title: apply nvidia igx patches for Oct 19 - Nov 28 2023 Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Patches for IGX. These are intended for releases that come after the r36.2 DP release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2045080/+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 2045079] [NEW] Lunar update: upstream stable patchset 2023-11-28
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-11-28 Ported from the following upstream stable releases: v6.1.54, v6.5.4 from git://git.kernel.org/ net/ipv6: SKB symmetric hash should incorporate transport ports mm: multi-gen LRU: rename lrugen->lists[] to lrugen->folios[] Multi-gen LRU: fix per-zone reclaim io_uring/net: don't overflow multishot accept io_uring: break out of iowq iopoll on teardown io_uring/sqpoll: fix io-wq affinity when IORING_SETUP_SQPOLL is used io_uring: Don't set affinity on a dying sqpoll thread drm/virtio: Conditionally allocate virtio_gpu_fence scsi: qla2xxx: Adjust IOCB resource on qpair create scsi: qla2xxx: Limit TMF to 8 per function scsi: qla2xxx: Fix deletion race condition scsi: qla2xxx: fix inconsistent TMF timeout scsi: qla2xxx: Fix command flush during TMF scsi: qla2xxx: Fix erroneous link up failure scsi: qla2xxx: Turn off noisy message log scsi: qla2xxx: Fix session hang in gnl scsi: qla2xxx: Fix TMF leak through scsi: qla2xxx: Remove unsupported ql2xenabledif option scsi: qla2xxx: Flush mailbox commands on chip reset scsi: qla2xxx: Fix smatch warn for qla_init_iocb_limit() scsi: qla2xxx: Error code did not return to upper layer scsi: qla2xxx: Fix firmware resource tracking null_blk: fix poll request timeout handling fbdev/ep93xx-fb: Do not assign to struct fb_info.dev clk: qcom: camcc-sc7180: fix async resume during probe drm/ast: Fix DRAM init on AST2200 ASoC: tegra: Fix SFC conversion for few rates clk: qcom: turingcc-qcs404: fix missing resume during probe arm64: dts: renesas: rzg2l: Fix txdv-skew-psec typos send channel sequence number in SMB3 requests after reconnects mm: hugetlb_vmemmap: fix a race between vmemmap pmd split lib/test_meminit: allocate pages up to order MAX_ORDER parisc: led: Fix LAN receive and transmit LEDs parisc: led: Reduce CPU overhead for disk & lan LED computation cifs: update desired access while requesting for directory lease pinctrl: cherryview: fix address_space_handler() argument dt-bindings: clock: xlnx,versal-clk: drop select:false clk: imx: pll14xx: dynamically configure PLL for 393216000/361267200Hz clk: imx: pll14xx: align pdiv with reference manual clk: qcom: gcc-mdm9615: use proper parent for pll0_vote clock soc: qcom: qmi_encdec: Restrict string length in decode clk: qcom: dispcc-sm8450: fix runtime PM imbalance on probe errors clk: qcom: lpasscc-sc7280: fix missing resume during probe clk: qcom: q6sstop-qcs404: fix missing resume during probe clk: qcom: mss-sc7180: fix missing resume during probe NFS: Fix a potential data corruption NFSv4/pnfs: minor fix for cleanup path in nfs4_get_device_info bus: mhi: host: Skip MHI reset if device is in RDDM kbuild: rpm-pkg: define _arch conditionally kbuild: do not run depmod for 'make modules_sign' tpm_crb: Fix an error handling path in crb_acpi_add() gfs2: Switch to wait_event in gfs2_logd gfs2: low-memory forced flush fixes mailbox: qcom-ipcc: fix incorrect num_chans counting kconfig: fix possible buffer overflow Input: iqs7222 - configure power mode before triggering ATI perf trace: Use zfree() to reduce chances of use after free perf trace: Really free the evsel->priv area pwm: atmel-tcb: Convert to platform remove callback returning void pwm: atmel-tcb: Harmonize resource allocation order pwm: atmel-tcb: Fix resource freeing in error path and remove backlight: gpio_backlight: Drop output GPIO direction check for initial power state Input: tca6416-keypad - always expect proper IRQ number in i2c client Input: tca6416-keypad - fix interrupt enable disbalance perf annotate bpf: Don't enclose non-debug code with an assert() x86/virt: Drop unnecessary check on extended CPUID level in cpu_has_svm() perf vendor events: Update the JSON/events descriptions for power10 platform perf vendor events: Drop some of the JSON/events for power10 platform perf vendor events: Drop STORES_PER_INST metric event for power10 platform perf top: Don't pass an ERR_PTR() directly to perf_session__delete() watchdog: intel-mid_wdt: add MODULE_ALIAS() to allow auto-load pwm: lpc32xx: Remove handling of PWM channels perf test stat_bpf_counters_cgrp: Fix shellcheck issue about logical operators perf test stat_bpf_counters_cgrp: Enhance perf stat cgroup BPF counter test drm/i915: mark requests for GuC virtual engines to avoid use-after-free blk-throttle: use calculate_io/bytes_allowed() for throtl_trim_slice() blk-throttle: consider 'carryover_ios/bytes' in throtl_trim_slice() smb: propagate error code of
[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
### VERIFICATION-FAILED FOCAL-PROPOSED ### makedumpfile original version: 1:1.6.7-1ubuntu2.4 makedumpfile proposed version: 1:1.6.7-1ubuntu2.5 kernel version: 5.15.0-89-generic hwe sudo apt install -y linux-crashdump sudo vim /etc/default/grub.d/kdump-tools.cfg # Add the line at the top of the file below USE_KDUMP=1 LOAD_KEXEC=true # Uncomment the makedumpfile line and change 31 to 32 MAKEDUMP_ARGS="-c -d 32" exit vim sudo vim /etc/default/grub.d/kdump-tools.cfg change 192 to either 256M or 512M sudo sysctl -w kernel.sysrq=1 sudo apt-get update-grub sudo reboot sudo su kdump-config show Needs to look similar to: root@focal:/home/ubuntu# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x7300 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-89-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-89-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic root=UUID=975b9a95-b58e-48da-bd23-dd01b13bcbad ro quiet splash vt.handoff=7 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz *most importantly the addr is not zero and the state is: ready to kdump. # trigger crash echo c > /proc/sysrq-trigger ... wait for reboot and login cd /var/crash/ There is a folder with a datetimestamp of the crash, inside the folder is the vmcore and dmesg files There is also a file called linux-image*.crash in /var/crash/ *Note: In bionic we get the cp message [6.946187] kdump-tools[622]: Starting kdump-tools: * running makedumpfile -c -d 32 /proc/vmcore /var/crash/202311221422/dump-incomplete [6.959932] kdump-tools[622]: Dump_level(32) is invalid. [6.964316] kdump-tools[622]: makedumpfile Failed. [6.976231] kdump-tools[622]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 25.084729] kdump-tools[622]: * kdump-tools: saved vmcore in /var/crash/202311221422 [ 26.355039] kdump-tools[622]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202311221422/dmesg.202311221422 [ 26.436513] kdump-tools[622]: The dmesg log is saved to /var/crash/202311221422/dmesg.202311221422. [ 26.443208] kdump-tools[622]: makedumpfile Completed. [ 26.449066] kdump-tools[622]: * kdump-tools: saved dmesg content in /var/crash/202311221422 [ 26.463950] kdump-tools[622]: Wed, 22 Nov 2023 14:22:50 + [ 26.490318] kdump-tools[622]: Rebooting. *Note: In Focal we don't Nov 28 13:35:54 focal kdump-tools[604]: Starting kdump-tools: Nov 28 13:35:54 focal kdump-tools[667]: Starting kdump-tools: Nov 28 13:35:54 focal kdump-tools[667]: * Creating symlink / Nov 28 13:35:54 focal kdump-tools[708]: * Creating symlink / Nov 28 13:35:54 focal kdump-tools[708]: n: failed to create symbolic link '/va: No such file or directory Nov 28 13:35:54 focal kdump-tools[713]: kdump-tools: Generating /var/lib/kdump/initrd.img-5.15.0-89-generic Nov 28 13:35:57 focal kdump-tools[667]: * Creating symlink /var/lib/kdump/initrd.img Nov 28 13:35:57 focal kdump-tools[667]: * Invalid symlink : /var/lib/kdump/vmlinuz Nov 28 13:35:57 focal kdump-tools[667]: * Creating symlink /var/lib/kdump/vmlinuz Nov 28 13:35:58 focal kdump-tools[667]: * loaded kdump kernel Nov 28 13:35:58 focal kdump-tools[3337]: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic root=UUID=975b9a95-b58e-48da-bd23-dd01b13bcbad ro quiet splash vt.handoff=7 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Nov 28 13:35:58 focal kdump-tools[3338]: loaded kdump kernel --- enabled proposed repo Remove any crashes from /var/crash/ install proposed version of makedumpfile "follow similar steps above if on new machine" /var/log/syslog Nov 28 15:10:19 focal kdump-tools[674]: Starting kdump-tools: Nov 28 15:10:19 focal kdump-tools[674]: * Creating symlink / * Creating symlink /var/lib/kdump/initrd.img Nov 28 15:10:20 focal kdump-tools[674]: * loaded kdump kernel Nov 28 15:10:20 focal kdump-tools: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic root=UUID=1887d6a1-cdd3-474f-a3a8-53703a658358 ro quiet splash vt.handoff=7 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Nov 28 15:10:20 focal kdump-tools: loaded kdump kernel You can produce a vmcore 2 ways. 1. by editing the file /etc/default/kdump-tools to commenting in MAKEDUMPFILE_ARGS="-c -d 32" 2. by command mv /usr/bin/makedumpfile /usr/bin/makedumpfile.bak My results show that with no changes to cause a crash, we see a dmesg and dump files created in the /var/crash/timestamp folder which is the correct
[Kernel-packages] [Bug 2038539] Re: bluetooth connections are unstable with linux-image-6.5.0-6-generic and above (MANTIC)
upgrade to kernel 6.6.0-13 slightly lessens the problem but does not
eliminate the drop outs again starting browsing seems to trigger drop
out to begin.. scheduler issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038539
Title:
bluetooth connections are unstable with linux-image-6.5.0-6-generic
and above (MANTIC)
Status in linux package in Ubuntu:
New
Bug description:
Seems some random network activity regularly breaks bluetooth connections..
headphones connect and reconnect or suffer breaks in sound etc.
Started with this kernel version linux-image-6.5.0-7 .. previous kernel
linux-image-6.5.0-5 works perfectly
Booting into the older kernel restores bluetooth stability.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1690 F wireplumber
/dev/snd/controlC0: derk 1690 F wireplumber
/dev/snd/seq:derk 1687 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Thu Oct 5 08:33:01 2023
InstallationDate: Installed on 2023-10-04 (1 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Slim 5 16ABR8
dmi.ec.firmware.release: 1.21
dmi.modalias:
dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8:
dmi.product.family: IdeaPad Slim 5 16ABR8
dmi.product.name: 82XG
dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8
dmi.product.version: IdeaPad Slim 5 16ABR8
dmi.sys.vendor: LENOVO
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1691 F wireplumber
/dev/snd/controlC0: derk 1691 F wireplumber
/dev/snd/seq:derk 1688 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-10-04 (12 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Slim 5 16ABR8
dmi.ec.firmware.release: 1.21
dmi.modalias:
[Kernel-packages] [Bug 2045069] Re: Azure: Deprecate Netvsc and implement MANA direct
https://lists.ubuntu.com/archives/kernel-team/2023-November/147282.html -- 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/2045069 Title: Azure: Deprecate Netvsc and implement MANA direct Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Lunar: In Progress Status in linux-azure source package in Mantic: In Progress Bug description: SRU Justification [Impact] Microsoft has asked for the inclusion of 3 patches that deprecate the use of netvsc in favor of MANA direct. hv_netvsc: Mark VF as slave before exposing it to user-mode: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=c807d6cd089d2f4951baa838081ec5ae3e2360f8 hv_netvsc: Fix race of register_netdevice_notifier and VF register: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=85520856466ed6bc3b1ccb013cddac70ceb437db hv_netvsc: fix race of netvsc and VF register_netdevice: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=d30fb712e52964f2cf9a9c14cf67078394044837 [Test Plan] Microsoft tested [Regression potential] User space that relies on netvsc will likely fail [Other Info] SF: #00374570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2045069/+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 2045069] [NEW] Azure: Deprecate Netvsc and implement MANA direct
Public bug reported: SRU Justification [Impact] Microsoft has asked for the inclusion of 3 patches that deprecate the use of netvsc in favor of MANA direct. hv_netvsc: Mark VF as slave before exposing it to user-mode: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=c807d6cd089d2f4951baa838081ec5ae3e2360f8 hv_netvsc: Fix race of register_netdevice_notifier and VF register: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=85520856466ed6bc3b1ccb013cddac70ceb437db hv_netvsc: fix race of netvsc and VF register_netdevice: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=d30fb712e52964f2cf9a9c14cf67078394044837 [Test Plan] Microsoft tested [Regression potential] User space that relies on netvsc will likely fail [Other Info] SF: #00374570 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Lunar) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Mantic) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Lunar) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Mantic) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/2045069 Title: Azure: Deprecate Netvsc and implement MANA direct Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Lunar: In Progress Status in linux-azure source package in Mantic: In Progress Bug description: SRU Justification [Impact] Microsoft has asked for the inclusion of 3 patches that deprecate the use of netvsc in favor of MANA direct. hv_netvsc: Mark VF as slave before exposing it to user-mode: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=c807d6cd089d2f4951baa838081ec5ae3e2360f8 hv_netvsc: Fix race of register_netdevice_notifier and VF register: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=85520856466ed6bc3b1ccb013cddac70ceb437db hv_netvsc: fix race of netvsc and VF register_netdevice: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=d30fb712e52964f2cf9a9c14cf67078394044837 [Test Plan] Microsoft tested [Regression potential] User space that relies on netvsc will likely fail [Other Info] SF: #00374570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2045069/+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 2042546] Re: Include cifs.ko in linux-modules package
We are still seeing this issue on 6.2.0-1016-azure kernel adminuser@ubuntu:~$ uname -a Linux ubuntu 6.2.0-1016-azure #16~22.04.1-Ubuntu SMP Tue Oct 10 17:11:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux adminuser@ubuntu:~$ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure adminuser@ubuntu:~$ ls -lh /lib/modules/6.2.0-1016-azure/kernel/fs/ total 120K drwxr-xr-x 2 root root 4.0K Nov 1 02:12 9p drwxr-xr-x 2 root root 4.0K Nov 1 02:12 autofs -rw-r--r-- 1 root root 38K Oct 10 16:03 binfmt_misc.ko drwxr-xr-x 2 root root 4.0K Nov 1 02:12 btrfs drwxr-xr-x 2 root root 4.0K Nov 1 02:12 cachefiles drwxr-xr-x 2 root root 4.0K Nov 1 02:12 ceph drwxr-xr-x 2 root root 4.0K Nov 1 02:12 dlm drwxr-xr-x 2 root root 4.0K Nov 1 02:12 fat drwxr-xr-x 2 root root 4.0K Nov 1 02:12 fscache drwxr-xr-x 2 root root 4.0K Nov 1 02:12 fuse drwxr-xr-x 2 root root 4.0K Nov 1 02:12 isofs drwxr-xr-x 2 root root 4.0K Nov 1 02:12 lockd drwxr-xr-x 2 root root 4.0K Nov 1 02:12 netfs drwxr-xr-x 5 root root 4.0K Nov 1 02:12 nfs drwxr-xr-x 2 root root 4.0K Nov 1 02:12 nfs_common drwxr-xr-x 2 root root 4.0K Nov 1 02:12 nfsd drwxr-xr-x 2 root root 4.0K Nov 1 02:12 nls drwxr-xr-x 2 root root 4.0K Nov 1 02:12 overlayfs drwxr-xr-x 2 root root 4.0K Nov 1 02:12 udf drwxr-xr-x 2 root root 4.0K Nov 1 02:12 ufs drwxr-xr-x 2 root root 4.0K Nov 1 02:12 xfs adminuser@ubuntu:~$ apt list --installed 2>/dev/null | grep -i cifs cifs-utils/jammy-updates,jammy-security,now 2:6.14-1ubuntu0.1 amd64 [installed] adminuser@ubuntu:~$ sudo mount -t cifs /mnt/ -o username= Password for @: mount error: cifs filesystem not supported by the system mount error(19): No such device Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) -- 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/2042546 Title: Include cifs.ko in linux-modules package Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+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 2044657] Re: zfs block cloning file system corruption
Apparently 2.2.1 did not fix the issue, there is an on-going PR https://github.com/openzfs/zfs/pull/15571 that has the latest fix for the data corruption. As a side note it also affects zfs 2.1 series (block cloning made it more evident, but apparently possible to happen on earlier zfs releases), would we see a linux-hwe-6.2 bump for this with a 2.1 patch? Below is the 2.1.x series PR: https://github.com/openzfs/zfs/pull/15578 ** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New -- 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/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.2 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+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 2042935] Re: NVIDIA pull request 1018-002v1, 1018-003v1, 1018-004v1
** Summary changed: - NVIDIA pull request 1018-002v1, 1018-003v1 + NVIDIA pull request 1018-002v1, 1018-003v1, 1018-004v1 ** Description changed: Apply pull requests from NVIDIA received on 2023-11-02. Ankur Pawar (1): NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 Fabrice Gasnier (1): usb: typec: ucsi: don't print PPM init deferred errors Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable NTFS fs Jim Lin (1): NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control Jon Hunter (1): NVIDIA: SAUCE: Remove support for summation channel control Ninad Malwade (1): NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable Revanth Kumar Uppala (1): NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver Ulf Hansson (1): mmc: sdhci-tegra: Add runtime PM and OPP support Apply pull requests from NVIDIA received on 2023-11-13 Gautham Srinivasan (1): - NVIDIA: SAUCE: arm64: configs: disable LOGO + NVIDIA: SAUCE: arm64: configs: disable LOGO Laxman Dewangan (1): - NVIDIA: SAUCE: platform: tegra: Add new config TEGRA_PROD_LEGACY + NVIDIA: SAUCE: platform: tegra: Add new config TEGRA_PROD_LEGACY Narayan Reddy (1): - NVIDIA: SAUCE: aquantia: issue PHY reset during phy init + NVIDIA: SAUCE: aquantia: issue PHY reset during phy init Sandipan Patra (1): - NVIDIA: SAUCE: arm64: config: Disable DMI config + NVIDIA: SAUCE: arm64: config: Disable DMI config Shubhi Garg (1): - NVIDIA: SAUCE: configs: defconfig: enable TPM configs + NVIDIA: SAUCE: configs: defconfig: enable TPM configs Vince Hsu (1): - NVIDIA: SAUCE: arm: configs: enable QFMT_V2 for quota + NVIDIA: SAUCE: arm: configs: enable QFMT_V2 for quota + + Apply pull request from NVIDIA received on 2023-11-27 + + EJ Hsu (1): + NVIDIA: SAUCE: pinctrl: tegra: Set SFIO mode to Mux Register + + Linus Walleij (1): + Revert "pinctrl: tegra: Add support to display pin function" + + Penny Chiu (3): + NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig + NVIDIA: SAUCE: arm64: configs: Enable NFS server support + NVIDIA: SAUCE: arm64: configs: Enable dm_multipath driver + + Thierry Reding (1): + pinctrl: tegra: Display pin function in pinconf-groups + + Vince Hsu (1): + NVIDIA: SAUCE: arm64: configs: enable few matches for netfliter + -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2042935 Title: NVIDIA pull request 1018-002v1, 1018-003v1, 1018-004v1 Status in linux-nvidia-tegra package in Ubuntu: New Bug description: Apply pull requests from NVIDIA received on 2023-11-02. Ankur Pawar (1): NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 Fabrice Gasnier (1): usb: typec: ucsi: don't print PPM init deferred errors Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable NTFS fs Jim Lin (1): NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control Jon Hunter (1): NVIDIA: SAUCE: Remove support for summation channel control Ninad Malwade (1): NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable Revanth Kumar Uppala (1): NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver Ulf Hansson (1): mmc: sdhci-tegra: Add runtime PM and OPP support Apply pull requests from NVIDIA received on 2023-11-13 Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: disable LOGO Laxman Dewangan (1): NVIDIA: SAUCE: platform: tegra: Add new config TEGRA_PROD_LEGACY Narayan Reddy (1): NVIDIA: SAUCE: aquantia: issue PHY reset during phy init Sandipan Patra (1): NVIDIA: SAUCE: arm64: config: Disable DMI config Shubhi Garg (1): NVIDIA: SAUCE: configs: defconfig: enable TPM configs Vince Hsu (1): NVIDIA: SAUCE: arm: configs: enable QFMT_V2 for quota Apply pull request from NVIDIA received on 2023-11-27 EJ Hsu (1): NVIDIA: SAUCE: pinctrl: tegra: Set SFIO mode to Mux
[Kernel-packages] [Bug 2039542] Re: Remove duplication of devm_pwmchip_add function definition
This is not verifiable in the main kernel since it affected stub code
which is not in use with that config. The only kernel running into it
was linux-kvm. This builds now and double checked that this was done by
the change:
@@ -483,11 +483,6 @@ static inline int devm_pwmchip_add(struct device *dev,
struct pwm_chip *chip)
return -EINVAL;
}
-static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip)
-{
- return -EINVAL;
-}
Note that the function name deleted is the same as the name of the
function directly before (as the @@ hint shows).
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Tags removed: verification-needed-lunar-linux
** Tags added: verification-done-lunar-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/2039542
Title:
Remove duplication of devm_pwmchip_add function definition
Status in linux package in Ubuntu:
Invalid
Status in linux-kvm package in Ubuntu:
New
Status in linux source package in Lunar:
Fix Committed
Status in linux-kvm source package in Lunar:
Fix Released
Bug description:
SRU Justification:
[Impact]
* Upstream commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub
for devm_pwmchip_add()", was applied the second time during the latest upstream
patchset (#LP: 2037005) for cycle 2023.10.02.
* `git am` did not detect that the changes were applied, leading to the same
function definition being duplicated.
* This was not caught when the main kernel was built because this code is
under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from
linux-kvm, has CONFIG_PWM=y.
* The problem was caught when lunar:linux-kvm was cranked and build failed
with the following error:
```
In file included from /build/lunar/drivers/acpi/acpi_lpss.c:23:
/build/lunar/include/linux/pwm.h:486:19: error: redefinition of
'devm_pwmchip_add'
486 | static inline int devm_pwmchip_add(struct device *dev, struct
pwm_chip *chip)
| ^~~~
/build/lunar/include/linux/pwm.h:481:19: note: previous definition of
'devm_pwmchip_add' with type 'int(struct device *, struct pwm_chip *)'
481 | static inline int devm_pwmchip_add(struct device *dev, struct
pwm_chip *chip)
| ^~~~
```
[Fix]
* Revert the commit.
* Because this affects only linux:kvm, it is necessary to apply this fix for
lunar:linux-kvm for cycle 2023.10.02, but the main kernel can wait for the next
cycle.
[Test plan]
* Since linux-kvm was the only kernel that had this issue, I applied the
patch to kvm after I rebased the latest changes from the parent and did a build
test.
* I also did a build test for linux:main just to make sure
[Where problems could occur]
* This change is pretty non-invasive, so nowhere
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039542/+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-gcp/6.5.0.1010.10)
All autopkgtests for the newly accepted linux-meta-gcp (6.5.0.1010.10) for mantic have finished running. The following regressions have been reported in tests triggered by the package: systemd/253.5-1ubuntu6.1 (arm64) 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/mantic/update_excuses.html#linux-meta-gcp [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: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix 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: Won't Fix 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: Won't Fix 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 packaging 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 2038587] Re: Turning COMPAT_32BIT_TIME off on ppc64el
Just to close the loop: https://lore.kernel.org/all/20231124082512.gw9...@kitsune.suse.cz/T/#m64b790e83ff7d7b3e7df5baa239fb23ab907daa7 -- 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/2038587 Title: Turning COMPAT_32BIT_TIME off on ppc64el Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: This will prevent existing 32-bit powerpcle binaries to operate correctly, if they are still using 32bit time. And even exists? 24.04 LTS is likely to be used for 10 years. And if allowed to overrun and remain active in the field in 2038 can lead to catastrophic failure in the field due to these syscalls enabled and used. I would like to request if we can turn off COMPAT_32BIT_TIME on every architecture, thus this will be arch by arch bug report, and arch by arch decision. This needs to be a per-arch decision, potentially taking into consideration bi-arch userspace support. config COMPAT_32BIT_TIME bool "Provide system calls for 32-bit time_t" default !64BIT || COMPAT help This enables 32 bit time_t support in addition to 64 bit time_t support. This is relevant on all 32-bit architectures, and 64-bit architectures as part of compat syscall handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2038587/+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 2039925] Re: Realtek RTS5264 SD 7.0 cardreader support
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1009.10
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-jammy-linux-oem-6.5' to 'verification-done-
jammy-linux-oem-6.5'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy-
linux-oem-6.5'.
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: kernel-spammed-jammy-linux-oem-6.5-v2
verification-needed-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 2041495] Re: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1009.10 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-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2041495 Title: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2041495 [Impact] NVME module left unready, therefore not recognized by the installation process, and/or after installation with following error messages: ``` kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0 kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0 ``` [Fix] Proposed fix in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/core.c?h=v6.5=6cc834ba62998c65c42d0c63499bdd35067151ec "nvme: avoid bogus CRTO values", in Linus' tree v6.6 already, as well as stable kernels v6.1.55 and v6.5.5. [Test Case] Apply to kernel and boot with the nvme module installed. Now the device should be probed with success. ``` kernel: [1.731760] nvme nvme0: pci function 1:e1:00.0 kernel: [1.731778] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [1.731780] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [1.731919] nvme nvme0: bad crto:0 cap:800203028033fff kernel: [1.735550] nvme nvme0: Shutdown timeout set to 10 seconds kernel: [1.753865] nvme nvme0: allocated 64 MiB host memory buffer. kernel: [1.794966] nvme nvme0: 16/0/0 default/read/poll queues kernel: [2.136735] nvme0n1: p1 p2 p3 ``` [Where problems could occur] This patch tries to set an appropriate CRTO (Controller Ready Timeouts) that may be reported incorrectly by some devices. There should be little (a bit longer CRTO) to no effect on devices performing normally before hands. [Other Info] While this has been in Linus' tree, Mantic/Lunar/oem-6.5 and oem-6.1 will be nominated. == original bug report == NVME module left unready, therefore not recognized by the installation process, and/or after installation with following error messages: kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0 kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2041495/+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 2043786] Re: RTL8111EPP: Fix the network lost after resume with DASH
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1009.10 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-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043786 Title: RTL8111EPP: Fix the network lost after resume with DASH Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] On the system installed RTL8111EPP with DASH, unable to get the network back upon system resume [Fix] handle DASH during system suspend and resume. [Test] Vendor tested on hardware, the ethernet is OK after resume. [Where problems could occur] It may break r8169 driver. No SRU for Jammy 5.15 kernel due to too many commits are needed to backport to support DASH. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043786/+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 2043551] Re: Fix headset microphone for Dell laptops with audio codec ALC295
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1009.10 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-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043551 Title: Fix headset microphone for Dell laptops with audio codec ALC295 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Dell laptops with Realtek audio codec ALC295 can't detect the plug-in of headset microphone and also fails to record audio from headset. [Fix] Backport the fix from Realtek on linux-next https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=4b21a669ca21ed8f24ef4530b2918be5730114de [Test Case] 1. Power on the Dell laptops with Realtek ALC295 HDA. 2. Plug in the headset microphone 3. Verify if the jack-detection working and recording function is working or not. [Where problems could occur] Only affect Dell laptops with the Realtek ALC295 HDA. Should be low risk since Dell laptops only support MIC2 as external MIC. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043551/+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 2044091] Re: Long resume on surprise dock unplug
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1009.10 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-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044091 Title: Long resume on surprise dock unplug Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Bug description: [Impact] In OEM-6.5 testing it was found long resume when doing surprise unplug for TBT4 dock while system is in s0i3. The resume takes 2+ minutes when this issue happens. This issue is caused by this commit which got picked up in 6.4 kernel. https://github.com/torvalds/linux/commit/e8b908146d44310473e43b3382eca126e12d279c [Fix] It has been fixed upstream by https://github.com/torvalds/linux/commit/c82458101d5490230d735caecce14c9c27b1010c Which is backported to 6.5.7 kernel. [Test case] Unplug the dock when in s0i3. [Where problems could happen] hard to think how this would break anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2044091/+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 2044096] Re: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1009.10 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-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044096 Title: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux source package in Mantic: In Progress Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: [Impact] Built-in audio speaker function not working on new Dell Oasis 13/14/16 laptops [Fix] Need to backport https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=f0d9da19d7de9e845e7a93a901c4b9658df6b492 to support dual speaker configuration on Dell Oasis series [Test Case] 1. Power on the Dell Oasis 13/14/16 laptops with CS35L41 HDA. 2. Verify the audio functions, including playback and capture [Where problems could occur] Add CS35L41 support on specific Dell laptops. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2044096/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
$ dpkg -X linux-buildinfo-5.15.0-91-generic_5.15.0-91.101_amd64.deb unpack $ grep ^wwan unpack/usr/lib/linux/5.15.0-91-generic/modules wwan wwan_hwsim ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- 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/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
dpkg -X linux-buildinfo-6.2.0-39-generic_6.2.0-39.40_amd64.deb unpack grep wwan unpack/usr/lib/linux/6.2.0-39-generic/modules ... wwan wwan_hwsim ** Tags removed: verification-needed-lunar-linux ** Tags added: verification-done-lunar-linux -- 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/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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-gcp/5.4.0.1119.121)
All autopkgtests for the newly accepted linux-meta-gcp (5.4.0.1119.121) for focal have finished running. The following regressions have been reported in tests triggered by the package: r8168/8.048.00-1ubuntu0.20.04.2 (amd64) systemd/245.4-4ubuntu3.22 (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-gcp [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: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix 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: Won't Fix 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: Won't Fix 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 packaging 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 2042546] Re: Include cifs.ko in linux-modules package
Downloaded linux-modules-6.2.0-39-generic_6.2.0-39.40_amd64.deb from the PPA unpacked it and ensured it contains the cifs module: ~/tmp/lunar/unpack$ find|grep cifs ./lib/modules/6.2.0-39-generic/kernel/fs/smb/client/cifs.ko ./lib/modules/6.2.0-39-generic/kernel/fs/smb/common/cifs_md4.ko ./lib/modules/6.2.0-39-generic/kernel/fs/smb/common/cifs_arc4.ko ** Tags removed: verification-needed-lunar-linux ** Tags added: verification-done-lunar-linux -- 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/2042546 Title: Include cifs.ko in linux-modules package Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+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 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
** Tags added: verification-done -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls 0 cork 0 nodelay 0 sendpage 0 splice 0 urgent data 0 * Instead of including the payload in the wrong >512 KB buckets, the output should be to have 19 reqs in the 8 KB buckets for TX stats and 9 reqs in the 8 KB bucket for RX stats. [Where problems could occur] * The changes are in common code /net/smc/smc_stats.h hence any potential negativ impact is not limited to a specific platform. but limited to statistics for shared memory communication (SMC) hardware statistics. * But limited to the functions SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB. * The bucket (aka pos) calculation is not that trivial, issues here could cause other calculation
[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
** Tags removed: verification-done ** Tags added: verification-done-jammy-linux verification-done-lunar-linux verification-done-mantic-linux -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls 0 cork 0 nodelay 0 sendpage 0 splice 0 urgent data 0 * Instead of including the payload in the wrong >512 KB buckets, the output should be to have 19 reqs in the 8 KB buckets for TX stats and 9 reqs in the 8 KB bucket for RX stats. [Where problems could occur] * The changes are in common code /net/smc/smc_stats.h hence any potential negativ impact is not limited to a specific platform. but limited to statistics for shared memory communication (SMC) hardware statistics. * But limited to the functions SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB.
[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
Thx @Boris and @Wenjia - I'll update the tags accordingly ... -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls 0 cork 0 nodelay 0 sendpage 0 splice 0 urgent data 0 * Instead of including the payload in the wrong >512 KB buckets, the output should be to have 19 reqs in the 8 KB buckets for TX stats and 9 reqs in the 8 KB bucket for RX stats. [Where problems could occur] * The changes are in common code /net/smc/smc_stats.h hence any potential negativ impact is not limited to a specific platform. but limited to statistics for shared memory communication (SMC) hardware statistics. * But limited to the functions SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB. * The bucket (aka pos) calculation is not that trivial, issues here
[Kernel-packages] [Bug 2039575] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2023-11-28 08:14 EDT--- Thanks you @Wenjia for successfully verifying that the updated kernels in -proposed for jammy, lunar and mantic solve the problem. With that, we can change / add the tags accordingly to: verification-done-jammy verification-done-lunar verification-done-mantic Thanks everyone for all your work. -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls 0 cork 0 nodelay 0 sendpage 0 splice 0 urgent data 0 * Instead of including the payload in the wrong >512 KB buckets, the output should be to have 19 reqs in the 8 KB buckets for TX stats and 9 reqs in the 8 KB bucket for RX stats. [Where problems could occur] * The changes are in common code /net/smc/smc_stats.h hence any potential negativ
[Kernel-packages] [Bug 2029281] Re: Soundwire support for Dell SKU0C87 devices
This bug was fixed in the package firmware-sof - 2.0-1ubuntu4.4
---
firmware-sof (2.0-1ubuntu4.4) jammy; urgency=medium
* Soundwire support for Dell SKU0C87 devices. LP: #2029281
- Add sof-v2.7 for Intel Meteor Lake hardware.
- Add more sof-v2.7.1 Intel MTL binaries
firmware-sof (2.0-1ubuntu4.3) jammy; urgency=medium
* Add RPL topology updates
- UBUNTU: SAUCE: Add topology updates for Intel RPL Dell 0C11 SKU.
(LP: #2038263)
-- Dimitri John Ledkov Fri, 17 Nov 2023
12:13:11 +
** Changed in: firmware-sof (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2029281
Title:
Soundwire support for Dell SKU0C87 devices
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Released
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Fix Released
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2029281
== firmware-sof ==
[Impact]
Missing soundwire firmware support for Intel MTL deivces.
[Fix]
Depends on sof-bin v2.7.1 release from
https://github.com/thesofproject/sof-bin/tree/v2023.09.1. Two commits
specifically:
*
https://github.com/thesofproject/sof-bin/commit/ad8dfcc182d3e0a5ce06a7fe9ed7717a04cad06b
("Add sof-v2.7 for Intel Meteor Lake hardware")
*
https://github.com/thesofproject/sof-bin/commit/5f010669084d64df29d77a436b6ffa0095565668
("Add more sof-v2.7.1 Intel MTL binaries")
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so oem-6.5/jammy is the target
series, and Mantic for best effort MTL support. Noble is also
nominated of course.
== linux ==
[Impact]
Missing soundwire support for Dell SKU0C87 deivces.
[Fix]
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so only OEM-6.5, Mantic, and
Unstable are nominated for fix.
== original bug description ==
kernel: sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4
kernel: sof-audio-pci-intel-mtl :00:1f.3: Direct firmware load for
intel/sof-ipc4/mtl/sof-mtl.ri failed with error -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof firmware file is
missing, you might need to
kernel: sof-audio-pci-intel-mtl :00:1f.3: download it from
https://github.com/thesofproject/sof-bin/
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: failed to load DSP
firmware -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof_probe_work failed
err: -2
kernel: kauditd_printk_skb: 33 callbacks suppressed
Required fixes:
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2029281/+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 2029281] Update Released
The verification of the Stable Release Update for firmware-sof 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 linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2029281
Title:
Soundwire support for Dell SKU0C87 devices
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Released
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Fix Released
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2029281
== firmware-sof ==
[Impact]
Missing soundwire firmware support for Intel MTL deivces.
[Fix]
Depends on sof-bin v2.7.1 release from
https://github.com/thesofproject/sof-bin/tree/v2023.09.1. Two commits
specifically:
*
https://github.com/thesofproject/sof-bin/commit/ad8dfcc182d3e0a5ce06a7fe9ed7717a04cad06b
("Add sof-v2.7 for Intel Meteor Lake hardware")
*
https://github.com/thesofproject/sof-bin/commit/5f010669084d64df29d77a436b6ffa0095565668
("Add more sof-v2.7.1 Intel MTL binaries")
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so oem-6.5/jammy is the target
series, and Mantic for best effort MTL support. Noble is also
nominated of course.
== linux ==
[Impact]
Missing soundwire support for Dell SKU0C87 deivces.
[Fix]
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so only OEM-6.5, Mantic, and
Unstable are nominated for fix.
== original bug description ==
kernel: sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4
kernel: sof-audio-pci-intel-mtl :00:1f.3: Direct firmware load for
intel/sof-ipc4/mtl/sof-mtl.ri failed with error -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof firmware file is
missing, you might need to
kernel: sof-audio-pci-intel-mtl :00:1f.3: download it from
https://github.com/thesofproject/sof-bin/
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: failed to load DSP
firmware -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof_probe_work failed
err: -2
kernel: kauditd_printk_skb: 33 callbacks suppressed
Required fixes:
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2029281/+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 2029281] Re: Soundwire support for Dell SKU0C87 devices
This bug was fixed in the package firmware-sof - 2.2.6-1ubuntu1.2
---
firmware-sof (2.2.6-1ubuntu1.2) mantic; urgency=medium
* Soundwire support for Dell SKU0C87 devices. LP: #2029281
- Add sof-v2.7 for Intel Meteor Lake hardware.
- Add more sof-v2.7.1 Intel MTL binaries
-- Dimitri John Ledkov Fri, 17 Nov 2023
16:32:36 +
** Changed in: firmware-sof (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2029281
Title:
Soundwire support for Dell SKU0C87 devices
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Released
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Fix Released
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2029281
== firmware-sof ==
[Impact]
Missing soundwire firmware support for Intel MTL deivces.
[Fix]
Depends on sof-bin v2.7.1 release from
https://github.com/thesofproject/sof-bin/tree/v2023.09.1. Two commits
specifically:
*
https://github.com/thesofproject/sof-bin/commit/ad8dfcc182d3e0a5ce06a7fe9ed7717a04cad06b
("Add sof-v2.7 for Intel Meteor Lake hardware")
*
https://github.com/thesofproject/sof-bin/commit/5f010669084d64df29d77a436b6ffa0095565668
("Add more sof-v2.7.1 Intel MTL binaries")
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so oem-6.5/jammy is the target
series, and Mantic for best effort MTL support. Noble is also
nominated of course.
== linux ==
[Impact]
Missing soundwire support for Dell SKU0C87 deivces.
[Fix]
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so only OEM-6.5, Mantic, and
Unstable are nominated for fix.
== original bug description ==
kernel: sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4
kernel: sof-audio-pci-intel-mtl :00:1f.3: Direct firmware load for
intel/sof-ipc4/mtl/sof-mtl.ri failed with error -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof firmware file is
missing, you might need to
kernel: sof-audio-pci-intel-mtl :00:1f.3: download it from
https://github.com/thesofproject/sof-bin/
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: failed to load DSP
firmware -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof_probe_work failed
err: -2
kernel: kauditd_printk_skb: 33 callbacks suppressed
Required fixes:
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2029281/+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 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11
This bug was fixed in the package firmware-sof - 2.0-1ubuntu4.4 --- firmware-sof (2.0-1ubuntu4.4) jammy; urgency=medium * Soundwire support for Dell SKU0C87 devices. LP: #2029281 - Add sof-v2.7 for Intel Meteor Lake hardware. - Add more sof-v2.7.1 Intel MTL binaries firmware-sof (2.0-1ubuntu4.3) jammy; urgency=medium * Add RPL topology updates - UBUNTU: SAUCE: Add topology updates for Intel RPL Dell 0C11 SKU. (LP: #2038263) -- Dimitri John Ledkov Fri, 17 Nov 2023 12:13:11 + ** Changed in: firmware-sof (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038263 Title: Add SoF topology support on Intel RaptorLake DELL SKU 0C11 Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Released Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Won't Fix Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: SRU Jusitification for firmware-sof [Impact] To support audio functions on RPL Dell SKU 0C11, it requires the topology file from sof-tplg-v2.2.7 [Fix] Pull the sof-rpl-rt711-l0-rt1316-l12.tplg from https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Test Case] Install the fixes on the target platform(RPL Dell SKU 0C11) and verify the audio function. 1. Install the firmware-sof on platform(RPL) Dell SKU 0C11 2. Make sure the audio output/input devices are not dummy in audio settings. [Where problems could occur] New firmware is only for the RPL platforms which requires the specific topology file. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Impact] Audio play/capture are not functional on specific Dell machines of Intel RPL platforms [Fix] Backport the fix from Intel in https://github.com/thesofproject/linux [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy` shown on the Audio output/input option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038263/+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 1495124] Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x2000000.
Launchpad has imported 2 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=104461. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2015-09-12T17:54:32+00:00 caravena wrote: Open bug in launchpad.net : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495124 dmesg: [ 1739.516411] iwlwifi :01:00.0: Microcode SW error detected. Restarting 0x200. [ 1739.516426] iwlwifi :01:00.0: CSR values: [ 1739.516435] iwlwifi :01:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [ 1739.516447] iwlwifi :01:00.0:CSR_HW_IF_CONFIG_REG: 0X00484b00 [ 1739.516458] iwlwifi :01:00.0: CSR_INT_COALESCING: 0Xff40 [ 1739.516469] iwlwifi :01:00.0: CSR_INT: 0X [ 1739.516479] iwlwifi :01:00.0:CSR_INT_MASK: 0X [ 1739.516491] iwlwifi :01:00.0: CSR_FH_INT_STATUS: 0X [ 1739.516502] iwlwifi :01:00.0: CSR_GPIO_IN: 0X0038 [ 1739.516513] iwlwifi :01:00.0: CSR_RESET: 0X [ 1739.516525] iwlwifi :01:00.0:CSR_GP_CNTRL: 0X080403c5 [ 1739.516537] iwlwifi :01:00.0: CSR_HW_REV: 0X00b0 [ 1739.516549] iwlwifi :01:00.0: CSR_EEPROM_REG: 0Xc4540ffd [ 1739.516561] iwlwifi :01:00.0: CSR_EEPROM_GP: 0X9801 [ 1739.516572] iwlwifi :01:00.0: CSR_OTP_GP_REG: 0X00030001 [ 1739.516583] iwlwifi :01:00.0: CSR_GIO_REG: 0X00080044 [ 1739.516594] iwlwifi :01:00.0:CSR_GP_UCODE_REG: 0Xf3ad [ 1739.516605] iwlwifi :01:00.0: CSR_GP_DRIVER_REG: 0X [ 1739.516617] iwlwifi :01:00.0: CSR_UCODE_DRV_GP1: 0X [ 1739.516628] iwlwifi :01:00.0: CSR_UCODE_DRV_GP2: 0X [ 1739.516639] iwlwifi :01:00.0: CSR_LED_REG: 0X0040 [ 1739.516651] iwlwifi :01:00.0:CSR_DRAM_INT_TBL_REG: 0X880c9dea [ 1739.516662] iwlwifi :01:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200 [ 1739.516674] iwlwifi :01:00.0: CSR_ANA_PLL_CFG: 0X [ 1739.516685] iwlwifi :01:00.0: CSR_MONITOR_STATUS_REG: 0X43f7ff57 [ 1739.516697] iwlwifi :01:00.0: CSR_HW_REV_WA_REG: 0X0001001a [ 1739.516708] iwlwifi :01:00.0:CSR_DBG_HPET_MEM_REG: 0X [ 1739.516716] iwlwifi :01:00.0: FH register values: [ 1739.516739] iwlwifi :01:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0c9e4600 [ 1739.516760] iwlwifi :01:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00c9e440 [ 1739.516781] iwlwifi :01:00.0: FH_RSCSR_CHNL0_WPTR: 0X00e0 [ 1739.516802] iwlwifi :01:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114 [ 1739.516822] iwlwifi :01:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc [ 1739.516843] iwlwifi :01:00.0:FH_MEM_RSSR_RX_STATUS_REG: 0X0703 [ 1739.516864] iwlwifi :01:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [ 1739.516885] iwlwifi :01:00.0:FH_TSSR_TX_STATUS_REG: 0X07ff0001 [ 1739.516906] iwlwifi :01:00.0: FH_TSSR_TX_ERROR_REG: 0X [ 1739.516916] iwlwifi :01:00.0: Loaded firmware version: 18.168.6.1 [ 1739.517047] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 1739.517055] iwlwifi :01:00.0: Status: 0x02CC, count: 6 [ 1739.517063] iwlwifi :01:00.0: 0x198A | ADVANCED_SYSASSERT [ 1739.517070] iwlwifi :01:00.0: 0x00015920 | uPc [ 1739.517076] iwlwifi :01:00.0: 0x00015910 | branchlink1 [ 1739.517082] iwlwifi :01:00.0: 0x00015910 | branchlink2 [ 1739.517088] iwlwifi :01:00.0: 0xDBEA | interruptlink1 [ 1739.517094] iwlwifi :01:00.0: 0x | interruptlink2 [ 1739.517100] iwlwifi :01:00.0: 0x0457 | data1 [ 1739.517107] iwlwifi :01:00.0: 0x0001 | data2 [ 1739.517114] iwlwifi :01:00.0: 0x01DC | line [ 1739.517121] iwlwifi :01:00.0: 0x8080E6B3 | beacon time [ 1739.517127] iwlwifi :01:00.0: 0x6723C94D | tsf low [ 1739.517134] iwlwifi :01:00.0: 0x | tsf hi [ 1739.517141] iwlwifi :01:00.0: 0x | time gp1 [ 1739.517147] iwlwifi :01:00.0: 0x672BAF8D | time gp2 [ 1739.517154] iwlwifi :01:00.0: 0x | time gp3 [ 1739.517161] iwlwifi :01:00.0: 0x754312A8 | uCode version [ 1739.517168] iwlwifi :01:00.0: 0x00B0 | hw version [ 1739.517176] iwlwifi :01:00.0: 0x00484B00 | board version [ 1739.517183] iwlwifi :01:00.0: 0x001C | hcmd [ 1739.517190] iwlwifi :01:00.0: 0x2F863000 | isr0 [ 1739.517198] iwlwifi :01:00.0: 0x1189F800 | isr1 [ 1739.517205] iwlwifi :01:00.0: 0x0E02 | isr2 [
[Kernel-packages] [Bug 2044003] Re: Don't produce linux-*-tools-{common, host} binary packages
** Also affects: linux-nvidia-6.2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-lowlatency (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-lowlatency-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-ibm (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-intel-iotg-5.15 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-iot (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-lowlatency-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-lowlatency-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-realtime (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-realtime (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-lowlatency (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-nvidia (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-iot (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-ibm (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe-5.15 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-intel-iotg-5.15 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-lowlatency-hwe-5.15 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-laptop (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-nvidia-6.2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-lowlatency-hwe-6.2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe-6.5 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-lowlatency-hwe-6.5 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-realtime (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-lowlatency (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-nvidia (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-iot (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-ibm (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-hwe-5.15 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-intel-iotg-5.15 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-lowlatency-hwe-5.15 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-laptop (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-nvidia-6.2 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-lowlatency-hwe-6.2 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-hwe-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-lowlatency-hwe-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: linux-bluefield (Ubuntu Focal) ** No longer affects: linux-bluefield (Ubuntu Mantic) ** No longer affects:
[Kernel-packages] [Bug 2044643] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-nvidia-6.2-tools-common
*** This bug is a duplicate of bug 2044003 ***
https://bugs.launchpad.net/bugs/2044003
** This bug has been marked a duplicate of bug 2044003
Don't produce linux-*-tools-{common,host} binary packages
--
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/2044643
Title:
package linux-tools-common (not installed) failed to install/upgrade:
trying to overwrite '/usr/bin/acpidbg', which is also in package
linux-nvidia-6.2-tools-common 6.2.0-1003.3~22.04.1
Status in linux package in Ubuntu:
New
Bug description:
linux-tools-common installs tools for kernel 5.15, and this conflicts
with kernel 6.2 nvidia tools.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-tools-common (not installed)
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
linux-tools-common:amd64: Install
linux-hwe-6.2-tools-6.2.0-37:amd64: Install
linux-tools-6.2.0-37-generic:amd64: Install
NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: serge 2070 F pulseaudio
/dev/snd/controlC0: serge 2070 F pulseaudio
/dev/snd/controlC1: serge 2070 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sun Nov 26 11:41:24 2023
DpkgTerminalLog:
Preparing to unpack .../linux-tools-common_5.15.0-89.99_all.deb ...
Unpacking linux-tools-common (5.15.0-89.99) ...
[1mdpkg:[0m error processing archive
/var/cache/apt/archives/linux-tools-common_5.15.0-89.99_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package
linux-nvidia-6.2-tools-common 6.2.0-1003.3~22.04.1
ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in
package linux-nvidia-6.2-tools-common 6.2.0-1003.3~22.04.1
InstallationDate: Installed on 2023-11-25 (0 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: Micro-Star International Co., Ltd. Titan GT77HX 13VI
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic
root=UUID=2c5910f0-f5b7-4403-9a5b-e432cf0bba22 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal,
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
SourcePackage: linux
Title: package linux-tools-common (not installed) failed to install/upgrade:
trying to overwrite '/usr/bin/acpidbg', which is also in package
linux-nvidia-6.2-tools-common 6.2.0-1003.3~22.04.1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/19/2023
dmi.bios.release: 1.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: E17Q2IMS.111
dmi.board.asset.tag: Default string
dmi.board.name: MS-17Q2
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17Q2IMS.111:bd10/19/2023:br1.17:svnMicro-StarInternationalCo.,Ltd.:pnTitanGT77HX13VI:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17Q2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17Q2.1:
dmi.product.family: GT
dmi.product.name: Titan GT77HX 13VI
dmi.product.sku: 17Q2.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044643/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
This issue never happened to me with my 3x FHD setup at work, but now I
am working from home with 2x 4K and 1x FHD and I am getting constant
corruptions.
--
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/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 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.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+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 2041702] Re: Jammy update: v5.15.132 upstream stable release
Skipped "USB: core: Fix oversight in SuperSpeed initialization" since we
already picked that to fix a regression.
Skipped "net/tls: do not free tls_rec on async operation in
bpf_exec_tx_verdict()" because it is already applied as CVE-2023-6176.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6176
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/2041702
Title:
Jammy update: v5.15.132 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.132 upstream stable release
from git://git.kernel.org/
ARM: dts: imx: update sdma node name format
ARM: dts: imx7s: Drop dma-apb interrupt-names
ARM: dts: imx: Adjust dma-apbh node name
ARM: dts: imx: Set default tuning step for imx7d usdhc
phy: qcom-snps-femto-v2: use qcom_snps_hsphy_suspend/resume error code
media: pulse8-cec: handle possible ping error
media: pci: cx23885: fix error handling for cx23885 ATSC boards
9p: virtio: make sure 'offs' is initialized in zc_request
ksmbd: fix out of bounds in smb3_decrypt_req()
ksmbd: no response from compound read
ASoC: da7219: Flush pending AAD IRQ when suspending
ASoC: da7219: Check for failure reading AAD IRQ events
ethernet: atheros: fix return value check in atl1c_tso_csum()
vxlan: generalize vxlan_parse_gpe_hdr and remove unused args
m68k: Fix invalid .section syntax
s390/dasd: use correct number of retries for ERP requests
s390/dasd: fix hanging device after request requeue
fs/nls: make load_nls() take a const parameter
ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
ASoc: codecs: ES8316: Fix DMIC config
ASoC: rt711: fix for JD event handling in ClockStop Mode0
ASoC: rt711-sdca: fix for JD event handling in ClockStop Mode0
ASoC: atmel: Fix the 8K sample parameter in I2SC master
platform/x86: intel: hid: Always call BTNL ACPI method
platform/x86/intel/hid: Add HP Dragonfly G2 to VGBS DMI quirks
platform/x86: huawei-wmi: Silence ambient light sensor
drm/amd/display: Exit idle optimizations before attempt to access PHY
ovl: Always reevaluate the file signature for IMA
ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
security: keys: perform capable check only on privileged operations
kprobes: Prohibit probing on CFI preamble symbol
clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
vmbus_testing: fix wrong python syntax for integer value comparison
net: usb: qmi_wwan: add Quectel EM05GV2
wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1()
idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
scsi: lpfc: Remove reftag check in DIF paths
scsi: qedi: Fix potential deadlock on _percpu->p_work_lock
net: hns3: restore user pause configure when disable autoneg
drm/amdgpu: Match against exact bootloader status
netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
bnx2x: fix page fault following EEH recovery
sctp: handle invalid error codes without calling BUG()
scsi: storvsc: Always set no_report_opcodes
scsi: lpfc: Fix incorrect big endian type assignment in bsg loopback path
ALSA: seq: oss: Fix racy open/close of MIDI devices
tracing: Introduce pipe_cpumask to avoid race on trace_pipes
platform/mellanox: Fix mlxbf-tmfifo not handling all virtio CONSOLE
notifications
arm64: lib: Import latest version of Arm Optimized Routines' strncmp
of: kexec: Mark ima_{free,stable}_kexec_buffer() as __init
udf: Check consistency of Space Bitmap Descriptor
udf: Handle error when adding extent to a file
Revert "net: macsec: preserve ingress frame ordering"
reiserfs: Check the return value from __getblk()
eventfd: prevent underflow for eventfd semaphores
fs: Fix error checking for d_hash_and_lookup()
tmpfs: verify {g,u}id mount options correctly
selftests/harness: Actually report SKIP for signal tests
ARM: ptrace: Restore syscall restart tracing
ARM: ptrace: Restore syscall skipping for tracers
refscale: Fix uninitalized use of wait_queue_head_t
OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
selftests/resctrl: Make resctrl_tests run using kselftest framework
selftests/resctrl: Add resctrl.h into build deps
selftests/resctrl: Don't leak buffer in
[Kernel-packages] [Bug 2043422] Re: Jammy update: v5.15.133 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/2043422 Title: Jammy update: v5.15.133 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.133 upstream stable release from git://git.kernel.org/ autofs: fix memory leak of waitqueues in autofs_catatonic_mode btrfs: output extra debug info if we failed to find an inline backref locks: fix KASAN: use-after-free in trace_event_raw_event_filelock_lock ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer kernel/fork: beware of __put_task_struct() calling context rcuscale: Move rcu_scale_writer() schedule_timeout_uninterruptible() to _idle() scftorture: Forgive memory-allocation failure if KASAN ACPI: video: Add backlight=native DMI quirk for Lenovo Ideapad Z470 perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 perf/imx_ddr: speed up overflow frequency of cycle hw_breakpoint: fix single-stepping when using bpf_overflow_handler ACPI: x86: s2idle: Catch multiple ACPI_TYPE_PACKAGE objects devlink: remove reload failed checks in params get/set callbacks crypto: lrw,xts - Replace strlcpy with strscpy wifi: ath9k: fix fortify warnings wifi: ath9k: fix printk specifier wifi: mwifiex: fix fortify warning wifi: wil6210: fix fortify warnings crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui() tpm_tis: Resend command to recover from data transfer errors mmc: sdhci-esdhc-imx: improve ESDHC_FLAG_ERR010450 alx: fix OOB-read compiler warning wifi: mac80211: check S1G action frame size netfilter: ebtables: fix fortify warnings in size_entry_mwt() wifi: mac80211_hwsim: drop short frames drm/bridge: tc358762: Instruct DSI host to generate HSE packets arm64: dts: qcom: sm6125-pdx201: correct ramoops pmsg-size arm64: dts: qcom: sm8150-kumano: correct ramoops pmsg-size arm64: dts: qcom: sm8250-edo: correct ramoops pmsg-size samples/hw_breakpoint: Fix kernel BUG 'invalid opcode: ' ALSA: hda: intel-dsp-cfg: add LunarLake support drm/amd/display: Blocking invalid 420 modes on HDMI TMDS for DCN31 drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable() bus: ti-sysc: Configure uart quirks for k3 SoC md: raid1: fix potential OOB in raid1_remove_disk() ext2: fix datatype of block number in ext2_xattr_set2() fs/jfs: prevent double-free in dbUnmount() after failed jfs_remount() jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount ARM: 9317/1: kexec: Make smp stop calls asynchronous powerpc/pseries: fix possible memory leak in ibmebus_bus_init() PCI: fu740: Set the number of MSI vectors media: dvb-usb-v2: af9035: Fix null-ptr-deref in af9035_i2c_master_xfer media: dw2102: Fix null-ptr-deref in dw2102_i2c_transfer() media: af9005: Fix null-ptr-deref in af9005_i2c_xfer media: anysee: fix null-ptr-deref in anysee_master_xfer media: az6007: Fix null-ptr-deref in az6007_i2c_xfer() media: dvb-usb-v2: gl861: Fix null-ptr-deref in gl861_i2c_master_xfer media: tuners: qt1010: replace BUG_ON with a regular error media: pci: cx23885: replace BUG with error return usb: cdns3: Put the cdns set active part outside the spin lock usb: gadget: fsl_qe_udc: validate endpoint index for ch9 udc tools: iio: iio_generic_buffer: Fix some integer type and calculation scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() serial: cpm_uart: Avoid suspicious locking usb: ehci: add workaround for chipidea PORTSC.PEC bug media: pci: ipu3-cio2: Initialise timing struct to avoid a compiler warning kobject: Add sanity check for kset->kobj.ktype in kset_register() interconnect: Fix locking for runpm vs reclaim printk: Consolidate console deferred printing jbd2: refactor wait logic for transaction updates into a common function jbd2: fix use-after-free of transaction_t race jbd2: kill t_handle_lock transaction spinlock jbd2: rename jbd_debug() to jbd2_debug() jbd2: correct the end of the journal recovery scan range mtd: rawnand: brcmnand: Allow SoC to provide I/O operations mtd: rawnand: brcmnand: Fix ECC level field setting for v7.2 controller MIPS: Use "grep -E" instead of "egrep" perf test: Remove bash construct from
[Kernel-packages] [Bug 2044023] Re: Jammy update: v5.15.134 upstream stable release
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/2044023
Title:
Jammy update: v5.15.134 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.134 upstream stable release
from git://git.kernel.org/
NFS: Use the correct commit info in nfs_join_page_group()
NFS: More fixes for nfs_direct_write_reschedule_io()
NFS/pNFS: Report EINVAL errors from connect() to the server
SUNRPC: Mark the cred for revalidation if the server rejects it
NFSv4.1: use EXCHGID4_FLAG_USE_PNFS_DS for DS server
NFSv4.1: fix pnfs MDS=DS session trunking
tracing: Make trace_marker{,_raw} stream-like
tracing: Increase trace array ref count on enable and filter files
ata: ahci: Drop pointless VPRINTK() calls and convert the remaining ones
ata: libahci: clear pending interrupt status
ext4: scope ret locally in ext4_try_to_trim_range()
ext4: change s_last_trim_minblks type to unsigned long
ext4: replace the traditional ternary conditional operator with with
max()/min()
ext4: move setting of trimmed bit into ext4_try_to_trim_range()
ext4: do not let fstrim block system suspend
tracing: Have event inject files inc the trace array ref count
netfilter: nft_set_rbtree: use read spinlock to avoid datapath contention
netfilter: nft_set_pipapo: call nft_trans_gc_queue_sync() in catchall GC
netfilter: nft_set_pipapo: stop GC iteration if GC transaction allocation
fails
netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration
netfilter: nf_tables: fix memleak when more than 255 elements expired
ASoC: meson: spdifin: start hw on dai probe
netfilter: nf_tables: disallow element removal on anonymous sets
bpf: Avoid deadlock when using queue and stack maps from NMI
selftests: tls: swap the TX and RX sockets in some tests
net/core: Fix ETH_P_1588 flow dissector
ASoC: imx-audmix: Fix return error with devm_clk_get()
iavf: do not process adminq tasks when __IAVF_IN_REMOVE_TASK is set
i40e: Add VF VLAN pruning
i40e: Fix VF VLAN offloading when port VLAN is configured
ionic: fix 16bit math issue when PAGE_SIZE >= 64KB
igc: Fix infinite initialization loop with early XDP redirect
powerpc/perf/hv-24x7: Update domain value check
dccp: fix dccp_v4_err()/dccp_v6_err() again
platform/x86: intel_scu_ipc: Check status after timeout in busy_loop()
platform/x86: intel_scu_ipc: Check status upon timeout in
ipc_wait_for_interrupt()
platform/x86: intel_scu_ipc: Don't override scu in
intel_scu_ipc_dev_simple_command()
platform/x86: intel_scu_ipc: Fail IPC send if still busy
x86/srso: Fix srso_show_state() side effect
x86/srso: Fix SBPB enablement for spec_rstack_overflow=off
net: hns3: fix GRE checksum offload issue
net: hns3: only enable unicast promisc when mac table full
net: hns3: fix fail to delete tc flower rules during reset issue
net: hns3: add 5ms delay before clear firmware reset irq source
net: bridge: use DEV_STATS_INC()
team: fix null-ptr-deref when team device type is changed
net: rds: Fix possible NULL-pointer dereference
netfilter: nf_tables: disable toggling dormant table state more than once
locking/seqlock: Do the lockdep annotation before locking in
do_write_seqcount_begin_nested()
net: ena: Flush XDP packets on error.
bnxt_en: Flush XDP for bnxt_poll_nitroa0()'s NAPI
igc: Expose tx-usecs coalesce setting to user
Fix up backport of 136191703038 ("interconnect: Teach lockdep about
icc_bw_lock order")
gpio: tb10x: Fix an error handling path in tb10x_gpio_probe()
i2c: mux: demux-pinctrl: check the return value of devm_kstrdup()
i2c: mux: gpio: Replace custom acpi_get_local_address()
i2c: mux: gpio: Add missing fwnode_handle_put()
xfs: bound maximum wait time for inodegc work
xfs: introduce xfs_inodegc_push()
xfs: explicitly specify cpu when forcing inodegc delayed work to run
immediately
xfs: check that per-cpu inodegc workers actually run on that cpu
xfs: disable reaping in fscounters scrub
xfs: fix xfs_inodegc_stop racing with mod_delayed_work
Input: i8042 - rename i8042-x86ia64io.h to i8042-acpipnpio.h
Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
netfilter: exthdr: add support for tcp option removal
netfilter: nft_exthdr: Fix
[Kernel-packages] [Bug 2044600] Re: package linux-hwe-5.15-headers-5.15.0-89 5.15.0-89.99~20.04.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/src/linux-hwe-5.15-head
Not exactly sure what you're trying to say but are you running any antivirus programs? They tend to cause these kind of issues. ** Changed in: linux-hwe-5.15 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2044600 Title: package linux-hwe-5.15-headers-5.15.0-89 5.15.0-89.99~20.04.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/src/linux-hwe-5.15-headers-5.15.0-89/lib/Kconfig.debug' a '/usr/src/linux-hwe-5.15-headers-5.15.0-89/lib/Kconfig.debug.dpkg- new': fin de fichero o de flujo inesperado Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: i tried to repai with simantec by reinstalling broken packges bit the error continues ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-hwe-5.15-headers-5.15.0-89 5.15.0-89.99~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126 Uname: Linux 5.15.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 23 20:04:57 2023 ErrorMessage: no se pudieron copiar los datos extraídos de './usr/src/linux-hwe-5.15-headers-5.15.0-89/lib/Kconfig.debug' a '/usr/src/linux-hwe-5.15-headers-5.15.0-89/lib/Kconfig.debug.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2023-09-12 (73 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: linux-hwe-5.15 Title: package linux-hwe-5.15-headers-5.15.0-89 5.15.0-89.99~20.04.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/src/linux-hwe-5.15-headers-5.15.0-89/lib/Kconfig.debug' a '/usr/src/linux-hwe-5.15-headers-5.15.0-89/lib/Kconfig.debug.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2044600/+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 2044657] Re: zfs block cloning file system corruption
zfs-linux (2.2.1-0ubuntu1) noble; urgency=medium * New upstream release. Uploaded. But I don't want to close this bug report, because it is not clear if that is everything yet or not. -- 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/2044657 Title: zfs block cloning file system corruption Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
I think we have some options to fix this. Yet, which would be a solution that could be packaged? If I understand https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html correctly there are the following options: Keep the GPU-Memory Running === Pro: * Only need to set a kernel module parameter Con: * Only works in S2 * Uses more power than necessary (at least if more than 256 MB graphic memory are used) * Does not work with suspend-to-disk (at least if I understood things right) Copy Memory to tmpfs Dump the graphic-memory into tmpfs. I wouldn't suggest using /run, but creating a driver-specific tmpfs that is large enough to hold the graphic memory. Pro: * Just works, as the kernel takes care of paging the tmpfs to disk in case of stand-by or suspend-to-disk. Con: * Delayed suspend and wakeup * Unexpected swap-usage -> OOM-Killer might kick in on suspend if there is not enough or no swap. Get everyone to work around it == Get all the affected applications to update their video-memory after suspend-to-X. Pro: * Does not have any of the Cons of the other solutions Con: * Probably very tedious. Keep it as it is Pro: * Minimal effort * Kind of works most of the time. Con: * Nobody is really happy. Comments? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: New Status in Mutter: Fix Released Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-460 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-525 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-535 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on
[Kernel-packages] [Bug 2044573] Re: Unable to upgrade from Ubuntu 22.o4 to Ubuntu 23.04
** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2044573 Title: Unable to upgrade from Ubuntu 22.o4 to Ubuntu 23.04 Status in linux-signed-hwe-6.2 package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Trying to upgrade Ubuntu to version 23.04 and I keep facing this issue. Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist- upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 24 16:55:54 2023 InstallationDate: Installed on 2023-11-23 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2023-11-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2044573/+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 2042884] Re: Lunar update: upstream stable patchset 2023-11-06
Skipped "USB: core: Fix oversight in SuperSpeed initialization" as we
already applied that one to fix the regression caused by "USB: core:
Unite old scheme and new scheme descriptor reads".
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Fix Committed
--
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/2042884
Title:
Lunar update: upstream stable patchset 2023-11-06
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Lunar:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2023-11-06
Ported from the following upstream stable releases:
v6.1.53, v6.4.16
from git://git.kernel.org/
Partially revert "drm/amd/display: Fix possible underflow for displays with
large vblank"
Revert "Revert drm/amd/display: Enable Freesync Video Mode by default"
powerpc/boot: Disable power10 features after BOOTAFLAGS assignment
media: uapi: HEVC: Add num_delta_pocs_of_ref_rps_idx field
Revert "MIPS: unhide PATA_PLATFORM"
phy: qcom-snps-femto-v2: use qcom_snps_hsphy_suspend/resume error code
media: amphion: use dev_err_probe
media: pulse8-cec: handle possible ping error
media: pci: cx23885: fix error handling for cx23885 ATSC boards
9p: virtio: fix unlikely null pointer deref in handle_rerror
9p: virtio: make sure 'offs' is initialized in zc_request
ksmbd: fix out of bounds in smb3_decrypt_req()
ksmbd: validate session id and tree id in compound request
ksmbd: no response from compound read
ksmbd: fix out of bounds in init_smb2_rsp_hdr()
ASoC: da7219: Flush pending AAD IRQ when suspending
ASoC: da7219: Check for failure reading AAD IRQ events
ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect
ethernet: atheros: fix return value check in atl1c_tso_csum()
m68k: Fix invalid .section syntax
s390/dasd: use correct number of retries for ERP requests
s390/dasd: fix hanging device after request requeue
fs/nls: make load_nls() take a const parameter
ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
ASoc: codecs: ES8316: Fix DMIC config
ASoC: rt711: fix for JD event handling in ClockStop Mode0
ASoC: rt711-sdca: fix for JD event handling in ClockStop Mode0
ASoC: atmel: Fix the 8K sample parameter in I2SC master
ALSA: usb-audio: Add quirk for Microsoft Modern Wireless Headset
platform/x86: intel: hid: Always call BTNL ACPI method
platform/x86/intel/hid: Add HP Dragonfly G2 to VGBS DMI quirks
platform/x86: think-lmi: Use kfree_sensitive instead of kfree
platform/x86: asus-wmi: Fix setting RGB mode on some TUF laptops
platform/x86: huawei-wmi: Silence ambient light sensor
drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr Clock
drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family
drm/amd/display: Exit idle optimizations before attempt to access PHY
ovl: Always reevaluate the file signature for IMA
ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
ALSA: usb-audio: Update for native DSD support quirks
staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER
security: keys: perform capable check only on privileged operations
kprobes: Prohibit probing on CFI preamble symbol
clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
vmbus_testing: fix wrong python syntax for integer value comparison
Revert "wifi: ath6k: silence false positive -Wno-dangling-pointer warning on
GCC 12"
net: dsa: microchip: KSZ9477 register regmap alignment to 32 bit boundaries
net: annotate data-races around sk->sk_{rcv|snd}timeo
net: usb: qmi_wwan: add Quectel EM05GV2
wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1()
powerpc/powermac: Use early_* IO variants in via_calibrate_decr()
idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
platform/x86/amd/pmf: Fix unsigned comparison with less than zero
scsi: lpfc: Remove reftag check in DIF paths
scsi: qedi: Fix potential deadlock on _percpu->p_work_lock
net: hns3: restore user pause configure when disable autoneg
drm/amdgpu: Match against exact bootloader status
wifi: cfg80211: remove links only on AP
wifi: mac80211: Use active_links instead of valid_links in Tx
netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
bnx2x: fix page fault following EEH recovery
cifs: fix sockaddr comparison
[Kernel-packages] [Bug 2039368] Re: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
uppon further inspection, the amdgpu traces are: > journalctl -k --grep UBSAN -ojson --output-fields=MESSAGE |jq -r .MESSAGE > |uniq UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1249:61 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1251:44 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1249:46 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1221:34 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1222:44 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1221:19 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1278:45 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1279:65 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1280:9 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1303:44 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1304:64 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1305:9 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:394:34 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:395:4 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:397:19 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1500:42 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1501:42 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1502:42 UBSAN: array-index-out-of-bounds in /build/linux-X4HRYL/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:929:40 I'm afraid they may be related to the kernel KSSP shenanigans landing in amdgpu, and not related at all to bcache (they just happen to be be USBSAN errors too). Should I open a separate bug report? -- 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/2039368 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 Status in linux package in Ubuntu: Confirmed Bug description: Since I upgraded from lunar to mantic I get a load of those errors (41 on a fresh boot) in dmesg: ``` [4.277343] UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 [4.277728] index 4 is out of range for type 'btree_iter_set [4]' [4.277925] CPU: 7 PID: 247 Comm: kworker/7:1 Not tainted 6.5.0-9-generic #9-Ubuntu [4.278132] Hardware name: Default string Default string/Default string, BIOS WRX80SU8-F6 06/08/2023 [4.278531] Workqueue: events register_cache_worker [bcache] [4.278754] Call Trace: [4.278949] [4.279143] dump_stack_lvl+0x48/0x70 [4.279337] dump_stack+0x10/0x20 [4.279526] __ubsan_handle_out_of_bounds+0xc6/0x110 [4.279721] bch_btree_iter_push+0x4e6/0x4f0 [bcache] [4.279929] bch_btree_node_read_done+0xcb/0x410 [bcache] [4.280142] bch_btree_node_read+0xf8/0x1e0 [bcache] [4.280349] ? __pfx_closure_sync_fn+0x10/0x10 [bcache] [4.280557] bch_btree_node_get.part.0+0x15c/0x330 [bcache] [4.280764] ? __bch_btree_ptr_invalid+0x66/0xe0 [bcache] [4.280975] ? __pfx_up_write+0x10/0x10 [4.281170] bch_btree_node_get+0x16/0x30 [bcache] [4.281375] run_cache_set+0x596/0x850 [bcache] [4.281578] ? srso_return_thunk+0x5/0x10 [4.281773] register_cache_set+0x1a2/0x210 [bcache] [4.281984] register_cache+0x11a/0x1a0 [bcache] [4.282187] register_cache_worker+0x22/0x80 [bcache] [4.282387] process_one_work+0x223/0x440 [4.282573] worker_thread+0x4d/0x3f0 [
[Kernel-packages] [Bug 2041999] Re: Mantic update: v6.5.4 upstream stable release
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- 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/2041999 Title: Mantic update: v6.5.4 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.5.4 upstream stable release from git://git.kernel.org/ net/ipv6: SKB symmetric hash should incorporate transport ports drm/virtio: Conditionally allocate virtio_gpu_fence scsi: ufs: core: Add advanced RPMB support where UFSHCI 4.0 does not support EHS length in UTRD scsi: qla2xxx: Adjust IOCB resource on qpair create scsi: qla2xxx: Limit TMF to 8 per function scsi: qla2xxx: Fix deletion race condition scsi: qla2xxx: fix inconsistent TMF timeout scsi: qla2xxx: Fix command flush during TMF scsi: qla2xxx: Fix erroneous link up failure scsi: qla2xxx: Turn off noisy message log scsi: qla2xxx: Fix session hang in gnl scsi: qla2xxx: Fix TMF leak through scsi: qla2xxx: Remove unsupported ql2xenabledif option scsi: qla2xxx: Flush mailbox commands on chip reset scsi: qla2xxx: Fix smatch warn for qla_init_iocb_limit() scsi: qla2xxx: Error code did not return to upper layer scsi: qla2xxx: Fix firmware resource tracking null_blk: fix poll request timeout handling kernfs: fix missing kernfs_iattr_rwsem locking fbdev/ep93xx-fb: Do not assign to struct fb_info.dev clk: qcom: camcc-sc7180: fix async resume during probe drm/ast: Fix DRAM init on AST2200 ASoC: tegra: Fix SFC conversion for few rates ARM: dts: samsung: exynos4210-i9100: Fix LCD screen's physical size arm64: tegra: Update AHUB clock parent and rate on Tegra234 arm64: tegra: Update AHUB clock parent and rate clk: qcom: turingcc-qcs404: fix missing resume during probe ARM: dts: qcom: msm8974pro-castor: correct inverted X of touchscreen arm64: dts: qcom: msm8953-vince: drop duplicated touschreen parent interrupt ARM: dts: qcom: msm8974pro-castor: correct touchscreen function names ARM: dts: qcom: msm8974pro-castor: correct touchscreen syna,nosleep-mode arm64: dts: renesas: rzg2l: Fix txdv-skew-psec typos ARM: dts: BCM5301X: Extend RAM to full 256MB for Linksys EA6500 V2 send channel sequence number in SMB3 requests after reconnects memcg: drop kmem.limit_in_bytes mm: hugetlb_vmemmap: fix a race between vmemmap pmd split lib/test_meminit: allocate pages up to order MAX_ORDER Multi-gen LRU: avoid race in inc_min_seq() parisc: led: Fix LAN receive and transmit LEDs parisc: led: Reduce CPU overhead for disk & lan LED computation cifs: update desired access while requesting for directory lease pinctrl: cherryview: fix address_space_handler() argument dt-bindings: clock: xlnx,versal-clk: drop select:false clk: imx: pll14xx: dynamically configure PLL for 393216000/361267200Hz clk: imx: pll14xx: align pdiv with reference manual clk: qcom: gcc-mdm9615: use proper parent for pll0_vote clock soc: qcom: qmi_encdec: Restrict string length in decode clk: qcom: dispcc-sm8450: fix runtime PM imbalance on probe errors clk: qcom: dispcc-sm8550: fix runtime PM imbalance on probe errors clk: qcom: lpasscc-sc7280: fix missing resume during probe clk: qcom: q6sstop-qcs404: fix missing resume during probe clk: qcom: mss-sc7180: fix missing resume during probe NFS: Fix a potential data corruption NFSv4/pnfs: minor fix for cleanup path in nfs4_get_device_info bus: mhi: host: Skip MHI reset if device is in RDDM kbuild: rpm-pkg: define _arch conditionally kbuild: do not run depmod for 'make modules_sign' kbuild: dummy-tools: make MPROFILE_KERNEL checks work on BE tpm_crb: Fix an error handling path in crb_acpi_add() gfs2: Switch to wait_event in gfs2_logd gfs2: low-memory forced flush fixes mailbox: qcom-ipcc: fix incorrect num_chans counting kconfig: fix possible buffer overflow tools/mm: fix undefined reference to pthread_once Input: iqs7222 - configure power mode before triggering ATI perf trace: Really free the evsel->priv area pwm: atmel-tcb: Harmonize resource allocation order pwm: atmel-tcb: Fix resource freeing in error path and remove backlight: lp855x: Initialize PWM state on first brightness change backlight: gpio_backlight: Drop output GPIO direction check for initial power state perf parse-events: Separate YYABORT and YYNOMEM cases perf
[Kernel-packages] [Bug 2043416] Re: Mantic update: v6.5.5 upstream stable release
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- 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/2043416 Title: Mantic update: v6.5.5 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.5.5 upstream stable release from git://git.kernel.org/ iomap: Fix possible overflow condition in iomap_write_delalloc_scan autofs: fix memory leak of waitqueues in autofs_catatonic_mode btrfs: handle errors properly in update_inline_extent_backref() btrfs: output extra debug info if we failed to find an inline backref locks: fix KASAN: use-after-free in trace_event_raw_event_filelock_lock ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer kernel/fork: beware of __put_task_struct() calling context rcuscale: Move rcu_scale_writer() schedule_timeout_uninterruptible() to _idle() scftorture: Forgive memory-allocation failure if KASAN ACPI: video: Add backlight=native DMI quirk for Lenovo Ideapad Z470 platform/chrome: cros_ec_lpc: Remove EC panic shutdown timeout x86/amd_nb: Add PCI IDs for AMD Family 1Ah-based models perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 s390/boot: cleanup number of page table levels setup kselftest/arm64: fix a memleak in zt_regs_run() perf/imx_ddr: speed up overflow frequency of cycle ACPI: video: Add backlight=native DMI quirk for Apple iMac12,1 and iMac12,2 hw_breakpoint: fix single-stepping when using bpf_overflow_handler ACPI: x86: s2idle: Catch multiple ACPI_TYPE_PACKAGE objects selftests/nolibc: fix up kernel parameters support selftests/nolibc: prevent out of bounds access in expect_vfprintf spi: sun6i: add quirk for dual and quad SPI modes support devlink: remove reload failed checks in params get/set callbacks crypto: lrw,xts - Replace strlcpy with strscpy ice: Don't tx before switchdev is fully configured wifi: ath9k: fix fortify warnings wifi: ath9k: fix printk specifier wifi: rtw88: delete timer and free skb queue when unloading wifi: mwifiex: fix fortify warning mt76: mt7921: don't assume adequate headroom for SDIO headers wifi: wil6210: fix fortify warnings can: sun4i_can: Add acceptance register quirk can: sun4i_can: Add support for the Allwinner D1 UBUNTU: [Config] updateconfigs for CAN_SUN4I net: Use sockaddr_storage for getsockopt(SO_PEERNAME). wifi: ath12k: Fix a NULL pointer dereference in ath12k_mac_op_hw_scan() wifi: ath12k: avoid array overflow of hw mode for preferred_hw_mode net/ipv4: return the real errno instead of -EINVAL crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui() Bluetooth: btusb: Add device 0489:e0f5 as MT7922 device Bluetooth: btusb: Add a new VID/PID 0489/e0f6 for MT7922 Bluetooth: btusb: Add new VID/PID 0489/e102 for MT7922 Bluetooth: btusb: Add new VID/PID 04ca/3804 for MT7922 Bluetooth: Fix hci_suspend_sync crash Bluetooth: btusb: Add support for another MediaTek 7922 VID/PID netlink: convert nlk->flags to atomic flags tpm_tis: Resend command to recover from data transfer errors mmc: sdhci-esdhc-imx: improve ESDHC_FLAG_ERR010450 alx: fix OOB-read compiler warning wifi: iwlwifi: pcie: avoid a warning in case prepare card failed wifi: mac80211: check S1G action frame size netfilter: ebtables: fix fortify warnings in size_entry_mwt() wifi: cfg80211: reject auth/assoc to AP with our address wifi: cfg80211: ocb: don't leave if not joined wifi: mac80211: check for station first in client probe wifi: mac80211_hwsim: drop short frames Revert "wifi: mac80211_hwsim: check the return value of nla_put_u32" libbpf: Free btf_vmlinux when closing bpf_object wifi: ath12k: Fix memory leak in rx_desc and tx_desc wifi: ath12k: add check max message length while scanning with extraie Fix nomenclature for USB and PCI wireless devices bpf: Consider non-owning refs trusted bpf: Consider non-owning refs to refcounted nodes RCU protected drm/bridge: tc358762: Instruct DSI host to generate HSE packets drm/edid: Add quirk for OSVR HDK 2.0 drm: bridge: samsung-dsim: Drain command transfer FIFO before transfer arm64: dts: qcom: sm6125-pdx201: correct ramoops pmsg-size arm64: dts: qcom: sm6125-sprout: correct ramoops pmsg-size arm64: dts: qcom: sm6350: correct ramoops pmsg-size arm64: dts: qcom: sm8150-kumano:
[Kernel-packages] [Bug 2044174] Re: Mantic update: v6.5.6 upstream stable release
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- 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/2044174 Title: Mantic update: v6.5.6 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.5.6 upstream stable release from git://git.kernel.org/ NFS: Fix error handling for O_DIRECT write scheduling NFS: Fix O_DIRECT locking issues NFS: More O_DIRECT accounting fixes for error paths NFS: Use the correct commit info in nfs_join_page_group() NFS: More fixes for nfs_direct_write_reschedule_io() NFS/pNFS: Report EINVAL errors from connect() to the server SUNRPC: Mark the cred for revalidation if the server rejects it NFSv4.1: use EXCHGID4_FLAG_USE_PNFS_DS for DS server NFSv4.1: fix pnfs MDS=DS session trunking media: v4l: Use correct dependency for camera sensor drivers media: via: Use correct dependency for camera sensor drivers gfs2: Fix another freeze/thaw hang netfs: Only call folio_start_fscache() one time for each folio btrfs: improve error message after failure to add delayed dir index item btrfs: remove BUG() after failure to insert delayed dir index item ext4: replace the traditional ternary conditional operator with with max()/min() ext4: move setting of trimmed bit into ext4_try_to_trim_range() ext4: do not let fstrim block system suspend netfilter: nft_set_rbtree: use read spinlock to avoid datapath contention netfilter: nft_set_pipapo: call nft_trans_gc_queue_sync() in catchall GC netfilter: nft_set_pipapo: stop GC iteration if GC transaction allocation fails netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration netfilter: nf_tables: fix memleak when more than 255 elements expired ASoC: meson: spdifin: start hw on dai probe netfilter: nf_tables: disallow element removal on anonymous sets bpf: Avoid deadlock when using queue and stack maps from NMI bpf: Avoid dummy bpf_offload_netdev in __bpf_prog_dev_bound_init ALSA: docs: Fix a typo of midi2_ump_probe option for snd-usb-audio ALSA: seq: Avoid delivery of events for disabled UMP groups ASoC: rt5640: Revert "Fix sleep in atomic context" ASoC: rt5640: Fix sleep in atomic context ASoC: rt5640: fix typos ASoC: rt5640: Do not disable/enable IRQ twice on suspend/resume ASoC: rt5640: Enable the IRQ on resume after configuring jack-detect ASoC: rt5640: Fix IRQ not being free-ed for HDA jack detect mode bpf: Fix a erroneous check after snprintf() selftests/bpf: fix unpriv_disabled check in test_verifier ALSA: hda/realtek: Splitting the UX3402 into two separate models netfilter: conntrack: fix extension size table netfilter: nf_tables: Fix entries val in rule reset audit log Compiler Attributes: counted_by: Adjust name and identifier expansion uapi: stddef.h: Fix header guard location uapi: stddef.h: Fix __DECLARE_FLEX_ARRAY for C++ memblock tests: Fix compilation errors. ASoC: SOF: ipc4-topology: fix wrong sizeof argument net: microchip: sparx5: Fix memory leak for vcap_api_rule_add_keyvalue_test() net: microchip: sparx5: Fix memory leak for vcap_api_rule_add_actionvalue_test() net: microchip: sparx5: Fix possible memory leak in vcap_api_encode_rule_test() net: microchip: sparx5: Fix possible memory leaks in test_vcap_xn_rule_creator() net: microchip: sparx5: Fix possible memory leaks in vcap_api_kunit selftests: tls: swap the TX and RX sockets in some tests net/core: Fix ETH_P_1588 flow dissector ALSA: seq: ump: Fix -Wformat-truncation warning ASoC: hdaudio.c: Add missing check for devm_kstrdup ASoC: imx-audmix: Fix return error with devm_clk_get() octeon_ep: fix tx dma unmap len values in SG iavf: do not process adminq tasks when __IAVF_IN_REMOVE_TASK is set ASoC: SOF: core: Only call sof_ops_free() on remove if the probe was successful iavf: add iavf_schedule_aq_request() helper iavf: schedule a request immediately after add/delete vlan i40e: Fix VF VLAN offloading when port VLAN is configured netfilter, bpf: Adjust timeouts of non-confirmed CTs in bpf_ct_insert_entry() ionic: fix 16bit math issue when PAGE_SIZE >= 64KB igc: Fix infinite initialization loop with early XDP redirect scsi: iscsi_tcp: restrict to TCP sockets powerpc/perf/hv-24x7: Update domain value check powerpc/dexcr: Move HASHCHK
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
for Jammy ** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu1.9.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5724133/+files/alsa-ucm-conf_1.2.6.3-1ubuntu1.9.debdiff ** Patch removed: "alsa-ucm-conf_1.2.9-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5722912/+files/alsa-ucm-conf_1.2.9-1ubuntu4.debdiff -- 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/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Released Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+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 2042902] Re: ucm2: soundwire: add rt713 SDCA device
for Lunar ** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu9.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5724132/+files/alsa-ucm-conf_1.2.6.3-1ubuntu9.3.debdiff -- 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/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Released Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+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 2042902] Re: ucm2: soundwire: add rt713 SDCA device
for Mantic ** Patch added: "alsa-ucm-conf_1.2.9-1ubuntu3.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5724131/+files/alsa-ucm-conf_1.2.9-1ubuntu3.1.debdiff -- 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/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Released Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+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 2042902] Re: ucm2: soundwire: add rt713 SDCA device
Thank you, @Christian. Appreciate you taking time to explain all these. I will try to be on IRC next time. I have changed the patch headers. Then dput to my personal PPA and installed that package on laptop successfully. https://launchpad.net/~artur-at- work/+archive/ubuntu/verification/+packages Attaching below the updated files. -- 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/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Released Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+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
