Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sometimes boot is delayed due to UFS initialization error #15

Closed
RussianNeuroMancer opened this issue Aug 6, 2019 · 3 comments
Closed

Comments

@RussianNeuroMancer
Copy link
Contributor

I noticed that sometimes Linux 5.2.0-99.5laptops1 from PPA boot delayed by following error:

[   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.777732] host_regs: 00000000: 1587031f 00000000 00000210 00000000
[   33.780508] host_regs: 00000010: 01000000 00010217 00000c96 00000000
[   33.783281] host_regs: 00000020: 00000000 00030e75 00000000 00000000
[   33.786061] host_regs: 00000030: 0000010f 00000001 80000010 00000000
[   33.788842] host_regs: 00000040: 00000000 00000000 00000000 00000000
[   33.791616] host_regs: 00000050: 661cd000 00000002 ab000080 00000000
[   33.794403] host_regs: 00000060: 00000001 ff1fffff 00000000 00000000
[   33.797195] host_regs: 00000070: 661cc000 00000002 00000000 00000000
[   33.799987] host_regs: 00000080: 00000001 00000000 00000000 00000000
[   33.802763] host_regs: 00000090: 00000002 15710000 00000000 00000003
[   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
[   33.811144] ufshcd-qcom 1d84000.ufshc: last_hibern8_exit_tstamp at 0 us, hibern8_exit_cnt = 0
[   33.813951] ufshcd-qcom 1d84000.ufshc: No record of pa_err uic errors
[   33.816735] ufshcd-qcom 1d84000.ufshc: No record of dl_err uic errors
[   33.819496] ufshcd-qcom 1d84000.ufshc: No record of nl_err uic errors
[   33.822236] ufshcd-qcom 1d84000.ufshc: No record of tl_err uic errors
[   33.824947] ufshcd-qcom 1d84000.ufshc: No record of dme_err uic errors
[   33.827660] ufshcd-qcom 1d84000.ufshc: clk: core_clk, rate: 200000000
[   33.830371] ufshcd-qcom 1d84000.ufshc: clk: core_clk_unipro, rate: 150000000
[   33.833118] HCI Vendor Specific Registers 00000000: 000000c8 00000000 00000000 00000000
[   33.835858] HCI Vendor Specific Registers 00000010: 00000000 00000000 00000001 5c5c052c
[   33.838566] HCI Vendor Specific Registers 00000020: 3f0113ff 30010001 00000000 00000000
[   33.841258] HCI Vendor Specific Registers 00000030: 00000000 00000000 02500000 00000000

Full log:
dmesg_ufs.zip

After booting completion UFS storage is accessible (but you already can see that in full log).

@RussianNeuroMancer RussianNeuroMancer changed the title Sometimes Linux 5.2 boot is delayed to UFS initialization error Sometimes Linux 5.2 boot is delayed due to UFS initialization error Aug 6, 2019
@RussianNeuroMancer
Copy link
Contributor Author

Same issue with Linux 5.3rc1, check logs attached to this message.

@RussianNeuroMancer RussianNeuroMancer changed the title Sometimes Linux 5.2 boot is delayed due to UFS initialization error Sometimes boot is delayed due to UFS initialization error Aug 10, 2019
@lag-linaro
Copy link
Collaborator

UFS support for these devices is now upstream.

Please report it there. Marc Gonzalez is probably your best bet. You can find him in the kernel logs.

Closing, as this isn't an issue specific to this project.

@RussianNeuroMancer
Copy link
Contributor Author

UFS support for these devices is now upstream.
Please report it there.

Thank for looking into this issue! Issue is reported to upstream now: https://bugzilla.kernel.org/show_bug.cgi?id=204685

Marc Gonzalez is probably your best bet. You can find him in the kernel logs.

Thanks for recommendation, I contacted him by e-mail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants