linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Can Guo <cang@codeaurora.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Asutosh Das <asutoshd@codeaurora.org>,
	martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, stern@rowland.harvard.edu
Subject: Re: [RFC PATCH v1 0/2] Fix deadlock in ufs
Date: Thu, 28 Jan 2021 10:47:36 +0800	[thread overview]
Message-ID: <49c894a55b56233814252bc59c24f7b4@codeaurora.org> (raw)
In-Reply-To: <YBHAyYRzlvqvB+N+@builder.lan>

On 2021-01-28 03:36, Bjorn Andersson wrote:
> On Wed 27 Jan 10:16 CST 2021, Asutosh Das wrote:
> 
>> On Wed, Jan 27 2021 at 07:25 -0800, Bjorn Andersson wrote:
>> > On Tue 26 Jan 20:00 PST 2021, Asutosh Das wrote:
>> >
>> > > This patchset attempts to fix a deadlock in ufs.
>> > > This deadlock occurs because the ufs host driver tries to resume
>> > > its child (wlun scsi device) to send SSU to it during its suspend.
>> > >
>> >
>> > I've been trying to bisect a regression currently seen on all Qualcomm
>> > boards I've tried running next-20210125 on, but have yet to figure out
>> > the actual culprit. I was hoping this might be related, but no.
>> >
>> > The following is the UFS related logs from a SDM845 board:
>> >
>> > [    4.556147] ufshcd-qcom 1d84000.ufshc: Adding to iommu group 10
>> > [   14.823635] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
>> > [   14.834483] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq-supply regulator, assuming enabled
>> > [   14.845022] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq2-supply regulator, assuming enabled
>> > [   14.859278] scsi host0: ufshcd
>> > [   14.894076] ufshcd-qcom 1d84000.ufshc: ufshcd_print_pwr_info:[RX, TX]: gear=[1, 1], lane[1, 1], pwr[SLOWAUTO_MODE, SLOWAUTO_MODE], rate = 0
>> > [   14.972730] ufshcd-qcom 1d84000.ufshc: ufshcd_find_max_sup_active_icc_level: Regulator capability was not set, actvIccLevel=0
>> > [   14.988386] scsi 0:0:0:49488: Well-known LUN    SKhynix  H28S7Q302BMR     A002 PQ: 0 ANSI: 6
>> > [   15.002508] scsi 0:0:0:49476: Well-known LUN    SKhynix  H28S7Q302BMR     A002 PQ: 0 ANSI: 6
>> > [   15.015848] scsi 0:0:0:49456: Well-known LUN    SKhynix  H28S7Q302BMR     A002 PQ: 0 ANSI: 6
>> > [   15.031551] scsi 0:0:0:0: Direct-Access     SKhynix  H28S7Q302BMR     A002 PQ: 0 ANSI: 6
>> > [   15.046885] scsi 0:0:0:1: Direct-Access     SKhynix  H28S7Q302BMR     A002 PQ: 0 ANSI: 6
>> > [   15.047204] sd 0:0:0:0: [sda] 14145536 4096-byte logical blocks: (57.9 GB/54.0 GiB)
>> > [   15.047274] sd 0:0:0:0: [sda] Write Protect is off
>> > [   15.047281] sd 0:0:0:0: [sda] Mode Sense: 00 32 00 10
>> > [   15.047418] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
>> > [   15.047488] sd 0:0:0:0: [sda] Optimal transfer size 786432 bytes
>> > [   15.062041] scsi 0:0:0:2: Direct-Access     SKhynix  H28S7Q302BMR     A002 PQ: 0 ANSI: 6
>> > [   15.062347] sd 0:0:0:1: [sdb] 1024 4096-byte logical blocks: (4.19 MB/4.00 MiB)
>> > [   15.062414] sd 0:0:0:1: [sdb] Write Protect is off
>> > [   15.062418] sd 0:0:0:1: [sdb] Mode Sense: 00 32 00 10
>> > [   15.062522] sd 0:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
>> > [   15.062582] sd 0:0:0:1: [sdb] Optimal transfer size 786432 bytes
>> > [   15.074503] scsi 0:0:0:3: Direct-Access     SKhynix  H28S7Q302BMR     A002 PQ: 0 ANSI: 6
>> > [   15.075092] sd 0:0:0:2: [sdc] 1024 4096-byte logical blocks: (4.19 MB/4.00 MiB)
>> > [   15.075161] sd 0:0:0:2: [sdc] Write Protect is off
>> > [   15.075166] sd 0:0:0:2: [sdc] Mode Sense: 00 32 00 10
>> > [   15.075292] sd 0:0:0:2: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
>> > [   15.075358] sd 0:0:0:2: [sdc] Optimal transfer size 786432 bytes
>> > [   15.093820] ufshcd-qcom 1d84000.ufshc: dme-set: attr-id 0x1583 val 0x0 failed 0 retries
>> > [   15.199208] ufshcd-qcom 1d84000.ufshc: dme-set: attr-id 0x1568 val 0x0 failed 0 retries
>> > [   15.400514] ufshcd-qcom 1d84000.ufshc: __ufshcd_issue_tm_cmd: task management cmd 0x80 timed-out
>> > [   15.409439] ufshcd-qcom 1d84000.ufshc: ufshcd_try_to_abort_task: no response from device. tag = 10, err -110
>> > [   15.479763] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   15.546285] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   15.612688] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   15.679057] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   15.685187] ufshcd-qcom 1d84000.ufshc: ufshcd_host_reset_and_restore: Host init failed -5
>> > [   15.754125] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   15.820405] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   15.886519] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   15.952976] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   15.959119] ufshcd-qcom 1d84000.ufshc: ufshcd_host_reset_and_restore: Host init failed -5
>> > [   16.027951] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   16.094499] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   16.161005] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   16.276723] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   16.282756] ufshcd-qcom 1d84000.ufshc: ufshcd_host_reset_and_restore: Host init failed -5
>> > [   16.360239] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   16.427425] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   16.497737] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   16.566869] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   16.572939] ufshcd-qcom 1d84000.ufshc: ufshcd_host_reset_and_restore: Host init failed -5
>> > [   16.642243] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   16.708590] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   16.774868] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   16.841364] ufshcd-qcom 1d84000.ufshc: Controller enable failed
>> > [   16.847492] ufshcd-qcom 1d84000.ufshc: ufshcd_host_reset_and_restore: Host init failed -5
>> > [   16.855938] ufshcd-qcom 1d84000.ufshc: ufshcd_err_handler: reset and restore failed with err -5
>> > [   16.936724] sd 0:0:0:2: [sdc] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=1s
>> > [   16.946151] sd 0:0:0:2: [sdc] tag#12 CDB: opcode=0x28 28 00 00 00 00 00 00 00 01 00
>> > [   16.953950] blk_update_request: I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
>> > [   16.963987] Buffer I/O error on dev sdc, logical block 0, async page read
>> > [   16.971263] sd 0:0:0:1: [sdb] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=1s
>> > [   16.980668] sd 0:0:0:1: [sdb] tag#13 CDB: opcode=0x28 28 00 00 00 00 00 00 00 01 00
>> > [   16.988457] blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
>> > [   16.998455] Buffer I/O error on dev sdb, logical block 0, async page read
>> > [   17.005438] sd 0:0:0:0: [sda] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=1s
>> > [   17.014887] sd 0:0:0:0: [sda] tag#15 CDB: opcode=0x28 28 00 00 00 00 00 00 00 01 00
>> > [   17.022639] blk_update_request: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
>> > [   17.032581] Buffer I/O error on dev sda, logical block 0, async page read
>> > [   17.060604] sd 0:0:0:2: [sdc] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
>> > [   17.070024] sd 0:0:0:2: [sdc] tag#11 CDB: opcode=0x28 28 00 00 00 00 00 00 00 01 00
>> > [   17.077811] blk_update_request: I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
>> > [   17.087785] Buffer I/O error on dev sdc, logical block 0, async page read
>> > [   17.094762]  sdc: unable to read partition table
>> > [   17.121375] sd 0:0:0:0: [sda] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
>> > [   17.124811] sd 0:0:0:1: [sdb] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
>> > [   17.130915] sd 0:0:0:0: [sda] tag#13 CDB: opcode=0x28 28 00 00 00 00 00 00 00 01 00
>> > [   17.138281] sd 0:0:0:2: [sdc] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
>> > [   17.138351] sd 0:0:0:2: [sdc] tag#9 CDB: opcode=0x28 28 00 00 00 03 f0 00 00 01 00
>> > [   17.138361] blk_update_request: I/O error, dev sdc, sector 8064 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
>> > [   17.140305] sd 0:0:0:1: [sdb] tag#14 CDB: opcode=0x28 28 00 00 00 00 00 00 00 01 00
>> > [   17.148070] blk_update_request: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
>> > [   17.157308] blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
>> > [   17.164973] Buffer I/O error on dev sda, logical block 0, async page read
>> > [   17.175522] Buffer I/O error on dev sdb, logical block 0, async page read
>> > [   17.183484]  sda: unable to read partition table
>> > [   17.193379]  sdb: unable to read partition table
>> > [   17.245890] sd 0:0:0:0: [sda] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
>> > [   17.255444] sd 0:0:0:0: [sda] tag#16 CDB: opcode=0x28 28 00 00 d7 d7 f0 00 00 01 00
>> > [   17.262309] sd 0:0:0:2: [sdc] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
>> > [   17.263226] blk_update_request: I/O error, dev sda, sector 113164160 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
>> > [   17.267751] sd 0:0:0:1: [sdb] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
>> > [   17.267804] sd 0:0:0:1: [sdb] tag#14 CDB: opcode=0x28 28 00 00 00 03 f0 00 00 01 00
>> > [   17.267820] blk_update_request: I/O error, dev sdb, sector 8064 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
>> > [   17.272473] sd 0:0:0:2: [sdc] tag#9 CDB: opcode=0x28 28 00 00 00 03 f0 00 00 01 00
>> > [   17.272480] blk_update_request: I/O error, dev sdc, sector 8064 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
>> > [   17.328934] Buffer I/O error on dev sdc, logical block 1008, async page read
>> > [   17.336400] Buffer I/O error on dev sdb, logical block 1008, async page read
>> > [   17.344184] Buffer I/O error on dev sda, logical block 14145520, async page read
>> > [   17.356908] sd 0:0:0:3: [sdd] Read Capacity(16) failed: Result: hostbyte=0x07 driverbyte=0x00
>> > [   17.365890] sd 0:0:0:3: [sdd] Sense not available.
>> > [   17.504489] sd 0:0:0:1: [sdb] Read Capacity(16) failed: Result: hostbyte=0x07 driverbyte=0x00
>> > [   17.513199] sd 0:0:0:1: [sdb] Sense not available.
>> > [   17.548648] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x07 driverbyte=0x00
>> > [   17.548875] sd 0:0:0:2: [sdc] Read Capacity(16) failed: Result: hostbyte=0x07 driverbyte=0x00
>> > [   17.557365] sd 0:0:0:0: [sda] Sense not available.
>> > [   17.570888] sd 0:0:0:2: [sdc] Sense not available.
>> > [   17.612557] sd 0:0:0:3: [sdd] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=0x00
>> > [   17.621302] sd 0:0:0:3: [sdd] Sense not available.
>> > [   17.720470] sd 0:0:0:3: [sdd] 0 512-byte logical blocks: (0 B/0 B)
>> > [   17.726895] sd 0:0:0:3: [sdd] 0-byte physical blocks
>> > [   17.756442] sd 0:0:0:1: [sdb] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=0x00
>> > [   17.765154] sd 0:0:0:1: [sdb] Sense not available.
>> > [   17.796694] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=0x00
>> > [   17.805550] sd 0:0:0:0: [sda] Sense not available.
>> > [   17.812461] sd 0:0:0:2: [sdc] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=0x00
>> > [   17.812479] sd 0:0:0:3: [sdd] Write Protect is off
>> > [   17.821124] sd 0:0:0:2: [sdc] Sense not available.
>> > [   17.831183] sd 0:0:0:3: [sdd] Mode Sense: 00 00 00 00
>> > [   17.916633] sd 0:0:0:3: [sdd] Asking for cache data failed
>> > [   17.922246] sd 0:0:0:3: [sdd] Assuming drive cache: write through
>> > [   17.928661] sd 0:0:0:1: [sdb] 0 4096-byte logical blocks: (0 B/0 B)
>> > [   17.964461] sd 0:0:0:2: [sdc] 0 4096-byte logical blocks: (0 B/0 B)
>> > [   17.968389] sd 0:0:0:0: [sda] 0 4096-byte logical blocks: (0 B/0 B)
>> > [   18.052598] sd 0:0:0:2: [sdc] Write Protect is on
>> > [   18.057654] sd 0:0:0:2: [sdc] Mode Sense: 00 01 1c 88
>> > [   18.140750] Buffer I/O error on dev sdc, logical block 1008, async page read
>> > [   18.148120] sdc: detected capacity change from 0 to 8192
>> > [   18.148436] sdb: detected capacity change from 0 to 8192
>> > [   18.153573] sd 0:0:0:2: [sdc] Attached SCSI disk
>> > [   18.161640] sd 0:0:0:1: [sdb] Attached SCSI disk
>> > [   18.272458] sda: detected capacity change from 0 to 113164288
>> > [   18.278440] sd 0:0:0:0: [sda] Attached SCSI disk
>> > [   18.336456] sd 0:0:0:3: [sdd] Read Capacity(16) failed: Result: hostbyte=0x07 driverbyte=0x00
>> > [   18.345155] sd 0:0:0:3: [sdd] Sense not available.
>> > [   18.437277] ufshcd-qcom 1d84000.ufshc: __ufshcd_query_descriptor: opcode 0x01 for idn 2 failed, index 4, err = -11
>> > [   18.588427] sd 0:0:0:3: [sdd] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=0x00
>> > [   18.597131] sd 0:0:0:3: [sdd] Sense not available.
>> > [   18.984425] sd 0:0:0:3: [sdd] Attached SCSI disk
>> > [   19.973658] ufshcd-qcom 1d84000.ufshc: __ufshcd_query_descriptor: opcode 0x01 for idn 2 failed, index 4, err = -11
>> > [   21.508706] ufshcd-qcom 1d84000.ufshc: __ufshcd_query_descriptor: opcode 0x01 for idn 2 failed, index 4, err = -11
>> > [   21.519204] ufshcd-qcom 1d84000.ufshc: ufshcd_read_desc_param: Failed reading descriptor. desc_id 2, desc_index 4, param_offset 6, ret -11
>> > [   21.577216] sd 0:0:0:0: Unexpected response from lun 4 while scanning, scan aborted
>> > [   22.181387] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   23.007510] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   23.076607] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   23.524907] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   24.133026] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   24.421140] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   24.549023] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   25.156985] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   25.253136] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   26.180950] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   26.597019] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   27.204984] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   27.493135] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   27.621022] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   28.228982] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   28.325152] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   29.252956] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   29.669021] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   30.276984] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   30.565140] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   30.693023] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   31.300983] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   31.397134] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   32.324954] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   32.741021] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   33.348985] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   33.637132] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   33.765258] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   34.372980] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   34.469142] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   35.396957] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   35.813018] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   36.420980] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   36.709133] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   36.837021] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   37.444979] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   37.541138] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   38.468955] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   38.885021] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   39.492983] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   39.781134] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   39.909017] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   40.516977] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   40.613135] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   41.540956] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   41.957016] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   42.564987] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   42.853130] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   42.981020] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   43.588980] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   43.685135] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   44.612954] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   45.029014] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   45.636979] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   45.925137] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   46.053022] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   46.660983] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> > [   46.757132] devfreq 1d84000.ufshc: dvfs failed with (-16) error
>> >
>> > Is this something that you've seen?
>> >
>> > Regards,
>> > Bjorn
>> 
>> Hi Bjorn
>> Nope, I've not seen this issue yet.
>> Looks like the commands are timing out, could be clocks/power, 
>> perhaps?
>> 
> 
> I've finally concluded that reverting 4543d9d78227 ("scsi: ufs: 
> Refactor
> ufshcd_init/exit_clk_scaling/gating()") fixes the problem and allow at
> least SDM845 to boot again (haven't yet tested the others).
> 
> I've not yet figured out why it's causing the regression.
> 

Hi Bjorn,

Thanks for pointing it out. I have sent out the fix - my mistake that I
removed two lines by mistake in commit 4543d9d78227. When I tested 
commit
4543d9d78227, I found that the two lines were missing, but I forgot to
add the two lines into 4543d9d78227 when I sent it out.

Regards,
Can Guo.

> Regards,
> Bjorn

  reply	other threads:[~2021-01-28  2:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27  4:00 [RFC PATCH v1 0/2] Fix deadlock in ufs Asutosh Das
2021-01-27  4:00 ` [RFC PATCH v1 1/2] block: bsg: resume scsi device before accessing Asutosh Das
2021-01-27  7:09   ` Avri Altman
2021-01-27  7:59     ` Can Guo
2021-01-27  8:53       ` Can Guo
2021-02-07  2:23   ` Bart Van Assche
2021-01-27  4:00 ` [RFC PATCH v1 2/2] scsi: ufs: Fix deadlock while suspending ufs host Asutosh Das
2021-01-27 15:22 ` [RFC PATCH v1 0/2] Fix deadlock in ufs Bjorn Andersson
2021-01-27 16:16   ` Asutosh Das
2021-01-27 19:36     ` Bjorn Andersson
2021-01-28  2:47       ` Can Guo [this message]
2021-01-28  3:26 ` [RFC PATCH v2 " Asutosh Das
2021-01-28  3:26 ` [RFC PATCH v2 1/2] block: bsg: resume platform device before accessing Asutosh Das
2021-01-28  3:26   ` [RFC PATCH v2 2/2] scsi: ufs: Fix deadlock while suspending ufs host Asutosh Das
2021-01-28 12:21     ` Avri Altman
2021-01-28 16:39       ` Asutosh Das
2021-01-28  9:33 ` [RFC PATCH v2 0/2] Fix deadlock in ufs Avri Altman
2021-01-28 17:19   ` Asutosh Das
2021-02-01 20:11 ` Asutosh Das (asd)
2021-02-01 20:27   ` Bart Van Assche
2021-02-01 21:48   ` Alan Stern
2021-02-02 20:52     ` Asutosh Das
2021-02-02 22:05       ` Alan Stern
2021-02-04  0:13         ` Asutosh Das
2021-02-04 19:48           ` Alan Stern
2021-02-04 21:14             ` Asutosh Das
2021-02-05  7:56               ` Avri Altman
2021-02-05 16:11                 ` Asutosh Das
2021-02-06  2:37                   ` Asutosh Das
2021-02-06 19:24                   ` Avri Altman
2021-02-08 16:24                     ` Asutosh Das

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49c894a55b56233814252bc59c24f7b4@codeaurora.org \
    --to=cang@codeaurora.org \
    --cc=asutoshd@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).