[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6d95ada-8988-f4ea-6eb3-ea2f3ac2362d@kernel.org>
Date: Wed, 14 Jun 2023 16:22:15 +0900
From: Damien Le Moal <dlemoal@...nel.org>
To: Kai-Heng Feng <kai.heng.feng@...onical.com>
Cc: Joe Breuer <linux-kernel@...reuer.net>,
Bart Van Assche <bvanassche@....org>,
Bagas Sanjaya <bagasdotme@...il.com>,
Pavel Machek <pavel@....cz>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <len.brown@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Kees Cook <keescook@...omium.org>,
Tony Luck <tony.luck@...el.com>,
"Guilherme G. Piccoli" <gpiccoli@...lia.com>,
Thorsten Leemhuis <linux@...mhuis.info>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Phillip Potter <phil@...lpotter.co.uk>,
Linux Power Management <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Hardening <linux-hardening@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>,
Linux SCSI <linux-scsi@...r.kernel.org>,
Alan Stern <stern@...land.harvard.edu>,
Dan Williams <dan.j.williams@...el.com>,
Hannes Reinecke <hare@...e.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Martin Kepplinger <martin.kepplinger@...i.sm>
Subject: Re: Fwd: Waking up from resume locks up on sr device
On 6/14/23 14:37, Kai-Heng Feng wrote:
> On Wed, Jun 14, 2023 at 12:49 PM Damien Le Moal <dlemoal@...nel.org> wrote:
>>
>> On 6/11/23 18:05, Joe Breuer wrote:
>>> I'm the reporter of this issue.
>>>
>>> I just tried this patch against 6.3.4, and it completely fixes my
>>> suspend/resume issue.
>>>
>>> The optical drive stays usable after resume, even suspending/resuming
>>> during playback of CDDA content works flawlessly and playback resumes
>>> seamlessly after system resume.
>>>
>>> So, from my perspective: Good one!
>>
>> In place of Bart's fix, could you please try this patch ?
>
> Issue still persists at my end, when /sys/power/pm_async is 0.
> device_pm_wait_for_dev() in its current form is only usable for async case.
Can you try this horrible hack to see if it works:
diff --git a/drivers/ata/libata-scsi.c b/drivers/ata/libata-scsi.c
index 9e79998e3958..87c093775a90 100644
--- a/drivers/ata/libata-scsi.c
+++ b/drivers/ata/libata-scsi.c
@@ -4590,6 +4590,7 @@ void ata_scsi_dev_rescan(struct work_struct *work)
ata_for_each_link(link, ap, EDGE) {
ata_for_each_dev(dev, link, ENABLED) {
struct scsi_device *sdev = dev->sdev;
+ struct device *sgdev;
if (!sdev)
continue;
@@ -4597,7 +4598,10 @@ void ata_scsi_dev_rescan(struct work_struct *work)
continue;
spin_unlock_irqrestore(ap->lock, flags);
- scsi_rescan_device(&(sdev->sdev_gendev));
+
+ sgdev = &sdev->sdev_gendev;
+ wait_for_completion(&sgdev->power.completion);
+ scsi_rescan_device(sgdev);
scsi_device_put(sdev);
spin_lock_irqsave(ap->lock, flags);
}
>
> Kai-Heng
>
>>
>> diff --git a/drivers/ata/libata-eh.c b/drivers/ata/libata-eh.c
>> index b80e68000dd3..a81eb4f882ab 100644
>> --- a/drivers/ata/libata-eh.c
>> +++ b/drivers/ata/libata-eh.c
>> @@ -4006,9 +4006,32 @@ static void ata_eh_handle_port_resume(struct
>> ata_port *ap)
>> /* tell ACPI that we're resuming */
>> ata_acpi_on_resume(ap);
>>
>> - /* update the flags */
>> spin_lock_irqsave(ap->lock, flags);
>> +
>> + /* Update the flags */
>> ap->pflags &= ~(ATA_PFLAG_PM_PENDING | ATA_PFLAG_SUSPENDED);
>> +
>> + /*
>> + * Resuming the port will trigger a rescan of the ATA device(s)
>> + * connected to it. Before scheduling the rescan, make sure that
>> + * the associated scsi device(s) are fully resumed as well.
>> + */
>> + ata_for_each_link(link, ap, HOST_FIRST) {
>> + ata_for_each_dev(dev, link, ENABLED) {
>> + struct scsi_device *sdev = dev->sdev;
>> +
>> + if (!sdev)
>> + continue;
>> + if (scsi_device_get(sdev))
>> + continue;
>> +
>> + spin_unlock_irqrestore(ap->lock, flags);
>> + device_pm_wait_for_dev(&ap->tdev,
>> + &sdev->sdev_gendev);
>> + scsi_device_put(sdev);
>> + spin_lock_irqsave(ap->lock, flags);
>> + }
>> + }
>> spin_unlock_irqrestore(ap->lock, flags);
>> }
>> #endif /* CONFIG_PM */
>>
>> Thanks !
>>
>> --
>> Damien Le Moal
>> Western Digital Research
>>
--
Damien Le Moal
Western Digital Research
Powered by blists - more mailing lists