From: Andrea Vai <andrea.vai@unipv.it>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <gregkh@linuxfoundation.org>, linux-usb@vger.kernel.org
Subject: Re: Slow I/O on USB media
Date: Mon, 17 Jun 2019 18:34:23 +0200 [thread overview]
Message-ID: <6ff3332b940f02d988d9bc578c1c293e8424e439.camel@unipv.it> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1906171202580.1738-100000@iolanthe.rowland.org>
Il giorno lun, 17/06/2019 alle 12.14 -0400, Alan Stern ha scritto:
> On Mon, 17 Jun 2019, Andrea Vai wrote:
>
> > [...]
> >
> > That happened ALL times, so I never encountered a kernel that made
> me
> > say "git bisect good".
>
> Really? That strongly suggests that the 4.20 kernel also should
> have
> been marked bad. Did you really test it exactly the same way as all
> the others? That is, did you go through the entire procedure
> starting
> with "git checkout v4.20", then running the build script, then the
> reboot and "uname -a", and then the test script?
well, honestly, no, because (sigh) I didn't know the "git checkout"
command, sorry. I started with building 4.20 from the source
downloaded with
wget https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/snapshot/linux-4.20.tar.gz
, then said "git bisect good v4.20".
Is this different from "git checkout v4.20"? I hope it is, so we have
found the mistake I have done.
> Or did you just run a few tests with the Fedora 4.20.13 kernel and
> assume that the results would be the same as those?
no, I am sure I have never used the Fedora kernel(s) during the last
bisect process.
>
> > [...]
>
> If _all_ the kernels you built and tested were bad then you
> probably
> did not start the bisection from the right commit.
so, I hope this is true :-)
>
> > By the way, I noticed an error ("Unexpected system error")
> reported
> > sometimes by the Fedora ABRT tool, that states "this is not a
> software
> > bug, the kernel log indicates it is a hardware error", or
> something
> > similar (sorry, at the moment I don't know exactly where to find
> it).
>
> Did you look in the kernel log?
Yes I did, but I didn't took care about it very much. I will do it
again, and report here, if as far as I understand you are saying that
it could be useful.
>
> > [...]
>
> Compare the mainstream 4.20 kernel with the Fedora 4.20.13 kernel.
> Also, maybe compare the mainstream 4.20.13 with Fedora's 4.20.13.
Sorry, what do you mean here by "compare"? And what is the
"mainstream"? If the mainstream is the one I got with wget, and if
"compare" means "see if they behave differently", so I have already
done it and they are both "good".
Thank you,
Andrea
next prev parent reply other threads:[~2019-06-17 16:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 13:18 Slow I/O on USB media Andrea Vai
2019-05-30 13:25 ` Greg KH
2019-06-03 11:13 ` Andrea Vai
2019-06-04 5:43 ` Greg KH
2019-06-04 7:26 ` Andrea Vai
2019-06-05 7:36 ` Andrea Vai
2019-06-05 14:26 ` Alan Stern
2019-06-05 15:46 ` Andrea Vai
2019-06-05 16:11 ` Alan Stern
2019-06-05 14:55 ` Greg KH
[not found] ` <0c2adde7154b0a6c8b2ad7fc5258916731b78775.camel@unipv.it>
2019-06-05 16:23 ` Andrea Vai
2019-06-05 17:39 ` Greg KH
2019-06-06 8:41 ` Andrea Vai
2019-06-06 9:03 ` Andrea Vai
2019-06-06 14:00 ` Andrea Vai
2019-06-06 14:30 ` Alan Stern
2019-06-06 14:47 ` Greg KH
2019-06-07 7:59 ` Andrea Vai
2019-06-08 7:43 ` Andrea Vai
2019-06-08 9:29 ` Andrea Vai
2019-06-10 14:38 ` Greg KH
2019-06-11 6:48 ` Andrea Vai
2019-06-10 14:40 ` Alan Stern
2019-06-10 14:55 ` Andrea Vai
2019-06-10 16:20 ` Alan Stern
2019-06-17 15:52 ` Andrea Vai
2019-06-17 16:14 ` Alan Stern
2019-06-17 16:34 ` Andrea Vai [this message]
2019-06-17 17:28 ` Alan Stern
2019-07-01 17:52 ` Andrea Vai
2019-07-01 18:57 ` Alan Stern
2019-06-10 14:37 ` Greg KH
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=6ff3332b940f02d988d9bc578c1c293e8424e439.camel@unipv.it \
--to=andrea.vai@unipv.it \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).