** Changed in: kunpeng920/ubuntu-18.04
Status: Fix Committed => Fix Released
** Changed in: kunpeng920
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/1953386
Title:
hisi_sas driver may oops in prep_ssp_v3_hw()
Status in kunpeng920:
Fix Released
Status in kunpeng920 ubuntu-18.04 series:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
[Impact]
The hisi_sas driver occasionally oopses on boot.
[ 32.724666] Unable to handle kernel NULL pointer dereference at virtual
address 00000110
[ 32.732720] Mem abort info:
[ 32.735504] ESR = 0x96000004
[ 32.738546] Exception class = DABT (current EL), IL = 32 bits
[ 32.744440] SET = 0, FnV = 0
[ 32.747482] EA = 0, S1PTW = 0
[ 32.750612] Data abort info:
[ 32.753478] ISV = 0, ISS = 0x00000004
[ 32.757298] CM = 0, WnR = 0
[ 32.760256] user pgtable: 4k pages, 48-bit VAs, pgd = (ptrval)
[ 32.766755] [0000000000000110] *pgd=0000000000000000
[ 32.771700] Internal error: Oops: 96000004 [#1] SMP
[ 32.776557] Modules linked in: realtek hibmc_drm aes_ce_blk aes_ce_cipher
ttm crct10dif_ce ghash_ce drm_kms_helper ixgbe(+) syscopyarea sha2_ce
sysfillrect sysimgblt fb_sys_fops ptp sha256_arm64 sha1_ce hns3
hisi_sas_v3_hw(+) hinic pps_core hisi_sas_main drm hclge mdio libsas ahci hnae3
scsi_transport_sas libahci gpio_dwapb hid_generic usbhid hid aes_neon_bs
aes_neon_blk crypto_simd cryptd aes_arm64
[ 32.811755] Process kworker/u256:1 (pid: 1280, stack limit = 0x
(ptrval))
[ 32.819118] CPU: 66 PID: 1280 Comm: kworker/u256:1 Not tainted 4.15.18+ #24
[ 32.826047] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2
CS V3.B160.01 01/15/2020
[ 32.834884] Workqueue: 0000:74:02.0_disco_q sas_discover_domain [libsas]
[ 32.839182] hns3 0000:bd:00.0 enp189s0f0: renamed from eth8
[ 32.841558] pstate: a0c00009 (NzCv daif +PAN +UAO)
[ 32.851878] pc : prep_ssp_v3_hw+0x64/0x340 [hisi_sas_v3_hw]
[ 32.857426] lr : hisi_sas_task_exec.constprop.0+0x304/0x640 [hisi_sas_main]
[ 32.864354] sp : ffff000021833a00
[ 32.867653] x29: ffff000021833a00 x28: ffffb790728621e0
[ 32.872940] x27: ffffb790728607d8 x26: ffffb79072861158
[ 32.878227] x25: ffffd7b07b9340a0 x24: 0000000000000028
[ 32.883515] x23: ffffd7906cd69400 x22: ffffd7906cd69418
[ 32.888802] x21: ffffb79072aad3d0 x20: ffff000021b33000
[ 32.894089] x19: ffffb79072aad3d0 x18: 0000000000000030
[ 32.899376] x17: 000000009e710776 x16: ffff3efb16aabb00
[ 32.904663] x15: ffffffffffffffff x14: ffff3efb976abcef
[ 32.909950] x13: 0000000000000006 x12: ffffb79072863480
[ 32.915237] x11: ffffb79072aad3e0 x10: ffffb79072861148
[ 32.920524] x9 : 0000000000000000 x8 : ffff000024cc0fb0
[ 32.925812] x7 : 0000000000000000 x6 : 000000000000003f
[ 32.931099] x5 : 0000000000000040 x4 : 00000000200000a0
[ 32.936386] x3 : ffffd79071e2d400 x2 : ffff000021833bb4
[ 32.941673] x1 : ffffb79072863460 x0 : 00000000280000a0
[ 32.946960] Call trace:
[ 32.949398] prep_ssp_v3_hw+0x64/0x340 [hisi_sas_v3_hw]
[ 32.954600] hisi_sas_task_exec.constprop.0+0x304/0x640 [hisi_sas_main]
[ 32.961184] hisi_sas_exec_internal_tmf_task+0xec/0x290 [hisi_sas_main]
[ 32.967767] hisi_sas_init_device+0x84/0x100 [hisi_sas_main]
[ 32.973401] hisi_sas_dev_found+0xa4/0x24c [hisi_sas_main]
[ 32.978864] sas_notify_lldd_dev_found+0x44/0xc0 [libsas]
[ 32.984239] sas_discover_end_dev+0x24/0x30 [libsas]
[ 32.989182] sas_ex_discover_devices+0x950/0xbfc [libsas]
[ 32.994557] sas_discover_root_expander+0x12c/0x150 [libsas]
[ 33.000192] sas_discover_domain+0x340/0x664 [libsas]
[ 33.005225] process_one_work+0x1bc/0x3ec
[ 33.009217] worker_thread+0x58/0x4a0
[ 33.012863] kthread+0x13c/0x170
[ 33.016077] ret_from_fork+0x10/0x18
[ 33.019638] Code: 2a004820 2a040000 f9400ed8 f9410061 (3943a319)
[ 33.025705] ---[ end trace da9256b7aa3297ba ]---
[Test Case]
Boot a hi1620-based server w/ root disk attached to hisi_sas v3 controller.
[Fix]
e1ba0b0b4451 scsi: hisi_sas: Fix to only call scsi_get_prot_op() for non-NULL
scsi_cmnd
[Where things could go wrong]
We could potentially be trading one boot time crash for another that hasn't
popped up in testing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1953386/+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
