Hello,

Any inputs folks on xen debugs provided? dom0 crashes when  xen/next kernel
is used in xcp 0.1.1.

Snippets of debugs...

(XEN) d0:v0: unhandled page fault (ec=0003)
(XEN) Pagetable walk from c07f8fd0:
(XEN)  L3[0x003] = 000000003c7f6001 000007f6
(XEN)  L2[0x003] = 000000003cfac067 00000fac
(XEN)  L1[0x1f8] = 800000003c7f8061 000007f8
(XEN) domain_crash_sync called from entry.S (ff1b47ee)
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.4.3-rc4-pre  x86_32p  debug=n  Not tainted ]----
...

Complete debugs attached one more time.

Thanks

On Thu, Apr 1, 2010 at 5:48 AM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:

> Hi Pasi,
>
> Sorry to bother. Any inputs on debugs provided?
>
> Thanks
>
>
> On Wed, Mar 31, 2010 at 2:10 PM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:
>
>> Attached xen debug logs. Just to update this is with xen/next and xcp0.1.1
>> as dom0. Inputs appreciated.
>>
>> Thanks
>>
>>
>>
>> On Wed, Mar 31, 2010 at 7:39 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
>>
>>> On Wed, Mar 31, 2010 at 06:55:54AM -0700, Ritu kaur wrote:
>>> >    Konrad, yes it is a null-modem cable. Cable was bought for this
>>> testing.
>>> >
>>>
>>> First get it working on baremetal Linux (non-Xen), then continue with
>>> Xen.
>>>
>>> -- Pasi
>>>
>>> >    Thanks
>>> >
>>> >    On Wed, Mar 31, 2010 at 6:42 AM, Konrad Rzeszutek Wilk
>>> >    <[1]konrad.wilk@oracle.com> wrote:
>>> >
>>> >      On Wed, Mar 31, 2010 at 06:15:59AM -0700, Ritu kaur wrote:
>>> >      > It's a onboard serial port. From dmesg there are ttyS0 and ttyS1
>>> ports
>>> >      are
>>> >      > shown and I have tried both of them.
>>> >
>>> >      And the cable you have, it is a null modem serial cable? Have you
>>> ever
>>> >      had serial cable working (say with baremetal Linux?)
>>> >
>>> > References
>>> >
>>> >    Visible links
>>> >    1. mailto:konrad.wilk@oracle.com
>>>
>>
>>
>