From: Greg KH <gregkh@linuxfoundation.org>
To: Patrik Nilsson <nipatriknilsson@gmail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>, linux-usb@vger.kernel.org
Subject: Re: high speed data to usb disk makes the kernel think that is has been unmounted
Date: Wed, 12 Aug 2020 08:14:51 +0200 [thread overview]
Message-ID: <20200812061451.GE1299081@kroah.com> (raw)
In-Reply-To: <ef2937d6-f8a8-fbc6-decd-eeb4af94e863@gmail.com>
On Tue, Aug 11, 2020 at 11:14:09PM +0200, Patrik Nilsson wrote:
>
> On 11/08/2020 21:31, Alan Stern wrote:
> > 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.
> I'm compiling the latest kernel to supply the kernel logs when done testing.
> It takes a while.
'make localmodconfig' is your friend. Should make a kernel that builds
in 5-10 minutes at most depending on your system.
thanks,
greg k-h
next prev parent reply other threads:[~2020-08-12 6:14 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
2020-08-11 21:14 ` Patrik Nilsson
2020-08-12 6:14 ` Greg KH [this message]
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=20200812061451.GE1299081@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=nipatriknilsson@gmail.com \
--cc=stern@rowland.harvard.edu \
/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