From: Avi Kivity <avi@redhat.com>
To: BuraphaLinux Server <buraphalinuxserver@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: random crash in post_kvm_run()
Date: Sat, 03 Jul 2010 13:28:26 +0300 [thread overview]
Message-ID: <4C2F10CA.6020907@redhat.com> (raw)
In-Reply-To: <AANLkTimfWm0j6iiKAK0U-7yjPY3FY7ofvaIoixejt_2C@mail.gmail.com>
On 07/02/2010 10:08 PM, BuraphaLinux Server wrote:
> Hello,
>
> I tried my best to do the bisection, and the result after many kernels was:
>
> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> [3ce672d48400e0112fec7a3cb6bb2120493c6e11] KVM: SVM: init_vmcb():
> remove redundant save->cr0 initialization
>
> So what do I do next?
You still need to test that last kernel. "0 revisions left" means that
after this test (and the last "git bisect good" or "git bisect bad")
you'll have the answer.
> I did not 'make mrproper' between each build -
> should I have done that?
>
No need.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-07-03 10:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 17:28 random crash in post_kvm_run() BuraphaLinux Server
2010-06-28 18:38 ` Brian Jackson
2010-06-30 17:57 ` BuraphaLinux Server
2010-06-29 12:16 ` Avi Kivity
2010-06-30 18:25 ` BuraphaLinux Server
2010-07-01 11:44 ` Avi Kivity
2010-07-02 19:08 ` BuraphaLinux Server
2010-07-03 10:28 ` Avi Kivity [this message]
2010-07-03 14:23 ` BuraphaLinux Server
2010-07-05 7:42 ` Avi Kivity
2010-07-05 8:52 ` BuraphaLinux Server
2010-07-05 10:15 ` Avi Kivity
2010-07-06 7:46 ` Avi Kivity
2010-07-06 8:37 ` Avi Kivity
2010-07-06 15:58 ` BuraphaLinux Server
2010-07-07 9:12 ` Avi Kivity
2010-06-30 18:06 ` Anthony Liguori
2010-06-30 18:32 ` BuraphaLinux Server
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=4C2F10CA.6020907@redhat.com \
--to=avi@redhat.com \
--cc=buraphalinuxserver@gmail.com \
--cc=kvm@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.