From: Alan Stern <stern@rowland.harvard.edu>
To: Patrik Nilsson <nipatriknilsson@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>, linux-usb@vger.kernel.org
Subject: Re: high speed data to usb disk makes the kernel think that is has been unmounted
Date: Tue, 11 Aug 2020 15:31:50 -0400 [thread overview]
Message-ID: <20200811193150.GA344152@rowland.harvard.edu> (raw)
In-Reply-To: <47a5804c-835a-f1a2-abce-50b3531f2556@gmail.com>
On Tue, Aug 11, 2020 at 08:34:53PM +0200, Patrik Nilsson wrote:
> Hi Greg,
> > Can you provide kernel logs? Odds are the disk disconnects itself as it
> > takes too much power or something.
> udev-kernel logs can be found:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886172
The bug report doesn't seem to contain any dmesg kernel logs showing
what happens when the problem occurs.
Also, the bug report indicates that you started to do a bisection
looking for the kernel version where the problem first appears, but
there's no mention of the final result.
The bug report also indicates that one of your tests involves copying
/dev/zero to a mounted disk device! That is highly likely to crash the
kernel regardless of what the hardware does. What happens if you
unmount the disk before running the test?
Alan Stern
next prev parent reply other threads:[~2020-08-11 19:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 17:19 high speed data to usb disk makes the kernel think that is has been unmounted Patrik Nilsson
2020-08-11 17:56 ` Greg KH
2020-08-11 18:34 ` Patrik Nilsson
2020-08-11 18:39 ` Greg KH
2020-08-11 19:31 ` Alan Stern [this message]
2020-08-11 21:14 ` Patrik Nilsson
2020-08-12 6:14 ` Greg KH
2020-08-16 15:31 ` Patrik Nilsson
2020-08-18 8:55 ` Greg KH
2020-08-18 18:22 ` Patrik Nilsson
2020-08-18 18:34 ` Alan Stern
2020-09-15 16:43 ` Patrik Nilsson
2020-09-15 18:24 ` Alan Stern
2020-12-05 11:49 ` Patrik Nilsson
2020-12-05 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=20200811193150.GA344152@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=nipatriknilsson@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