[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 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-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. 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-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
** Tags removed: verification-needed-jammy ** Tags added: verification-donejammy ** Tags removed: verification-donejammy ** Tags added: verification-done-jammy -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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 removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-nvidia verification-needed-jammy -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663]
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
This issue is already verified with -generic kernel. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi_trng_v2 cppc_cpufreq
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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 removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1005.7~20.04.1 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! -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140]
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
** Changed in: kunpeng920/ubuntu-20.04-hwe 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
This bug was fixed in the package linux - 5.15.0-50.56 --- linux (5.15.0-50.56) jammy; urgency=medium * jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148) * CVE-2022-3176 - io_uring: refactor poll update - io_uring: move common poll bits - io_uring: kill poll linking optimisation - io_uring: inline io_poll_complete - io_uring: correct fill events helpers types - io_uring: clean cqe filling functions - io_uring: poll rework - io_uring: remove poll entry from list when canceling all - io_uring: bump poll refs to full 31-bits - io_uring: fail links when poll fails - io_uring: fix wrong arm_poll error handling - io_uring: fix UAF due to missing POLLFREE handling * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' linux (5.15.0-49.55) jammy; urgency=medium * jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785) * amdgpu module crash after 5.15 kernel update (LP: #1981883) - drm/amdgpu: fix check in fbdev init * scsi: hisi_sas: Increase debugfs_dump_index after dump is completed (LP: #1982070) - scsi: hisi_sas: Increase debugfs_dump_index after dump is completed * [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103) - s390/qeth: cache link_info for ethtool * WARN in trace_event_dyn_put_ref (LP: #1987232) - tracing/perf: Fix double put of trace event when init fails * Jammy update: v5.15.60 upstream stable release (LP: #1989221) - x86/speculation: Make all RETbleed mitigations 64-bit only - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - selftests/bpf: Check dst_port only on the client socket - block: fix default IO priority handling again - tools/vm/slabinfo: Handle files in debugfs - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - crypto: arm64/poly1305 - fix a read out-of-bound - KVM: x86: do not report a vCPU as preempted outside instruction boundaries - KVM: x86: do not set st->preempted when going back to user space - KVM: selftests: Make hyperv_clock selftest more stable - tools/kvm_stat: fix display of error when multiple processes are found - selftests: KVM: Handle compiler optimizations in ucall - KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user() - arm64: set UXN on swapper page tables - btrfs: zoned: prevent allocation from previous data relocation BG - btrfs: zoned: fix critical section of relocation inode writeback - Bluetooth: hci_bcm: Add BCM4349B1 variant - Bluetooth: hci_bcm: Add DT compatible for CYW55572 - dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding - Bluetooth: btusb: Add support of IMC Networks PID 0x3568 - Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007 - Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675 - Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558 - Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587 - Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586 - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.15.60 * Jammy update: v5.15.59 upstream stable release (LP: #1989218) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - Revert "ocfs2: mount shared volume without ha stack" - ntfs: fix use-after-free in ntfs_ucsncmp() - fs: sendfile handles O_NONBLOCK of out_fd - secretmem: fix unhandled fault in truncate - mm: fix page leak with multiple threads mapping the same page - hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte - asm-generic: remove a broken and needless ifdef conditional - s390/archrandom: prevent CPACF trng invocations in interrupt context - nouveau/svm: Fix to migrate all requested pages - drm/simpledrm: Fix return type of simpledrm_simple_display_pipe_mode_valid() - watch_queue: Fix missing rcu annotation - watch_queue: Fix missing locking in add_watch_to_object() - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save. - ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
Jammy kernel 5.15.0-50.56 works for me. Thanks. ** Tags added: verification-done-jammy -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi_trng_v2 cppc_cpufreq sch_fq_codel ip_tables x_tables autofs4
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
This bug is awaiting verification that the linux/5.15.0-50.56 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] []
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
I can not reproduce on 5.4.0-125.141-generic kernel. The only Ubuntu kernel affected is 5.15. ** Changed in: kunpeng920/ubuntu-20.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Kinetic) 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
** Changed in: linux (Ubuntu Jammy) 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi_trng_v2 cppc_cpufreq sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
Dig deeper with 5.4 kernels and it also support debugfs with hisi_sas but can not clean cherry-pick the mainline patch. I will try to reproduce this issue with 5.4 kernel and find out if we need to backport. -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
Patch sent. https://lists.ubuntu.com/archives/kernel- team/2022-September/132987.html -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi_trng_v2 cppc_cpufreq sch_fq_codel ip_tables x_tables autofs4 btrfs
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
Patch hits mainline kernel since v5.16. When Kinetic kernel rolls to v5.19, this issue will be fix for 22.10. ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu) Assignee: Ike Panhc (ikepanhc) => (unassigned) ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Fix Committed -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] []
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
** Description changed: - Bug Description] - When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. + [Impact] + Trigger dump on hisi_sas in debugfs will cause kernel oops. + + [Test Plan] + 1) modprobe hisi_sas_main with "debugfs_enable=1" + 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump + 3) dmesg | grep Oops + + [Regression Risk] + Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. + + + [Bug Description] + When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi_trng_v2 cppc_cpufreq sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core realtek hibmc_drm drm_vram_helper drm_ttm_helper ttm i2c_algo_bit drm_kms_helper syscopyarea sysfillrect crct10dif_ce
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: In Progress Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi_trng_v2 cppc_cpufreq sch_fq_codel ip_tables