On Mon, 2010-08-09 at 01:18 +0100, Ben Hutchings wrote:
On Wed, 2010-08-04 at 15:05 +0200, Zdenek Salvet wrote:
On Wed, Aug 04, 2010 at 03:23:52AM +0100, Ben Hutchings wrote:
I found root cause of the problem; after I added following fix to lenny
xen kernel, none of 56 domU froze again
On Wed, 2010-08-04 at 15:05 +0200, Zdenek Salvet wrote:
On Wed, Aug 04, 2010 at 03:23:52AM +0100, Ben Hutchings wrote:
I found root cause of the problem; after I added following fix to lenny
xen kernel, none of 56 domU froze again in one week of testing:
[...]
That sounds promising.
On Wed, Aug 04, 2010 at 03:23:52AM +0100, Ben Hutchings wrote:
I found root cause of the problem; after I added following fix to lenny
xen kernel, none of 56 domU froze again in one week of testing:
[...]
That sounds promising. Is this patch based on a change made by the
upstream Xen or
On Mon, 2010-08-02 at 15:03 +0200, Zdenek Salvet wrote:
Package: linux-image-2.6.26-2-xen-686
Version: 2.6.26-24
Severity: important
Bug #534880 in not yet fixed in lenny :-(
Right, and it is not marked as fixed there. I don't know why it has
been archived.
I found root cause of the
Package: linux-image-2.6.26-2-xen-686
Version: 2.6.26-24
Severity: important
Bug #534880 in not yet fixed in lenny :-(
I found root cause of the problem; after I added following fix to lenny
xen kernel, none of 56 domU froze again in one week of testing:
---
5 matches
Mail list logo