On Mon, 2012-07-23 at 12:51 -0700, John Stultz wrote:
> On 07/19/2012 01:48 PM, Christoph Biedl wrote:
> > John Stultz wrote...
> >
> >> Attached is the test case I used to reproduce and test the solution
> >> to the hard-hang deadlock.
> > I was wondering whether anybody managed to crash a virtual
On 07/19/2012 01:48 PM, Christoph Biedl wrote:
John Stultz wrote...
Attached is the test case I used to reproduce and test the solution
to the hard-hang deadlock.
I was wondering whether anybody managed to crash a virtualbox guest
using your program. No avail, using version 4.1.18 on the host
On Tue, 2012-07-17 at 03:05 -0400, John Stultz wrote:
> Here is backport of the leapsecond fixes to 3.2-stable. These are less
> straight forward, and should get closer review.
[...]
All queued up for 3.2, thanks.
Ben.
--
Ben Hutchings
73.46% of all statistics are made up.
signature.asc
Descr
John Stultz wrote...
> Attached is the test case I used to reproduce and test the solution
> to the hard-hang deadlock.
I was wondering whether anybody managed to crash a virtualbox guest
using your program. No avail, using version 4.1.18 on the host and the
guest kernel running several 3.0.x (x
On 07/17/2012 12:05 AM, John Stultz wrote:
1) Deadlock leapsecond issue that a few reports described.
I spent some time over the weekend trying to find a way to reproduce
the hard-hang issue some folks were reporting after the leapsecond.
Initially I didn't think the 6b43ae8a619d17 leap-second h
Here is backport of the leapsecond fixes to 3.2-stable. These are less
straight forward, and should get closer review.
This patch set addresses two issues:
1) Deadlock leapsecond issue that a few reports described.
I spent some time over the weekend trying to find a way to reproduce
the hard-han
6 matches
Mail list logo
