Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

2.6.31-rc6 didn't have any problems under Xen 3.4.1.
I didn't test it as vanilla.

Boris.

--- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@xxxxxx> wrote:

From: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, fedora-xen@xxxxxxxxxx
Date: Tuesday, September 8, 2009, 3:22 PM

On Tue, Sep 08, 2009 at 12:14:54PM -0700, Boris Derzhavets wrote:
> Console drops into the same stack trace in  both cases.
>

Jeremy: Any ideas could some recent change in pv_ops dom0 kernel cause
usb stuff to stop working with >4096M of dom0 memory?

dom0_mem=4096M works
dom0_mem=4097M fails with stacktrace

Boris: What was the last kernel that worked without backtraces?
Also, does that same kernel work as baremetal (without Xen) ?

-- Pasi

>
> --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
>
> From: Pasi Kärkkäinen <pasik@xxxxxx>
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
> Cc: "Mark Schloesser" <mark.schloesser@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, fedora-xen@xxxxxxxxxx
> Date: Tuesday, September 8, 2009, 2:49 PM
>
> On Tue, Sep 08, 2009 at 11:46:05AM -0700, Boris Derzhavets wrote:
> > System boots up with dom0_mem=4096M.
> >
>
> Does it boot up with dom0_mem=4097M ?
>
> How about dom0_mem=6144M ?
>
> -- Pasi
>
> > Boris.
> >
> > --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> >
> > From: Pasi Kärkkäinen <pasik@xxxxxx>
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
> > Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, fedora-xen@xxxxxxxxxx, "Mark Schloesser" <mark.schloesser@xxxxxxxxxxxxxx>
> > Date: Tuesday, September 8, 2009, 1:47 PM
> >
> > On Tue, Sep 08, 2009 at 10:38:08AM -0700, Boris Derzhavets wrote:
> > > Call trace:
> >
> >
> > OK. How much memory you have?
> >
> > Does it happen with dom0_mem=2048M? Does it happen with dom0_mem=4096M?
> >
> > -- Pasi
> >
> > > > > >
> > > > > >    usb_hc_died + .....
> > > > > >    usb_add_hcd +.....
> > > > > >    usb_hcd_pci_probe + ....
> > > > > >    do_work_for_cpu + .....
> > > > > >    local_pci_probe + ...
> > > > > >    do_work_for_cpu +.....
> > > > > >    kthread +.....
> > > > > >    child_rip+....
> > > > > >    restore_args + .....
> > > > > >    child_rip + .....
> > > > > >    Code :
> > >  .   .   .   .
> > > > > >    .  .  .   .
> > > > > >
> > > > > >    RIP [<ffff...c7>] usb_kick_khubd + 0x10/0x25
> > > > > >    RSP < ffff ... e0>
> > > > > >    CR2: 00000...098
> > > > > >
> > > > > >    ---[ end trace 8219......]----
> > > > > >
> > > > > >    uhci_hcd 0000:00:1a:0 host controller process error, something bad
> > > > > >    happened !
> > > > > >    uhci_hcd 0000:00:1a:0 host controller halted , very bad
> > > > > >    uhci_hcd 0000:00:1a:0  HC died, cleaning up
> > >
> > >
> > > --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> > >
> > > From: Pasi Kärkkäinen <pasik@xxxxxx>
> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > > To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
> > > Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, fedora-xen@xxxxxxxxxx, "Mark Schloesser" <mark.schloesser@xxxxxxxxxxxxxx>
> > > Date: Tuesday, September 8, 2009, 12:17 PM
> > >
> > > On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote:
> > > > Finally,
> > > >
> > > > title Xen 3.4.1  Fedora 12  (2.6.31-rc8 ) (/dev/sdb1)
> > > >
> > > >   root (hd1,0)
> > > >
> > > >   kernel /xen-3.4.1.gz dom0_mem=1024M
> > > >
> > > >   module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0
> > > >
> > > >   module /initrd-2.6.31-rc8.img
> > > >
> > > > I have to specify dom0_mem, otherwise stack trace.
> > > >
> > >
> > > Hmm... what kind of stack trace you get without dom0_mem specified?
> > >
> > > -- Pasi
>
>
>
>
>       

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

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