On Tue, 2006-08-29 at 23:16 +0100, Ewan Mellor wrote:
> On Tue, Aug 22, 2006 at 04:50:54PM -0500, Hollis Blanchard wrote:
>
> > Since this patch wasn't committed, the shadow2 changes created
> > conflicts. Here is the respin. Note that I have not tested with shadow2,
> > but as you can see below t
This hasn't hit us in xenppc-unstable because we're downlevel, but
here's what I committed in the merge tree:
diff -r 030a041bbe90 xen/arch/powerpc/boot_of.c
--- a/xen/arch/powerpc/boot_of.cTue Aug 29 06:53:58 2006 -0400
+++ b/xen/arch/powerpc/boot_of.cTue Aug 29 17:45:56 2006 -050
Hollis Blanchard wrote:
On Tue, 2006-08-29 at 22:06 +0100, Ian Campbell wrote:
On Tue, 2006-08-29 at 15:24 -0500, Hollis Blanchard wrote:
Hi Ian, I needed the following patch to avoid lots of these warnings:
elf.c:238: warning: pointer of type `void *' used in arithmetic
Fix void* arit
On Tue, Aug 22, 2006 at 04:50:54PM -0500, Hollis Blanchard wrote:
> Since this patch wasn't committed, the shadow2 changes created
> conflicts. Here is the respin. Note that I have not tested with shadow2,
> but as you can see below the math doesn't need to be so complicated.
>
> Ewan, please app
On Tue, 2006-08-29 at 22:06 +0100, Ian Campbell wrote:
> On Tue, 2006-08-29 at 15:24 -0500, Hollis Blanchard wrote:
> > Hi Ian, I needed the following patch to avoid lots of these warnings:
> > elf.c:238: warning: pointer of type `void *' used in arithmetic
> >
> > Fix void* arithmetic warning
Hi Ian, these functions should be static. It would only be a style issue
except PowerPC actually #includes elf.c twice, to support both 32- and
64-bit ELF binaries. Please apply.
Make xen_elfnote_string() and xen_elfnote_numeric() static.
Signed-off-by: Hollis Blanchard <[EMAIL PROTECTED]>
--- a
Most common cause of this is hanging the U3/U4. Do you have a
hardware
debugger to see where this happens?
It's been my experience that RISCWatch isn't very helpful in these
situations (e.g. can't stop the processor). When the northbridge goes,
JTAG becomes unhappy.
Works fine for me, don't
This patch check-stops my box.
For those of you with Maples, the 405 console spits out those nasty:
Error: Magic number in message area NVRAM is not valid.
errors.
This is proof (well, a strong indicator, heh) that the U4
is indeed hung.
Segher
_
It is quite stable in that the secondary processors reliably join
the
idle domain and wait for free pages to scrub, handling 0x980
interrupts
with no problem.
What's this 980 exception?
Perhaps my phrasing is bad. I was referring to the hypervisor
decrementor interrupt (hdec).
Ah yes, I f
On Mon, 2006-08-28 at 23:04 -0400, Amos Waterland wrote:
>
> I'm really suprised you are not seeing it. Make sure to scroll up in
> the console output of your domU boot ...
Honestly, I never see console output from my init, because the Xen
console driver sucks and I haven't invested the time to
On Tue, 2006-08-29 at 09:02 +0200, Segher Boessenkool wrote:
> > It is quite stable in that the secondary processors reliably join the
> > idle domain and wait for free pages to scrub, handling 0x980
> > interrupts with no problem.
>
> What's this 980 exception?
Hypervisor decrementer. It's a g
This patch check-stops my box.
For those of you with Maples, the 405 console spits out those nasty:
Error: Magic number in message area NVRAM is not valid.
errors.
If I sync the console I get as far as:
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to
switch input to Xen).
z
On Tue, Aug 29, 2006 at 09:02:58AM +0200, Segher Boessenkool wrote:
> >It is quite stable in that the secondary processors reliably join the
> >idle domain and wait for free pages to scrub, handling 0x980
> >interrupts
> >with no problem.
>
> What's this 980 exception?
Perhaps my phrasing is ba
On Aug 29, 2006, at 2:49 AM, Tony Breeds wrote:
From: Tony Breeds <[EMAIL PROTECTED]>
While getting xend/domU up and runngin today I noticed what
look like a couple of typos.
AFAICT do_dom0_op will return 0 or -1, so the failure test in
tools/libxc/powerpc64/xc_memory.c has the wrong operator
# HG changeset patch
# User Jimi Xenidis <[EMAIL PROTECTED]>
# Node ID 9c485899125450b3901ecb664e71c26a75009c8e
# Parent 03b9714ea388fa82a3f1344aece67b1b6ef1
[POWERPC][TOOLS] any non-zero result is an error
---
tools/libxc/powerpc64/xc_memory.c |2 +-
1 files changed, 1 insertion(+), 1 de
# HG changeset patch
# User Jimi Xenidis <[EMAIL PROTECTED]>
# Node ID 5d02e1740961aa13099c3f0f23d9df13223f8456
# Parent f05a3e9d3e8f67a47afe4f528084d87c2e9d07ce
[XEN][POWERPC] cleanup for (;;);
When the port first started, we didn't even have panic() working
properly so we used "for(;;);" loops
# HG changeset patch
# User Jimi Xenidis <[EMAIL PROTECTED]>
# Node ID 03b9714ea388fa82a3f1344aece67b1b6ef1
# Parent 5d02e1740961aa13099c3f0f23d9df13223f8456
[POWERPC][XEN][TOOLS] Fix a couple of typos
While getting xend/domU up and runngin today I noticed what
look like a couple of typos.
A
Believe it or not I document this warning here:
http://wiki.xensource.com/xenwiki/XenPPC/Run/XM
so yes it is reproducible.
I think its a side effect from a large initrd and completely a linux
bug, in fact you can google where others have the problem.
I believe you would get this from zIamge
It is quite stable in that the secondary processors reliably join the
idle domain and wait for free pages to scrub, handling 0x980
interrupts
with no problem.
What's this 980 exception?
However, the domU's sometimes hang during initialization. When the
domU
hangs, it seems the whole machi
19 matches
Mail list logo
