[Kernel-packages] [Bug 1977946] Re: README points to non-existent URL
Link changed to the proposed wiki. pbuilder succeeded, README updated. ** Patch added: "1-0.12.16ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1977946/+attachment/5596248/+files/1-0.12.16ubuntu1.debdiff ** Changed in: ubuntu-fan (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1977946 Title: README points to non-existent URL Status in ubuntu-fan package in Ubuntu: Fix Committed Bug description: /usr/share/doc/ubuntu-fan/README.gz (ubuntu-fan/README) reads: "More information on the Fan, including more detailed configuration information, can be found at http://www.ubuntu.com/fan."; However, the aforementioned URL (with and without trailing dot) does not exist. Is this supposed to point to https://wiki.ubuntu.com/FanNetworking instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1977946/+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 1977946] Re: README points to non-existent URL
** Changed in: ubuntu-fan (Ubuntu) Assignee: (unassigned) => Akbarkhon Variskhanov (kbar) ** Changed in: ubuntu-fan (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1977946 Title: README points to non-existent URL Status in ubuntu-fan package in Ubuntu: In Progress Bug description: /usr/share/doc/ubuntu-fan/README.gz (ubuntu-fan/README) reads: "More information on the Fan, including more detailed configuration information, can be found at http://www.ubuntu.com/fan."; However, the aforementioned URL (with and without trailing dot) does not exist. Is this supposed to point to https://wiki.ubuntu.com/FanNetworking instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1977946/+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 1976533] Re: [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices
This is now in progress based on LP#1978240 "Jammy update: v5.15.39 upstream stable release" hence aligning the status. ** Changed in: ubuntu-z-systems Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress -- 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/1976533 Title: [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: Description: s390/dasd: Fix data corruption for ESE devices Symptom: Filesystem errors and data inconsistency. Problem: Wrong tracks are formatted or the same track is formatted twice. 1. For ESE devices we get an error when accessing an unformatted track. The handling of this error will return zero data for read requests and format the track on demand before writing to it. To do this the code needs to distinguish between read and write requests. This is done with data from the blocklayer request. A pointer to the blocklayer request is stored in the CQR. If there is an error on the device an ERP request is built to do error recovery. While the ERP request is mostly a copy of the original CQR the pointer to the blocklayer request is not copied to not accidentally pass it back to the blocklayer without cleanup. This leads to the error that during ESE handling after an ERP request was built it is not possible to determine the IO direction. This leads to the formatting of a track for read requests which might in turn lead to data corruption. 2. When using alias devices a track might be accessed by multiple requests simultaneously and there is a race window that a track gets formatted twice resulting in data loss. Solution: 1. Return the callback data of the original request in case there are ERP requests build on top of it and thus determine the correct IO direction. 2. Prevent the double format by remembering the amount of formatted tracks when starting a request and comparing this number before actually formatting a track on the fly. If the number has changed there is a chance that the current track was finally formatted in between. As a result do not format the track and restart the current IO to check. Reproduction: Prepare an ESE DASD device using dasdfmt and fdasd. Install any filesystem on the prepared partitions and issue regular I/O using dd or any other tool while Alias DASD devices are set online as well. Upstream-ID: 5b53a405e4658580e1faf7c217db3f55a21ba849 71f3871657370dbbaf942a1c758f64e49a36c70f Problem-ID:198418 Preventive:yes Date: 2022-06-01 Author:hoepp...@linux.ibm.com Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1976533/+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 1978151] Re: Kernel Panic Running Specific Docker Image
*** This bug is a duplicate of bug 1977919 *** https://bugs.launchpad.net/bugs/1977919 ** This bug has been marked a duplicate of bug 1977919 Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1978151 Title: Kernel Panic Running Specific Docker Image Status in linux-gcp package in Ubuntu: New Bug description: This panic occur only on the latest Linux kernel release. * 5.13.0-1030-gcp is broken * 5.13.0-1027-gcp is okay * 5.13.0-1024-gcp is okay Steps to reproduce: 1) Ensure kernel version is 5.13.0-1030-gcp. 2) sudo apt update 3) sudo apt install docker.io 4) sudo docker run releases-docker.jfrog.io/jfrog/artifactory-pro:7.25.7 Expected behavior: The container runs without issue. Actual behavior (the logs got slightly garbled, but): Kernel panics with: [ 1237.492662] kernel BUG at include/linux/fs.h:3104! [ 1237.497925] invalid opcode: [#1] SMP PTI [ 1Jun 9 18:20:15 23b7ootlooptest ker.502540]nel: [ 1237.4926 CPU: 1 PID: 58] 19[2 cut here ]5 C Jun 9omm: 18:20:15 bootlo doptest kernel: [ 1237.492662] keranel BUG at incltude/linux/fs.h:3e No104! Jun 9 18:t2 0:15 bootlooptetst kernel: [ 123ainted 5.13.07.497925] invali1030-gcp #3d opcode: [6~20.04.#1] SMP PTI 1-Ubuntu [ 1237.535282] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [ 1237.545178] RIP: 0010:__fput+0x247/0x250 [ 1237.549477] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 7e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 1237.569173] RSP: 0018:b8b280b0fe18 EFLAGS: 00010246 [ 1237.574909] RAX: RBX: 000a801d RCX: 97f011bf7000 [ 1237.586271] RDX: 97f011ae9280 RSI: 0001 RDI: [ 1237.593886] RBP: b8b280b0fe40 R08: 97f011aef140 R09: 97f022482570 [ 1237.601492] R10: b8b280b0fe18 R11: 97f026038910 R12: 97f026038900 [ 1237.608820] R13: 97f022482570 R14: 97f011ae92a0 R15: 97f0346bbc00 [ 1237.616301] FS: () GS:97f03bd0() knlGS: [ 1237.624680] CS: 0010 DS: ES: CR0: 80050033 [ 1237.630646] CR2: 7f08b7f7eff0 CR3: 00010e810001 CR4: 003706e0 [ 1237.637892] DR0: DR1: DR2: [ 1237.645134] DR3: DR6: fffe0ff0 DR7: 0400 [ 1237.652379] Call Trace: [ 1237.655022] [ 1237.657242] fput+0xe/0x10 [ 1237.660585] task_work_run+0x70/0xb0 [ 1237.664623] do_exit+0x37b/0xaf0 [ 1237.668064] do_group_exit+0x43/0xb0 [ 1237.671930] __x64_sys_exit_group+0x18/0x20 [ 1237.676586] do_syscall_64+0x40/0xb0 [ 1237.680298] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1237.685880] RIP: 0033:0x7f08b7f7f026 [ 1237.689680] Code: Unable to access opcode bytes at RIP 0x7f08b7f7effc. [ 1237.697194] RSP: 002b:7ffc949c3fe8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 1237.705346] RAX: ffda RBX: 7f08b8271880 RCX: 7f08b7f7f026 [ 1237.712960] RDX: RSI: 003c RDI: [ 1237.720554] RBP: R08: 00e7 R09: ff80 [ 1237.729387] R10: 7ffc949c3eb4 R11: 0246 R12: 7f08b8271880 [ 1237.737128] R13: 0002 R14: 7f08b827a388 R15: [ 1237.744398] [ 1237.746716] Modules linked in: veth xt_conntrack xt_MASQUERADE xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd input_leds psmouse virtio_net serio_raw net_failover efi_pstore failover sch_fq_codel drm virtio_rng ip_tables x_tables autofs4 [ 1237.788902] ---[ end trace e45b85d1ea54b719 ]--- Other information: lsb-release -rd prints: Description: Ubuntu 20.04.4 LTS Release: 20.04 apt-cache policy linux-image-5.13.0-1030-gcp prints: linux-image-5.13.0-1030-gcp: Installed: 5.13.0-1030.36~20.04.1 Candidate: 5.13.0-1030.36~20.04.1 Version table: *** 5.13.0-1030.36~20.04.1 500 500 http://us-east1.gce.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy docker.io prints: docker.io: Installed: 20.10.12-0ubuntu2~20.04.1 Candidate: 20.10.12-0ubuntu2~20.04.1 Version table: *** 20.10.12-0ubuntu2~20.04.1 500 500
[Kernel-packages] [Bug 1978253] Re: Intel DG2: [drm] ERROR Writing dc state to 0x1 failed, now 0xffffffff
Will have an update of the whole driver soon. Mark invalid. ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1978253 Title: Intel DG2: [drm] ERROR Writing dc state to 0x1 failed, now 0x Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Invalid Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1978253/+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 1978252] Re: Fix screen flickering caused by PSR on Intel TGL platform
** Tags added: oem-priority originate-from-1976234 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978252 Title: Fix screen flickering caused by PSR on Intel TGL platform Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Screen flickers on certain Intel TGL laptops. [Fix] Enable PSR2 selective fetch along with several PSR fixes. [Test] Screen flickers can no longer be observed on affected laptops. [Where problems could occur] PSR can be glitchy. Fortunately it's not system breaking so we can push subsequent fixes if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978252/+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 1978253] [NEW] Intel DG2: [drm] ERROR Writing dc state to 0x1 failed, now 0xffffffff
Public bug reported: TBD. ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978253 Title: Intel DG2: [drm] ERROR Writing dc state to 0x1 failed, now 0x Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1978253/+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 1978252] [NEW] Fix screen flickering caused by PSR on Intel TGL platform
Public bug reported: [Impact] Screen flickers on certain Intel TGL laptops. [Fix] Enable PSR2 selective fetch along with several PSR fixes. [Test] Screen flickers can no longer be observed on affected laptops. [Where problems could occur] PSR can be glitchy. Fortunately it's not system breaking so we can push subsequent fixes if needed. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Medium -- 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/1978252 Title: Fix screen flickering caused by PSR on Intel TGL platform Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Screen flickers on certain Intel TGL laptops. [Fix] Enable PSR2 selective fetch along with several PSR fixes. [Test] Screen flickers can no longer be observed on affected laptops. [Where problems could occur] PSR can be glitchy. Fortunately it's not system breaking so we can push subsequent fixes if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978252/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
For those who can't update, because the machine starts docker at startup and so crashes before you can get a shell open to upgrade to 1031, here's my method (on gcp) stop and edit machine to detach disk attach to another machine boot that and mount somewhere edit /boot/grub/grub.cfg and add single as a kernel commandline parameter shutdown temp box and detach disk reattach disk to original machine and boot connect via serial console sudo systemctl disable docker remove single from grub.cfg and reboot ssh in and update to latest kernel and reboot sudo systemctl enable docker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghan
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
Updated kernels are in flight. The updated kernel packages and versions are: linux-aws-5.13- 5.13.0-1029.32~20.04.1 linux-azure-5.13 - 5.13.0-1029.34~20.04.1 linux-gcp-5.13- 5.13.0-1031.37~20.04.1 linux-oracle-5.13 - 5.13.0-1034.40~20.04.1 The azure and gcp kernels are already in focal-updates. The aws kernel is in focal-proposed and the oracle kernel should be there very soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff
[Kernel-packages] [Bug 1976511] Re: kernel taint ( warning ) caused by smpboot.c: on 5.4.0
Checked on a machine in my lab with that CPU (Intel Xeon Platinum 8380) and this does not happen there... So I'd initially blame something related to firmware, perhaps, but since it also resolves with the 5.13 HWE, that is a little confusing. Can you try a different CPU in this machine with 5.4 ( like a Xeon Gold, or Silver, or a smaller Platinum?) And does this happen on other models with the same CPU? -- 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/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: Apr 6 02:33:31 G292-280 kernel: [0.007531] [ cut here ] Apr 6 02:33:31 G292-280 kernel: [0.007531] sched: CPU #20's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. Apr 6 02:33:31 G292-280 kernel: [0.007531] WARNING: CPU: 20 PID: 0 at /build/linux-hwe-5.4-9Mb2g5/linux-hwe-5.4-5.4.0/arch/x86/kernel/smpboot.c:426 topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Modules linked in: Apr 6 02:33:31 G292-280 kernel: [0.007531] CPU: 20 PID: 0 Comm: swapper/20 Not tainted 5.4.0-107-generic #121~18.04.1-Ubuntu Apr 6 02:33:31 G292-280 kernel: [0.007531] Hardware name: GIGABYTE G292-280-00/MG52-G20-00, BIOS F02 10/28/2021 Apr 6 02:33:31 G292-280 kernel: [0.007531] RIP: 0010:topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Code: 41 5c 5d c3 80 3d 1e 75 ba 01 00 75 ec 89 f1 41 89 d9 89 fe 45 89 e0 48 c7 c7 b8 00 b4 a6 c6 05 04 75 ba 01 01 e8 b4 c7 03 00 <0f> 0b eb cb 0f 1f 44 00 00 55 0f b6 05 a3 8d f0 01 c6 05 9c 8d f0 Apr 6 02:33:31 G292-280 kernel: [0.007531] RSP: :b76b58e17eb8 EFLAGS: 00010086 Apr 6 02:33:31 G292-280 kernel: [0.007531] RAX: RBX: RCX: a7264e88 Apr 6 02:33:31 G292-280 kernel: [0.007531] RDX: a7264e88 RSI: 0096 RDI: 0046 Apr 6 02:33:31 G292-280 kernel: [0.007531] RBP: b76b58e17ec8 R08: R09: 0002f680 Apr 6 02:33:31 G292-280 kernel: [0.007531] R10: 8b69bf80 R11: 02c0 R12: 0001 Apr 6 02:33:31 G292-280 kernel: [0.007531] R13: 0014 R14: 0014 R15: 0002 Apr 6 02:33:31 G292-280 kernel: [0.007531] FS: () GS:8b69bf80() knlGS: Apr 6 02:33:31 G292-280 kernel: [0.007531] CS: 0010 DS: ES: CR0: 80050033 Apr 6 02:33:31 G292-280 kernel: [0.007531] CR2: CR3: 007ee1a0a001 CR4: 00760ee0 Apr 6 02:33:31 G292-280 kernel: [0.007531] DR0: DR1: DR2: Apr 6 02:33:31 G292-280 kernel: [0.007531] DR3: DR6: fffe0ff0 DR7: 0400 Apr 6 02:33:31 G292-280 kernel: [0.007531] PKRU: Apr 6 02:33:31 G292-280 kernel: [0.007531] Call Trace: Apr 6 02:33:31 G292-280 kernel: [0.007531] set_cpu_sibling_map+0x14f/0x600 Apr 6 02:33:31 G292-280 kernel: [0.007531] start_secondary+0x6e/0x1c0 Apr 6 02:33:31 G292-280 kernel: [0.007531] secondary_startup_64+0xa4/0xb0 Apr 6 02:33:31 G292-280 kernel: [0.007531] ---[ end trace 789d1f3abd3d96d4 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
On GCP the fix hit apt. So the easiest way to fix now is simply `sudo apt update && sudo apt upgrade` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.610166] RAX: RBX: 000a801d
[Kernel-packages] [Bug 1978133] Re: System freeze followed by kernel panic or blank screen
It happens more often when the laptop is idle. In the logs I see a pattern of messages like: "systemd-logind: hibernation is restricted; see man kernel_lockdown.7" and they intensify right before the system hangs. Secure boot is enabled, and hibernation is disabled by default. I only use suspend-to-ram after 20 minutes of inactivity, set through GNOME settings. -- 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/1978133 Title: System freeze followed by kernel panic or blank screen Status in linux package in Ubuntu: Confirmed Bug description: System keeps freezing in many different circumstances. I don't know how to reproduce this. Only happens on Ubuntu 22.04. Earlier versions were fine - tested Ubuntu impish and Debian bullseye. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 1593 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 12:22:34 2022 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0DC2CG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978133/+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 1978244] Re: [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress -- 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/1978244 Title: [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] Screen corruption can occur when s2idle resume. [Fix] Check that DMCUB is running and wait for auto-load. [Test] Verified on hardware, stress s2idle and passed. [Where problems could occur] Low risk, It may break s2idle on AMD GPU driver. This commit is in 5.17. OEM kernels already got this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978244/+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 1978244] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1978244 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978244 Title: [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] Screen corruption can occur when s2idle resume. [Fix] Check that DMCUB is running and wait for auto-load. [Test] Verified on hardware, stress s2idle and passed. [Where problems could occur] Low risk, It may break s2idle on AMD GPU driver. This commit is in 5.17. OEM kernels already got this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978244/+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 1977834] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977834 Title: not update Status in linux package in Ubuntu: Confirmed Bug description: Can not upgrade An upgrade from 'groovy' to 'impish' is not supported with this tool. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-63-generic 5.8.0-63.71 ProcVersionSignature: Ubuntu 5.8.0-63.71-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mrigank1667 F pulseaudio /dev/snd/controlC1: mrigank1667 F pulseaudio /dev/snd/pcmC1D0p: mrigank1667 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 7 17:30:59 2022 InstallationDate: Installed on 2020-11-29 (554 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 001 Device 003: ID 064e:c342 Suyin Corp. Bus 001 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 240 G3 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=e2f92801-af02-4cba-b7c7-f4638cdcfc39 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-63-generic N/A linux-backports-modules-5.8.0-63-generic N/A linux-firmware1.190.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2022-06-07 (0 days ago) dmi.bios.date: 03/12/2018 dmi.bios.release: 15.68 dmi.bios.vendor: Insyde dmi.bios.version: F.44 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 220D dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.44:bd03/12/2018:br15.68:efr86.56:svnHewlett-Packard:pnHP240G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn220D:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=CON B=HP S=PAV dmi.product.name: HP 240 G3 Notebook PC dmi.product.sku: K1C59PA#ACJ dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977834/+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 1977857] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977857 Title: [amdgpu] denial of service by WebGL - GPU crashes with system impairment Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu 20.04.04 with Kernel 5.13.0-46-generic on AMD Ryzen V1605B Platform with integrated Radeon Vega 8 GPU. I am currently working on an Web application using tensorflowjs, which in turn uses WebGL for computations. When "provoking" the GPU by a lot of memory allocations, it can easily be crashed with consequences for the whole system. Symptoms include: -Chromium browser hung in a way that the current tab cant be reloaded. Browser restart fixes this sometimes. Otherwise see below. -Chromium browser exiting, and can't be restarted. Any attempt to run it just hangs without opening a window at all. Using terminal-only applications still works as normal. System reboot fixes this. But.. -After triggering the bugs above, quite often system restart fails (system hang on shutdown). Only power cycling fixes this. -Sometimes whole system freezing, and can't be restarted. SSH connections stall too. All of these can be triggered by a rogue website, and provide risk of denial and data loss. Of course we can blame Chromium first for unsane memory management, but even a rogue userspace application should not render the GPU useless or stalled forever. We can also blame mesa I guess, but as amdgpu is the kernel part is has to handle such attacks in my opinion. I've also changed to updated Mesa from obiaf ppa, which won't fix the whole situation. Maybe also amdgpu firmware is part of the problem. Sadly I didn't collect the dmesg traces of all those crashes, but there where plenty of different messages there. I will add dmesg traces here, if it's happen again (but currently I try to stabilize the system less crashes will happen). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977857/+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 1977857] Re: [amdgpu] denial of service by WebGL - GPU crashes with system impairment
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1977857 Title: [amdgpu] denial of service by WebGL - GPU crashes with system impairment Status in linux package in Ubuntu: New Bug description: Using Ubuntu 20.04.04 with Kernel 5.13.0-46-generic on AMD Ryzen V1605B Platform with integrated Radeon Vega 8 GPU. I am currently working on an Web application using tensorflowjs, which in turn uses WebGL for computations. When "provoking" the GPU by a lot of memory allocations, it can easily be crashed with consequences for the whole system. Symptoms include: -Chromium browser hung in a way that the current tab cant be reloaded. Browser restart fixes this sometimes. Otherwise see below. -Chromium browser exiting, and can't be restarted. Any attempt to run it just hangs without opening a window at all. Using terminal-only applications still works as normal. System reboot fixes this. But.. -After triggering the bugs above, quite often system restart fails (system hang on shutdown). Only power cycling fixes this. -Sometimes whole system freezing, and can't be restarted. SSH connections stall too. All of these can be triggered by a rogue website, and provide risk of denial and data loss. Of course we can blame Chromium first for unsane memory management, but even a rogue userspace application should not render the GPU useless or stalled forever. We can also blame mesa I guess, but as amdgpu is the kernel part is has to handle such attacks in my opinion. I've also changed to updated Mesa from obiaf ppa, which won't fix the whole situation. Maybe also amdgpu firmware is part of the problem. Sadly I didn't collect the dmesg traces of all those crashes, but there where plenty of different messages there. I will add dmesg traces here, if it's happen again (but currently I try to stabilize the system less crashes will happen). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977857/+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 1978244] [NEW] [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
Public bug reported: [Impact] Screen corruption can occur when s2idle resume. [Fix] Check that DMCUB is running and wait for auto-load. [Test] Verified on hardware, stress s2idle and passed. [Where problems could occur] Low risk, It may break s2idle on AMD GPU driver. This commit is in 5.17. OEM kernels already got this commit. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1978244 Title: [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: [Impact] Screen corruption can occur when s2idle resume. [Fix] Check that DMCUB is running and wait for auto-load. [Test] Verified on hardware, stress s2idle and passed. [Where problems could occur] Low risk, It may break s2idle on AMD GPU driver. This commit is in 5.17. OEM kernels already got this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978244/+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 1977834] Re: not update
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1977834 Title: not update Status in linux package in Ubuntu: New Bug description: Can not upgrade An upgrade from 'groovy' to 'impish' is not supported with this tool. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-63-generic 5.8.0-63.71 ProcVersionSignature: Ubuntu 5.8.0-63.71-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mrigank1667 F pulseaudio /dev/snd/controlC1: mrigank1667 F pulseaudio /dev/snd/pcmC1D0p: mrigank1667 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 7 17:30:59 2022 InstallationDate: Installed on 2020-11-29 (554 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 001 Device 003: ID 064e:c342 Suyin Corp. Bus 001 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 240 G3 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=e2f92801-af02-4cba-b7c7-f4638cdcfc39 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-63-generic N/A linux-backports-modules-5.8.0-63-generic N/A linux-firmware1.190.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2022-06-07 (0 days ago) dmi.bios.date: 03/12/2018 dmi.bios.release: 15.68 dmi.bios.vendor: Insyde dmi.bios.version: F.44 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 220D dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.44:bd03/12/2018:br15.68:efr86.56:svnHewlett-Packard:pnHP240G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn220D:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=CON B=HP S=PAV dmi.product.name: HP 240 G3 Notebook PC dmi.product.sku: K1C59PA#ACJ dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977834/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
For Debian and Ubuntu, I used "sudo grub-reboot 2", which forces grub menu 2's kernel on next reboot. Once rebooted, use "dpkg-l | grep 1028" and apt remove each package relate to kernel 1028. Apt will also update grub for you. Don't forget to uninstall or "break" unattended-upgrades, which is how my server got the new kernel in the first place. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 0
[Kernel-packages] [Bug 1978240] [NEW] Jammy update: v5.15.39 upstream stable release
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: v5.15.39 upstream stable release from git://git.kernel.org/ MIPS: Fix CP0 counter erratum detection for R4k CPUs parisc: Merge model and model name into one line in /proc/cpuinfo ALSA: hda/realtek: Add quirk for Yoga Duet 7 13ITL6 speakers ALSA: fireworks: fix wrong return count shorter than expected by 4 bytes mmc: sdhci-msm: Reset GCC_SDCC_BCR register for SDHC mmc: sunxi-mmc: Fix DMA descriptors allocated above 32 bits mmc: core: Set HS clock speed before sending HS CMD13 gpiolib: of: fix bounds check for 'gpio-reserved-ranges' x86/fpu: Prevent FPU state corruption KVM: x86/svm: Account for family 17h event renumberings in amd_pmc_perf_hw_id iommu/vt-d: Calculate mask for non-aligned flushes iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range() drm/amd/display: Avoid reading audio pattern past AUDIO_CHANNELS_COUNT drm/amdgpu: do not use passthrough mode in Xen dom0 RISC-V: relocate DTB if it's outside memory region Revert "SUNRPC: attempt AF_LOCAL connect on setup" timekeeping: Mark NMI safe time accessors as notrace firewire: fix potential uaf in outbound_phy_packet_callback() firewire: remove check of list iterator against head past the loop body firewire: core: extend card->lock in fw_core_handle_bus_reset net: stmmac: disable Split Header (SPH) for Intel platforms genirq: Synchronize interrupt thread startup ASoC: da7219: Fix change notifications for tone generator frequency ASoC: wm8958: Fix change notifications for DSP controls ASoC: meson: Fix event generation for AUI ACODEC mux ASoC: meson: Fix event generation for G12A tohdmi mux ASoC: meson: Fix event generation for AUI CODEC mux s390/dasd: fix data corruption for ESE devices s390/dasd: prevent double format of tracks for ESE devices s390/dasd: Fix read for ESE with blksize < 4k s390/dasd: Fix read inconsistency for ESE DASD devices can: grcan: grcan_close(): fix deadlock can: isotp: remove re-binding of bound socket can: grcan: use ofdev->dev when allocating DMA memory can: grcan: grcan_probe(): fix broken system id check for errata workaround needs can: grcan: only use the NAPI poll budget for RX nfc: replace improper check device_is_registered() in netlink related functions nfc: nfcmrvl: main: reorder destructive operations in nfcmrvl_nci_unregister_dev to avoid bugs NFC: netlink: fix sleep in atomic bug when firmware download timeout gpio: visconti: Fix fwnode of GPIO IRQ gpio: pca953x: fix irq_stat not updated when irq is disabled (irq_mask not set) hwmon: (adt7470) Fix warning on module removal hwmon: (pmbus) disable PEC if not enabled ASoC: dmaengine: Restore NULL prepare_slave_config() callback ASoC: soc-ops: fix error handling iommu/vt-d: Drop stop marker messages iommu/dart: check return value after calling platform_get_resource() net/mlx5e: Fix trust state reset in reload net/mlx5e: Don't match double-vlan packets if cvlan is not set net/mlx5e: CT: Fix queued up restore put() executing after relevant ft release net/mlx5e: Fix the calling of update_buffer_lossy() API net/mlx5: Avoid double clear or set of sync reset requested net/mlx5: Fix deadlock in sync reset flow selftests/seccomp: Don't call read() on TTY from background pgrp SUNRPC release the transport of a relocated task with an assigned transport RDMA/siw: Fix a condition race issue in MPA request processing RDMA/irdma: Flush iWARP QP if modified to ERR from RTR state RDMA/irdma: Reduce iWARP QP destroy time RDMA/irdma: Fix possible crash due to NULL netdev in notifier NFSv4: Don't invalidate inode attributes on delegation return net: ethernet: mediatek: add missing of_node_put() in mtk_sgmii_init() net: dsa: mt7530: add missing of_node_put() in mt7530_setup() net: stmmac: dwmac-sun8i: add missing of_node_put() in sun8i_dwmac_register_mdio_mux() net: mdio: Fix ENOMEM return value in BCM6368 mux bus controller net: cpsw: add missing of_node_put() in cpsw_probe_dt() net: igmp: respect RCU rules in ip_mc_source() and ip_mc_msfilter() net: emaclite: Add error handling for of_address_to_resource() selftests/net: so_txtime: fix parsing of start time stamp on 32 bit systems selftests/net: so_txtime: usage(): fix documentation of default clock drm/msm/dp: remove fail safe mode related code btrfs: do not BUG_ON() on failure to update inode when setting xattr hinic: fix bug of wq out of bound access mld: respect RCU rules in ip6_mc_source() and ip6_mc_msfilter() rxrpc: Enable IPv6 checksums on transport socket selftests: mirror_gre_bridge_1q: Avoid changing PVID while interface is opera
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
@n1sni - wanted to extend my thanks as well, but on ubuntu 20.04 that settings was not present in /etc/default/grub, so i had to uninstall 1028 and install 1025. After adding that setting, and reloading and rebooting the change didn't take place, hence the reinstall. Going to make an AMI, until this fix is released. sudo apt remove linux-image-5.13.0-1028-aws linux-image-aws -y Then sudo apt install -y linux-image-5.13.0-1025-aws Then reboot. If you reboot between you won't have a kernel and won't be able to reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913
[Kernel-packages] [Bug 1978234] Re: Jammy update: v5.15.38 upstream stable release
** Description changed: + SRU Justification - 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: - 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.38 upstream stable release + from git://git.kernel.org/ -v5.15.38 upstream stable release -from git://git.kernel.org/ + usb: mtu3: fix USB 3.0 dual-role-switch from device to host + USB: quirks: add a Realtek card reader + USB: quirks: add STRING quirk for VCOM device + USB: serial: whiteheat: fix heap overflow in WHITEHEAT_GET_DTR_RTS + USB: serial: cp210x: add PIDs for Kamstrup USB Meter Reader + USB: serial: option: add support for Cinterion MV32-WA/MV32-WB + USB: serial: option: add Telit 0x1057, 0x1058, 0x1075 compositions + usb: xhci: tegra:Fix PM usage reference leak of tegra_xusb_unpowergate_partitions + xhci: Enable runtime PM on second Alderlake controller + xhci: stop polling roothubs after shutdown + xhci: increase usb U3 -> U0 link resume timeout from 100ms to 500ms + iio: dac: ad5592r: Fix the missing return value. + iio: dac: ad5446: Fix read_raw not returning set value + iio: magnetometer: ak8975: Fix the error handling in ak8975_power_on() + iio: imu: inv_icm42600: Fix I2C init possible nack + usb: misc: fix improper handling of refcount in uss720_probe() + usb: core: Don't hold the device lock while sleeping in do_proc_control() + usb: typec: ucsi: Fix reuse of completion structure + usb: typec: ucsi: Fix role swapping + usb: gadget: uvc: Fix crash when encoding data for usb request + usb: gadget: configfs: clear deactivation flag in configfs_composite_unbind() + usb: dwc3: Try usb-role-switch first in dwc3_drd_init + usb: dwc3: core: Fix tx/rx threshold settings + usb: dwc3: core: Only handle soft-reset in DCTL + usb: dwc3: gadget: Return proper request status + usb: dwc3: pci: add support for the Intel Meteor Lake-P + usb: cdns3: Fix issue for clear halt endpoint + usb: phy: generic: Get the vbus supply + serial: imx: fix overrun interrupts in DMA mode + serial: amba-pl011: do not time out prematurely when draining tx fifo + serial: 8250: Also set sticky MCR bits in console restoration + serial: 8250: Correct the clock for EndRun PTP/1588 PCIe device + arch_topology: Do not set llc_sibling if llc_id is invalid + ceph: fix possible NULL pointer dereference for req->r_session + bus: mhi: host: pci_generic: Add missing poweroff() PM callback + bus: mhi: host: pci_generic: Flush recovery worker during freeze + arm64: dts: imx8mm-venice: fix spi2 pin configuration + pinctrl: samsung: fix missing GPIOLIB on ARM64 Exynos config + hex2bin: make the function hex_to_bin constant-time + hex2bin: fix access beyond string end + riscv: patch_text: Fixup last cpu should be master + x86/pci/xen: Disable PCI/MSI[-X] masking for XEN_HVM guests + iocost: don't reset the inuse weight of under-weighted debtors + virtio_net: fix wrong buf address calculation when using xdp + cpufreq: qcom-hw: fix the race between LMH worker and cpuhp + cpufreq: qcom-cpufreq-hw: Fix throttle frequency value on EPSS platforms + video: fbdev: udlfb: properly check endpoint type + arm64: dts: meson: remove CPU opps below 1GHz for G12B boards + arm64: dts: meson: remove CPU opps below 1GHz for SM1 boards + iio:imu:bmi160: disable regulator in error path + mtd: rawnand: fix ecc parameters for mt7622 + xsk: Fix l2fwd for copy mode + busy poll combo + arm64: dts: imx8qm: Correct SCU clock controller's compatible property + USB: Fix xhci event ring dequeue pointer ERDP update issue + ARM: dts: imx6qdl-apalis: Fix sgtl5000 detection issue + arm64: dts: imx8mn: Fix SAI nodes + arm64: dts: meson-sm1-bananapi-m5: fix wrong GPIO pin labeling for CON1 + phy: samsung: Fix missing of_node_put() in exynos_sata_phy_probe + phy: samsung: exynos5250-sata: fix missing device put in probe error paths + ARM: OMAP2+: Fix refcount leak in omap_gic_of_init + bus: ti-sysc: Make omap3 gpt12 quirk handling SoC specific + ARM: dts: dra7: Fix suspend warning for vpe powerdomain + phy: ti: omap-usb2: Fix error handling in omap_usb2_enable_clocks + ARM: dts: at91: Map MCLK for wm8731 on at91sam9g20ek + ARM: dts: at91: sama5d4_xplained: fix pinctrl phandle name + ARM: dts: at91:
[Kernel-packages] [Bug 1978234] Re: Jammy update: v5.15.38 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1978234 Title: Jammy update: v5.15.38 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress 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.38 upstream stable release from git://git.kernel.org/ usb: mtu3: fix USB 3.0 dual-role-switch from device to host USB: quirks: add a Realtek card reader USB: quirks: add STRING quirk for VCOM device USB: serial: whiteheat: fix heap overflow in WHITEHEAT_GET_DTR_RTS USB: serial: cp210x: add PIDs for Kamstrup USB Meter Reader USB: serial: option: add support for Cinterion MV32-WA/MV32-WB USB: serial: option: add Telit 0x1057, 0x1058, 0x1075 compositions usb: xhci: tegra:Fix PM usage reference leak of tegra_xusb_unpowergate_partitions xhci: Enable runtime PM on second Alderlake controller xhci: stop polling roothubs after shutdown xhci: increase usb U3 -> U0 link resume timeout from 100ms to 500ms iio: dac: ad5592r: Fix the missing return value. iio: dac: ad5446: Fix read_raw not returning set value iio: magnetometer: ak8975: Fix the error handling in ak8975_power_on() iio: imu: inv_icm42600: Fix I2C init possible nack usb: misc: fix improper handling of refcount in uss720_probe() usb: core: Don't hold the device lock while sleeping in do_proc_control() usb: typec: ucsi: Fix reuse of completion structure usb: typec: ucsi: Fix role swapping usb: gadget: uvc: Fix crash when encoding data for usb request usb: gadget: configfs: clear deactivation flag in configfs_composite_unbind() usb: dwc3: Try usb-role-switch first in dwc3_drd_init usb: dwc3: core: Fix tx/rx threshold settings usb: dwc3: core: Only handle soft-reset in DCTL usb: dwc3: gadget: Return proper request status usb: dwc3: pci: add support for the Intel Meteor Lake-P usb: cdns3: Fix issue for clear halt endpoint usb: phy: generic: Get the vbus supply serial: imx: fix overrun interrupts in DMA mode serial: amba-pl011: do not time out prematurely when draining tx fifo serial: 8250: Also set sticky MCR bits in console restoration serial: 8250: Correct the clock for EndRun PTP/1588 PCIe device arch_topology: Do not set llc_sibling if llc_id is invalid ceph: fix possible NULL pointer dereference for req->r_session bus: mhi: host: pci_generic: Add missing poweroff() PM callback bus: mhi: host: pci_generic: Flush recovery worker during freeze arm64: dts: imx8mm-venice: fix spi2 pin configuration pinctrl: samsung: fix missing GPIOLIB on ARM64 Exynos config hex2bin: make the function hex_to_bin constant-time hex2bin: fix access beyond string end riscv: patch_text: Fixup last cpu should be master x86/pci/xen: Disable PCI/MSI[-X] masking for XEN_HVM guests iocost: don't reset the inuse weight of under-weighted debtors virtio_net: fix wrong buf address calculation when using xdp cpufreq: qcom-hw: fix the race between LMH worker and cpuhp cpufreq: qcom-cpufreq-hw: Fix throttle frequency value on EPSS platforms video: fbdev: udlfb: properly check endpoint type arm64: dts: meson: remove CPU opps below 1GHz for G12B boards arm64: dts: meson: remove CPU opps below 1GHz for SM1 boards iio:imu:bmi160: disable regulator in error path mtd: rawnand: fix ecc parameters for mt7622 xsk: Fix l2fwd for copy mode + busy poll combo arm64: dts: imx8qm: Correct SCU clock controller's compatible property USB: Fix xhci event ring dequeue pointer ERDP update issue ARM: dts: imx6qdl-apalis: Fix sgtl5000 detection issue arm64: dts: imx8mn: Fix SAI nodes arm64: dts: meson-sm1-bananapi-m5: fix wrong GPIO pin labeling for CON1 phy: samsung: Fix missing of_node_put() in exynos_sata_phy_probe phy: samsung: exynos5250-sata: fix missing device put in probe error paths ARM: OMAP2+: Fix refcount leak in omap_gic_of_init bus: ti-sysc: Make omap3 gpt12 quirk handling SoC specific ARM: dts: dra7: Fix suspend warning for vpe powerdomain phy: ti: omap-usb2: Fix error handling in omap_usb2_enable_clocks ARM: dts: at91: Map MCLK for wm8731 on at91sam9g20ek ARM:
[Kernel-packages] [Bug 1978234] [NEW] Jammy update: v5.15.38 upstream stable release
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: v5.15.38 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1978234 Title: Jammy update: v5.15.38 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress 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.38 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978234/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
I would like to echo earlier comments, I think that all affected kernel packages should be pulled from the APT repositories, I also think that all cloud images built with the bad kernel should be pulled too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796
[Kernel-packages] [Bug 1977946] Re: README points to non-existent URL
** Changed in: ubuntu-fan (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1977946 Title: README points to non-existent URL Status in ubuntu-fan package in Ubuntu: Confirmed Bug description: /usr/share/doc/ubuntu-fan/README.gz (ubuntu-fan/README) reads: "More information on the Fan, including more detailed configuration information, can be found at http://www.ubuntu.com/fan."; However, the aforementioned URL (with and without trailing dot) does not exist. Is this supposed to point to https://wiki.ubuntu.com/FanNetworking instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1977946/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
@n1sni - thank you for your post. With 5.13.0-1028-aws I could only run hello-world without killing the host. Reverting back to 5.13.0-1025-aws from 5.13.0-1028-aws I can now run our build containers without problems. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [
[Kernel-packages] [Bug 1961338] [linux-hwe-5.11/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- 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/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
So this was painful for us. AWS hosted server running Ubuntu 20.04.4 LTS. Just for others, here are the steps we took thanks to the other comments here: We had to force shut down the machine and wait (aws console). Then we got this script running, and started the machine back up: while true; do ssh -o ConnectTimeout=2 -i <.pem file> ubuntu@ "sudo systemctl disable docker.service; sudo systemctl disable containerd.service" done --- Now, ssh into machine normally, and this is what we ran in our case: sudo -i cd /boot/grub grep -Ei 'submenu|menuentry ' /boot/grub/grub.cfg | sed -re "s/(.? )'([^']+)'.*/\1 \2/" The result on mine was: --- menuentry Ubuntu submenu Advanced options for Ubuntu menuentry Ubuntu, with Linux 5.13.0-1028-aws # <-- BAD BAD BAD menuentry Ubuntu, with Linux 5.13.0-1028-aws (recovery mode) menuentry Ubuntu, with Linux 5.13.0-1025-aws # <-- what we want menuentry Ubuntu, with Linux 5.13.0-1025-aws (recovery mode) menuentry Ubuntu, with Linux 5.4.0-1029-aws menuentry Ubuntu, with Linux 5.4.0-1029-aws (recovery mode) menuentry Ubuntu 20.04.4 LTS (20.04) (on /dev/nvme0n1p1) submenu Advanced options for Ubuntu 20.04.4 LTS (20.04) (on /dev/nvme0n1p1) menuentry Ubuntu (on /dev/nvme0n1p1) menuentry Ubuntu, with Linux 5.13.0-1028-aws (on /dev/nvme0n1p1) menuentry Ubuntu, with Linux 5.13.0-1028-aws (recovery mode) (on /dev/nvme0n1p1) menuentry Ubuntu, with Linux 5.13.0-1025-aws (on /dev/nvme0n1p1) menuentry Ubuntu, with Linux 5.13.0-1025-aws (recovery mode) (on /dev/nvme0n1p1) menuentry Ubuntu, with Linux 5.4.0-1029-aws (on /dev/nvme0n1p1) menuentry Ubuntu, with Linux 5.4.0-1029-aws (recovery mode) (on /dev/nvme0n1p1) --- So we wanted off 1028, and back to 1025. Edited: vi /etc/default/grub changed: GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 5.13.0-1025-aws" NOTE: the first half is the "MENUENTRY" from above, then ">" and then the submenu. Saved run: grub-mkconfig -o /boot/grub/grub.cfg sudo reboot then, after reboot: sudo systemctl enable docker.service; sudo systemctl enable containerd.service sudo reboot Should be back up! It seems like upgrading to the newest kernel also helps based on the above, but will try that later. Hope this helps someone like you all helped us!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Cal
[Kernel-packages] [Bug 1978151] [NEW] Kernel Panic Running Specific Docker Image
Public bug reported: This panic occur only on the latest Linux kernel release. * 5.13.0-1030-gcp is broken * 5.13.0-1027-gcp is okay * 5.13.0-1024-gcp is okay Steps to reproduce: 1) Ensure kernel version is 5.13.0-1030-gcp. 2) sudo apt update 3) sudo apt install docker.io 4) sudo docker run releases-docker.jfrog.io/jfrog/artifactory-pro:7.25.7 Expected behavior: The container runs without issue. Actual behavior (the logs got slightly garbled, but): Kernel panics with: [ 1237.492662] kernel BUG at include/linux/fs.h:3104! [ 1237.497925] invalid opcode: [#1] SMP PTI [ 1Jun 9 18:20:15 23b7ootlooptest ker.502540]nel: [ 1237.4926 CPU: 1 PID: 58] 19[2 cut here ]5 C Jun 9omm: 18:20:15 bootlo doptest kernel: [ 1237.492662] keranel BUG at incltude/linux/fs.h:3e No104! Jun 9 18:t2 0:15 bootlooptetst kernel: [ 123ainted 5.13.07.497925] invali1030-gcp #3d opcode: [6~20.04.#1] SMP PTI 1-Ubuntu [ 1237.535282] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [ 1237.545178] RIP: 0010:__fput+0x247/0x250 [ 1237.549477] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 7e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 1237.569173] RSP: 0018:b8b280b0fe18 EFLAGS: 00010246 [ 1237.574909] RAX: RBX: 000a801d RCX: 97f011bf7000 [ 1237.586271] RDX: 97f011ae9280 RSI: 0001 RDI: [ 1237.593886] RBP: b8b280b0fe40 R08: 97f011aef140 R09: 97f022482570 [ 1237.601492] R10: b8b280b0fe18 R11: 97f026038910 R12: 97f026038900 [ 1237.608820] R13: 97f022482570 R14: 97f011ae92a0 R15: 97f0346bbc00 [ 1237.616301] FS: () GS:97f03bd0() knlGS: [ 1237.624680] CS: 0010 DS: ES: CR0: 80050033 [ 1237.630646] CR2: 7f08b7f7eff0 CR3: 00010e810001 CR4: 003706e0 [ 1237.637892] DR0: DR1: DR2: [ 1237.645134] DR3: DR6: fffe0ff0 DR7: 0400 [ 1237.652379] Call Trace: [ 1237.655022] [ 1237.657242] fput+0xe/0x10 [ 1237.660585] task_work_run+0x70/0xb0 [ 1237.664623] do_exit+0x37b/0xaf0 [ 1237.668064] do_group_exit+0x43/0xb0 [ 1237.671930] __x64_sys_exit_group+0x18/0x20 [ 1237.676586] do_syscall_64+0x40/0xb0 [ 1237.680298] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1237.685880] RIP: 0033:0x7f08b7f7f026 [ 1237.689680] Code: Unable to access opcode bytes at RIP 0x7f08b7f7effc. [ 1237.697194] RSP: 002b:7ffc949c3fe8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 1237.705346] RAX: ffda RBX: 7f08b8271880 RCX: 7f08b7f7f026 [ 1237.712960] RDX: RSI: 003c RDI: [ 1237.720554] RBP: R08: 00e7 R09: ff80 [ 1237.729387] R10: 7ffc949c3eb4 R11: 0246 R12: 7f08b8271880 [ 1237.737128] R13: 0002 R14: 7f08b827a388 R15: [ 1237.744398] [ 1237.746716] Modules linked in: veth xt_conntrack xt_MASQUERADE xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd input_leds psmouse virtio_net serio_raw net_failover efi_pstore failover sch_fq_codel drm virtio_rng ip_tables x_tables autofs4 [ 1237.788902] ---[ end trace e45b85d1ea54b719 ]--- Other information: lsb-release -rd prints: Description:Ubuntu 20.04.4 LTS Release:20.04 apt-cache policy linux-image-5.13.0-1030-gcp prints: linux-image-5.13.0-1030-gcp: Installed: 5.13.0-1030.36~20.04.1 Candidate: 5.13.0-1030.36~20.04.1 Version table: *** 5.13.0-1030.36~20.04.1 500 500 http://us-east1.gce.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy docker.io prints: docker.io: Installed: 20.10.12-0ubuntu2~20.04.1 Candidate: 20.10.12-0ubuntu2~20.04.1 Version table: *** 20.10.12-0ubuntu2~20.04.1 500 500 http://us-east1.gce.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 20.10.7-0ubuntu5~20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages 19.03.8-0ubuntu1 500 500 http://us-east1.gce.archive.ubuntu.com/ubuntu focal/universe amd64 Packages ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1978151 Title: Kernel Panic Running Specific Docker Imag
[Kernel-packages] [Bug 1976127] Re: upcoming update
This is CVE-2022-1966. ** Information type changed from Private Security to Public Security ** Summary changed: - upcoming update + netfilter newset stateless expression UAF ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1966 ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Description changed: - placeholder + [Impact] + An unprivileged user could exploit a use-after-free vulnerability on nftables by using network namespaces. + + [Test case] + Test PoC at https://seclists.org/oss-sec/2022/q2/159. + + [Potential regression] + nftables users could be affected. -- 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/1976127 Title: netfilter newset stateless expression UAF Status in linux package in Ubuntu: Fix Released Bug description: [Impact] An unprivileged user could exploit a use-after-free vulnerability on nftables by using network namespaces. [Test case] Test PoC at https://seclists.org/oss-sec/2022/q2/159. [Potential regression] nftables users could be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976127/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
Sorry for my ignorance of the software development procedure for Ubuntu, but now that this fix has been committed, how long until it is available via apt on the normal release channels? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280
[Kernel-packages] [Bug 1976363] Re: netfilter newset OOB write
** Summary changed: - upcoming update - nf oob + netfilter newset OOB write -- 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/1976363 Title: netfilter newset OOB write Status in linux package in Ubuntu: Fix Released Bug description: [Impact] An unprivileged user could write out-of-bounds by using nftables under a network namespace. [Test case] Test the PoC available at https://seclists.org/oss-sec/2022/q2/164. [Potential regression] nftables could be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976363/+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 1978145] Re: Request to back port vmci patches to Ubuntu kernel
Since this is a request to port patches from upstream to Ubuntu kernels,
setting the status to 'Confirmed'.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1978145
Title:
Request to back port vmci patches to Ubuntu kernel
Status in linux package in Ubuntu:
Confirmed
Bug description:
The request is to bring vmci to TOT and back port the following patches into
Ubuntu kernels.
1. fac608138c6136126faadafa5554cc0bbabf3c44 ("VMCI: dma dg: whitespace
formatting change for vmci register defines")
2. e283a0e8b7ea83915e988ed059384af166b444c0 ("VMCI: dma dg: add MMIO access
to registers")
3. eed2298d936087a1c85e0fa6f7170028e4f4fded ("VMCI: dma dg: detect DMA
datagram capability")
4. 8cb520bea1470ca205980fbf030ed1f472f4af2f ("VMCI: dma dg: set OS page
size")
5. cc68f2177fcbfe2dbe5e9514789b96ba5995ec1e ("VMCI: dma dg: register dummy
IRQ handlers for DMA datagrams")
6. 5ee109828e73bbe4213c373988608d8f33e03d78 ("VMCI: dma dg: allocate send
and receive buffers for DMA datagrams")
7. 22aa5c7f323022477b70e044eb00e6bfea9498e8 ("VMCI: dma dg: add support for
DMA datagrams sends")
8. 463713eb6164b6577f8e91447c7745628215531b ("VMCI: dma dg: add support for
DMA datagrams receive")
9. 77e861619baea5a7c934e47fda74b03c0b072aec ("VMCI: Fix some error handling
paths in vmci_guest_probe_device()")
10. c8e9b30ccae605bf1dbeaf03971f9b83f70b928d ("VMCI: Release
notification_bitmap in error path")
11. 5df0e734b8c39598effe0f17e5bd8ff7748a0693 ("VMCI: Check exclusive_vectors
when freeing interrupt 1")
12. 1f7142915d304804a9bd952245fce92786b1b62f ("VMCI: Add support for ARM64")
13. ba03a9bbd17b149c373c0ea44017f35fc2cd0f28 ("VMCI: Release resource if the
work is already queued")
Thanks,
Vishnu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978145/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
@cz172638 - we are aware that the 5.15 Focal backport kernels have this issue as well. However, since 5.15 is not the default -edge kernel yet, it will have to wait until the next SRU cycle due for release 20-June, 2022. ** Changed in: linux-oracle-5.13 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oracle-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux-oracle-5.13 (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws-5.13 (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-azure-5.13 (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-gcp-5.13 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-gcp-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux-gcp-5.13 (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-intel-iotg-5.15 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-intel-iotg-5.15 (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux-intel-iotg-5.15 (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-intel-iotg-5.15 (Ubuntu Focal) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: 000
[Kernel-packages] [Bug 1978145] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1978145
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1978145
Title:
Request to back port vmci patches to Ubuntu kernel
Status in linux package in Ubuntu:
Incomplete
Bug description:
The request is to bring vmci to TOT and back port the following patches into
Ubuntu kernels.
1. fac608138c6136126faadafa5554cc0bbabf3c44 ("VMCI: dma dg: whitespace
formatting change for vmci register defines")
2. e283a0e8b7ea83915e988ed059384af166b444c0 ("VMCI: dma dg: add MMIO access
to registers")
3. eed2298d936087a1c85e0fa6f7170028e4f4fded ("VMCI: dma dg: detect DMA
datagram capability")
4. 8cb520bea1470ca205980fbf030ed1f472f4af2f ("VMCI: dma dg: set OS page
size")
5. cc68f2177fcbfe2dbe5e9514789b96ba5995ec1e ("VMCI: dma dg: register dummy
IRQ handlers for DMA datagrams")
6. 5ee109828e73bbe4213c373988608d8f33e03d78 ("VMCI: dma dg: allocate send
and receive buffers for DMA datagrams")
7. 22aa5c7f323022477b70e044eb00e6bfea9498e8 ("VMCI: dma dg: add support for
DMA datagrams sends")
8. 463713eb6164b6577f8e91447c7745628215531b ("VMCI: dma dg: add support for
DMA datagrams receive")
9. 77e861619baea5a7c934e47fda74b03c0b072aec ("VMCI: Fix some error handling
paths in vmci_guest_probe_device()")
10. c8e9b30ccae605bf1dbeaf03971f9b83f70b928d ("VMCI: Release
notification_bitmap in error path")
11. 5df0e734b8c39598effe0f17e5bd8ff7748a0693 ("VMCI: Check exclusive_vectors
when freeing interrupt 1")
12. 1f7142915d304804a9bd952245fce92786b1b62f ("VMCI: Add support for ARM64")
13. ba03a9bbd17b149c373c0ea44017f35fc2cd0f28 ("VMCI: Release resource if the
work is already queued")
Thanks,
Vishnu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978145/+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 1978145] [NEW] Request to back port vmci patches to Ubuntu kernel
Public bug reported:
The request is to bring vmci to TOT and back port the following patches into
Ubuntu kernels.
1. fac608138c6136126faadafa5554cc0bbabf3c44 ("VMCI: dma dg: whitespace
formatting change for vmci register defines")
2. e283a0e8b7ea83915e988ed059384af166b444c0 ("VMCI: dma dg: add MMIO access to
registers")
3. eed2298d936087a1c85e0fa6f7170028e4f4fded ("VMCI: dma dg: detect DMA
datagram capability")
4. 8cb520bea1470ca205980fbf030ed1f472f4af2f ("VMCI: dma dg: set OS page size")
5. cc68f2177fcbfe2dbe5e9514789b96ba5995ec1e ("VMCI: dma dg: register dummy IRQ
handlers for DMA datagrams")
6. 5ee109828e73bbe4213c373988608d8f33e03d78 ("VMCI: dma dg: allocate send and
receive buffers for DMA datagrams")
7. 22aa5c7f323022477b70e044eb00e6bfea9498e8 ("VMCI: dma dg: add support for
DMA datagrams sends")
8. 463713eb6164b6577f8e91447c7745628215531b ("VMCI: dma dg: add support for
DMA datagrams receive")
9. 77e861619baea5a7c934e47fda74b03c0b072aec ("VMCI: Fix some error handling
paths in vmci_guest_probe_device()")
10. c8e9b30ccae605bf1dbeaf03971f9b83f70b928d ("VMCI: Release
notification_bitmap in error path")
11. 5df0e734b8c39598effe0f17e5bd8ff7748a0693 ("VMCI: Check exclusive_vectors
when freeing interrupt 1")
12. 1f7142915d304804a9bd952245fce92786b1b62f ("VMCI: Add support for ARM64")
13. ba03a9bbd17b149c373c0ea44017f35fc2cd0f28 ("VMCI: Release resource if the
work is already queued")
Thanks,
Vishnu
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1978145
Title:
Request to back port vmci patches to Ubuntu kernel
Status in linux package in Ubuntu:
New
Bug description:
The request is to bring vmci to TOT and back port the following patches into
Ubuntu kernels.
1. fac608138c6136126faadafa5554cc0bbabf3c44 ("VMCI: dma dg: whitespace
formatting change for vmci register defines")
2. e283a0e8b7ea83915e988ed059384af166b444c0 ("VMCI: dma dg: add MMIO access
to registers")
3. eed2298d936087a1c85e0fa6f7170028e4f4fded ("VMCI: dma dg: detect DMA
datagram capability")
4. 8cb520bea1470ca205980fbf030ed1f472f4af2f ("VMCI: dma dg: set OS page
size")
5. cc68f2177fcbfe2dbe5e9514789b96ba5995ec1e ("VMCI: dma dg: register dummy
IRQ handlers for DMA datagrams")
6. 5ee109828e73bbe4213c373988608d8f33e03d78 ("VMCI: dma dg: allocate send
and receive buffers for DMA datagrams")
7. 22aa5c7f323022477b70e044eb00e6bfea9498e8 ("VMCI: dma dg: add support for
DMA datagrams sends")
8. 463713eb6164b6577f8e91447c7745628215531b ("VMCI: dma dg: add support for
DMA datagrams receive")
9. 77e861619baea5a7c934e47fda74b03c0b072aec ("VMCI: Fix some error handling
paths in vmci_guest_probe_device()")
10. c8e9b30ccae605bf1dbeaf03971f9b83f70b928d ("VMCI: Release
notification_bitmap in error path")
11. 5df0e734b8c39598effe0f17e5bd8ff7748a0693 ("VMCI: Check exclusive_vectors
when freeing interrupt 1")
12. 1f7142915d304804a9bd952245fce92786b1b62f ("VMCI: Add support for ARM64")
13. ba03a9bbd17b149c373c0ea44017f35fc2cd0f28 ("VMCI: Release resource if the
work is already queued")
Thanks,
Vishnu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978145/+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 1976425] Re: Release of nvidia-graphics-drivers UDA/ERD 515.48.07 for Bionic, Focal, Impish, Jammy, Kinetic
** Summary changed: - Release of nvidia-graphics-drivers 515.48.07 for Bionic, Focal, Impish, Jammy, Kinetic + Release of nvidia-graphics-drivers UDA/ERD 515.48.07 for Bionic, Focal, Impish, Jammy, Kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1976425 Title: Release of nvidia-graphics-drivers UDA/ERD 515.48.07 for Bionic, Focal, Impish, Jammy, Kinetic Status in linux-restricted-modules package in Ubuntu: New Status in linux-restricted-modules source package in Bionic: New Status in linux-restricted-modules source package in Focal: New Status in linux-restricted-modules source package in Impish: New Status in linux-restricted-modules source package in Jammy: New Status in linux-restricted-modules source package in Kinetic: New Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Nvidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Changelog] RELEASE HIGHLIGHTS Published the source code to a variant of the NVIDIA Linux kernel modules dual-licensed as MIT/GPLv2. The source is available here: https://github.com/NVIDIA/open-gpu-kernel-modules and will be updated each driver release. Please see the "Open Linux Kernel Modules" chapter in the README for details. Added support for the VK_EXT_external_memory_dma_buf and VK_EXT_image_drm_format_modifier Vulkan extensions. To use this functionality, the nvidia-drm kernel module must be loaded with DRM KMS mode setting enabled. See the DRM KMS section of the README for guidance on enabling mode setting. Changed nvidia-suspend.service, nvidia-resume.service, and nvidia-hibernate.service to use WantedBy= rather than RequiredBy= dependencies for systemd-suspend.service and systemd-hibernate.service. This avoids a problem where suspend or hibernate fails if the NVIDIA driver is uninstalled without disabling these services first. See https://github.com/systemd/systemd/issues/21991 If these services were manually enabled, it may be necessary to update their dependencies by running sudo systemctl reenable nvidia-suspend.service nvidia-resume.service nvidia-hibernate.service Interlaced modes are now disabled when active stereo is enabled. NVIDIA X Server Settings will now display the quit confirmation dialog automatically if only there are pending changes that need to be manually saved. The corresponding configuration option to control the appearance of the quit dialog was thus also removed. Removed the warning message about mismatches between the compiler used to build the Linux kernel and the compiler used to build the NVIDIA kernel modules from nvidia-installer. Modern compilers are less likely to cause problems when this type of mismatch occurs, and it has become common in many distributions to build the Linux kernel with a different compiler than the default system compiler. Updated nvidia-installer to skip test-loading the kernel modules on systems where no supported NVIDIA GPUs are detected. Updated nvidia-installer to avoid a race condition which could cause the kernel module test load to fail due to udev automatically loading kernel modules left over from an existing NVIDIA driver installation. This failure resulted in an installation error message "Kernel module load error: File exists". Updated the RTD3 Video Memory Utilization Threshold (NVreg_DynamicPowerManagementVideoMemoryThreshold) maximum value from 200 MB to 1024 MB. Improved performance of GLX and Vulkan applications running in gamescope. Added a "kernelopen" feature tag to the supported-gpus.json file, to indicate which GPUs are compatible with open-gpu-kernel-modules. Improved Vulkan swapchain creation failure reporting. Applications can use the VK_EXT_debug_utils extension to receive additional information when an error was encountered in vkCreateSwapchainKHR(). Added a new configuration option for NVIDIA NGX to allow disabling the DSO signature check. See the "NGX" chapter of the README for more information. Fixed an issue where HDMI audio output was not working in some cases, especially w
[Kernel-packages] [Bug 1978136] [NEW] bluetooth devices searching infinite
Public bug reported: Even I don't see any message that any device was found. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 19:01:59 2022 InstallationDate: Installed on 2022-01-16 (143 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1978136 Title: bluetooth devices searching infinite Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Even I don't see any message that any device was found. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 19:01:59 2022 InstallationDate: Installed on 2022-01-16 (143 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1978136/+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 1978133] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978133 Title: System freeze followed by kernel panic or blank screen Status in linux package in Ubuntu: Confirmed Bug description: System keeps freezing in many different circumstances. I don't know how to reproduce this. Only happens on Ubuntu 22.04. Earlier versions were fine - tested Ubuntu impish and Debian bullseye. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 1593 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 12:22:34 2022 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0DC2CG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978133/+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 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
i'm seeing the same on an asm1064+jbm575 sata pcie card. it also appears to completely break one of the cards if you 2 sata pcie cards connected too. ie: i've recently bought and added an asm1166+jmb575 card which appears to work on all ports. the existing asm1064 based card is now failing to show any connected drive. testing 1 card at a time - functionally ok, but still the 'UBSAN: array- index-out-of-bounds' in dmesg with the asm1064+jbm575 card, so cards themselves appear good. -- 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTe
[Kernel-packages] [Bug 1978133] Re: System freeze followed by kernel panic or blank screen
** Attachment added: "journalctl blank screen" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978133/+attachment/5595973/+files/journalctl-blank-screen.log -- 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/1978133 Title: System freeze followed by kernel panic or blank screen Status in linux package in Ubuntu: New Bug description: System keeps freezing in many different circumstances. I don't know how to reproduce this. Only happens on Ubuntu 22.04. Earlier versions were fine - tested Ubuntu impish and Debian bullseye. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 1593 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 12:22:34 2022 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0DC2CG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978133/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
Bug confirmed on Oracle Cloud running Ubuntu 20.04.4 Kernel 5.13.0-1033-oracle. Workaround with ssh by Gerard(g-kok) works. thx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: In Progress Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-gcp-5.13 source package in Focal: Confirmed Status in linux-intel-iotg-5.15 source package in Focal: Confirmed Status in linux-oracle-5.13 source package in Focal: Confirmed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.610166] RAX: RBX: 0
[Kernel-packages] [Bug 1978133] [NEW] System freeze followed by kernel panic or blank screen
Public bug reported: System keeps freezing in many different circumstances. I don't know how to reproduce this. Only happens on Ubuntu 22.04. Earlier versions were fine - tested Ubuntu impish and Debian bullseye. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 1593 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 12:22:34 2022 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0DC2CG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "journalctl kernel panic" https://bugs.launchpad.net/bugs/1978133/+attachment/5595953/+files/journalctl-kernel-panic.log -- 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/1978133 Title: System freeze followed by kernel panic or blank screen Status in linux package in Ubuntu: New Bug description: System keeps freezing in many different circumstances. I don't know how to reproduce this. Only happens on Ubuntu 22.04. Earlier versions were fine - tested Ubuntu impish and Debian bullseye. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 1593 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 12:22:34 2022 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0DC2CG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978133/+subscriptions
[Kernel-packages] [Bug 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic
The fabric-manager-510 and libnvidia-nscq-510 were tested across all series on an A100 system. All testing passed the standard cuda testing. The packages tested were from https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/ppa/+packages?field.name_filter=-510&field.status_filter=published&field.series_filter= -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1975509 Title: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic Status in fabric-manager-510 package in Ubuntu: New Status in libnvidia-nscq-510 package in Ubuntu: New Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510-server package in Ubuntu: Fix Committed Status in fabric-manager-510 source package in Bionic: New Status in libnvidia-nscq-510 source package in Bionic: New Status in linux-restricted-modules source package in Bionic: Confirmed Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Released Status in fabric-manager-510 source package in Focal: New Status in libnvidia-nscq-510 source package in Focal: New Status in linux-restricted-modules source package in Focal: Confirmed Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Released Status in fabric-manager-510 source package in Impish: New Status in libnvidia-nscq-510 source package in Impish: New Status in linux-restricted-modules source package in Impish: Confirmed Status in nvidia-graphics-drivers-510-server source package in Impish: Fix Released Status in fabric-manager-510 source package in Jammy: New Status in libnvidia-nscq-510 source package in Jammy: New Status in linux-restricted-modules source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510-server source package in Jammy: Fix Released Status in fabric-manager-510 source package in Kinetic: New Status in libnvidia-nscq-510 source package in Kinetic: New Status in linux-restricted-modules source package in Kinetic: Confirmed Status in nvidia-graphics-drivers-510-server source package in Kinetic: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 kinetic/jammy/impish/focal/bionic === * New upstream release (LP: #1975509): - When calculating the address of grid barrier allocated for a CUDA stream, there was an off-by-one error. The address calculation is corrected in thisrelease. - An issue that caused an AC cycle test to fail with "AssertionError: NVLink links with inappropriate status found" is resolved. - An issue that caused NX 11 to become nonresponsive during a graphics operation is resolved. - Linking issues were observed when using libnvfm.so. Now and other depend tools use dynamic linking with libstdc++ and libgcc. - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some non-fatal nvlink interrupts is resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-510/+bug/1975509/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
linux-intel-iotg-5.15: 5.15.0-1003 good 5.15.0-1008 bad also reproducer (using podman) is smaller: podman run --rm -it alpine:3.16 ls which knocks down system versus podman run --rm -it busybox ls which doesn't -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: In Progress Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-gcp-5.13 source package in Focal: Confirmed Status in linux-intel-iotg-5.15 source package in Focal: Confirmed Status in linux-oracle-5.13 source package in Focal: Confirmed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796]
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
@mruffel: interesting, I am right now already at 5.15.0-37-generic from: APT-Sources: http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages I gave up with custom Kernels as it seemed they provide no clear improvement better then running the ubuntu package with iommu turned of as you recommended. The last I tried was 5.18.1, but that doesn't work with the virtualbox dkms stuff which I depend on for work. I assume this wont better with 5.19, but i can try later. I cannot say for sure if / how much of the problem existed in 21.10 because my usage scenario changed around the time when I updated - a new work project, more videocalls, and I am traveling and use the laptop more for media consumption as youtube and videos like this: https://www.zdf.de/gesellschaft/markus-lanz/markus-lanz-vom-7-juni-2022-100.html I had twice weekly videocalls with Teams in the browser which drove the CPU up and the fans on, but did not stutter to a point of being impossible. But now I (try to) use Zoom, every day, and it's basically not possible - I have to use my (twice as old and much weaker mobile CPU) windows tablet for this. I cannot "easily" start a full clean install as I need the machine for daily work, and setting everything up from scratch takes some while - but I will try to get a second disk to be able to do it but keep the exiting install to work as good as it is. I might be able to restore a pre-update state of my system into a free logical volume and run this. Will see how far i get! It might very well be that I have multiple problems at once and every one of them contributes a bit to the poor performance I see, also because multiple changes seem to lead to slightly better behaviour each: * turning iommu off makes things from extremely unsmooth to nearly acceptable * turning intel_boost off makes things a bit better and acceptable * moving from gnome to lxde gets me even pretty stutter free video(but not the UX I want...) It could be a combination of kernel / graphics library / gnome(-shell)... OR it could be *only* a kernel thing, but slightly suboptimal behaviour of graphics libaries and gnome. E.g. gnome-shell has a lot of short cpu load peaks on a single core, which should normally not block everything else but maybe can lead to video stuttering when process/IO management and scheduling are wrong in the first place... I'll keep testing and experimenting when I have spare time and report any findings here... -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-3
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
I can confirm going back to 5.13.0-1027-gcp from 5.13.0-1030-gcp fixed it for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: In Progress Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-gcp-5.13 source package in Focal: Confirmed Status in linux-intel-iotg-5.15 source package in Focal: Confirmed Status in linux-oracle-5.13 source package in Focal: Confirmed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.610166] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12
[Kernel-packages] [Bug 1971428] Re: CPU pipe A FIFO underrun
Taking a screenshot definitely triggers this for me, although it also happens on other occasions. -- 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/1971428 Title: CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Bug description: Upgraded from Ubuntu 20.04 to 22.04 at the release date. I get a blinking screen about 2-3 times a day. Dmesg shows the following: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Lenovo Thinkpad T480s connected to Lenovo Thinkpad Basic Docking Station, type 40AG. I'm not doing anything special when this happens. I've been using the same monitor, dock and cables for several years. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: oystein6834 F wireplumber /dev/snd/controlC1: oystein6834 F wireplumber /dev/snd/controlC0: oystein6834 F wireplumber /dev/snd/seq:oystein6832 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 3 14:46:03 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-08-03 (273 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20L8002VMX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e9eb1db1-6947-4826-85ca-b36e8bdf8f75 ro quiet splash i915.enable_psr=0 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-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-21 (11 days ago) WifiSyslog: dmi.bios.date: 11/17/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET72W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8002VMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN22ET72W(1.49):bd11/17/2021:br1.49:efr1.22:svnLENOVO:pn20L8002VMX:pvrThinkPadT480s:rvnLENOVO:rn20L8002VMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8002VMX dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971428/+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 1975460] Re: ubuntu 22.04 kernel 5.15.0.x iwlwifi cannot load firmware, wifi card does not work: Intel Corporation Wireless 7260
OK, I have tried stock ubuntu kernel version 5.15.0-37-generic
With /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="verbose intel_iommu=off"
firmware loads, wifi works.
[ 15.752699] iwlwifi :3d:00.0: loaded firmware version 17.3216344376.0
7260-17.ucode op_mode iwlmvm
[ 15.867847] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless N
7260, REV=0x144
[ 16.102146] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 16.104876] iwlwifi :3d:00.0 wlp61s0: renamed from wlan0
So yes, this is a workaround.
Maybe this should be set up by default in the kernel somehow.
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1975460
Title:
ubuntu 22.04 kernel 5.15.0.x iwlwifi cannot load firmware, wifi card
does not work: Intel Corporation Wireless 7260
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
With ubuntu 20.04, it worked.
After upgrading to 22.04, stopped working.
I have 2 pcs. of HP zbook G2, they both have the same error after upgrade.
Can't work!!
Booting back to old linux kernel 5.13.x wifi works again!
No windows installed, not a dual boot.
I have other older hp laptop which has a different wifi card, that
works well with the new kernel.
Please fix this bug.
Thank you!
Full ubuntu-bug report has been sent also.
Error msg:
[ 23.227024] iwlwifi :3d:00.0: loaded firmware version 17.3216344376.0
7260-17.ucode op_mode iwlmvm
[ 23.309876] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless N
7260, REV=0x144
[ 28.356103] iwlwifi :3d:00.0: Failed to load firmware chunk!
[ 28.356123] iwlwifi :3d:00.0: iwlwifi transaction failed, dumping
registers
[ 28.356140] iwlwifi :3d:00.0: iwlwifi device config registers:
[ 28.356415] iwlwifi :3d:00.0: : 08b18086 00100406 0280006b
0010 d014
[ 28.356437] iwlwifi :3d:00.0: 0020:
c0608086 00c8 0100
[ 28.356459] iwlwifi :3d:00.0: 0040: 00020010 10008ec0 00130c10
0106ec11 101100ca
[ 28.356480] iwlwifi :3d:00.0: 0060: 00080812 0405
00010001
[ 28.356523] iwlwifi :3d:00.0: 0080:
[ 28.356566] iwlwifi :3d:00.0: 00a0:
[ 28.356607] iwlwifi :3d:00.0: 00c0: c823d001
0d00 00814005 fee003f8
[ 28.356649] iwlwifi :3d:00.0: 00e0:
[ 28.356691] iwlwifi :3d:00.0: 0100: 14010001 4000
00462031 2000 2000 000e
[ 28.356732] iwlwifi :3d:00.0: 0120:
[ 28.356774] iwlwifi :3d:00.0: 0140: 14c10003 ff64778d e8b1fcff
15410018 08460846 0001000b 0141cafe 00f01e1f
[ 28.356815] iwlwifi :3d:00.0: iwlwifi device memory mapped registers:
[ 28.356891] iwlwifi :3d:00.0: : 00489204 8040 2000
0800
[ 28.356933] iwlwifi :3d:00.0: 0020: 0009 080003c5 0144
8000 803a 80008040 00080046
[ 28.356978] iwlwifi :3d:00.0: iwlwifi device AER capability structure:
[ 28.357034] iwlwifi :3d:00.0: : 14010001 4000
00462031 2000 2000 000e
[ 28.357075] iwlwifi :3d:00.0: 0020:
[ 28.357100] iwlwifi :3d:00.0: iwlwifi parent port (:3c:01.0)
config registers:
[ 28.357274] iwlwifi :3c:01.0: : 240412d8 00180407 06040005
00010010 003d3d3c 01f1
[ 28.357316] iwlwifi :3c:01.0: 0020: d010d010 0001fff1
0040 0002010a
[ 28.357357] iwlwifi :3c:01.0: 0040: ffc34c01 0008
00816405 fee002d8
[ 28.357399] iwlwifi :3c:01.0: 0060: 0034b009 04001060
04000800 8000 0a730100 76b50080 21901d27
[ 28.357440] iwlwifi :3c:01.0: 0080: 000f 3308
00790010 8000 116b 000f0022
[ 28.357482] iwlwifi :3c:01.0: 00a0:
c00d 240412d8
[ 28.357524] iwlwifi :3c:01.0: 00c0: 00620010 8001 0010
01203c11 10110042 014803c0
[ 28.357565] iwlwifi :3c:01.0: 00e0: 00040800 0400
00010042
[ 28.357607] iwlwifi :3c:01.0: 0100:
[Kernel-packages] [Bug 1978087] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => Low ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1978087 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: Invalid Bug description: not installed ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arsss 1298 F pulseaudio /dev/snd/controlC0: arsss 1298 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jun 9 17:19:39 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu3 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20369 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=2a960677-859f-46a6-9471-a9c94e8b41bd 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. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.release: 0.29 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G40-70 dmi.ec.firmware.release: 0.29 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:br0.29:efr0.29:svnLENOVO:pn20369:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG40-70:skuLENOVO_MT_20369_BU_idea_FM_LenovoG40-70: dmi.product.family: IDEAPAD dmi.product.name: 20369 dmi.product.sku: LENOVO_MT_20369_BU_idea_FM_Lenovo G40-70 dmi.product.version: Lenovo G40-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1978087/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
We can confirm on: 5.13.0-1028-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: In Progress Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-gcp-5.13 source package in Focal: Confirmed Status in linux-intel-iotg-5.15 source package in Focal: Confirmed Status in linux-oracle-5.13 source package in Focal: Confirmed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.610166] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.615417] RDX: 9152cf075280 RSI: 0
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
@timg-tpi Yes, in https://bugs.launchpad.net/bugs/1977973 I found 5.13.0-1027-gcp to work fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: In Progress Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-gcp-5.13 source package in Focal: Confirmed Status in linux-intel-iotg-5.15 source package in Focal: Confirmed Status in linux-oracle-5.13 source package in Focal: Confirmed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.610166] RAX: RBX: 000a801d RCX: 9152e07
[Kernel-packages] [Bug 1977508] Re: [UBUNTU 20.04] zfcp: fix failed recovery on gone remote port, non-NPIV FCP dev
** Tags added: upstream-stable -- 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/1977508 Title: [UBUNTU 20.04] zfcp: fix failed recovery on gone remote port, non-NPIV FCP dev Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Description: zfcp: fix failed recovery on gone remote port, non-NPIV FCP dev Symptom: With non-NPIV FCP devices, failed recovery on gone remote port. As follow-on error, failed paths after storage target NPIV failover with IBM FCP storage based on Spectrum Virtualize such as FlashSystem 9200, V7000, SAN Volume Controller, etc. Problem: Suppose we have an environment with a number of non-NPIV FCP devices (virtual HBAs / FCP devices / zfcp "adapter"s) sharing the same physical FCP channel (HBA port) and its I_T nexus. Plus a number of storage target ports zoned to such shared channel. Now one target port logs out of the fabric causing an RSCN. Zfcp reacts with an ADISC ELS and subsequent port recovery depending on the ADISC result. This happens on all such FCP devices (in different Linux images) concurrently as they all receive a copy of this RSCN. In the following we look at one of those FCP devices. Requests other than FSF_QTCB_FCP_CMND can be slow until they get a response. Depending on which requests are affected by slow responses, there are different recovery outcomes. Solution: Here we want to fix failed recoveries on port or adapter level by avoiding recovery requests that can be slow. We need the cached N_Port_ID for the remote port "link" test with ADISC. Just before sending the ADISC, we now intentionally forget the old cached N_Port_ID. The idea is that on receiving an RSCN for a port, we have to assume that any cached information about this port is stale. This forces a fresh new GID_PN [FC-GS] nameserver lookup on any subsequent recovery for the same port. Since we typically can still communicate with the nameserver efficiently, we now reach steady state quicker: Either the nameserver still does not know about the port so we stop recovery, or the nameserver already knows the port potentially with a new N_Port_ID and we can successfully and quickly perform open port recovery. For the one case, where ADISC returns successfully, we re-initialize port->d_id because that case does not involve any port recovery. This also solves a problem if the storage WWPN quickly logs into the fabric again but with a different N_Port_ID. Such as on virtual WWPN takeover during target NPIV failover. [https://www.redbooks.ibm.com/abstracts/redp5477.html] In that case the RSCN from the storage FDISC was ignored by zfcp and we could not successfully recover the failover. On some later failback on the storage, we could have been lucky if the virtual WWPN got the same old N_Port_ID from the SAN switch as we still had cached. Then the related RSCN triggered a successful port reopen recovery. However, there is no guarantee to get the same N_Port_ID on NPIV FDISC. Even though NPIV-enabled FCP devices are not affected by this problem, this code change optimizes recovery time for gone remote ports as a side effect. The timely drop of cached N_Port_IDs prevents unnecessary slow open port attempts. Reproduction: With a sufficiently shared FCP channel with non-NPIV FCP devs, perform SAN switch port disable on the storage side, or trigger storage target NPIV failover such as with Spectrum Virtualize CLI command "stopsystem -node 2". Upstream-ID: 8c9db6679be4348b8aae108e11d4be2f83976e30 Master-BZ-ID: 196197 Distros: Ubuntu 20.04 Ubuntu 21.10 Ubuntu 22.04 Author: Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977508/+subscriptions -- Mailing list: https://launchpad.net/~kerne
[Kernel-packages] [Bug 1976533] Re: [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices
** Tags added: tracking-upstream-stable ** Tags removed: tracking-upstream-stable ** Tags added: upstream-stable -- 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/1976533 Title: [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Description: s390/dasd: Fix data corruption for ESE devices Symptom: Filesystem errors and data inconsistency. Problem: Wrong tracks are formatted or the same track is formatted twice. 1. For ESE devices we get an error when accessing an unformatted track. The handling of this error will return zero data for read requests and format the track on demand before writing to it. To do this the code needs to distinguish between read and write requests. This is done with data from the blocklayer request. A pointer to the blocklayer request is stored in the CQR. If there is an error on the device an ERP request is built to do error recovery. While the ERP request is mostly a copy of the original CQR the pointer to the blocklayer request is not copied to not accidentally pass it back to the blocklayer without cleanup. This leads to the error that during ESE handling after an ERP request was built it is not possible to determine the IO direction. This leads to the formatting of a track for read requests which might in turn lead to data corruption. 2. When using alias devices a track might be accessed by multiple requests simultaneously and there is a race window that a track gets formatted twice resulting in data loss. Solution: 1. Return the callback data of the original request in case there are ERP requests build on top of it and thus determine the correct IO direction. 2. Prevent the double format by remembering the amount of formatted tracks when starting a request and comparing this number before actually formatting a track on the fly. If the number has changed there is a chance that the current track was finally formatted in between. As a result do not format the track and restart the current IO to check. Reproduction: Prepare an ESE DASD device using dasdfmt and fdasd. Install any filesystem on the prepared partitions and issue regular I/O using dd or any other tool while Alias DASD devices are set online as well. Upstream-ID: 5b53a405e4658580e1faf7c217db3f55a21ba849 71f3871657370dbbaf942a1c758f64e49a36c70f Problem-ID:198418 Preventive:yes Date: 2022-06-01 Author:hoepp...@linux.ibm.com Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1976533/+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 1977510] Re: [UBUNTU 20.04] hypfs: fix listing z/VM guests with access control group set
** Tags added: upstream-stable -- 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/1977510 Title: [UBUNTU 20.04] hypfs: fix listing z/VM guests with access control group set Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Description: hypfs: fix listing z/VM guests with access control group set Symptom: hypfs/hyptop info doesn't include z/VM guests with access control group set Problem: Currently if z/VM guest is allowed to retrieve hypervisor performance data globally for all guests (privilege class B) the query is formed in a way to include all guests but the group name is left empty. This leads to that z/VM guests which have access control group set not being included in the results (even local vm). Solution: Change the query group identifier from empty to "any" to retrieve information about all guests from any groups (or without a group set). Reproduction: Run hyptop under z/VM from a guest with privilege class B and some guest(s) with RACF/ACI groups set. Upstream-ID: 663d34c8df98740f1e90241e78e456d00b3c6cad Master-BZ ID: 196350 Distros: Ubuntu 20.04 Preventive:yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977510/+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 1977962] Re: [UBUNTU 21.10] s390/perf: obtain sie_block from the right address
I'm glad to see that commit:
c9bfb460c3e4 c9bfb460c3e4da2462e16b0f0b200990b36b1dd2 "s390/perf: obtain
sie_block from the right address"
is tagged (upstream) for stable updates with:
Cc: sta...@vger.kernel.org
With that, this commit will automatically be picked up by the Ubuntu kernel
teams
"Focal update: v5.4.xxx upstream stable release" process.
This hasn't happened yet with the latest ticket:
"Focal update: v5.4.191 upstream stable release" - LP#1976116
but will be soon.
This LP bug will be used for tracking the status.
** Tags added: tracking-upstream-stable
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags removed: tracking-upstream-stable
** Tags added: upstream-stable
--
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/1977962
Title:
[UBUNTU 21.10] s390/perf: obtain sie_block from the right address
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
Description: s390/perf: obtain sie_block from the right address
Symptom: Read from unitialized stack memory, incorrect guest
perf data reported, possibly system crash.
Problem: When perf is instructed to record a software-based event and
to trace the guest, i.e. using the following command:
perf kvm --guest --guestvmlinux=endless.elf top -e cpu-clock
The reported guest instruction pointer is inaccurate or
the system may crash.
This is caused by the sie_block being taken from empty1[0]
in sie_block() in arch/s390/kernel/perf_event.c, but since
1179f170b6f0 ("s390: fix fpu restore in entry.S")
it resides at empty1[1].
Solution: Obtain sie_block from the right address in sie_block().
Reproduction: 1. Start a KVM guest executing an endless loop.
2. Determine the instruction address of the loop.
3. Start perf recording for any software event and trace
the guest, for example using this command:
perf kvm --guest --guestvmlinux=endless.elf top -e
cpu-clock
4. The reported guest instruction addresses don't match
the loop's instruction address or the system crashes.
Upstream-ID: c9bfb460c3e4da2462e16b0f0b200990b36b1dd2
BBPF Probl.ID: 198450
Preventive:yes
Reported: -
SupportTicket: -
Reference: -
Date: 2022-06-02
Author:n...@linux.ibm.com
Component: kernel
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c9bfb460c3e4da2462e16b0f0b200990b36b1dd2
Problem occurs / affects impish and jammy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977962/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
@electricdaemon - please start a new bug report with sufficient detail that someone can diagnose the problem. Is this a regression from previous versions ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: In Progress Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-gcp-5.13 source package in Focal: Confirmed Status in linux-intel-iotg-5.15 source package in Focal: Confirmed Status in linux-oracle-5.13 source package in Focal: Confirmed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.610166] R
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
@electricdaemon - please start a new bug report with sufficient detail that someone can diagnose the problem. Is this a regression from previous versions ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: In Progress Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-gcp-5.13 source package in Focal: Confirmed Status in linux-intel-iotg-5.15 source package in Focal: Confirmed Status in linux-oracle-5.13 source package in Focal: Confirmed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.610166] R
[Kernel-packages] [Bug 1967856] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595908/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2] No
[Kernel-packages] [Bug 1967856] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595905/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2] No
[Kernel-packages] [Bug 1967856] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595906/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error
[Kernel-packages] [Bug 1967856] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595910/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2] No s
[Kernel-packages] [Bug 1967856] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595907/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno
[Kernel-packages] [Bug 1967856] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595909/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2] No such file
[Kernel-packages] [Bug 1967856] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595911/+files/acpidump.txt ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 r
[Kernel-packages] [Bug 1967856] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595904/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2] No such fi
[Kernel-packages] [Bug 1967856] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595903/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2] No such
[Kernel-packages] [Bug 1967856] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595902/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 1967856] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595901/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2]
[Kernel-packages] [Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
This issue has been fixed by a patch to the openvswitch datapath code in the kernel [0]. The patched kernel would be required when used in conjunction with OVN 21.12 or newer, which translates to Focal (yoga UCA), Jammy and Kinetic. 0: https://lore.kernel.org/netdev/20220606221140.488984-1-i.maxim...@ovn.org/T/#u ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete ** Also affects: openvswitch (Ubuntu Kinetic) Importance: High Status: Invalid ** Also affects: ovn (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: openvswitch (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ovn (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: openvswitch (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ovn (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: ovn (Ubuntu Jammy) Status: New => Invalid ** Changed in: ovn (Ubuntu Focal) Status: New => Invalid ** Changed in: openvswitch (Ubuntu Jammy) Status: New => Invalid ** Changed in: openvswitch (Ubuntu Focal) Status: New => Invalid ** Tags added: apport-collected jammy uec-images ** Description changed: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,t
[Kernel-packages] [Bug 1967856] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1967856 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Incomplete Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: New Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Incomplete Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,cod
[Kernel-packages] [Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: openvswitch (Ubuntu) Status: Triaged => 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/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Incomplete Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: New Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: New Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Incomplete Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : ke
[Kernel-packages] [Bug 1978087] [NEW] package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned er
Public bug reported: not installed ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arsss 1298 F pulseaudio /dev/snd/controlC0: arsss 1298 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jun 9 17:19:39 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu3 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20369 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=2a960677-859f-46a6-9471-a9c94e8b41bd 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. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.release: 0.29 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G40-70 dmi.ec.firmware.release: 0.29 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:br0.29:efr0.29:svnLENOVO:pn20369:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG40-70:skuLENOVO_MT_20369_BU_idea_FM_LenovoG40-70: dmi.product.family: IDEAPAD dmi.product.name: 20369 dmi.product.sku: LENOVO_MT_20369_BU_idea_FM_Lenovo G40-70 dmi.product.version: Lenovo G40-70 dmi.sys.vendor: LENOVO ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1978087 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: not installed ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arsss 1298 F pulseaudio /dev/snd/controlC0: arsss 1298 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jun 9 17:19:39 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu3 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20369 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=2a960677-859f-46a6-9471-a9c94e8b41bd 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. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.release: 0.29 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO d
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
below kernels on azure have this issue. please hold on the new images which contain these kernel releases. thanks. focal/linux-azure-5.13: 5.13.0-1026-azure focal/linux-azure-5.15: 5.15.0-1008-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: In Progress Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-gcp-5.13 source package in Focal: Confirmed Status in linux-intel-iotg-5.15 source package in Focal: Confirmed Status in linux-oracle-5.13 source package in Focal: Confirmed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b502
[Kernel-packages] [Bug 1977835] Re: Focal update: upstream stable patchset 2022-06-07
** Tags added: oem-priority originate-from-1977682 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1977835 Title: Focal update: upstream stable patchset 2022-06-07 Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Confirmed Status in linux-oem-5.14 source package in Focal: New 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 2022-06-07 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1977835/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
Test kernel posted fixes crash but has another bug with unkillable stuck defunct docker-proxy service causing more issues. Bug is not solved. Tested on Linux AWS Lightsail instance. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: In Progress Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-gcp-5.13 source package in Focal: Confirmed Status in linux-intel-iotg-5.15 source package in Focal: Confirmed Status in linux-oracle-5.13 source package in Focal: Confirmed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 0
[Kernel-packages] [Bug 1924741] Re: Load Broadcom firmware for Dell Bluetooth device [413c:8197]
This issue was fixed by a patch to `bluetooth-next`, which was accepted
into the v5.15 kernel included with Ubuntu 22.04 LTS.
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
next.git/commit/?id=340cd23d9dec58b1b07ecaa205a161faf50eab8a
I can confirm that, if present, the `BCM20702A1-413c-8197.hcd` patch is
loaded for my BCM20702A0 device on stock Ubuntu, and thus duplex audio
for both HSP and HFP modes works as expected.
--
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/1924741
Title:
Load Broadcom firmware for Dell Bluetooth device [413c:8197]
Status in linux package in Ubuntu:
Fix Released
Bug description:
The Broadcom Bluetooth kernel module supports loading patches for
specific hardware devices. Which devices require patchram support is
defined in an array of structs in the kernel module `btusb`, which
allow matching by Vendor ID and, optionally, Product ID.
The Dell-branded device `413c:8197` requires the patch
`BCM20702A1-413c-8197.hcd`[1] to be loaded in order for HSP/HFP
functionality to work (A2DP and AVRCP work without the patch).
However, the patch is not sought for this device by `btusb`.
In 2011, `413c:8197` was included in the module[2], but not marked as
requiring patchram. Later, in 2017, a blanket entry was added for all
Dell-branded (`413c`) devices[3], marking them as requiring patchram.
However, the previous entry for `413c:8197` was not removed and
appears to block the patchram requirement from being added for this
device (presumably the algorithm stops searching after the first
match). The code stands like so:
```
static const struct usb_device_id btusb_table[] = {
...
/* Broadcom BCM20702A0 */
{ USB_DEVICE(0x413c, 0x8197) },
...
/* Dell Computer - Broadcom based */
{ USB_VENDOR_AND_INTERFACE_INFO(0x413c, 0xff, 0x01, 0x01),
.driver_info = BTUSB_BCM_PATCHRAM },
```
I would like to request removal of the earlier entry to facilitate
patchram support for device `413c:8197`.
I have tested this as working on my Dell Precision M6700 running
Ubuntu 20.04 with kernel `5.4.0-71-generic`.
[1]:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM20702A1-413c-8197.hcd
[2]:
https://github.com/torvalds/linux/commit/d13431ca3eb2a2c14314f04813cdc11cd869f150
[3]:
https://github.com/torvalds/linux/commit/fdfddc601713d4ed564b0bd25b29415bd622020a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924741/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-intel-iotg-5.15 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: In Progress Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-gcp-5.13 source package in Focal: Confirmed Status in linux-intel-iotg-5.15 source package in Focal: Confirmed Status in linux-oracle-5.13 source package in Focal: Confirmed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.610166] RA
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-intel-iotg-5.15 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: In Progress Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-gcp-5.13 source package in Focal: Confirmed Status in linux-intel-iotg-5.15 source package in Focal: Confirmed Status in linux-oracle-5.13 source package in Focal: Confirmed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.610166] RAX: 000
[Kernel-packages] [Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel
** Tags added: jellyfish-edge-staging -- 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/1842320 Title: Out of Memory on boot with 5.2.0 kernel Status in grub: Unknown Status in OEM Priority Project: In Progress Status in grub2-signed package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d". Can still boot using the previous 5.0.0-25-generic kernel, but the 5.2.0-15-generic fails to start. On selecting Ubuntu from Grub, the message "error: out of memory." is immediately shown. Pressing a key attempts to start boot-up but fails to mount root fs. Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free shows the following (run from Gnome terminal): totalusedfree shared buff/cache available Mem:7906564 1761196 3833240 1020216 2312128 4849224 Swap: 1003516 0 1003516 Kernel packages installed: linux-generic 5.2.0.15.16 amd64 linux-headers-5.2.0-15 5.2.0-15.16 all linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64 linux-headers-generic 5.2.0.15.16 amd64 linux-image-5.0.0-25-generic 5.0.0-25.26 amd64 linux-image-5.2.0-15-generic 5.2.0-15.16+signed1 amd64 linux-image-generic5.2.0.15.16 amd64 linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64 linux-modules-extra-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-extra-5.2.0-15-generic 5.2.0-15.16 amd64 Photo of kernel panic attached. NVMe drive partition layout (GPT): Device StartEnd Sectors Size Type /dev/nvme0n1p120481050623 1048576 512M EFI System /dev/nvme0n1p2 10506242549759 1499136 732M Linux filesystem /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem $ sudo pvs PV VGFmt Attr PSizePFree /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a-- <475.71g0 $ sudo lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root ubuntu-vg -wi-ao 474.75g swap_1 ubuntu-vg -wi-ao 980.00m Partition 3 is LUKS encrypted. Root LV is ext4. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gmckeown 1647 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-15 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision FHD Camera Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.181 Tags: eoan Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.25:bd05/17/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 2QH38EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1842320/+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 1971144] Re: Black screen after login when using CKLau-64HUA KVM switch
** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971144 Title: Black screen after login when using CKLau-64HUA KVM switch Status in linux package in Ubuntu: Confirmed Bug description: After I log in from the login screen, I just get a black screen. To get a GUI, I then press "CTL+Alt+F4", to get a console login, and then do "sudo startx". I have tried both options from the bottom right corner for logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Mon May 2 14:01:43 2022 DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 5.13.0-22-generic, x86_64: installed bcmwl/6.30.223.271+bdcom, 5.13.0-40-generic, x86_64: installed bcmwl/6.30.223.271+bdcom, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:0141] InstallationDate: Installed on 2020-11-28 (520 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. Macmini7,1 ProcEnviron: LANGUAGE=en_ZA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=278bd098-563c-4e88-85c7-d0dd2d492987 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (3 days ago) dmi.bios.date: 09/16/2021 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 432.40.8.0.1 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-35C5E08120C7EEAF dmi.board.vendor: Apple Inc. dmi.board.version: Macmini7,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-35C5E08120C7EEAF dmi.modalias: dmi:bvnAppleInc.:bvr432.40.8.0.1:bd09/16/2021:br0.1:svnAppleInc.:pnMacmini7,1:pvr1.0:rvnAppleInc.:rnMac-35C5E08120C7EEAF:rvrMacmini7,1:cvnAppleInc.:ct10:cvrMac-35C5E08120C7EEAF:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: Macmini7,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/ubuntu/+source/linux/+bug/1971144/+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 1924741] Re: Load Broadcom firmware for Dell Bluetooth device [413c:8197]
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1924741
Title:
Load Broadcom firmware for Dell Bluetooth device [413c:8197]
Status in linux package in Ubuntu:
Fix Released
Bug description:
The Broadcom Bluetooth kernel module supports loading patches for
specific hardware devices. Which devices require patchram support is
defined in an array of structs in the kernel module `btusb`, which
allow matching by Vendor ID and, optionally, Product ID.
The Dell-branded device `413c:8197` requires the patch
`BCM20702A1-413c-8197.hcd`[1] to be loaded in order for HSP/HFP
functionality to work (A2DP and AVRCP work without the patch).
However, the patch is not sought for this device by `btusb`.
In 2011, `413c:8197` was included in the module[2], but not marked as
requiring patchram. Later, in 2017, a blanket entry was added for all
Dell-branded (`413c`) devices[3], marking them as requiring patchram.
However, the previous entry for `413c:8197` was not removed and
appears to block the patchram requirement from being added for this
device (presumably the algorithm stops searching after the first
match). The code stands like so:
```
static const struct usb_device_id btusb_table[] = {
...
/* Broadcom BCM20702A0 */
{ USB_DEVICE(0x413c, 0x8197) },
...
/* Dell Computer - Broadcom based */
{ USB_VENDOR_AND_INTERFACE_INFO(0x413c, 0xff, 0x01, 0x01),
.driver_info = BTUSB_BCM_PATCHRAM },
```
I would like to request removal of the earlier entry to facilitate
patchram support for device `413c:8197`.
I have tested this as working on my Dell Precision M6700 running
Ubuntu 20.04 with kernel `5.4.0-71-generic`.
[1]:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM20702A1-413c-8197.hcd
[2]:
https://github.com/torvalds/linux/commit/d13431ca3eb2a2c14314f04813cdc11cd869f150
[3]:
https://github.com/torvalds/linux/commit/fdfddc601713d4ed564b0bd25b29415bd622020a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924741/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
** Also affects: linux-intel-iotg-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: New Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: In Progress Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-gcp-5.13 source package in Focal: Confirmed Status in linux-intel-iotg-5.15 source package in Focal: New Status in linux-oracle-5.13 source package in Focal: Confirmed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.610166] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12
[Kernel-packages] [Bug 1971144] [NEW] Black screen after login when using CKLau-64HUA KVM switch
You have been subscribed to a public bug: After I log in from the login screen, I just get a black screen. To get a GUI, I then press "CTL+Alt+F4", to get a console login, and then do "sudo startx". I have tried both options from the bottom right corner for logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Mon May 2 14:01:43 2022 DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 5.13.0-22-generic, x86_64: installed bcmwl/6.30.223.271+bdcom, 5.13.0-40-generic, x86_64: installed bcmwl/6.30.223.271+bdcom, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:0141] InstallationDate: Installed on 2020-11-28 (520 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. Macmini7,1 ProcEnviron: LANGUAGE=en_ZA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=278bd098-563c-4e88-85c7-d0dd2d492987 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (3 days ago) dmi.bios.date: 09/16/2021 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 432.40.8.0.1 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-35C5E08120C7EEAF dmi.board.vendor: Apple Inc. dmi.board.version: Macmini7,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-35C5E08120C7EEAF dmi.modalias: dmi:bvnAppleInc.:bvr432.40.8.0.1:bd09/16/2021:br0.1:svnAppleInc.:pnMacmini7,1:pvr1.0:rvnAppleInc.:rnMac-35C5E08120C7EEAF:rvrMacmini7,1:cvnAppleInc.:ct10:cvrMac-35C5E08120C7EEAF:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: Macmini7,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy ubuntu -- Black screen after login when using CKLau-64HUA KVM switch https://bugs.launchpad.net/bugs/1971144 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973086] Re: System won't go into suspend normally with kernel above 5.13.0-35
Just updating to mention this problem is still present in 5.13.0-48 -- 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/1973086 Title: System won't go into suspend normally with kernel above 5.13.0-35 Status in linux-hwe package in Ubuntu: New Bug description: Problem: The system does not suspend normally when using a kernel above version 5.13.0-35, and instead locks up and must be reset. 1) Ubuntu Studio 20.04 Description: Ubuntu 20.04.4 LTS Release: 20.04 2) Kernel 5.13.0-37, 5.13.0-40, 5.13.0-41 all do the same... 3) What I expect to happen: System goes into STR state normally and can be resumed upon pressing the power button. 4) What happens instead: Screen goes blank, hard drives spin down, then spin back up again, screen stays blank, system does not enter STR state (CPU, GPU, PSU fans keeps running etc), and system is now locked up and can't be recovered unless hard reset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1973086/+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 1977962] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2022-06-09 03:12 EDT---
*** Bug 198475 has been marked as a duplicate of this bug. ***
--
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/1977962
Title:
[UBUNTU 21.10] s390/perf: obtain sie_block from the right address
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
Description: s390/perf: obtain sie_block from the right address
Symptom: Read from unitialized stack memory, incorrect guest
perf data reported, possibly system crash.
Problem: When perf is instructed to record a software-based event and
to trace the guest, i.e. using the following command:
perf kvm --guest --guestvmlinux=endless.elf top -e cpu-clock
The reported guest instruction pointer is inaccurate or
the system may crash.
This is caused by the sie_block being taken from empty1[0]
in sie_block() in arch/s390/kernel/perf_event.c, but since
1179f170b6f0 ("s390: fix fpu restore in entry.S")
it resides at empty1[1].
Solution: Obtain sie_block from the right address in sie_block().
Reproduction: 1. Start a KVM guest executing an endless loop.
2. Determine the instruction address of the loop.
3. Start perf recording for any software event and trace
the guest, for example using this command:
perf kvm --guest --guestvmlinux=endless.elf top -e
cpu-clock
4. The reported guest instruction addresses don't match
the loop's instruction address or the system crashes.
Upstream-ID: c9bfb460c3e4da2462e16b0f0b200990b36b1dd2
BBPF Probl.ID: 198450
Preventive:yes
Reported: -
SupportTicket: -
Reference: -
Date: 2022-06-02
Author:n...@linux.ibm.com
Component: kernel
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c9bfb460c3e4da2462e16b0f0b200990b36b1dd2
Problem occurs / affects impish and jammy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977962/+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 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
** Changed in: mutter (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in mutter source package in Jammy:
Fix Released
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
also present in linux-image-5.15.0-1008-intel-iotg: ## [ 1666.319425] [ cut here ] [ 1666.319433] kernel BUG at include/linux/fs.h:3082! [ 1666.319443] invalid opcode: [#3] SMP NOPTI [ 1666.319449] CPU: 0 PID: 17586 Comm: ls Tainted: G D 5.15.0-1008-intel-iotg #11~20.04.1-Ubuntu [ 1666.319454] Hardware name: Dell Inc. Precision 5560/XX, BIOS 1.8.0 02/08/2022 [ 1666.319457] RIP: 0010:__fput+0x265/0x270 [ 1666.319466] Code: 00 48 85 ff 0f 84 6d fe ff ff f6 c7 40 0f 85 64 fe ff ff e8 6d 39 00 00 e9 5a fe ff ff 4c 89 f7 e8 70 96 02 00 e9 97 fe ff ff <0f> 0b 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 [ 1666.319471] RSP: 0018:b3d605127d70 EFLAGS: 00010246 [ 1666.319477] RAX: RBX: 000a801d RCX: [ 1666.319480] RDX: RSI: 9ffb59f1 RDI: [ 1666.319483] RBP: b3d605127d98 R08: 942c84c70780 R09: 942c8c60b520 [ 1666.319485] R10: 0010 R11: 9433ef5f0c40 R12: 942c86b08300 [ 1666.319488] R13: 942c8c60b520 R14: 942c9079d060 R15: 942c8a54ef00 [ 1666.319490] FS: () GS:9433ef40() knlGS: [ 1666.319494] CS: 0010 DS: ES: CR0: 80050033 [ 1666.319497] CR2: 7ffcbd0a85c9 CR3: 000236f96001 CR4: 00770ef0 [ 1666.319500] PKRU: 5554 [ 1666.319503] Call Trace: [ 1666.319505] [ 1666.319510] fput+0xe/0x10 [ 1666.319515] task_work_run+0x6d/0xb0 [ 1666.319523] exit_to_user_mode_prepare+0x1b2/0x1c0 [ 1666.319529] syscall_exit_to_user_mode+0x27/0x50 [ 1666.319536] do_syscall_64+0x69/0xc0 [ 1666.319543] ? handle_mm_fault+0xd8/0x2b0 [ 1666.319550] ? exit_to_user_mode_prepare+0x3d/0x1c0 [ 1666.319555] ? do_user_addr_fault+0x1dc/0x650 [ 1666.319560] ? irqentry_exit_to_user_mode+0x9/0x20 [ 1666.319565] ? irqentry_exit+0x19/0x30 [ 1666.319569] ? exc_page_fault+0x89/0x160 [ 1666.319573] ? asm_exc_page_fault+0x8/0x30 [ 1666.319580] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1666.319585] RIP: 0033:0x60003530 [ 1666.319592] Code: Unable to access opcode bytes at RIP 0x60003506. [ 1666.319595] RSP: 002b:7ffcbd0a83e0 EFLAGS: 0200 ORIG_RAX: 003b [ 1666.319599] RAX: RBX: RCX: [ 1666.319602] RDX: RSI: RDI: [ 1666.319604] RBP: R08: R09: [ 1666.319606] R10: R11: R12: [ 1666.319608] R13: R14: R15: [ 1666.319612] [ 1666.319614] Modules linked in: overlay uhid rfcomm ccm snd_hda_codec_hdmi cmac algif_hash algif_skcipher af_alg bnep binfmt_misc joydev snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_ctl_led snd_sof_xtensa_dsp snd_sof snd_hda_codec_realtek snd_soc_hdac_hda snd_hda_ext_core snd_hda_codec_generic snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress intel_tcc_cooling ac97_bus snd_pcm_dmaengine x86_pkg_temp_thermal snd_hda_intel intel_powerclamp snd_intel_dspcfg snd_intel_sdw_acpi mei_dal mei_hdcp dell_laptop coretemp snd_hda_codec intel_rapl_msr kvm_intel snd_hda_core dell_wmi snd_hwdep ledtrig_audio kvm iwlmvm snd_pcm dell_smbios dcdbas snd_seq_midi mac80211 intel_cstate snd_seq_midi_event snd_rawmidi libarc4 nls_iso8859_1 dell_wmi_descriptor wmi_bmof firmware_attributes_class serio_raw uvcvideo snd_seq videobuf2_vmalloc efi_pstore hid_sensor_custom_intel_hinge [ 1666.319704] snd_seq_device videobuf2_memops hid_sensor_als iwlwifi videobuf2_v4l2 hid_sensor_trigger snd_timer r8153_ecm hci_uart cdc_ether industrialio_triggered_buffer iwlmei videobuf2_common usbnet kfifo_buf processor_thermal_device_pci_legacy ee1004 hid_sensor_iio_common input_leds cfg80211 industrialio r8152 processor_thermal_device videodev snd btqca btusb processor_thermal_rfim mei_me processor_thermal_mbox btrtl pmt_telemetry btbcm cros_ec_ishtp mii processor_thermal_rapl mc hid_multitouch soundcore mei pmt_class cros_ec btintel ucsi_acpi intel_rapl_common bluetooth typec_ucsi intel_soc_dts_iosf typec ecdh_generic ecc dptf_power int3403_thermal soc_button_array int340x_thermal_zone mac_hid intel_skl_int3472 intel_hid int3400_thermal acpi_thermal_rel sparse_keymap acpi_pad acpi_tad ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack sch_fq_codel nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ipmi_devintf ip6_tables ipmi_msghandler msr [ 1666.319801] iptable_filter parport_pc bpfilter ppdev lp parport sunrpc ip_tables x_tables autofs4 dm_crypt usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid i915 i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillre
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
hit same problem using podman in rootless on linux-image-5.15.0-1008-intel-iotg: ## [ 1666.319425] [ cut here ] [ 1666.319433] kernel BUG at include/linux/fs.h:3082! [ 1666.319443] invalid opcode: [#3] SMP NOPTI [ 1666.319449] CPU: 0 PID: 17586 Comm: ls Tainted: G D 5.15.0-1008-intel-iotg #11~20.04.1-Ubuntu [ 1666.319454] Hardware name: Dell Inc. Precision 5560/XX, BIOS 1.8.0 02/08/2022 [ 1666.319457] RIP: 0010:__fput+0x265/0x270 [ 1666.319466] Code: 00 48 85 ff 0f 84 6d fe ff ff f6 c7 40 0f 85 64 fe ff ff e8 6d 39 00 00 e9 5a fe ff ff 4c 89 f7 e8 70 96 02 00 e9 97 fe ff ff <0f> 0b 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 [ 1666.319471] RSP: 0018:b3d605127d70 EFLAGS: 00010246 [ 1666.319477] RAX: RBX: 000a801d RCX: [ 1666.319480] RDX: RSI: 9ffb59f1 RDI: [ 1666.319483] RBP: b3d605127d98 R08: 942c84c70780 R09: 942c8c60b520 [ 1666.319485] R10: 0010 R11: 9433ef5f0c40 R12: 942c86b08300 [ 1666.319488] R13: 942c8c60b520 R14: 942c9079d060 R15: 942c8a54ef00 [ 1666.319490] FS: () GS:9433ef40() knlGS: [ 1666.319494] CS: 0010 DS: ES: CR0: 80050033 [ 1666.319497] CR2: 7ffcbd0a85c9 CR3: 000236f96001 CR4: 00770ef0 [ 1666.319500] PKRU: 5554 [ 1666.319503] Call Trace: [ 1666.319505] [ 1666.319510] fput+0xe/0x10 [ 1666.319515] task_work_run+0x6d/0xb0 [ 1666.319523] exit_to_user_mode_prepare+0x1b2/0x1c0 [ 1666.319529] syscall_exit_to_user_mode+0x27/0x50 [ 1666.319536] do_syscall_64+0x69/0xc0 [ 1666.319543] ? handle_mm_fault+0xd8/0x2b0 [ 1666.319550] ? exit_to_user_mode_prepare+0x3d/0x1c0 [ 1666.319555] ? do_user_addr_fault+0x1dc/0x650 [ 1666.319560] ? irqentry_exit_to_user_mode+0x9/0x20 [ 1666.319565] ? irqentry_exit+0x19/0x30 [ 1666.319569] ? exc_page_fault+0x89/0x160 [ 1666.319573] ? asm_exc_page_fault+0x8/0x30 [ 1666.319580] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1666.319585] RIP: 0033:0x60003530 [ 1666.319592] Code: Unable to access opcode bytes at RIP 0x60003506. [ 1666.319595] RSP: 002b:7ffcbd0a83e0 EFLAGS: 0200 ORIG_RAX: 003b [ 1666.319599] RAX: RBX: RCX: [ 1666.319602] RDX: RSI: RDI: [ 1666.319604] RBP: R08: R09: [ 1666.319606] R10: R11: R12: [ 1666.319608] R13: R14: R15: [ 1666.319612] [ 1666.319614] Modules linked in: overlay uhid rfcomm ccm snd_hda_codec_hdmi cmac algif_hash algif_skcipher af_alg bnep binfmt_misc joydev snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_ctl_led snd_sof_xtensa_dsp snd_sof snd_hda_codec_realtek snd_soc_hdac_hda snd_hda_ext_core snd_hda_codec_generic snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress intel_tcc_cooling ac97_bus snd_pcm_dmaengine x86_pkg_temp_thermal snd_hda_intel intel_powerclamp snd_intel_dspcfg snd_intel_sdw_acpi mei_dal mei_hdcp dell_laptop coretemp snd_hda_codec intel_rapl_msr kvm_intel snd_hda_core dell_wmi snd_hwdep ledtrig_audio kvm iwlmvm snd_pcm dell_smbios dcdbas snd_seq_midi mac80211 intel_cstate snd_seq_midi_event snd_rawmidi libarc4 nls_iso8859_1 dell_wmi_descriptor wmi_bmof firmware_attributes_class serio_raw uvcvideo snd_seq videobuf2_vmalloc efi_pstore hid_sensor_custom_intel_hinge [ 1666.319704] snd_seq_device videobuf2_memops hid_sensor_als iwlwifi videobuf2_v4l2 hid_sensor_trigger snd_timer r8153_ecm hci_uart cdc_ether industrialio_triggered_buffer iwlmei videobuf2_common usbnet kfifo_buf processor_thermal_device_pci_legacy ee1004 hid_sensor_iio_common input_leds cfg80211 industrialio r8152 processor_thermal_device videodev snd btqca btusb processor_thermal_rfim mei_me processor_thermal_mbox btrtl pmt_telemetry btbcm cros_ec_ishtp mii processor_thermal_rapl mc hid_multitouch soundcore mei pmt_class cros_ec btintel ucsi_acpi intel_rapl_common bluetooth typec_ucsi intel_soc_dts_iosf typec ecdh_generic ecc dptf_power int3403_thermal soc_button_array int340x_thermal_zone mac_hid intel_skl_int3472 intel_hid int3400_thermal acpi_thermal_rel sparse_keymap acpi_pad acpi_tad ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack sch_fq_codel nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ipmi_devintf ip6_tables ipmi_msghandler msr [ 1666.319801] iptable_filter parport_pc bpfilter ppdev lp parport sunrpc ip_tables x_tables autofs4 dm_crypt usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid i915 i2c_a
[Kernel-packages] [Bug 1977510] Re: [UBUNTU 20.04] hypfs: fix listing z/VM guests with access control group set
I'm glad to see that the commit: 663d34c8df98 663d34c8df98740f1e90241e78e456d00b3c6cad "s390/hypfs: include z/VM guests with access control group set" got tagged for stable update: "Cc: sta...@vger.kernel.org" With that, such commits will automatically be picked up by the Ubuntu kernel team's " update: vx.x.xxx upstream stable release" process. And this already happend for this upstream commit 663d34c8df98 "s390/hypfs: include z/VM guests with access control group set" and it landed as: c69c6a859ddf in focal and is included in "Ubuntu-5.4.0-108.122" and newer kernels, 2c1d2cb370a0 in impish and is included in "Ubuntu-5.13.0-40.45" and newer kernels, and as 385f0593f13e in jammy and is included in "Ubuntu-5.15.0-20.20" and newer kernels. And since the commit got upstream accepted with 5.17, it will automatically be part of the planned kinetic kernel (5.19). With this I'm closing this bug as Fix Released. ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Fix Released ** Changed in: linux (Ubuntu Impish) Status: New => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Released ** Changed in: ubuntu-z-systems Status: New => 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/1977510 Title: [UBUNTU 20.04] hypfs: fix listing z/VM guests with access control group set Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Description: hypfs: fix listing z/VM guests with access control group set Symptom: hypfs/hyptop info doesn't include z/VM guests with access control group set Problem: Currently if z/VM guest is allowed to retrieve hypervisor performance data globally for all guests (privilege class B) the query is formed in a way to include all guests but the group name is left empty. This leads to that z/VM guests which have access control group set not being included in the results (even local vm). Solution: Change the query group identifier from empty to "any" to retrieve information about all guests from any groups (or without a group set). Reproduction: Run hyptop under z/VM from a guest with privilege class B and some guest(s) with RACF/ACI groups set. Upstream-ID: 663d34c8df98740f1e90241e78e456d00b3c6cad Master-BZ ID: 196350 Distros: Ubuntu 20.04 Preventive:yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977510/+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
