linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jérôme Carretero" <cJ-ko@zougloub.eu>
To: Alan Stern <stern@rowland.harvard.edu>, Joe Perches <joe@perches.com>
Cc: Tejun Heo <tj@kernel.org>, Hans de Goede <hdegoede@redhat.com>,
	Jens <jens-bugzilla.kernel.org@spamfreemail.de>,
	Andrey Astafyev <1@246060.ru>, Oliver Neukum <oneukum@suse.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Seagate External SMR drive USB resets... why? / USB storage debugging
Date: Wed, 15 Nov 2017 18:27:08 -0500	[thread overview]
Message-ID: <20171115182708.25b97ebe@Vantage.cJ> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1711151656350.1363-100000@iolanthe.rowland.org>

On Wed, 15 Nov 2017 17:02:39 -0500 (EST)
Alan Stern <stern@rowland.harvard.edu> wrote:

> > > - It looks like (haven't tested it yet) the CONFIG_DYNAMIC_DEBUG
> > > isn't used with the USB mass storage debugging infrastructure,
> > > please confirm? If unused, are we interested to have a patch that
> > > would go back to regular pr_debug() that can work with dynamic
> > > debugging?  
> 
> dev_dbg() please, not pr_debug().  But yes, that would be worthwhile.

Yes obviously.

Adding Joe Perches to the loop as he did a refactor of USB mass storage
a while ago.


> Note, however, that usb-storage debugging is meant only for debugging
> problems in the usb-storage driver itself, not for debugging problems
> in attached devices.  We use usbmon or wireshark for the latter.

OK but I find that a "reset" message without any reason is not
as helpful as it could have been. At the minimum I'll try to scratch my
own itch and see if I can go at the bottom of my issue.


Regards,

-- 
Jérôme

  parent reply	other threads:[~2017-11-15 23:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 15:13 [PATCH] uas: Add US_FL_NO_ATA_1X quirk for one more Seagate device Hans de Goede
2017-11-12 21:42 ` Jérôme Carretero
     [not found]   ` <20171112164234.48b5185c-WI5o+PA4G9BYumZHjSPV5A@public.gmane.org>
2017-11-13  4:01     ` Andrey Astafyev
2017-11-13  6:14       ` Jérôme Carretero
2017-11-13  6:16         ` Andrey Astafyev
2017-11-13  7:14           ` Jérôme Carretero
     [not found]         ` <20171113011438.458369bf-WI5o+PA4G9BYumZHjSPV5A@public.gmane.org>
2017-11-13  9:04           ` Hans de Goede
     [not found]             ` <3d276729-63f7-9727-4a22-55849712439c-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-13 17:38               ` Jérôme Carretero
     [not found]                 ` <20171113123814.4e70a498-WI5o+PA4G9BYumZHjSPV5A@public.gmane.org>
2017-11-15 21:43                   ` Seagate External SMR drive USB resets (was: Re: [PATCH] uas: Add US_FL_NO_ATA_1X quirk for one more Seagate device) Jérôme Carretero
     [not found]                     ` <20171115164314.74ce972f-WI5o+PA4G9BYumZHjSPV5A@public.gmane.org>
2017-11-15 21:49                       ` Jérôme Carretero
     [not found]                         ` <20171115164902.00d1330d-WI5o+PA4G9BYumZHjSPV5A@public.gmane.org>
2017-11-15 22:02                           ` Alan Stern
2017-11-15 22:40                             ` James Bottomley
2017-11-15 23:17                               ` Jérôme Carretero
2017-11-16  4:21                                 ` Seagate External SMR drive USB resets (XHCI transfer error, not timeout) Jérôme Carretero
     [not found]                                   ` <20171115232129.102a1122-WI5o+PA4G9BYumZHjSPV5A@public.gmane.org>
2017-11-16 19:42                                     ` Alan Stern
2017-11-17 22:19                                       ` Jérôme Carretero
2017-11-18 16:57                                         ` Alan Stern
2017-11-15 23:27                             ` Jérôme Carretero [this message]
     [not found]                               ` <20171115182708.25b97ebe-WI5o+PA4G9BYumZHjSPV5A@public.gmane.org>
2017-11-15 23:40                                 ` Seagate External SMR drive USB resets... why? / USB storage debugging Bart Van Assche

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=20171115182708.25b97ebe@Vantage.cJ \
    --to=cj-ko@zougloub.eu \
    --cc=1@246060.ru \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=jens-bugzilla.kernel.org@spamfreemail.de \
    --cc=joe@perches.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=stern@rowland.harvard.edu \
    --cc=tj@kernel.org \
    /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).