From: Valdis.Kletnieks@vt.edu
To: Avi Kivity <avi@redhat.com>, Beth Kon <eak@us.ibm.com>,
rostedt@goodmis.org, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: Wierdness - linux-next KVM patch breaks Dell Latitude D820, KVM not in kernel
Date: Sat, 12 Sep 2009 16:55:33 -0400 [thread overview]
Message-ID: <125228.1252788933@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 09 Sep 2009 14:59:12 EDT." <25165.1252522752@turing-police.cc.vt.edu>
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
On Wed, 09 Sep 2009 14:59:12 EDT, Valdis.Kletnieks@vt.edu said:
> So hopefully excluding kvm.git I'll track down the *original* hang...
>
> Wish me luck. ;)
And luck was not to be had. Apparently 'git bisect skip' has some bad O(n**2)
issues - I tried to exclude the kvm.git tree, and it ended up running literally
overnight with no signs of stopping (see the gory details here:
https://bugzilla.redhat.com/show_bug.cgi?id=522599 ) Now, I probably *could*
cobble up something to do the skip as a series of little 20-40 commit skips,
but that's just getting nuts. ;)
Given that I'm having little luck bisecting this issue in linux-next and
we're now into the merge window, does anybody have a *better* idea than letting
the issue get into Linus's tree around -rc1, and hope that bisects more nicely
than linux-next did, so -rc2 has a fix for it?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2009-09-12 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 14:07 Valdis.Kletnieks
2009-09-08 13:32 ` Beth Kon
2009-09-08 19:41 ` Valdis.Kletnieks
2009-09-09 14:25 ` Avi Kivity
2009-09-09 17:34 ` Valdis.Kletnieks
2009-09-09 17:38 ` Avi Kivity
2009-09-09 18:59 ` Valdis.Kletnieks
2009-09-12 20:55 ` Valdis.Kletnieks [this message]
2009-09-13 11:39 ` Avi Kivity
2009-09-20 15:50 ` Valdis.Kletnieks
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=125228.1252788933@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=eak@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®