* ufshcd_abort: Device abort task at tag 7
@ 2019-08-28 9:09 Marc Gonzalez
2019-08-28 19:20 ` Bjorn Andersson
0 siblings, 1 reply; 5+ messages in thread
From: Marc Gonzalez @ 2019-08-28 9:09 UTC (permalink / raw)
To: SCSI, MSM
Cc: Avri Altman, Alim Akhtar, Bjorn Andersson, Lee Jones,
Ard Biesheuvel, Evan Green, Douglas Anderson, Vivek Gautam,
Nikita Shvets, Stanley Chu
Hello,
Someone posted a bug report for UFS on an sdm850 tablet:
https://bugzilla.kernel.org/show_bug.cgi?id=204685
If I'm reading the boot logs right, this board is EFI rather than DT.
(Lee: EFI on qcom is one of your areas, right?
The UFSHC driver is DT-aware, but is it EFI-aware?)
[ 0.000000] efi: memattr: Unexpected EFI Memory Attributes table version -1347440721
I suppose this may be safely ignored?
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.2.0-99-generic root=UUID=66e85825-5c21-4120-b4ee-e17e4cdc1e58 ro efi=novamap ignore_loglevel clk_ignore_unused pd_ignore_unused console=tty0
IIUC, the kernel is supposed to boot successfully even without
"clk_ignore_unused pd_ignore_unused" (tangential, unrelated)
Bjorn, any ideas? Ever see this issue?
Regards.
Notable events:
[ 2.438780] geni_se_qup 8c0000.geniqup: Err getting AHB clks -517
[ 2.439030] geni_se_qup ac0000.geniqup: Err getting AHB clks -517
[ 2.453050] ufshcd-qcom 1d84000.ufshc: ufshcd_get_vreg: vcc get failed, err=-517
[ 2.458477] ufshcd-qcom 1d84000.ufshc: Initialization failed
[ 2.540980] ufshcd-qcom 1d84000.ufshc: ufs_qcom_init: required phy device. hasn't probed yet. err = -517
[ 2.540986] ufshcd-qcom 1d84000.ufshc: ufshcd_variant_hba_init: variant qcom init failed err -517
[ 2.541052] ufshcd-qcom 1d84000.ufshc: Initialization failed
[ 2.695052] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
[ 2.699182] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq-supply regulator, assuming enabled
[ 2.706287] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq2-supply regulator, assuming enabled
[ 2.866207] ufshcd-qcom 1d84000.ufshc: ufshcd_find_max_sup_active_icc_level: Regulator capability was not set, actvIccLevel=0
[ 33.772190] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 7
[ 33.774946] sd 0:0:0:5: [sdf] tag#7 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
[ 33.805525] ufshcd-qcom 1d84000.ufshc: hba->ufs_version = 0x210, hba->capabilities = 0x1587031f
[ 33.808338] ufshcd-qcom 1d84000.ufshc: hba->outstanding_reqs = 0xab000080, hba->outstanding_tasks = 0x0
[ 34.045961] ufshcd-qcom 1d84000.ufshc: UPIU[7] - issue time 3165714 us
[ 34.047069] ufshcd-qcom 1d84000.ufshc: UPIU[7] - complete time 0 us
[ 34.048196] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Transfer Request Descriptor phys@0x2661cd0e0
[ 34.051799] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Request UPIU phys@0xdf045400
[ 34.055715] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Response UPIU phys@0xdf045600
[ 34.062761] ufshcd-qcom 1d84000.ufshc: UPIU[7] - PRDT - 1 entries phys@0xdf045800
[ 34.065836] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: cmd pending in the device. tag = 7
[ 34.168171] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x01 timed-out
[ 34.169822] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -110
[ 34.171497] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 29
[ 34.174951] ufshcd-qcom 1d84000.ufshc: UPIU[29] - issue time 3036529 us
[ 34.176740] ufshcd-qcom 1d84000.ufshc: UPIU[29] - complete time 0 us
[ 34.178534] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Transfer Request Descriptor phys@0x2661cd3a0
[ 34.184172] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Request UPIU phys@0xdf055c00
[ 34.190105] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Response UPIU phys@0xdf055e00
[ 34.200535] ufshcd-qcom 1d84000.ufshc: UPIU[29] - PRDT - 1 entries phys@0xdf056000
[ 34.202707] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
[ 34.204910] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 25
[ 34.209414] ufshcd-qcom 1d84000.ufshc: UPIU[25] - issue time 3017240 us
[ 34.211722] ufshcd-qcom 1d84000.ufshc: UPIU[25] - complete time 0 us
[ 34.214048] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Transfer Request Descriptor phys@0x2661cd320
[ 34.221259] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Request UPIU phys@0xdf052c00
[ 34.228788] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Response UPIU phys@0xdf052e00
[ 34.241869] ufshcd-qcom 1d84000.ufshc: UPIU[25] - PRDT - 1 entries phys@0xdf053000
[ 34.244578] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
[ 34.247307] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 24
[ 34.252877] ufshcd-qcom 1d84000.ufshc: UPIU[24] - issue time 3018666 us
[ 34.255718] ufshcd-qcom 1d84000.ufshc: UPIU[24] - complete time 0 us
[ 34.258540] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Transfer Request Descriptor phys@0x2661cd300
[ 34.266987] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Request UPIU phys@0xdf052000
[ 34.275500] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Response UPIU phys@0xdf052200
[ 34.289559] ufshcd-qcom 1d84000.ufshc: UPIU[24] - PRDT - 1 entries phys@0xdf052400
[ 34.292343] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
[ 34.295114] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 27
[ 34.300650] ufshcd-qcom 1d84000.ufshc: UPIU[27] - issue time 3040502 us
[ 34.303419] ufshcd-qcom 1d84000.ufshc: UPIU[27] - complete time 0 us
[ 34.306159] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Transfer Request Descriptor phys@0x2661cd360
[ 34.314450] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Request UPIU phys@0xdf054400
[ 34.322892] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Response UPIU phys@0xdf054600
[ 34.336707] ufshcd-qcom 1d84000.ufshc: UPIU[27] - PRDT - 1 entries phys@0xdf054800
[ 34.339447] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
[ 34.342173] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 31
[ 34.347604] ufshcd-qcom 1d84000.ufshc: UPIU[31] - issue time 3036762 us
[ 34.350345] ufshcd-qcom 1d84000.ufshc: UPIU[31] - complete time 0 us
[ 34.353042] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Transfer Request Descriptor phys@0x2661cd3e0
[ 34.361194] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Request UPIU phys@0xdf057400
[ 34.369347] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Response UPIU phys@0xdf057600
[ 34.383041] ufshcd-qcom 1d84000.ufshc: UPIU[31] - PRDT - 1 entries phys@0xdf057800
[ 34.385789] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
[ 34.508188] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
[ 34.511533] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
[ 34.616170] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
[ 34.619542] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
[ 34.724170] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
[ 34.727563] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
[ 34.832169] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
[ 34.835539] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
[ 34.940170] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
[ 34.943576] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
[ 35.048171] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
[ 35.051618] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
[ 35.095792] ufshcd-qcom 1d84000.ufshc: ufshcd_print_pwr_info:[RX, TX]: gear=[1, 1], lane[1, 1], pwr[SLOWAUTO_MODE, SLOWAUTO_MODE], rate = 0
[ 35.099829] ufshcd-qcom 1d84000.ufshc: UPIU[7] - issue time 3165714 us
[ 35.103402] ufshcd-qcom 1d84000.ufshc: UPIU[7] - complete time 0 us
[ 35.106937] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Transfer Request Descriptor phys@0x2661cd0e0
[ 35.117587] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Request UPIU phys@0xdf045400
[ 35.128237] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Response UPIU phys@0xdf045600
[ 35.145785] ufshcd-qcom 1d84000.ufshc: UPIU[7] - PRDT - 1 entries phys@0xdf045800
[ 35.152773] ufshcd-qcom 1d84000.ufshc: UPIU[24] - issue time 3018666 us
[ 35.156346] ufshcd-qcom 1d84000.ufshc: UPIU[24] - complete time 0 us
[ 35.159906] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Transfer Request Descriptor phys@0x2661cd300
[ 35.170605] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Request UPIU phys@0xdf052000
[ 35.181279] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Response UPIU phys@0xdf052200
[ 35.198877] ufshcd-qcom 1d84000.ufshc: UPIU[24] - PRDT - 1 entries phys@0xdf052400
[ 35.205904] ufshcd-qcom 1d84000.ufshc: UPIU[25] - issue time 3017240 us
[ 35.209398] ufshcd-qcom 1d84000.ufshc: UPIU[25] - complete time 0 us
[ 35.212913] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Transfer Request Descriptor phys@0x2661cd320
[ 35.223656] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Request UPIU phys@0xdf052c00
[ 35.234408] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Response UPIU phys@0xdf052e00
[ 35.252106] ufshcd-qcom 1d84000.ufshc: UPIU[25] - PRDT - 1 entries phys@0xdf053000
[ 35.259137] ufshcd-qcom 1d84000.ufshc: UPIU[27] - issue time 3040502 us
[ 35.262691] ufshcd-qcom 1d84000.ufshc: UPIU[27] - complete time 0 us
[ 35.266202] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Transfer Request Descriptor phys@0x2661cd360
[ 35.276857] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Request UPIU phys@0xdf054400
[ 35.287652] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Response UPIU phys@0xdf054600
[ 35.305317] ufshcd-qcom 1d84000.ufshc: UPIU[27] - PRDT - 1 entries phys@0xdf054800
[ 35.312298] ufshcd-qcom 1d84000.ufshc: UPIU[29] - issue time 3036529 us
[ 35.315788] ufshcd-qcom 1d84000.ufshc: UPIU[29] - complete time 0 us
[ 35.319240] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Transfer Request Descriptor phys@0x2661cd3a0
[ 35.329591] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Request UPIU phys@0xdf055c00
[ 35.339727] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Response UPIU phys@0xdf055e00
[ 35.356361] ufshcd-qcom 1d84000.ufshc: UPIU[29] - PRDT - 1 entries phys@0xdf056000
[ 35.363009] ufshcd-qcom 1d84000.ufshc: UPIU[31] - issue time 3036762 us
[ 35.366321] ufshcd-qcom 1d84000.ufshc: UPIU[31] - complete time 0 us
[ 35.369646] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Transfer Request Descriptor phys@0x2661cd3e0
[ 35.379815] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Request UPIU phys@0xdf057400
[ 35.389919] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Response UPIU phys@0xdf057600
[ 35.406573] ufshcd-qcom 1d84000.ufshc: UPIU[31] - PRDT - 1 entries phys@0xdf057800
[ 35.506995] ufshcd-qcom 1d84000.ufshc: ufshcd_print_pwr_info:[RX, TX]: gear=[3, 3], lane[2, 2], pwr[FAST MODE, FAST MODE], rate = 2
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ufshcd_abort: Device abort task at tag 7
2019-08-28 9:09 ufshcd_abort: Device abort task at tag 7 Marc Gonzalez
@ 2019-08-28 19:20 ` Bjorn Andersson
2019-08-30 13:16 ` russianneuromancer
0 siblings, 1 reply; 5+ messages in thread
From: Bjorn Andersson @ 2019-08-28 19:20 UTC (permalink / raw)
To: Marc Gonzalez
Cc: SCSI, MSM, Avri Altman, Alim Akhtar, Lee Jones, Ard Biesheuvel,
Evan Green, Douglas Anderson, Vivek Gautam, Nikita Shvets,
Stanley Chu
On Wed 28 Aug 02:09 PDT 2019, Marc Gonzalez wrote:
> Hello,
>
> Someone posted a bug report for UFS on an sdm850 tablet:
> https://bugzilla.kernel.org/show_bug.cgi?id=204685
>
> If I'm reading the boot logs right, this board is EFI rather than DT.
It's UEFI-based and Linux will either operate based on DT or ACPI
tables, depending on what was provided.
> (Lee: EFI on qcom is one of your areas, right?
> The UFSHC driver is DT-aware, but is it EFI-aware?)
>
> [ 0.000000] efi: memattr: Unexpected EFI Memory Attributes table version -1347440721
> I suppose this may be safely ignored?
>
> [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.2.0-99-generic root=UUID=66e85825-5c21-4120-b4ee-e17e4cdc1e58 ro efi=novamap ignore_loglevel clk_ignore_unused pd_ignore_unused console=tty0
> IIUC, the kernel is supposed to boot successfully even without
> "clk_ignore_unused pd_ignore_unused" (tangential, unrelated)
>
> Bjorn, any ideas? Ever see this issue?
>
I don't remember the exact splats seen, but I would suggest that this is
retested after applying the following series:
https://lore.kernel.org/linux-arm-msm/20190828191756.24312-1-bjorn.andersson@linaro.org/T/#u
Regards,
Bjorn
> Regards.
>
>
> Notable events:
>
> [ 2.438780] geni_se_qup 8c0000.geniqup: Err getting AHB clks -517
> [ 2.439030] geni_se_qup ac0000.geniqup: Err getting AHB clks -517
>
> [ 2.453050] ufshcd-qcom 1d84000.ufshc: ufshcd_get_vreg: vcc get failed, err=-517
> [ 2.458477] ufshcd-qcom 1d84000.ufshc: Initialization failed
>
> [ 2.540980] ufshcd-qcom 1d84000.ufshc: ufs_qcom_init: required phy device. hasn't probed yet. err = -517
> [ 2.540986] ufshcd-qcom 1d84000.ufshc: ufshcd_variant_hba_init: variant qcom init failed err -517
> [ 2.541052] ufshcd-qcom 1d84000.ufshc: Initialization failed
>
> [ 2.695052] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
> [ 2.699182] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq-supply regulator, assuming enabled
> [ 2.706287] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq2-supply regulator, assuming enabled
> [ 2.866207] ufshcd-qcom 1d84000.ufshc: ufshcd_find_max_sup_active_icc_level: Regulator capability was not set, actvIccLevel=0
>
> [ 33.772190] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 7
> [ 33.774946] sd 0:0:0:5: [sdf] tag#7 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
> [ 33.805525] ufshcd-qcom 1d84000.ufshc: hba->ufs_version = 0x210, hba->capabilities = 0x1587031f
> [ 33.808338] ufshcd-qcom 1d84000.ufshc: hba->outstanding_reqs = 0xab000080, hba->outstanding_tasks = 0x0
>
> [ 34.045961] ufshcd-qcom 1d84000.ufshc: UPIU[7] - issue time 3165714 us
> [ 34.047069] ufshcd-qcom 1d84000.ufshc: UPIU[7] - complete time 0 us
> [ 34.048196] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Transfer Request Descriptor phys@0x2661cd0e0
> [ 34.051799] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Request UPIU phys@0xdf045400
> [ 34.055715] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Response UPIU phys@0xdf045600
> [ 34.062761] ufshcd-qcom 1d84000.ufshc: UPIU[7] - PRDT - 1 entries phys@0xdf045800
> [ 34.065836] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: cmd pending in the device. tag = 7
> [ 34.168171] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x01 timed-out
> [ 34.169822] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -110
> [ 34.171497] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 29
> [ 34.174951] ufshcd-qcom 1d84000.ufshc: UPIU[29] - issue time 3036529 us
> [ 34.176740] ufshcd-qcom 1d84000.ufshc: UPIU[29] - complete time 0 us
> [ 34.178534] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Transfer Request Descriptor phys@0x2661cd3a0
> [ 34.184172] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Request UPIU phys@0xdf055c00
> [ 34.190105] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Response UPIU phys@0xdf055e00
> [ 34.200535] ufshcd-qcom 1d84000.ufshc: UPIU[29] - PRDT - 1 entries phys@0xdf056000
> [ 34.202707] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
> [ 34.204910] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 25
> [ 34.209414] ufshcd-qcom 1d84000.ufshc: UPIU[25] - issue time 3017240 us
> [ 34.211722] ufshcd-qcom 1d84000.ufshc: UPIU[25] - complete time 0 us
> [ 34.214048] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Transfer Request Descriptor phys@0x2661cd320
> [ 34.221259] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Request UPIU phys@0xdf052c00
> [ 34.228788] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Response UPIU phys@0xdf052e00
> [ 34.241869] ufshcd-qcom 1d84000.ufshc: UPIU[25] - PRDT - 1 entries phys@0xdf053000
> [ 34.244578] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
> [ 34.247307] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 24
> [ 34.252877] ufshcd-qcom 1d84000.ufshc: UPIU[24] - issue time 3018666 us
> [ 34.255718] ufshcd-qcom 1d84000.ufshc: UPIU[24] - complete time 0 us
> [ 34.258540] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Transfer Request Descriptor phys@0x2661cd300
> [ 34.266987] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Request UPIU phys@0xdf052000
> [ 34.275500] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Response UPIU phys@0xdf052200
> [ 34.289559] ufshcd-qcom 1d84000.ufshc: UPIU[24] - PRDT - 1 entries phys@0xdf052400
> [ 34.292343] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
> [ 34.295114] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 27
> [ 34.300650] ufshcd-qcom 1d84000.ufshc: UPIU[27] - issue time 3040502 us
> [ 34.303419] ufshcd-qcom 1d84000.ufshc: UPIU[27] - complete time 0 us
> [ 34.306159] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Transfer Request Descriptor phys@0x2661cd360
> [ 34.314450] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Request UPIU phys@0xdf054400
> [ 34.322892] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Response UPIU phys@0xdf054600
> [ 34.336707] ufshcd-qcom 1d84000.ufshc: UPIU[27] - PRDT - 1 entries phys@0xdf054800
> [ 34.339447] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
> [ 34.342173] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 31
> [ 34.347604] ufshcd-qcom 1d84000.ufshc: UPIU[31] - issue time 3036762 us
> [ 34.350345] ufshcd-qcom 1d84000.ufshc: UPIU[31] - complete time 0 us
> [ 34.353042] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Transfer Request Descriptor phys@0x2661cd3e0
> [ 34.361194] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Request UPIU phys@0xdf057400
> [ 34.369347] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Response UPIU phys@0xdf057600
> [ 34.383041] ufshcd-qcom 1d84000.ufshc: UPIU[31] - PRDT - 1 entries phys@0xdf057800
> [ 34.385789] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
> [ 34.508188] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
> [ 34.511533] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
> [ 34.616170] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
> [ 34.619542] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
> [ 34.724170] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
> [ 34.727563] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
> [ 34.832169] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
> [ 34.835539] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
> [ 34.940170] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
> [ 34.943576] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
> [ 35.048171] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
> [ 35.051618] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
> [ 35.095792] ufshcd-qcom 1d84000.ufshc: ufshcd_print_pwr_info:[RX, TX]: gear=[1, 1], lane[1, 1], pwr[SLOWAUTO_MODE, SLOWAUTO_MODE], rate = 0
> [ 35.099829] ufshcd-qcom 1d84000.ufshc: UPIU[7] - issue time 3165714 us
> [ 35.103402] ufshcd-qcom 1d84000.ufshc: UPIU[7] - complete time 0 us
> [ 35.106937] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Transfer Request Descriptor phys@0x2661cd0e0
> [ 35.117587] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Request UPIU phys@0xdf045400
> [ 35.128237] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Response UPIU phys@0xdf045600
> [ 35.145785] ufshcd-qcom 1d84000.ufshc: UPIU[7] - PRDT - 1 entries phys@0xdf045800
> [ 35.152773] ufshcd-qcom 1d84000.ufshc: UPIU[24] - issue time 3018666 us
> [ 35.156346] ufshcd-qcom 1d84000.ufshc: UPIU[24] - complete time 0 us
> [ 35.159906] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Transfer Request Descriptor phys@0x2661cd300
> [ 35.170605] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Request UPIU phys@0xdf052000
> [ 35.181279] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Response UPIU phys@0xdf052200
> [ 35.198877] ufshcd-qcom 1d84000.ufshc: UPIU[24] - PRDT - 1 entries phys@0xdf052400
> [ 35.205904] ufshcd-qcom 1d84000.ufshc: UPIU[25] - issue time 3017240 us
> [ 35.209398] ufshcd-qcom 1d84000.ufshc: UPIU[25] - complete time 0 us
> [ 35.212913] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Transfer Request Descriptor phys@0x2661cd320
> [ 35.223656] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Request UPIU phys@0xdf052c00
> [ 35.234408] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Response UPIU phys@0xdf052e00
> [ 35.252106] ufshcd-qcom 1d84000.ufshc: UPIU[25] - PRDT - 1 entries phys@0xdf053000
> [ 35.259137] ufshcd-qcom 1d84000.ufshc: UPIU[27] - issue time 3040502 us
> [ 35.262691] ufshcd-qcom 1d84000.ufshc: UPIU[27] - complete time 0 us
> [ 35.266202] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Transfer Request Descriptor phys@0x2661cd360
> [ 35.276857] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Request UPIU phys@0xdf054400
> [ 35.287652] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Response UPIU phys@0xdf054600
> [ 35.305317] ufshcd-qcom 1d84000.ufshc: UPIU[27] - PRDT - 1 entries phys@0xdf054800
> [ 35.312298] ufshcd-qcom 1d84000.ufshc: UPIU[29] - issue time 3036529 us
> [ 35.315788] ufshcd-qcom 1d84000.ufshc: UPIU[29] - complete time 0 us
> [ 35.319240] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Transfer Request Descriptor phys@0x2661cd3a0
> [ 35.329591] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Request UPIU phys@0xdf055c00
> [ 35.339727] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Response UPIU phys@0xdf055e00
> [ 35.356361] ufshcd-qcom 1d84000.ufshc: UPIU[29] - PRDT - 1 entries phys@0xdf056000
> [ 35.363009] ufshcd-qcom 1d84000.ufshc: UPIU[31] - issue time 3036762 us
> [ 35.366321] ufshcd-qcom 1d84000.ufshc: UPIU[31] - complete time 0 us
> [ 35.369646] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Transfer Request Descriptor phys@0x2661cd3e0
> [ 35.379815] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Request UPIU phys@0xdf057400
> [ 35.389919] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Response UPIU phys@0xdf057600
> [ 35.406573] ufshcd-qcom 1d84000.ufshc: UPIU[31] - PRDT - 1 entries phys@0xdf057800
> [ 35.506995] ufshcd-qcom 1d84000.ufshc: ufshcd_print_pwr_info:[RX, TX]: gear=[3, 3], lane[2, 2], pwr[FAST MODE, FAST MODE], rate = 2
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ufshcd_abort: Device abort task at tag 7
2019-08-28 19:20 ` Bjorn Andersson
@ 2019-08-30 13:16 ` russianneuromancer
2019-09-02 8:12 ` Lee Jones
0 siblings, 1 reply; 5+ messages in thread
From: russianneuromancer @ 2019-08-30 13:16 UTC (permalink / raw)
To: Bjorn Andersson, Marc Gonzalez
Cc: SCSI, MSM, Avri Altman, Alim Akhtar, Lee Jones, Ard Biesheuvel,
Evan Green, Douglas Anderson, Vivek Gautam, Stanley Chu
Hello!
> I don't remember the exact splats seen, but I would suggest that this is
> retested after applying the following series:
>
> https://lore.kernel.org/linux-arm-msm/20190828191756.24312-1-bjorn.andersson@linaro.org/T/#u
Turns out this patches is already applied to kernel running on this device, but one line in dts was missing:
https://github.com/aarch64-laptops/linux/pull/2
With this line issue is no longer reproducible with DT boot. Thank you!
As I understand it's planned to eventually boot this devices via ACPI.
@Lee Jones, is my understanding correct?
29.08.2019, 03:20, "Bjorn Andersson" <bjorn.andersson@linaro.org>:
> On Wed 28 Aug 02:09 PDT 2019, Marc Gonzalez wrote:
>
>> Hello,
>>
>> Someone posted a bug report for UFS on an sdm850 tablet:
>> https://bugzilla.kernel.org/show_bug.cgi?id=204685
>>
>> If I'm reading the boot logs right, this board is EFI rather than DT.
>
> It's UEFI-based and Linux will either operate based on DT or ACPI
> tables, depending on what was provided.
>
>> (Lee: EFI on qcom is one of your areas, right?
>> The UFSHC driver is DT-aware, but is it EFI-aware?)
>>
>> [ 0.000000] efi: memattr: Unexpected EFI Memory Attributes table version -1347440721
>> I suppose this may be safely ignored?
>>
>> [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.2.0-99-generic root=UUID=66e85825-5c21-4120-b4ee-e17e4cdc1e58 ro efi=novamap ignore_loglevel clk_ignore_unused pd_ignore_unused console=tty0
>> IIUC, the kernel is supposed to boot successfully even without
>> "clk_ignore_unused pd_ignore_unused" (tangential, unrelated)
>>
>> Bjorn, any ideas? Ever see this issue?
>
> I don't remember the exact splats seen, but I would suggest that this is
> retested after applying the following series:
>
> https://lore.kernel.org/linux-arm-msm/20190828191756.24312-1-bjorn.andersson@linaro.org/T/#u
>
> Regards,
> Bjorn
>
>> Regards.
>>
>> Notable events:
>>
>> [ 2.438780] geni_se_qup 8c0000.geniqup: Err getting AHB clks -517
>> [ 2.439030] geni_se_qup ac0000.geniqup: Err getting AHB clks -517
>>
>> [ 2.453050] ufshcd-qcom 1d84000.ufshc: ufshcd_get_vreg: vcc get failed, err=-517
>> [ 2.458477] ufshcd-qcom 1d84000.ufshc: Initialization failed
>>
>> [ 2.540980] ufshcd-qcom 1d84000.ufshc: ufs_qcom_init: required phy device. hasn't probed yet. err = -517
>> [ 2.540986] ufshcd-qcom 1d84000.ufshc: ufshcd_variant_hba_init: variant qcom init failed err -517
>> [ 2.541052] ufshcd-qcom 1d84000.ufshc: Initialization failed
>>
>> [ 2.695052] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
>> [ 2.699182] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq-supply regulator, assuming enabled
>> [ 2.706287] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq2-supply regulator, assuming enabled
>> [ 2.866207] ufshcd-qcom 1d84000.ufshc: ufshcd_find_max_sup_active_icc_level: Regulator capability was not set, actvIccLevel=0
>>
>> [ 33.772190] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 7
>> [ 33.774946] sd 0:0:0:5: [sdf] tag#7 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
>> [ 33.805525] ufshcd-qcom 1d84000.ufshc: hba->ufs_version = 0x210, hba->capabilities = 0x1587031f
>> [ 33.808338] ufshcd-qcom 1d84000.ufshc: hba->outstanding_reqs = 0xab000080, hba->outstanding_tasks = 0x0
>>
>> [ 34.045961] ufshcd-qcom 1d84000.ufshc: UPIU[7] - issue time 3165714 us
>> [ 34.047069] ufshcd-qcom 1d84000.ufshc: UPIU[7] - complete time 0 us
>> [ 34.048196] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Transfer Request Descriptor phys@0x2661cd0e0
>> [ 34.051799] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Request UPIU phys@0xdf045400
>> [ 34.055715] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Response UPIU phys@0xdf045600
>> [ 34.062761] ufshcd-qcom 1d84000.ufshc: UPIU[7] - PRDT - 1 entries phys@0xdf045800
>> [ 34.065836] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: cmd pending in the device. tag = 7
>> [ 34.168171] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x01 timed-out
>> [ 34.169822] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -110
>> [ 34.171497] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 29
>> [ 34.174951] ufshcd-qcom 1d84000.ufshc: UPIU[29] - issue time 3036529 us
>> [ 34.176740] ufshcd-qcom 1d84000.ufshc: UPIU[29] - complete time 0 us
>> [ 34.178534] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Transfer Request Descriptor phys@0x2661cd3a0
>> [ 34.184172] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Request UPIU phys@0xdf055c00
>> [ 34.190105] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Response UPIU phys@0xdf055e00
>> [ 34.200535] ufshcd-qcom 1d84000.ufshc: UPIU[29] - PRDT - 1 entries phys@0xdf056000
>> [ 34.202707] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
>> [ 34.204910] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 25
>> [ 34.209414] ufshcd-qcom 1d84000.ufshc: UPIU[25] - issue time 3017240 us
>> [ 34.211722] ufshcd-qcom 1d84000.ufshc: UPIU[25] - complete time 0 us
>> [ 34.214048] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Transfer Request Descriptor phys@0x2661cd320
>> [ 34.221259] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Request UPIU phys@0xdf052c00
>> [ 34.228788] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Response UPIU phys@0xdf052e00
>> [ 34.241869] ufshcd-qcom 1d84000.ufshc: UPIU[25] - PRDT - 1 entries phys@0xdf053000
>> [ 34.244578] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
>> [ 34.247307] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 24
>> [ 34.252877] ufshcd-qcom 1d84000.ufshc: UPIU[24] - issue time 3018666 us
>> [ 34.255718] ufshcd-qcom 1d84000.ufshc: UPIU[24] - complete time 0 us
>> [ 34.258540] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Transfer Request Descriptor phys@0x2661cd300
>> [ 34.266987] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Request UPIU phys@0xdf052000
>> [ 34.275500] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Response UPIU phys@0xdf052200
>> [ 34.289559] ufshcd-qcom 1d84000.ufshc: UPIU[24] - PRDT - 1 entries phys@0xdf052400
>> [ 34.292343] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
>> [ 34.295114] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 27
>> [ 34.300650] ufshcd-qcom 1d84000.ufshc: UPIU[27] - issue time 3040502 us
>> [ 34.303419] ufshcd-qcom 1d84000.ufshc: UPIU[27] - complete time 0 us
>> [ 34.306159] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Transfer Request Descriptor phys@0x2661cd360
>> [ 34.314450] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Request UPIU phys@0xdf054400
>> [ 34.322892] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Response UPIU phys@0xdf054600
>> [ 34.336707] ufshcd-qcom 1d84000.ufshc: UPIU[27] - PRDT - 1 entries phys@0xdf054800
>> [ 34.339447] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
>> [ 34.342173] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 31
>> [ 34.347604] ufshcd-qcom 1d84000.ufshc: UPIU[31] - issue time 3036762 us
>> [ 34.350345] ufshcd-qcom 1d84000.ufshc: UPIU[31] - complete time 0 us
>> [ 34.353042] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Transfer Request Descriptor phys@0x2661cd3e0
>> [ 34.361194] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Request UPIU phys@0xdf057400
>> [ 34.369347] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Response UPIU phys@0xdf057600
>> [ 34.383041] ufshcd-qcom 1d84000.ufshc: UPIU[31] - PRDT - 1 entries phys@0xdf057800
>> [ 34.385789] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: failed with err -5
>> [ 34.508188] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
>> [ 34.511533] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
>> [ 34.616170] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
>> [ 34.619542] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
>> [ 34.724170] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
>> [ 34.727563] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
>> [ 34.832169] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
>> [ 34.835539] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
>> [ 34.940170] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
>> [ 34.943576] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
>> [ 35.048171] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x08 timed-out
>> [ 35.051618] ufshcd-qcom 1d84000.ufshc: ufshcd_eh_device_reset_handler: failed with err -110
>> [ 35.095792] ufshcd-qcom 1d84000.ufshc: ufshcd_print_pwr_info:[RX, TX]: gear=[1, 1], lane[1, 1], pwr[SLOWAUTO_MODE, SLOWAUTO_MODE], rate = 0
>> [ 35.099829] ufshcd-qcom 1d84000.ufshc: UPIU[7] - issue time 3165714 us
>> [ 35.103402] ufshcd-qcom 1d84000.ufshc: UPIU[7] - complete time 0 us
>> [ 35.106937] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Transfer Request Descriptor phys@0x2661cd0e0
>> [ 35.117587] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Request UPIU phys@0xdf045400
>> [ 35.128237] ufshcd-qcom 1d84000.ufshc: UPIU[7] - Response UPIU phys@0xdf045600
>> [ 35.145785] ufshcd-qcom 1d84000.ufshc: UPIU[7] - PRDT - 1 entries phys@0xdf045800
>> [ 35.152773] ufshcd-qcom 1d84000.ufshc: UPIU[24] - issue time 3018666 us
>> [ 35.156346] ufshcd-qcom 1d84000.ufshc: UPIU[24] - complete time 0 us
>> [ 35.159906] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Transfer Request Descriptor phys@0x2661cd300
>> [ 35.170605] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Request UPIU phys@0xdf052000
>> [ 35.181279] ufshcd-qcom 1d84000.ufshc: UPIU[24] - Response UPIU phys@0xdf052200
>> [ 35.198877] ufshcd-qcom 1d84000.ufshc: UPIU[24] - PRDT - 1 entries phys@0xdf052400
>> [ 35.205904] ufshcd-qcom 1d84000.ufshc: UPIU[25] - issue time 3017240 us
>> [ 35.209398] ufshcd-qcom 1d84000.ufshc: UPIU[25] - complete time 0 us
>> [ 35.212913] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Transfer Request Descriptor phys@0x2661cd320
>> [ 35.223656] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Request UPIU phys@0xdf052c00
>> [ 35.234408] ufshcd-qcom 1d84000.ufshc: UPIU[25] - Response UPIU phys@0xdf052e00
>> [ 35.252106] ufshcd-qcom 1d84000.ufshc: UPIU[25] - PRDT - 1 entries phys@0xdf053000
>> [ 35.259137] ufshcd-qcom 1d84000.ufshc: UPIU[27] - issue time 3040502 us
>> [ 35.262691] ufshcd-qcom 1d84000.ufshc: UPIU[27] - complete time 0 us
>> [ 35.266202] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Transfer Request Descriptor phys@0x2661cd360
>> [ 35.276857] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Request UPIU phys@0xdf054400
>> [ 35.287652] ufshcd-qcom 1d84000.ufshc: UPIU[27] - Response UPIU phys@0xdf054600
>> [ 35.305317] ufshcd-qcom 1d84000.ufshc: UPIU[27] - PRDT - 1 entries phys@0xdf054800
>> [ 35.312298] ufshcd-qcom 1d84000.ufshc: UPIU[29] - issue time 3036529 us
>> [ 35.315788] ufshcd-qcom 1d84000.ufshc: UPIU[29] - complete time 0 us
>> [ 35.319240] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Transfer Request Descriptor phys@0x2661cd3a0
>> [ 35.329591] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Request UPIU phys@0xdf055c00
>> [ 35.339727] ufshcd-qcom 1d84000.ufshc: UPIU[29] - Response UPIU phys@0xdf055e00
>> [ 35.356361] ufshcd-qcom 1d84000.ufshc: UPIU[29] - PRDT - 1 entries phys@0xdf056000
>> [ 35.363009] ufshcd-qcom 1d84000.ufshc: UPIU[31] - issue time 3036762 us
>> [ 35.366321] ufshcd-qcom 1d84000.ufshc: UPIU[31] - complete time 0 us
>> [ 35.369646] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Transfer Request Descriptor phys@0x2661cd3e0
>> [ 35.379815] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Request UPIU phys@0xdf057400
>> [ 35.389919] ufshcd-qcom 1d84000.ufshc: UPIU[31] - Response UPIU phys@0xdf057600
>> [ 35.406573] ufshcd-qcom 1d84000.ufshc: UPIU[31] - PRDT - 1 entries phys@0xdf057800
>> [ 35.506995] ufshcd-qcom 1d84000.ufshc: ufshcd_print_pwr_info:[RX, TX]: gear=[3, 3], lane[2, 2], pwr[FAST MODE, FAST MODE], rate = 2
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ufshcd_abort: Device abort task at tag 7
2019-08-30 13:16 ` russianneuromancer
@ 2019-09-02 8:12 ` Lee Jones
2019-09-03 15:17 ` russianneuromancer
0 siblings, 1 reply; 5+ messages in thread
From: Lee Jones @ 2019-09-02 8:12 UTC (permalink / raw)
To: russianneuromancer
Cc: Bjorn Andersson, Marc Gonzalez, SCSI, MSM, Avri Altman,
Alim Akhtar, Ard Biesheuvel, Evan Green, Douglas Anderson,
Vivek Gautam, Stanley Chu
On Fri, 30 Aug 2019, russianneuromancer@ya.ru wrote:
> Hello!
>
>
> > I don't remember the exact splats seen, but I would suggest that this is
> > retested after applying the following series:
> >
> > https://lore.kernel.org/linux-arm-msm/20190828191756.24312-1-bjorn.andersson@linaro.org/T/#u
>
> Turns out this patches is already applied to kernel running on this device, but one line in dts was missing:
>
> https://github.com/aarch64-laptops/linux/pull/2
>
> With this line issue is no longer reproducible with DT boot. Thank you!
>
> As I understand it's planned to eventually boot this devices via ACPI.
>
> @Lee Jones, is my understanding correct?
No, not exactly. We can boot these devices using ACPI, but with
limited functionality (when compared with booting using DT). There
are too many black-boxes when booting with ACPI - something that can
only be resolved with Qualcomm's help.
Booting with ACPI helps us to use generic Linux distribution
installers, but it is expected for users to switch to DT once the OS
is installed.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ufshcd_abort: Device abort task at tag 7
2019-09-02 8:12 ` Lee Jones
@ 2019-09-03 15:17 ` russianneuromancer
0 siblings, 0 replies; 5+ messages in thread
From: russianneuromancer @ 2019-09-03 15:17 UTC (permalink / raw)
To: Lee Jones
Cc: Bjorn Andersson, Marc Gonzalez, SCSI, MSM, Avri Altman,
Alim Akhtar, Ard Biesheuvel, Evan Green, Douglas Anderson,
Vivek Gautam, Stanley Chu
Hello!
> Booting with ACPI helps us to use generic Linux distribution
> installers, but it is expected for users to switch to DT once the OS
> is installed.
Thank you for clarification!
Should I close my bugreport when Bjorn's "Qualcomm UFS device reset support" series will hit upstream, or I should wait for additional fix that applicable for ACPI boot as well?
I don't know if this boot delay is Ok for generic installer image, and it's not up to me to decide this, which is why I ask.
02.09.2019, 16:12, "Lee Jones" <lee.jones@linaro.org>:
> On Fri, 30 Aug 2019, russianneuromancer@ya.ru wrote:
>
>> Hello!
>>
>> > I don't remember the exact splats seen, but I would suggest that this is
>> > retested after applying the following series:
>> >
>> > https://lore.kernel.org/linux-arm-msm/20190828191756.24312-1-bjorn.andersson@linaro.org/T/#u
>>
>> Turns out this patches is already applied to kernel running on this device, but one line in dts was missing:
>>
>> https://github.com/aarch64-laptops/linux/pull/2
>>
>> With this line issue is no longer reproducible with DT boot. Thank you!
>>
>> As I understand it's planned to eventually boot this devices via ACPI.
>>
>> @Lee Jones, is my understanding correct?
>
> No, not exactly. We can boot these devices using ACPI, but with
> limited functionality (when compared with booting using DT). There
> are too many black-boxes when booting with ACPI - something that can
> only be resolved with Qualcomm's help.
>
> Booting with ACPI helps us to use generic Linux distribution
> installers, but it is expected for users to switch to DT once the OS
> is installed.
>
> --
> Lee Jones [李琼斯]
> Linaro Services Technical Lead
> Linaro.org │ Open source software for ARM SoCs
> Follow Linaro: Facebook | Twitter | Blog
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-09-03 15:25 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-28 9:09 ufshcd_abort: Device abort task at tag 7 Marc Gonzalez
2019-08-28 19:20 ` Bjorn Andersson
2019-08-30 13:16 ` russianneuromancer
2019-09-02 8:12 ` Lee Jones
2019-09-03 15:17 ` russianneuromancer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).