From: Alan Stern <stern@rowland.harvard.edu>
To: James Dutton <james.dutton@gmail.com>
Cc: USB mailing list <linux-usb@vger.kernel.org>
Subject: Re: usb disk drive disconnect making readonly
Date: Fri, 6 May 2022 10:35:10 -0400 [thread overview]
Message-ID: <YnUyHu7o7OPawXZG@rowland.harvard.edu> (raw)
In-Reply-To: <CAAMvbhHsUL6gQ365wZW4J8RCbnhwEt0RDUc5NA4=RSS2bjnK_A@mail.gmail.com>
Please use Reply-To-All so that your messages get sent to the mailing
list as well as to me.
On Thu, May 05, 2022 at 11:32:14PM +0100, James Dutton wrote:
> On Thu, 5 May 2022 at 15:16, Alan Stern <stern@rowland.harvard.edu> wrote:
>
> >
> > There is no way to know what is going on unless you provide a lot more
> > information. The dmesg log showing what happens during one of these
> > disconnect/reconnect events would be a good start (although it probably
> > won't be enough).
> >
> > Alan Stern
>
> Hi Alan,
>
> Here are some log messages. I suspect the storage device is going into
> some sort of sleep mode, and the kernel does not seem to be able to
> wake it up again.
> The device is a USB to NVME adapter. Using the chip: Realtek RTL9210
> The log is perfectly normal up until the 2nd line below onwards:
...
That log isn't sufficient.
It would be a big help if instead of sending your kernel log file, you send
the output of the "dmesg" program. And don't send just the part
starting where the problem begins; we need to see what happened before
that as well.
In addition, it would help if you enable USB debugging before the
problem occurs:
echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control
Alan Stern
next prev parent reply other threads:[~2022-05-06 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 20:16 usb disk drive disconnect making readonly James Dutton
2022-05-05 14:16 ` Alan Stern
[not found] ` <CAAMvbhHsUL6gQ365wZW4J8RCbnhwEt0RDUc5NA4=RSS2bjnK_A@mail.gmail.com>
2022-05-06 14:35 ` Alan Stern [this message]
2022-05-06 20:48 ` James Dutton
2022-05-07 15:39 ` 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=YnUyHu7o7OPawXZG@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=james.dutton@gmail.com \
--cc=linux-usb@vger.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