From: Brad Campbell <lists2009@fnarfbargle.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Saso Slavicic <saso.linux@astim.si>,
kvm@vger.kernel.org
Subject: Re: XP machine freeze
Date: Tue, 31 Mar 2015 08:27:45 +0800 [thread overview]
Message-ID: <5519EA01.4010102@fnarfbargle.com> (raw)
In-Reply-To: <5519BBF4.7080600@redhat.com>
On 31/03/15 05:11, Paolo Bonzini wrote:
>
>
> On 22/03/2015 16:31, Brad Campbell wrote:
>>
>>
>> No help I'm afraid, but at least I can conclusively say that 3.16 is
>> good, and 3.17 is bad.
>
> Can you try more specifically around the first KVM pull request? That
> would be between c9b88e958182 (presumed good) and 8533ce727188 (presumed
> bad)?
>
G'day Paolo,
I can and will. Right now I'm toward the end of the bisect run I
detailed in my previous e-mail, however disturbingly git bisect
visualize shows no kvm commits at all. I'm beginning to think that
something non-deterministic is just making this easier or harder to hit.
Bad kernels usually go bad in a day at most, good kernels I've been
leaving for up to 5 days.
Here's where the log is at right now. visualize shows 68 commits and I
can't see any of them being even remotely related to kvm.
brad@srv:/raid10/src/linux$ git bisect log
git bisect start
# good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16
git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6
# bad: [bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9] Linux 3.17
git bisect bad bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9
# good: [f2d7e4d4398092d14fb039cb4d38e502d3f019ee] checkpatch: add
fix_insert_line and fix_delete_line helpers
git bisect good f2d7e4d4398092d14fb039cb4d38e502d3f019ee
# good: [c309bfa9b481e7dbd3e1ab819271bf3009f44859] Merge tag
'for-linus-20140808' of git://git.infradead.org/linux-mtd
git bisect good c309bfa9b481e7dbd3e1ab819271bf3009f44859
# bad: [433ab34d26e29d0f036c3f514a09ae96f973d8c5] Merge
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
git bisect bad 433ab34d26e29d0f036c3f514a09ae96f973d8c5
# bad: [d27c0d90184a13e9e9f28c38e84f889a259f6b5f] Merge branch
'x86-efi-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
git bisect bad d27c0d90184a13e9e9f28c38e84f889a259f6b5f
# bad: [913847586290d5de22659e2a6195d91ff24d5aa6] Merge branch
'linux-3.17' of git://anongit.freedesktop.org/git/nouveau/linux-2.6
git bisect bad 913847586290d5de22659e2a6195d91ff24d5aa6
# good: [d1e458fe671baf1e60afafc88bda090202a412f1] svcrdma: remove
rdma_create_qp() failure recovery logic
git bisect good d1e458fe671baf1e60afafc88bda090202a412f1
# bad: [023f78b02c729070116fa3a7ebd4107a032d3f5c] Merge branch
'for-next' of git://git.samba.org/sfrench/cifs-2.6
git bisect bad 023f78b02c729070116fa3a7ebd4107a032d3f5c
# bad: [ad1f5caf34390bb20fdbb4eaf71b0494e89936f0] Merge branch 'fixes'
of git://ftp.arm.linux.org.uk/~rmk/linux-arm
git bisect bad ad1f5caf34390bb20fdbb4eaf71b0494e89936f0
If someone could give me some hard tests to do along the lines of what
Saso is up to I could probably get that done faster. With the right bad
kernel I can reproduce this lockup in a matter of hours.
Regards,
Brad
next prev parent reply other threads:[~2015-03-31 0:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 15:10 XP machine freeze Saso Slavicic
2015-03-19 0:51 ` Marcelo Tosatti
2015-03-30 16:19 ` Saso Slavicic
2015-03-22 15:31 ` Brad Campbell
2015-03-30 21:11 ` Paolo Bonzini
2015-03-31 0:27 ` Brad Campbell [this message]
2015-03-31 6:29 ` Saso Slavicic
2015-03-31 7:18 ` Brad Campbell
2015-03-31 8:56 ` Paolo Bonzini
2015-03-31 11:16 ` Brad Campbell
2015-03-31 11:23 ` Paolo Bonzini
2015-04-04 10:55 ` Brad Campbell
2015-04-13 4:07 ` Brad Campbell
2015-04-13 12:38 ` Paolo Bonzini
2015-04-13 12:45 ` Brad Campbell
2015-04-13 14:02 ` Paolo Bonzini
2015-04-13 14:25 ` Brad Campbell
2015-04-19 15:27 ` Brad Campbell
2015-04-19 15:48 ` Nadav Amit
2015-04-19 16:50 ` Brad Campbell
2015-04-19 17:16 ` Paolo Bonzini
2015-04-13 12:47 ` Saso Slavicic
2015-04-13 13:33 ` Radim Krčmář
2015-04-13 13:34 ` Nadav Amit
2015-04-13 14:01 ` Paolo Bonzini
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=5519EA01.4010102@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=saso.linux@astim.si \
/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.