[Bug 1921825] Re: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related
This bug was fixed in the package linux-gke - 5.4.0-1041.43
---
linux-gke (5.4.0-1041.43) focal; urgency=medium
* focal/linux-gke: 5.4.0-1041.43 -proposed tracker (LP: #1922201)
* Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing
interrupt handler!) possibly iscsi related (LP: #1921825)
- scsi: iscsi: iscsi_tcp: Avoid holding spinlock while calling getpeername()
linux-gke (5.4.0-1040.42) focal; urgency=medium
* focal/linux-gke: 5.4.0-1040.42 -proposed tracker (LP: #1921027)
* Enforce CONFIG_DRM_BOCHS=m (LP: #1916290)
- [Config] [gke] updateconfigs for CONFIG_DRM_BOCHS
[ Ubuntu: 5.4.0-71.79 ]
* focal/linux: 5.4.0-71.79 -proposed tracker (LP: #1921040)
* selftests: bpf verifier fails after sanitize_ptr_alu fixes (LP: #1920995)
- bpf: Simplify alu_limit masking for pointer arithmetic
- bpf: Add sanity check for upper ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* Packaging resync (LP: #1786013)
- update dkms package versions
* Fix missing HDMI/DP audio on NVidia card after S3 (LP: #1918228)
- ALSA: hda/hdmi: Reduce hda_jack_tbl lookup at unsol event handling
- ALSA: hda/hdmi: Don't use standard hda_jack for generic HDMI jacks
- ALSA: hda/hdmi: Move runtime PM resume into hdmi_present_sense_via_verbs()
- ALSA: hda/hdmi: Move ELD parse and jack reporting into update_eld()
* Focal update: v5.4.101 upstream stable release (LP: #1918170)
- HID: make arrays usage and value to be the same
- USB: quirks: sort quirk entries
- usb: quirks: add quirk to start video capture on ELMO L-12F document
camera
reliable
- ntfs: check for valid standard information attribute
- arm64: tegra: Add power-domain for Tegra210 HDA
- scripts: use pkg-config to locate libcrypto
- scripts: set proper OpenSSL include dir also for sign-file
- mm: unexport follow_pte_pmd
- mm: simplify follow_pte{,pmd}
- KVM: do not assume PTE is writable after follow_pfn
- mm: provide a saner PTE walking API for modules
- KVM: Use kvm_pfn_t for local PFN variable in hva_to_pfn_remapped()
- NET: usb: qmi_wwan: Adding support for Cinterion MV31
- cxgb4: Add new T6 PCI device id 0x6092
- cifs: Set CIFS_MOUNT_USE_PREFIX_PATH flag on setting cifs_sb->prepath.
- scripts/recordmcount.pl: support big endian for ARCH sh
- Linux 5.4.101
* Focal update: v5.4.100 upstream stable release (LP: #1918168)
- KVM: SEV: fix double locking due to incorrect backport
- net: qrtr: Fix port ID for control messages
- net: bridge: Fix a warning when del bridge sysfs
- Xen/x86: don't bail early from clear_foreign_p2m_mapping()
- Xen/x86: also check kernel mapping in set_foreign_p2m_mapping()
- Xen/gntdev: correct dev_bus_addr handling in gntdev_map_grant_pages()
- Xen/gntdev: correct error checking in gntdev_map_grant_pages()
- xen/arm: don't ignore return errors from set_phys_to_machine
- xen-blkback: don't "handle" error by BUG()
- xen-netback: don't "handle" error by BUG()
- xen-scsiback: don't "handle" error by BUG()
- xen-blkback: fix error handling in xen_blkbk_map()
- media: pwc: Use correct device for DMA
- btrfs: fix backport of 2175bf57dc952 in 5.4.95
- Linux 5.4.100
* Focal update: v5.4.99 upstream stable release (LP: #1918167)
- gpio: ep93xx: fix BUG_ON port F usage
- gpio: ep93xx: Fix single irqchip with multi gpiochips
- tracing: Do not count ftrace events in top level enable output
- tracing: Check length before giving out the filter buffer
- arm/xen: Don't probe xenbus as part of an early initcall
- cgroup: fix psi monitor for root cgroup
- arm64: dts: rockchip: Fix PCIe DT properties on rk3399
- arm64: dts: qcom: sdm845: Reserve LPASS clocks in gcc
- ARM: OMAP2+: Fix suspcious RCU usage splats for omap_enter_idle_coupled
- platform/x86: hp-wmi: Disable tablet-mode reporting by default
- ovl: perform vfs_getxattr() with mounter creds
- cap: fix conversions on getxattr
- ovl: skip getxattr of security labels
- nvme-pci: ignore the subsysem NQN on Phison E16
- drm/amd/display: Add more Clock Sources to DCN2.1
- drm/amd/display: Fix dc_sink kref count in emulated_link_detect
- drm/amd/display: Free atomic state after drm_atomic_commit
- drm/amd/display: Decrement refcount of dc_sink before reassignment
- riscv: virt_addr_valid must check the address belongs to linear mapping
- bfq-iosched: Revert "bfq: Fix computation of shallow depth"
- ARM: dts: lpc32xx: Revert set default clock rate of HCLK PLL
- ARM: ensure the signal page contains defined contents
- ARM: kexec: fix oops after TLB are invalidated
- vmlinux.lds.h: Create section for protection against instrumentation
- lkdtm: don't move ctors to .rodata
- mt76: dma: fix a possible memory leak in mt76_add_fragment()
- drm/vc4: hvs: Fix
[Bug 1921825] Re: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921825 Title: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1921825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921825] Re: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related
** Changed in: linux-gke (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921825 Title: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1921825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921825] Re: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related
** Description changed: + [Impact] + Kernel panic during high iscsi activity + + This stacktrace [ 223.386958] BUG: scheduling while atomic: iscsiadm/18136/0x0200 [ 223.393390] Modules linked in: tcp_diag inet_diag xt_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs sch_htb ebt_ip ebtable_filter ebtables veth xt_mark br_netfilter iptable_mangle xt_MASQUERADE xt_comment xt_addrtype iptable_nat binfmt_misc iptable_filter bpfilter xt_conntrack nf_nat bridge stp llc xfrm_user xfrm_algo 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 glue_helper input_leds serio_raw sch_fq_codel sunrpc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi virtio_rng 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 psmouse virtio_net net_failover failover [ 223.393429] CPU: 6 PID: 18136 Comm: iscsiadm Kdump: loaded Not tainted 5.4.0-1033-gke #35~18.04.1-Ubuntu [ 223.393430] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [ 223.393430] Call Trace: [ 223.393439] dump_stack+0x6d/0x95 [ 223.393464] __schedule_bug+0x55/0x70 [ 223.393467] __schedule+0x61b/0x710 [ 223.393469] schedule+0x33/0xa0 [ 223.393472] __lock_sock+0x7d/0xc0 [ 223.393475] ? wait_woken+0x80/0x80 [ 223.393477] lock_sock_nested+0x64/0x70 [ 223.393479] inet_getname+0xaa/0xe0 [ 223.393482] kernel_getpeername+0x1b/0x20 [ 223.393485] iscsi_sw_tcp_conn_get_param+0xa6/0x110 [iscsi_tcp] [ 223.393494] show_conn_ep_param_ISCSI_PARAM_CONN_ADDRESS+0x7e/0xa0 [scsi_transport_iscsi] [ 223.393496] dev_attr_show+0x1d/0x50 [ 223.393499] sysfs_kf_seq_show+0xa1/0x110 [ 223.393502] kernfs_seq_show+0x27/0x30 [ 223.393504] seq_read+0xda/0x420 [ 223.393506] kernfs_fop_read+0x141/0x1a0 [ 223.393510] __vfs_read+0x1b/0x40 [ 223.393512] vfs_read+0x8e/0x130 [ 223.393513] ksys_read+0xa7/0xe0 [ 223.393515] __x64_sys_read+0x1a/0x20 [ 223.393518] do_syscall_64+0x57/0x190 [ 223.393521] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 223.393523] RIP: 0033:0x7f45793ce910 [ 223.393525] Code: b6 fe ff ff 48 8d 3d 0f be 08 00 48 83 ec 08 e8 06 db 01 00 66 0f 1f 44 00 00 83 3d f9 2d 2c 00 00 75 10 b8 00 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 de 9b 01 00 48 89 04 24 [ 223.393526] RSP: 002b:7ffd9fa13688 EFLAGS: 0246 ORIG_RAX: [ 223.393527] RAX: ffda RBX: 7ffd9fa13820 RCX: 7f45793ce910 [ 223.393528] RDX: 0100 RSI: 7ffd9fa13720 RDI: 0003 [ 223.393528] RBP: 7ffd9fa13720 R08: R09: [ 223.393529] R10: 0064 R11: 0246 R12: 0003 [ 223.393530] R13: 7ffd9fa13c60 R14: 555b0d613708 R15: 555b0d613300 [ 223.393581] sd 1:0:0:0: [sdb] Write Protect is off [ 223.393583] sd 1:0:0:0: [sdb] Mode Sense: 43 00 10 08 [ 223.393660] iscsiadm[18136]: segfault at 7ffd9fa12e58 ip 555b0ccd95af sp 7ffd9fa12e60 error 6 in iscsiadm[555b0ccb4000+58000] [ 223.393666] Code: ba 00 02 00 00 48 81 ec 10 04 00 00 48 89 e7 48 8d 9c 24 00 02 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 08 04 00 00 31 c0 3c ed 00 00 ba 00 02 00 00 4c 89 ee 48 89 e7 e8 6c ed 00 00 ba [ 223.394992] sd 1:0:0:0: alua: transition timeout set to 60 seconds [ 223.394997] sd 1:0:0:0: alua: port group 02 state N non-preferred supports TOlUSNA [ 223.395018] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 223.395435] Kernel panic - not syncing: Aiee, killing interrupt handler! [ 223.396802] sd 1:0:0:0: [sdb] Optimal transfer size 262144 bytes [ 223.402387] CPU: 6 PID: 18136 Comm: iscsiadm Kdump: loaded Tainted: G W 5.4.0-1033-gke #35~18.04.1-Ubuntu [ 223.402388] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [ 223.402389] Call Trace: [ 223.402395] dump_stack+0x6d/0x95 [ 223.402398] panic+0xfe/0x2e4 [ 223.402400] do_exit+0x899/0xb90 [ 223.402402] do_group_exit+0x43/0xa0 [ 223.402406] get_signal+0x14f/0x860 [ 223.402409] do_signal+0x34/0x6d0 [ 223.402414] ? __bad_area_nosemaphore+0x149/0x1f0 [ 223.457597] exit_to_usermode_loop+0x8e/0x100 [ 223.462090] prepare_exit_to_usermode+0x91/0xa0 [ 223.466782] retint_user+0x8/0x8 [ 223.470131] RIP: 0033:0x555b0ccd95af [ 223.473827] Code: ba 00 02 00 00 48 81 ec 10 04 00 00 48 89 e7 48 8d 9c 24 00 02 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 08 04 00 00 31 c0 3c ed 00 00 ba 00 02 00 00 4c 89 ee 48 89 e7 e8 6c ed 00 00 ba [ 223.492991] RSP: 002b:7ffd9fa12e60 EFLAGS: 00010246 [ 223.498333]
[Bug 1921825] Re: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related
** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gcp (Ubuntu) ** No longer affects: linux-gcp (Ubuntu Focal) ** Changed in: linux-gke (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gke (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921825 Title: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1921825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921825] Re: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related
** Description changed: This stacktrace [ 223.386958] BUG: scheduling while atomic: iscsiadm/18136/0x0200 [ 223.393390] Modules linked in: tcp_diag inet_diag xt_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs sch_htb ebt_ip ebtable_filter ebtables veth xt_mark br_netfilter iptable_mangle xt_MASQUERADE xt_comment xt_addrtype iptable_nat binfmt_misc iptable_filter bpfilter xt_conntrack nf_nat bridge stp llc xfrm_user xfrm_algo 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 glue_helper input_leds serio_raw sch_fq_codel sunrpc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi virtio_rng 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 psmouse virtio_net net_failover failover [ 223.393429] CPU: 6 PID: 18136 Comm: iscsiadm Kdump: loaded Not tainted 5.4.0-1033-gke #35~18.04.1-Ubuntu [ 223.393430] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [ 223.393430] Call Trace: [ 223.393439] dump_stack+0x6d/0x95 [ 223.393464] __schedule_bug+0x55/0x70 [ 223.393467] __schedule+0x61b/0x710 [ 223.393469] schedule+0x33/0xa0 [ 223.393472] __lock_sock+0x7d/0xc0 [ 223.393475] ? wait_woken+0x80/0x80 [ 223.393477] lock_sock_nested+0x64/0x70 [ 223.393479] inet_getname+0xaa/0xe0 [ 223.393482] kernel_getpeername+0x1b/0x20 [ 223.393485] iscsi_sw_tcp_conn_get_param+0xa6/0x110 [iscsi_tcp] [ 223.393494] show_conn_ep_param_ISCSI_PARAM_CONN_ADDRESS+0x7e/0xa0 [scsi_transport_iscsi] [ 223.393496] dev_attr_show+0x1d/0x50 [ 223.393499] sysfs_kf_seq_show+0xa1/0x110 [ 223.393502] kernfs_seq_show+0x27/0x30 [ 223.393504] seq_read+0xda/0x420 [ 223.393506] kernfs_fop_read+0x141/0x1a0 [ 223.393510] __vfs_read+0x1b/0x40 [ 223.393512] vfs_read+0x8e/0x130 [ 223.393513] ksys_read+0xa7/0xe0 [ 223.393515] __x64_sys_read+0x1a/0x20 [ 223.393518] do_syscall_64+0x57/0x190 [ 223.393521] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 223.393523] RIP: 0033:0x7f45793ce910 [ 223.393525] Code: b6 fe ff ff 48 8d 3d 0f be 08 00 48 83 ec 08 e8 06 db 01 00 66 0f 1f 44 00 00 83 3d f9 2d 2c 00 00 75 10 b8 00 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 de 9b 01 00 48 89 04 24 [ 223.393526] RSP: 002b:7ffd9fa13688 EFLAGS: 0246 ORIG_RAX: [ 223.393527] RAX: ffda RBX: 7ffd9fa13820 RCX: 7f45793ce910 [ 223.393528] RDX: 0100 RSI: 7ffd9fa13720 RDI: 0003 [ 223.393528] RBP: 7ffd9fa13720 R08: R09: [ 223.393529] R10: 0064 R11: 0246 R12: 0003 [ 223.393530] R13: 7ffd9fa13c60 R14: 555b0d613708 R15: 555b0d613300 [ 223.393581] sd 1:0:0:0: [sdb] Write Protect is off [ 223.393583] sd 1:0:0:0: [sdb] Mode Sense: 43 00 10 08 [ 223.393660] iscsiadm[18136]: segfault at 7ffd9fa12e58 ip 555b0ccd95af sp 7ffd9fa12e60 error 6 in iscsiadm[555b0ccb4000+58000] [ 223.393666] Code: ba 00 02 00 00 48 81 ec 10 04 00 00 48 89 e7 48 8d 9c 24 00 02 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 08 04 00 00 31 c0 3c ed 00 00 ba 00 02 00 00 4c 89 ee 48 89 e7 e8 6c ed 00 00 ba [ 223.394992] sd 1:0:0:0: alua: transition timeout set to 60 seconds [ 223.394997] sd 1:0:0:0: alua: port group 02 state N non-preferred supports TOlUSNA [ 223.395018] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 223.395435] Kernel panic - not syncing: Aiee, killing interrupt handler! [ 223.396802] sd 1:0:0:0: [sdb] Optimal transfer size 262144 bytes [ 223.402387] CPU: 6 PID: 18136 Comm: iscsiadm Kdump: loaded Tainted: G W 5.4.0-1033-gke #35~18.04.1-Ubuntu [ 223.402388] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [ 223.402389] Call Trace: [ 223.402395] dump_stack+0x6d/0x95 [ 223.402398] panic+0xfe/0x2e4 [ 223.402400] do_exit+0x899/0xb90 [ 223.402402] do_group_exit+0x43/0xa0 [ 223.402406] get_signal+0x14f/0x860 [ 223.402409] do_signal+0x34/0x6d0 [ 223.402414] ? __bad_area_nosemaphore+0x149/0x1f0 [ 223.457597] exit_to_usermode_loop+0x8e/0x100 [ 223.462090] prepare_exit_to_usermode+0x91/0xa0 [ 223.466782] retint_user+0x8/0x8 [ 223.470131] RIP: 0033:0x555b0ccd95af [ 223.473827] Code: ba 00 02 00 00 48 81 ec 10 04 00 00 48 89 e7 48 8d 9c 24 00 02 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 08 04 00 00 31 c0 3c ed 00 00 ba 00 02 00 00 4c 89 ee 48 89 e7 e8 6c ed 00 00 ba [ 223.492991] RSP: 002b:7ffd9fa12e60 EFLAGS: 00010246 [ 223.498333] RAX: RBX: 7ffd9fa13060 RCX: 7f45
