On Fri, Dec 16, 2011 at 07:44:10PM -0600, Anthony Liguori wrote:
> Fairly certain this bisect is a red herring.
>
> tglx reported this the other day in IRC. He narrowed it down to
> virtio-serial. He was able to reproduce it both with kvm tools and
> QEMU.
I looked at this a bit more closely, a
On Fri, Dec 16, 2011 at 07:44:10PM -0600, Anthony Liguori wrote:
> On 12/16/2011 06:53 PM, Max Filippov wrote:
> >>>git bisect says this. I didn't believe it first time, so I ran it
> >>>twice with a few modifications, and it pointed to the same commit both
> >>>times ...
> >>
> >>Richard,
> >>cou
On 12/16/2011 06:53 PM, Max Filippov wrote:
git bisect says this. I didn't believe it first time, so I ran it
twice with a few modifications, and it pointed to the same commit both
times ...
Richard,
could you please elaborate on your testcase and configuration
(host/target architecture, comma
On 12/16/2011 06:07 PM, Richard W.M. Jones wrote:
git bisect says this. I didn't believe it first time, so I ran it
twice with a few modifications, and it pointed to the same commit both
times ...
67882fd177389527510eb36b3f7712011a835545 is the first bad commit
commit 67882fd177389527510eb36b3
On 12/16/2011 06:07 PM, Richard W.M. Jones wrote:
git bisect says this. I didn't believe it first time, so I ran it
twice with a few modifications, and it pointed to the same commit both
times ...
Need more details because it doesn't appear to be broken to me.
What guest, what's your command
>> git bisect says this. I didn't believe it first time, so I ran it
>> twice with a few modifications, and it pointed to the same commit both
>> times ...
>
> Richard,
> could you please elaborate on your testcase and configuration
> (host/target architecture, command lines, etc).
Ok, I've found
> git bisect says this. I didn't believe it first time, so I ran it
> twice with a few modifications, and it pointed to the same commit both
> times ...
Richard,
could you please elaborate on your testcase and configuration
(host/target architecture, command lines, etc).
> 67882fd177389527510eb3
git bisect says this. I didn't believe it first time, so I ran it
twice with a few modifications, and it pointed to the same commit both
times ...
67882fd177389527510eb36b3f7712011a835545 is the first bad commit
commit 67882fd177389527510eb36b3f7712011a835545
Author: Max Filippov
Date: Tue Se
