Re: [Xen-devel] Re: NX related build failure in latest pv_ops dom0 hackery tree

[Christophe Saout <christophe@xxxxxxxx>]

Hi Jeremy,

> > just got the netconsole output from the machine, and yes, it's the AHCI
> > initialisation problem.  The older "hackery" kernel didn't boot either
> > (didn't check if it's the same problem).
>
> That would be interesting to know.  push2/xen/dom0/master would also be 
> an interesting result.

Ok, you are right.  The hackery kernel sees a different issue.  The AHCI
setup actually works and hard disks are detected, but then it crashes in
my initrd:

Write protecting the kernel read-only data: 5868k
init[1] general protection ip:ffffe42f sp:ffc5cfa4 error:0

(the init process is a bash in this case)

Note that this probably has to do with the fact that my initrd is 32 bit
and hence runs in 32 bit compat mode (I was just to lazy to make me a
new one when I initially bought my first 64 machine).

The funny thing is that I also see this when running the kernel under
qemu but just assumed a problem in qemu and never investigated.  qemu is
emulating an AMD CPU I think, so maybe it's something related to
sysenter vs. syscall or something. (?)  Because 32 bit compat mode under
XEN works on my Intel notebook.

So I guess if I redo the initramfs as 64 bit the hackery kernel would
boot.  Maybe someone else who has the kernel running on an AMD machine
can test 32 bit compat mode to confirm this observation?

Ok, back to the AHCI issue, test push2/xen/dom0/master is ongoing.

        Christophe



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel