Il giorno mar, 04/01/2011 alle 13.53 +, Ian Campbell ha scritto:
On Tue, 2011-01-04 at 14:48 +0100, Giuseppe Sacco wrote:
[...]
Thanks. Unfortunately there doesn't seem to be anything of interest in
the xm dmesg output. It's possible that you need to add loglvl=all
guest_loglvl=all to the
On Thu, 2010-12-30 at 16:02 +0100, Giuseppe Sacco wrote:
A new crash on that machine, after upgrading kernel, is shown here:
Dec 29 22:21:28 atf-124 kernel: [49041.588528] [ cut here
]
Dec 29 22:21:28 atf-124 kernel: [49041.591269] kernel BUG at
Hi Ian,
thanks for working on this report.
Il giorno mar, 04/01/2011 alle 11.53 +, Ian Campbell ha scritto:
On Thu, 2010-12-30 at 16:02 +0100, Giuseppe Sacco wrote:
A new crash on that machine, after upgrading kernel, is shown here:
Dec 29 22:21:28 atf-124 kernel: [49041.588528]
Hi Ian,
Il giorno mar, 04/01/2011 alle 11.53 +, Ian Campbell ha scritto:
On Thu, 2010-12-30 at 16:02 +0100, Giuseppe Sacco wrote:
[...]
I would expect some log on the hypervisor console (xm dmesg) which
corresponds with this hypercall failure, which would be very useful to
see..
I just
On Tue, 2011-01-04 at 14:48 +0100, Giuseppe Sacco wrote:
Hi Ian,
Il giorno mar, 04/01/2011 alle 11.53 +, Ian Campbell ha scritto:
On Thu, 2010-12-30 at 16:02 +0100, Giuseppe Sacco wrote:
[...]
I would expect some log on the hypervisor console (xm dmesg) which
corresponds with this
A new crash on that machine, after upgrading kernel, is shown here:
Dec 29 22:21:28 atf-124 kernel: [49041.588528] [ cut here
]
Dec 29 22:21:28 atf-124 kernel: [49041.591269] kernel BUG at
/build/buildd-linux-2.6_2.6.32-29-i386-Of6Yt1/linux-2.6-2.6
6 matches
Mail list logo