All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zebediah Figura <zfigura@codeweavers.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	usb-storage@lists.one-eyed-alien.net, linux-usb@vger.kernel.org
Subject: Re: Bug 207877: ASMedia drive (174c:55aa) hangs in ioctl CDROM_DRIVE_STATUS when mounting a DVD
Date: Thu, 28 May 2020 11:21:08 -0500	[thread overview]
Message-ID: <232b68f8-9a5c-89fd-2e12-bf63f49dbe38@codeweavers.com> (raw)
In-Reply-To: <20200528160420.GA14188@rowland.harvard.edu>

On 5/28/20 11:04 AM, Alan Stern wrote:
> On Thu, May 28, 2020 at 10:02:07AM -0500, Zebediah Figura wrote:
>> On 5/28/20 2:54 AM, Greg KH wrote:
>>> On Wed, May 27, 2020 at 11:23:13PM -0500, Zebediah Figura wrote:
>>>> Hello all,
>>>>
>>>> I was asked to report this bug here. There's more details in the bug report,
>>>> but it's been proposed that there's a deadlock between device_reset() in
>>>> scsiglue.c and usb_stor_control_thread().
>>>
>>> What bug report where?  Can you provide a link and the details here in
>>> the email?
>>
>> Oops, meant to link it and forgot. Sorry about that.
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=207877
> 
> This doesn't look like a deadlock to me, at least, not a deadlock
> involving the device reset code.
> 
> Your next step should be to collect a usbmon trace showing what happens
> when the problem occurs.  See the instructions in
> Documentation/usb/usbmon.rst.

Thanks, I've attached a usbmon trace to the bug. It seems the kernel 
submits a bulk input transfer that never receives a response. I hope my 
drive isn't broken...

  reply	other threads:[~2020-05-28 16:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28  4:23 Bug 207877: ASMedia drive (174c:55aa) hangs in ioctl CDROM_DRIVE_STATUS when mounting a DVD Zebediah Figura
2020-05-28  7:54 ` Greg KH
2020-05-28 15:02   ` Zebediah Figura
2020-05-28 16:04     ` Alan Stern
2020-05-28 16:21       ` Zebediah Figura [this message]
2020-05-28 17:05         ` Alan Stern
2020-05-28 19:27           ` Zebediah Figura
2020-05-30  1:03             ` Alan Stern

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=232b68f8-9a5c-89fd-2e12-bf63f49dbe38@codeweavers.com \
    --to=zfigura@codeweavers.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=usb-storage@lists.one-eyed-alien.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.