[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <176524933116.418581.12440014725918073406.b4-ty@oracle.com>
Date: Mon, 8 Dec 2025 22:21:06 -0500
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: Po-Wen Kao <powenkao@...gle.com>
Cc: "Martin K . Petersen" <martin.petersen@...cle.com>,
Alim Akhtar <alim.akhtar@...sung.com>,
Avri Altman <avri.altman@....com>,
Bart Van Assche <bvanassche@....org>,
"James E.J. Bottomley" <James.Bottomley@...senPartnership.com>,
Peter Wang <peter.wang@...iatek.com>, Bean Huo <beanhuo@...ron.com>,
Manivannan Sadhasivam <mani@...nel.org>,
"Bao D. Nguyen" <quic_nguyenb@...cinc.com>,
Adrian Hunter <adrian.hunter@...el.com>,
"open list:UNIVERSAL FLASH STORAGE HOST CONTROLLER DRIVER" <linux-scsi@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] scsi: ufs: core: Fix EH failure after wlun resume error
On Wed, 12 Nov 2025 06:32:02 +0000, Po-Wen Kao wrote:
> When a W-LUN resume fails, its parent devices in the SCSI hierarchy,
> including the scsi_target, may be runtime suspended. Subsequently, the
> error handler in ufshcd_recover_pm_error() fails to set the W-LUN
> device back to active because the parent target is not active.
> This results in the following errors:
>
> google-ufshcd 3c2d0000.ufs: ufshcd_err_handler started; HBA state eh_fatal; ...
> ufs_device_wlun 0:0:0:49488: START_STOP failed for power mode: 1, result 40000
> ufs_device_wlun 0:0:0:49488: ufshcd_wl_runtime_resume failed: -5
> ...
> ufs_device_wlun 0:0:0:49488: runtime PM trying to activate child device 0:0:0:49488 but parent (target0:0:0) is not active
>
> [...]
Applied to 6.19/scsi-queue, thanks!
[1/1] scsi: ufs: core: Fix EH failure after wlun resume error
https://git.kernel.org/mkp/scsi/c/b4bb6daf4ac4
--
Martin K. Petersen
Powered by blists - more mailing lists