[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable


  • To: Pasi Kärkkäinen <pasik@xxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Tue, 8 Sep 2009 12:14:54 -0700 (PDT)
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, fedora-xen@xxxxxxxxxx, Mark Schloesser <mark.schloesser@xxxxxxxxxxxxxx>
  • Delivery-date: Tue, 08 Sep 2009 12:15:22 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=gXUfo0lf9gzEWSpG9P5GNmUPWzZv3gzT2ML42HXl9ikyw5GA0TvyPvbeM04iLJECnzq0/5Wn0SLcQEh8jmxMEYHjF3P/LQ/yKft++jYJGrKFdfWfX0BF+lxuvzrnhrGgxoBM2S5KB6CpubmvXvUAs/7yYr4ndVgjKlFRMDZtmI0=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Console drops into the same stack trace in  both cases.

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: "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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.