linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pedro Ribeiro <pedrib@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: xfs list <linux-xfs@vger.kernel.org>
Subject: Re: Bug when mounting XFS with external SATA drives in USB enclosures
Date: Sun, 24 Nov 2019 01:12:18 +0700	[thread overview]
Message-ID: <192321f0-f79d-8b2d-4bfc-9316ae6fa2e6@gmail.com> (raw)
In-Reply-To: <CAJCQCtSXhX8VFYwp9j7RXD3_CHPMC83D6W-mCS80byxmor1PCg@mail.gmail.com>


On 23/11/2019 23:56, Chris Murphy wrote:
> 
> What about checking for differences in kernel messages between the
> stripped down and stocked kernel, during device discovery. That is
> connect no drives, boot the stripped kernel with the problem, connect
> one of the problem USB devices, record the kernel messages that
> result. Repeat that with the stock Debian kernel that doesn't exhibit
> the bug.

I'm not sure if you received it in the first email, but I have a zipfile
with the dmesg output of both the Debian config and my own config, as
well as the configs themselves.

If for some reason the mailing list didn't process the attachment, you
can download it from here:
https://gofile.io/?c=6TaB3p

Not sure if there a way to enable more verbose output?

> 
> My guess is this is some obscure USB related bug. There are a ton of
> bugs with USB enclosure firmware, controllers, and drivers.
> 

Possibly, although it affects 3 different enclosures, so it should not
be something enclosure specific, but affect a common layer.


> Also, is this USB enclosure directly connected to the computer? Or to
> a powered hub? I have inordinate problems with USB enclosures directly
> connected to an Intel NUC, but when connected to a Dyconn USB hub with
> external power source, the problems all go away. And my understanding
> is the hub doesn't just act like a repeater. It pretty much rewrites
> the entire stream. So there's something screwy going on either with
> the Intel controller I have, or the USB-SATA bridge chip, that causes
> confusing that the hub eliminates.

All connected directly to the computer, two via USB-3, one via USB-C,
same errors.


> 

  reply	other threads:[~2019-11-23 18:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-23  3:21 Bug when mounting XFS with external SATA drives in USB enclosures Pedro Ribeiro
2019-11-23 16:56 ` Chris Murphy
2019-11-23 18:12   ` Pedro Ribeiro [this message]
2019-11-23 18:26 ` Eric Sandeen
2019-11-24  6:49   ` Pedro Ribeiro
2019-11-24 19:16     ` Eric Sandeen
2019-11-25  2:30       ` Pedro Ribeiro

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=192321f0-f79d-8b2d-4bfc-9316ae6fa2e6@gmail.com \
    --to=pedrib@gmail.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lists@colorremedies.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).