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
>
> >
> > --- On Tue, 9/8/09, Boris Derzhavets <
bderzhavets@xxxxxxxxx> wrote:
> >
> > From: Boris Derzhavets <
bderzhavets@xxxxxxxxx>
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Mark Schloesser" <
mark.schloesser@xxxxxxxxxxxxxx>
> > Cc:
xen-devel@xxxxxxxxxxxxxxxxxxx,
fedora-xen@xxxxxxxxxx> > Date: Tuesday, September 8, 2009, 11:20 AM
> >
> > That's a working grub entry :
> >
> > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)
> > root (hd1,0)
> > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all
> > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen
> > module /initrd-2.6.31-rc8.img
> >
> > B.
> >
> > --- On Tue, 9/8/09, Boris Derzhavets <
bderzhavets@xxxxxxxxx> wrote:
> >
> > From: Boris Derzhavets <
bderzhavets@xxxxxxxxx>
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Mark Schloesser" <
mark.schloesser@xxxxxxxxxxxxxx>
> > Cc:
xen-devel@xxxxxxxxxxxxxxxxxxx,
fedora-xen@xxxxxxxxxx> > Date: Tuesday, September 8, 2009, 9:31
> > AM
> >
> > I was able to get login
prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:-
> >
> > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)
> > root (hd1,0)
> > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1
> > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen
> > module /initrd-2.6.31-rc8.img
> >
> > Then disconnected NUL modem cable and loaded Dom0 via :
> >
> > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)
> > root (hd1,0)
> > kernel /xen-3.4.1.gz
> > dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1
> > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen
> >
module /initrd-2.6.31-rc8.img
> >
> > Usual
> > Grub entry drops console to stack trace.
> > Dmesg output is attached.
> >
> > Boris.
> > --- On Tue, 9/8/09, Mark Schloesser <
mark.schloesser@xxxxxxxxxxxxxx> wrote:
> >
> > From: Mark Schloesser <
mark.schloesser@xxxxxxxxxxxxxx>
> > 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:
fedora-xen@xxxxxxxxxx> > Date: Tuesday, September 8, 2009, 8:13 AM
> >
> > Top commit in my checkout is:
> >
> > commit 3b316bf67dcbe550e648703475e811fc0cedc705
> > Merge: 226206a 27a3a52
> > Author: Jeremy Fitzhardinge <
jeremy.fitzhardinge@xxxxxxxxxx>
> > Date: Thu Sep 3 16:25:12 2009
> > -0700
> >
> > Mark
> >
> >
> > Boris Derzhavets wrote:
> > > Yep ;)
> > >
> > > Please, run
> > > # git log|more
> > > in linux-2.6-xen ( obtained via git clone).
> > > I am wondering what was the top commit for good build 2.6.31-rc8
> > > I am trying to bisect.
>
> >
> > > Boris.
> > >
> > >
> > > --- On Sun, 9/6/09, Mark Schloesser <
mark.schloesser@xxxxxxxxxxxxxx> wrote:
> > >
> > > From: Mark Schloesser <
mark.schloesser@xxxxxxxxxxxxxx>
> > > 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> > > Date: Sunday, September 6, 2009, 12:17 PM
> > >
> > > I am on standard F11, using a fresh install and then updated all
> > > packages
> > before doing anything xen related. Xen build was done with
> > > current xen-unstable checkout using only "xen" and "tools" build
> > > targets. I have no libvirt or libvirt-preview currently. My Xorg still
> > > does not want to come up btw :)
> > >
> > > Do you need anything else?
> > >
> > > Mark
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> > -----Inline Attachment Follows-----
> >
> > --
> > Fedora-xen mailing list
> >
Fedora-xen@xxxxxxxxxx> >
https://www.redhat.com/mailman/listinfo/fedora-xen> >
> >
> >
> >
> > -----Inline Attachment Follows-----
> >
> > --
> > Fedora-xen mailing list
> >
Fedora-xen@xxxxxxxxxx> >
https://www.redhat.com/mailman/listinfo/fedora-xen> >
> >
> >
> >
> > _______________________________________________
> > 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>
>
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxhttp://lists.xensource.com/xen-devel
