From: Oliver Neukum <oneukum@suse.com>
To: Tushar Nimkar <tnimkar@codeaurora.org>, linux-usb-owner@vger.kernel.org
Cc: TusharNimkar <tushar.nims@gmail.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Greg KH <gregkh@linuxfoundation.org>,
AlanStern <stern@rowland.harvard.edu>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Fwd: usb: uas: device reset most the time while enumeration- usb3.0
Date: Mon, 04 Jun 2018 16:27:25 +0200 [thread overview]
Message-ID: <1528122445.4851.3.camel@suse.com> (raw)
Am Dienstag, den 29.05.2018, 14:32 +0530 schrieb Tushar Nimkar:
> Hi,
>
> On 2018-05-28 18:12, Oliver Neukum wrote:
> > Am Donnerstag, den 24.05.2018, 20:13 +0530 schrieb Tushar Nimkar:
> > > We have built SCSI as module will it cause any problem to enable
> > > CONFIG_SCSI_SCAN_ASYNC ?
> >
> > No, that should work. But the failure is bizzare. You say
>
> yes there is no problem! I have run some test over night.
> > synchronous scanning fails, but async scan works?
>
> yes!
Odd. Extremely odd. Does this show on all architectures?
I am asking because that is the crucial question.
I see two possibilities
1. the sync probing code has a bug that shows only on some
architectures
2. architectures were a coincidence - the drive is broken
We absolutely need to know what is happening.
I am afraid this will have to be tested on another architecture.
Regards
Oliver
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-06-04 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 14:27 Oliver Neukum [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-05 12:48 Fwd: usb: uas: device reset most the time while enumeration- usb3.0 Tushar Nimkar
2018-05-29 9:02 Tushar Nimkar
2018-05-28 12:42 Oliver Neukum
2018-05-24 14:43 Tushar Nimkar
2018-05-17 13:34 Oliver Neukum
2018-05-17 6:59 Tushar Nimkar
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=1528122445.4851.3.camel@suse.com \
--to=oneukum@suse.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb-owner@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=stern@rowland.harvard.edu \
--cc=tnimkar@codeaurora.org \
--cc=tushar.nims@gmail.com \
/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).