impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq

Bug #1952933 reported by dann frazier
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Committed
Undecided
dann frazier
Impish
Fix Committed
Low
dann frazier
Jammy
Fix Released
Medium
dann frazier

Bug Description

During MAAS deployment:

[ 107.768146] Unable to handle kernel read from unreadable memory at virtual address 0000000000000000

 domain : maas [ 107.943413] Mem abort info:

 rootserver: 10.229.32.21 rootpath:
 filename :[ 108.043666] ESR = 0x96000004
 lpxelinux.0
:: root=squash:http://10.229.32.21:5248/images/ubu[ 108.147045] EC = 0x25: DABT (current EL), IL = 32 bits
ntu/arm64/xgene-uboot/impish/stable/squashfs
:: mount_squash do[ 108.277541] SET = 0, FnV = 0
wnloading http://10.229.32.21:5248/images/ubuntu/arm64/xgene-ubo[ 108.380921] EA = 0, S1PTW = 0
ot/impish/stable/squashfs to /root.tmp.img
Connecting to 10.229[ 108.485351] Data abort info:
.32.21:5248 (10.229.32.21:5248)
[ 108.586639] ISV = 0, ISS = 0x00000004
[ 108.667060] CM = 0, WnR = 0
[ 108.702635] user pgtable: 4k pages, 48-bit VAs, pgdp=000000401ce02000
root.tmp.img [ 108.779941] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000
  4% [ 108.884372] Internal error: Oops: 96000004 [#1] SMP
[ 108.948102] Modules linked in: raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx4_ib ib_uverbs ib_core mlx4_en mlx4_core gpio_keys_polled gpio_dwapb crct10dif_ce ahci_xgene gpio_xgene_sb aes_neon_bs aes_neon_blk crypto_simd cryptd
[ 109.286243] CPU: 0 PID: 11 Comm: ksoftirqd/0 Not tainted 5.13.0-20-generic #20-Ubuntu
[ 109.380233] Hardware name: HP ProLiant m400 Server Cartridge (DT)
[ 109.453258] pstate: 60400005 (nZCv daif +PAN -UAO -TCO BTYPE=--)
[ 109.525342] pc : mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en]
[ 109.589087] lr : mlx4_en_poll_rx_cq+0x7c/0x17c [mlx4_en]
[ 109.652828] sp : ffff8000129cbc60
[ 109.692470] x29: ffff8000129cbc60 x28: 000000000000012c x27: ffff000ff7e95fc0
[ 109.778115] x26: 00000000ffffffff x25: ffff000020908508 x24: ffff000021b40940
[ 109.863763] x23: ffff000020908508 x22: ffff000020908400 x21: ffff000021b40000
[ 109.949409] x20: 0000000000000040 x19: 0000000000000040 x18: 0000000000000014
[ 110.035056] x17: 000000001122e350 x16: 00000000cb46f8bb x15: 00000000e2b6a183
[ 110.120703] x14: 0000000026fff11e x13: 000000009312ff0b x12: 0000000000000000
[ 110.206349] x11: 0000000000000006 x10: 0000000000000040 x9 : ffff800009119320
[ 110.291997] x8 : ffff000008acdc00 x7 : 00000000000002c0 x6 : 00000000ffffdff8
[ 110.377642] x5 : ffff000003940000 x4 : ffff000003960040 x3 : ffff000021c20000
[ 110.463289] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[ 110.548937] Call trace:
[ 110.578147] mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en]
[ 110.637719] __napi_poll+0x40/0x1e0
[ 110.679551] net_rx_action+0x2d8/0x34c
[ 110.724513] __do_softirq+0x128/0x388
[ 110.768432] run_ksoftirqd+0x6c/0x94
[ 110.811308] smpboot_thread_fn+0x15c/0x1a0
[ 110.860443] kthread+0x114/0x120
[ 110.899145] ret_from_fork+0x10/0x18
[ 110.942024] Code: 1100fc41 1a82b021 13067c21 93407c21 (f8617800)
[ 111.015158] ---[ end trace b37ae99414884442 ]---
[ 111.070550] Kernel panic - not syncing: Oops: Fatal exception in interrupt
[ 111.152964] SMP: stopping secondary CPUs
[ 111.200016] Kernel Offset: 0x80000 from 0xffff800010000000
[ 111.265837] PHYS_OFFSET: 0x4000000000
[ 111.309651] CPU features: 0x00000251,00000046
[ 111.361915] Memory Limit: none
[ 111.398431] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]---

Tags: impish
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : 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 1952933

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 Impish):
status: New → Incomplete
tags: added: impish
dann frazier (dannf)
Changed in linux (Ubuntu Impish):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
dann frazier (dannf) wrote :

I've identified the problem(s) and reported it upstream:

  https://<email address hidden>/T/#m4d8283082c3fded15050e03a9ad8aef53ad07394

Revision history for this message
dann frazier (dannf) wrote :

Upstream has gone ahead and reverted the problematic patches, and they are flowing into the various stable trees.

Changed in linux (Ubuntu Impish):
status: Confirmed → In Progress
Changed in linux (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → dann frazier (dannf)
Changed in linux (Ubuntu Impish):
assignee: nobody → dann frazier (dannf)
Revision history for this message
dann frazier (dannf) wrote :

Now fixed in upstream release v5.15.33.

dann frazier (dannf)
Changed in linux (Ubuntu Jammy):
status: In Progress → Fix Committed
dann frazier (dannf)
Changed in linux (Ubuntu Jammy):
status: Fix Committed → Fix Released
Stefan Bader (smb)
Changed in linux (Ubuntu Impish):
importance: Undecided → Low
Changed in linux (Ubuntu Jammy):
importance: Undecided → Medium
Changed in linux (Ubuntu Impish):
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.