All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Vai <andrea.vai@unipv.it>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: Slow I/O on USB media
Date: Wed, 05 Jun 2019 09:36:04 +0200	[thread overview]
Message-ID: <9b013238be4e3c63e33181a954d1ecc3287d22e4.camel@unipv.it> (raw)
In-Reply-To: <20190604054300.GE1588@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 780 bytes --]

Hi,
Il giorno mar, 04/06/2019 alle 07.43 +0200, Greg KH ha scritto:
> On Mon, Jun 03, 2019 at 01:13:48PM +0200, Andrea Vai wrote:
> > Il giorno gio, 30/05/2019 alle 06.25 -0700, Greg KH ha scritto:
> > > [...]
> > Hi,
> > 
> > > Any chance you can use 'git bisect' to find the offending
> commit?
> > Yes, I am doing it as I managed to build the kernel from source
> 
> Great!  What did you find?

# first bad commit: [534903d60376b4989b76ec445630aa10f2bc3043]
drm/atomic: Use explicit old crtc state in
drm_atomic_add_affected_planes()

By the way, as I am not expert, is there a way to double-check that I
bisected correctly? (such as, e.g., test with the version before this
one, and then with this commit applied?)

Attached: "git bisect log" output.

Thanks, and bye,
Andrea

[-- Attachment #2: bisectlog.txt --]
[-- Type: text/plain, Size: 3051 bytes --]

git bisect start
# bad: [cd6c84d8f0cdc911df435bb075ba22ce3c605b07] Linux 5.2-rc2
git bisect bad cd6c84d8f0cdc911df435bb075ba22ce3c605b07
# good: [8fe28cb58bcb235034b64cbbb7550a8a43fd88be] Linux 4.20
git bisect good 8fe28cb58bcb235034b64cbbb7550a8a43fd88be
# bad: [d72cb8c7d9dbd9ce820c80f3fddb56b296ba96fc] Merge tag 'riscv-for-linus-5.1-mw0' of git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux
git bisect bad d72cb8c7d9dbd9ce820c80f3fddb56b296ba96fc
# bad: [c9bef4a651769927445900564781a9c99fdf6258] Merge tag 'pinctrl-v4.21-1' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl
git bisect bad c9bef4a651769927445900564781a9c99fdf6258
# bad: [e0c38a4d1f196a4b17d2eba36afff8f656a4f1de] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next
git bisect bad e0c38a4d1f196a4b17d2eba36afff8f656a4f1de
# bad: [c2f1f3e0e17d94ab0c66d83e669492cb9e9a3698] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-next
git bisect bad c2f1f3e0e17d94ab0c66d83e669492cb9e9a3698
# bad: [b3cc2bfe7244e848f5e8caa77bbdc72c04abd17c] Merge tag 'i3c/for-4.21' of git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux
git bisect bad b3cc2bfe7244e848f5e8caa77bbdc72c04abd17c
# good: [2ac5e38ea4203852d6e99edd3cf11f044b0a409f] Merge drm/drm-next into drm-intel-next-queued
git bisect good 2ac5e38ea4203852d6e99edd3cf11f044b0a409f
# bad: [fb878d106b7738ae7cdb513f98876b22bd6a485f] Merge tag 'exynos-drm-next-for-v4.21' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-next
git bisect bad fb878d106b7738ae7cdb513f98876b22bd6a485f
# bad: [818182dd1097fdc492aaef9b08755ea13274352d] Merge tag 'imx-drm-next-2018-12-03' of git://git.pengutronix.de/git/pza/linux into drm-next
git bisect bad 818182dd1097fdc492aaef9b08755ea13274352d
# bad: [ae4ba1936ab97c6a2733a243370f303da3c11839] drm/sun4i: frontend: Determine input mode based on the number of planes
git bisect bad ae4ba1936ab97c6a2733a243370f303da3c11839
# bad: [b39b5394fabc79acbaafb26b777fd348c868bf7e] drm/gem: Add drm_gem_object_funcs
git bisect bad b39b5394fabc79acbaafb26b777fd348c868bf7e
# bad: [7db647aa8b134059c3b8f26b1dd2e1aa5b91e2ca] drm/meson: Add primary plane scaling
git bisect bad 7db647aa8b134059c3b8f26b1dd2e1aa5b91e2ca
# bad: [eb8dd3abeb4dffab6c373e87d09fc3b5858ac158] drm/vc4: Prefer PPF over TPZ when dst >= 2/3 src
git bisect bad eb8dd3abeb4dffab6c373e87d09fc3b5858ac158
# bad: [783195ec1cada862d54dee8f312a60bcbba5c0e4] drm/syncobj: disable the timeline UAPI for now v2
git bisect bad 783195ec1cada862d54dee8f312a60bcbba5c0e4
# bad: [b2432adf33e8c8eb81afaba3030f0ba0145ce7d4] drm/atomic: Use explicit old/new state in drm_atomic_crtc_check()
git bisect bad b2432adf33e8c8eb81afaba3030f0ba0145ce7d4
# bad: [534903d60376b4989b76ec445630aa10f2bc3043] drm/atomic: Use explicit old crtc state in drm_atomic_add_affected_planes()
git bisect bad 534903d60376b4989b76ec445630aa10f2bc3043
# first bad commit: [534903d60376b4989b76ec445630aa10f2bc3043] drm/atomic: Use explicit old crtc state in drm_atomic_add_affected_planes()

  parent reply	other threads:[~2019-06-05  7:36 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 [this message]
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
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=9b013238be4e3c63e33181a954d1ecc3287d22e4.camel@unipv.it \
    --to=andrea.vai@unipv.it \
    --cc=gregkh@linuxfoundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.