[Kernel-packages] [Bug 1958416] Re: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64
This bug was fixed in the package linux-gcp - 5.4.0-1097.106 --- linux-gcp (5.4.0-1097.106) focal; urgency=medium * focal/linux-gcp: 5.4.0-1097.106 -proposed tracker (LP: #1997813) * b/linux-gcp-5.4: log_check WARNING on n2d-standard-64 (LP: #1958416) - x86, swiotlb: Adjust SWIOTLB bounce buffer size for SEV guests [ Ubuntu: 5.4.0-136.153 ] * focal/linux: 5.4.0-136.153 -proposed tracker (LP: #1997835) * Expose built-in trusted and revoked certificates (LP: #1996892) - [Packaging] Expose built-in trusted and revoked certificates * [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait (LP: #1995941) - KVM: s390: pv: don't present the ecall interrupt twice * [UBUNTU 20.04] boot: Add s390x secure boot trailer (LP: #1996071) - s390/boot: add secure boot trailer * Fix rfkill causing soft blocked wifi (LP: #1996198) - platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi * md: Replace snprintf with scnprintf (LP: #1993315) - md: Replace snprintf with scnprintf * input/keyboard: the keyboard on some Asus laptops can't work (LP: #1992266) - ACPI: resource: Skip IRQ override on Asus Vivobook K3402ZA/K3502ZA - ACPI: resource: Add ASUS model S5402ZA to quirks * Focal update: v5.4.218 upstream stable release (LP: #1995530) - mm: pagewalk: Fix race between unmap and page walker - perf tools: Fixup get_current_dir_name() compilation - firmware: arm_scmi: Add SCMI PM driver remove routine - dmaengine: xilinx_dma: cleanup for fetching xlnx,num-fstores property - dmaengine: xilinx_dma: Report error in case of dma_set_mask_and_coherent API failure - ARM: dts: fix Moxa SDIO 'compatible', remove 'sdhci' misnomer - scsi: qedf: Fix a UAF bug in __qedf_probe() - net/ieee802154: fix uninit value bug in dgram_sendmsg - um: Cleanup syscall_handler_t cast in syscalls_32.h - um: Cleanup compiler warning in arch/x86/um/tls_32.c - arch: um: Mark the stack non-executable to fix a binutils warning - usb: mon: make mmapped memory read only - USB: serial: ftdi_sio: fix 300 bps rate for SIO - mmc: core: Replace with already defined values for readability - mmc: core: Terminate infinite loop in SD-UHS voltage switch - rpmsg: qcom: glink: replace strncpy() with strscpy_pad() - nilfs2: fix leak of nilfs_root in case of writer thread creation failure - nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure - ceph: don't truncate file in atomic_open - random: clamp credited irq bits to maximum mixed - ALSA: hda: Fix position reporting on Poulsbo - efi: Correct Macmini DMI match in uefi cert quirk - USB: serial: qcserial: add new usb-id for Dell branded EM7455 - random: restore O_NONBLOCK support - random: avoid reading two cache lines on irq randomness - random: use expired timer rather than wq for mixing fast pool - Input: xpad - add supported devices as contributed on github - Input: xpad - fix wireless 360 controller breaking after suspend - Linux 5.4.218 * Focal update: v5.4.217 upstream stable release (LP: #1995528) - xfs: fix misuse of the XFS_ATTR_INCOMPLETE flag - xfs: introduce XFS_MAX_FILEOFF - xfs: truncate should remove all blocks, not just to the end of the page cache - xfs: fix s_maxbytes computation on 32-bit kernels - xfs: fix IOCB_NOWAIT handling in xfs_file_dio_aio_read - xfs: refactor remote attr value buffer invalidation - xfs: fix memory corruption during remote attr value buffer invalidation - xfs: move incore structures out of xfs_da_format.h - xfs: streamline xfs_attr3_leaf_inactive - xfs: fix uninitialized variable in xfs_attr3_leaf_inactive - xfs: remove unused variable 'done' - Makefile.extrawarn: Move -Wcast-function-type-strict to W=1 - docs: update mediator information in CoC docs - Linux 5.4.217 * Focal update: v5.4.216 upstream stable release (LP: #1995526) - uas: add no-uas quirk for Hiksemi usb_disk - usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS - uas: ignore UAS for Thinkplus chips - net: usb: qmi_wwan: Add new usb-id for Dell branded EM7455 - clk: ingenic-tcu: Properly enable registers before accessing timers - ARM: dts: integrator: Tag PCI host with device_type - ntfs: fix BUG_ON in ntfs_lookup_inode_by_name() - libata: add ATA_HORKAGE_NOLPM for Pioneer BDR-207M and BDR-205 - mmc: moxart: fix 4-bit bus width and remove 8-bit bus width - mm/page_alloc: fix race condition between build_all_zonelists and page allocation - mm: prevent page_frag_alloc() from corrupting the memory - mm/migrate_device.c: flush TLB while holding PTL - mm: fix madivse_pageout mishandling on non-LRU page - media: dvb_vb2: fix possible out of bound access - ARM: dts: Move am33xx and am43xx mmc nodes to sdhci-omap driver - ARM: dts: am33xx: Fix MMCHS0 dma
[Kernel-packages] [Bug 1958416] Re: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64
This warning + kernel taint has now gone with linux-gcp/5.4.0-1096.105. Thanks! ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1958416 Title: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux-gcp source package in Focal: Fix Committed Bug description: [Impact] Small SWIOTLB might cause DMA failures during High IO on GCP instances using SEV. [Test case] Boot n2d-standard-2 or n2d-standard-64 instances on GCP, issue a lot of IO, and look for DMA overflow or full swiotlb messages on dmesg. [Potential regression] Boot failures should not be discarded when SWIOTLB cannot be allocated. -- ubuntu_boot log_check fails with: WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 From the serial console: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938685] [ cut here ] Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] Modules linked in: ip6table_filter ip6_tables iptable_filter bpfilter nls_iso8859_1 input_leds pvpanic serio_raw mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper psmouse i2c_piix4 gve Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] CPU: 34 PID: 8648 Comm: apt-check Not tainted 5.4.0-1060-gcp #64~18.04.1-Ubuntu Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938714] RIP: 0010:report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] Code: 48 83 ec 08 48 8b 87 30 02 00 00 48 89 75 f8 48 85 c0 74 26 4c 8b 00 b8 fe ff ff ff 49 39 c0 76 0d 80 3d 47 67 b2 01 00 74 2e <0f> 0b c9 c3 48 83 bf 40 02 00 00 00 75 e9 eb f0 80 3d 2f 67 b2 01 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] RSP: 0018:bd77cf99f4e0 EFLAGS: 00010282 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RAX: RBX: 9773f8b960b0 RCX: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RDX: RSI: 9753ff897448 RDI: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] RBP: bd77cf99f4e8 R08: 0305 R09: 0022 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] R10: 0016dfee R11: bd77cf99f218 R12: 0002 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938720] R13: 9753abfe9000 R14: 0001 R15: 0100 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] FS: 7f55bb523740() GS:9753ff88() knlGS: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] CS: 0010 DS: ES: CR0: 80050033 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938724] CR2: 7f55b41d6000 CR3: 801f6be28000 CR4: 00340ee0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938726] Call Trace: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938730] dma_direct_map_page+0xe2/0xf0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938731] dma_direct_map_sg+0x6c/0xc0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938735] nvme_queue_rq+0x6fb/0xbd0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938738] __blk_mq_try_issue_directly+0x139/0x200 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938741] ?
[Kernel-packages] [Bug 1958416] Re: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64
This bug is awaiting verification that the linux-gcp/5.4.0-1096.105 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-gcp verification-needed-focal -- 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/1958416 Title: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux-gcp source package in Focal: Fix Committed Bug description: [Impact] Small SWIOTLB might cause DMA failures during High IO on GCP instances using SEV. [Test case] Boot n2d-standard-2 or n2d-standard-64 instances on GCP, issue a lot of IO, and look for DMA overflow or full swiotlb messages on dmesg. [Potential regression] Boot failures should not be discarded when SWIOTLB cannot be allocated. -- ubuntu_boot log_check fails with: WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 From the serial console: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938685] [ cut here ] Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] Modules linked in: ip6table_filter ip6_tables iptable_filter bpfilter nls_iso8859_1 input_leds pvpanic serio_raw mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper psmouse i2c_piix4 gve Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] CPU: 34 PID: 8648 Comm: apt-check Not tainted 5.4.0-1060-gcp #64~18.04.1-Ubuntu Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938714] RIP: 0010:report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] Code: 48 83 ec 08 48 8b 87 30 02 00 00 48 89 75 f8 48 85 c0 74 26 4c 8b 00 b8 fe ff ff ff 49 39 c0 76 0d 80 3d 47 67 b2 01 00 74 2e <0f> 0b c9 c3 48 83 bf 40 02 00 00 00 75 e9 eb f0 80 3d 2f 67 b2 01 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] RSP: 0018:bd77cf99f4e0 EFLAGS: 00010282 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RAX: RBX: 9773f8b960b0 RCX: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RDX: RSI: 9753ff897448 RDI: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] RBP: bd77cf99f4e8 R08: 0305 R09: 0022 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] R10: 0016dfee R11: bd77cf99f218 R12: 0002 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938720] R13: 9753abfe9000 R14: 0001 R15: 0100 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] FS: 7f55bb523740() GS:9753ff88() knlGS: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] CS: 0010 DS: ES: CR0: 80050033 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938724] CR2: 7f55b41d6000 CR3: 801f6be28000 CR4: 00340ee0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938726]
[Kernel-packages] [Bug 1958416] Re: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64
** Changed in: linux-gcp (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1958416 Title: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux-gcp source package in Focal: Fix Committed Bug description: [Impact] Small SWIOTLB might cause DMA failures during High IO on GCP instances using SEV. [Test case] Boot n2d-standard-2 or n2d-standard-64 instances on GCP, issue a lot of IO, and look for DMA overflow or full swiotlb messages on dmesg. [Potential regression] Boot failures should not be discarded when SWIOTLB cannot be allocated. -- ubuntu_boot log_check fails with: WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 From the serial console: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938685] [ cut here ] Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] Modules linked in: ip6table_filter ip6_tables iptable_filter bpfilter nls_iso8859_1 input_leds pvpanic serio_raw mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper psmouse i2c_piix4 gve Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] CPU: 34 PID: 8648 Comm: apt-check Not tainted 5.4.0-1060-gcp #64~18.04.1-Ubuntu Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938714] RIP: 0010:report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] Code: 48 83 ec 08 48 8b 87 30 02 00 00 48 89 75 f8 48 85 c0 74 26 4c 8b 00 b8 fe ff ff ff 49 39 c0 76 0d 80 3d 47 67 b2 01 00 74 2e <0f> 0b c9 c3 48 83 bf 40 02 00 00 00 75 e9 eb f0 80 3d 2f 67 b2 01 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] RSP: 0018:bd77cf99f4e0 EFLAGS: 00010282 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RAX: RBX: 9773f8b960b0 RCX: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RDX: RSI: 9753ff897448 RDI: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] RBP: bd77cf99f4e8 R08: 0305 R09: 0022 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] R10: 0016dfee R11: bd77cf99f218 R12: 0002 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938720] R13: 9753abfe9000 R14: 0001 R15: 0100 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] FS: 7f55bb523740() GS:9753ff88() knlGS: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] CS: 0010 DS: ES: CR0: 80050033 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938724] CR2: 7f55b41d6000 CR3: 801f6be28000 CR4: 00340ee0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938726] Call Trace: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938730] dma_direct_map_page+0xe2/0xf0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938731] dma_direct_map_sg+0x6c/0xc0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938735] nvme_queue_rq+0x6fb/0xbd0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938738] __blk_mq_try_issue_directly+0x139/0x200 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938741] ? mempool_free_slab+0x1/0x20 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot
[Kernel-packages] [Bug 1958416] Re: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Triaged ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- 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/1958416 Title: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux-gcp source package in Focal: In Progress Bug description: [Impact] Small SWIOTLB might cause DMA failures during High IO on GCP instances using SEV. [Test case] Boot n2d-standard-2 or n2d-standard-64 instances on GCP, issue a lot of IO, and look for DMA overflow or full swiotlb messages on dmesg. [Potential regression] Boot failures should not be discarded when SWIOTLB cannot be allocated. -- ubuntu_boot log_check fails with: WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 From the serial console: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938685] [ cut here ] Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] Modules linked in: ip6table_filter ip6_tables iptable_filter bpfilter nls_iso8859_1 input_leds pvpanic serio_raw mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper psmouse i2c_piix4 gve Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] CPU: 34 PID: 8648 Comm: apt-check Not tainted 5.4.0-1060-gcp #64~18.04.1-Ubuntu Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938714] RIP: 0010:report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] Code: 48 83 ec 08 48 8b 87 30 02 00 00 48 89 75 f8 48 85 c0 74 26 4c 8b 00 b8 fe ff ff ff 49 39 c0 76 0d 80 3d 47 67 b2 01 00 74 2e <0f> 0b c9 c3 48 83 bf 40 02 00 00 00 75 e9 eb f0 80 3d 2f 67 b2 01 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] RSP: 0018:bd77cf99f4e0 EFLAGS: 00010282 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RAX: RBX: 9773f8b960b0 RCX: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RDX: RSI: 9753ff897448 RDI: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] RBP: bd77cf99f4e8 R08: 0305 R09: 0022 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] R10: 0016dfee R11: bd77cf99f218 R12: 0002 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938720] R13: 9753abfe9000 R14: 0001 R15: 0100 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] FS: 7f55bb523740() GS:9753ff88() knlGS: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] CS: 0010 DS: ES: CR0: 80050033 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938724] CR2: 7f55b41d6000 CR3: 801f6be28000 CR4: 00340ee0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938726] Call Trace: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938730] dma_direct_map_page+0xe2/0xf0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938731] dma_direct_map_sg+0x6c/0xc0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938735] nvme_queue_rq+0x6fb/0xbd0 Jan 19 12:54:30
[Kernel-packages] [Bug 1958416] Re: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64
** Description changed: - ubuntu_boot log_check fails with: WARNING: CPU: 34 PID: 8648 at - /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 - report_addr+0x33/0x90 + [Impact] + Small SWIOTLB might cause DMA failures during High IO on GCP instances using SEV. + + [Test case] + Boot n2d-standard-2 or n2d-standard-64 instances on GCP, issue a lot of IO, and look for DMA overflow or full swiotlb messages on dmesg. + + [Potential regression] + Boot failures should not be discarded when SWIOTLB cannot be allocated. + + + -- + + + ubuntu_boot log_check fails with: WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 From the serial console: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938685] [ cut here ] Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] Modules linked in: ip6table_filter ip6_tables iptable_filter bpfilter nls_iso8859_1 input_leds pvpanic serio_raw mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper psmouse i2c_piix4 gve Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] CPU: 34 PID: 8648 Comm: apt-check Not tainted 5.4.0-1060-gcp #64~18.04.1-Ubuntu Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938714] RIP: 0010:report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] Code: 48 83 ec 08 48 8b 87 30 02 00 00 48 89 75 f8 48 85 c0 74 26 4c 8b 00 b8 fe ff ff ff 49 39 c0 76 0d 80 3d 47 67 b2 01 00 74 2e <0f> 0b c9 c3 48 83 bf 40 02 00 00 00 75 e9 eb f0 80 3d 2f 67 b2 01 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] RSP: 0018:bd77cf99f4e0 EFLAGS: 00010282 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RAX: RBX: 9773f8b960b0 RCX: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RDX: RSI: 9753ff897448 RDI: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] RBP: bd77cf99f4e8 R08: 0305 R09: 0022 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] R10: 0016dfee R11: bd77cf99f218 R12: 0002 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938720] R13: 9753abfe9000 R14: 0001 R15: 0100 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] FS: 7f55bb523740() GS:9753ff88() knlGS: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] CS: 0010 DS: ES: CR0: 80050033 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938724] CR2: 7f55b41d6000 CR3: 801f6be28000 CR4: 00340ee0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938726] Call Trace: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938730] dma_direct_map_page+0xe2/0xf0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938731] dma_direct_map_sg+0x6c/0xc0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938735] nvme_queue_rq+0x6fb/0xbd0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938738] __blk_mq_try_issue_directly+0x139/0x200 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938741] ? mempool_free_slab+0x1/0x20 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938743] blk_mq_request_issue_directly+0x4b/0xe0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938744] blk_mq_try_issue_list_directly+0x46/0xb0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938746] blk_mq_sched_insert_requests+0xb7/0x100 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938747]
