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

[Boris Derzhavets]

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

From: Mark Schloesser 
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Boris Derzhavets" 
Cc: [e-mail]
Date: Tuesday, September 8, 2009, 8:13 AM

Top commit in my checkout is:

commit 3b316bf67dcbe550e648703475e811fc0cedc705
Merge: 226206a 27a3a52
Author: Jeremy Fitzhardinge 
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  wrote:
>
> From: Mark Schloesser 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: [e-mail], [e-mail]
> 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

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

[Boris Derzhavets]

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

From: Boris Derzhavets 
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Mark Schloesser" 
Cc: [e-mail], [e-mail]
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  wrote:

From: Mark Schloesser 
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Boris Derzhavets" 
Cc: [e-mail]
Date: Tuesday, September 8, 2009, 8:13 AM

Top commit in my checkout is:

commit 3b316bf67dcbe550e648703475e811fc0cedc705
Merge: 226206a 27a3a52
Author: Jeremy Fitzhardinge 
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  wrote:
>
> From: Mark Schloesser 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: [e-mail], [e-mail]
> 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
[e-mail]
https://www.redhat.com/mailman/listinfo/fedora-xen

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

[Boris Derzhavets]

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.

Boris.

--- On Tue, 9/8/09, Boris Derzhavets  wrote:

From: Boris Derzhavets 
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Mark Schloesser" 
Cc: [e-mail], [e-mail]
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  wrote:

From: Boris Derzhavets 
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Mark Schloesser" 
Cc: [e-mail], [e-mail]
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  wrote:

From: Mark Schloesser 
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Boris Derzhavets" 
Cc: [e-mail]
Date: Tuesday, September 8, 2009, 8:13 AM

Top commit in my checkout is:

commit 3b316bf67dcbe550e648703475e811fc0cedc705
Merge: 226206a 27a3a52
Author: Jeremy Fitzhardinge 
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  wrote:
>
> From: Mark Schloesser 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: [e-mail], [e-mail]
> 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
[e-mail]
https://www.redhat.com/mailman/listinfo/fedora-xen

-----Inline Attachment Follows-----

--
Fedora-xen mailing list
[e-mail]
https://www.redhat.com/mailman/listinfo/fedora-xen

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

[Pasi Kärkkäinen]

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  wrote:
>
> From: Boris Derzhavets 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Mark Schloesser" 
> Cc: [e-mail], [e-mail]
> 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  wrote:
>
> From: Boris Derzhavets 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Mark Schloesser" 
> Cc: [e-mail], [e-mail]
> 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  wrote:
>
> From: Mark Schloesser 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: [e-mail]
> Date: Tuesday, September 8, 2009, 8:13 AM
>
> Top commit in my checkout is:
>
> commit 3b316bf67dcbe550e648703475e811fc0cedc705
> Merge: 226206a 27a3a52
> Author: Jeremy Fitzhardinge 
> 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  wrote:
> >
> > From: Mark Schloesser 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Boris Derzhavets" 
> > Cc: [e-mail], [e-mail]
> > 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
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
> -----Inline Attachment Follows-----
>
> --
> Fedora-xen mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
> Xen-devel mailing list
> [e-mail]
> http://lists.xensource.com/xen-devel

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

[Boris Derzhavets]

Call trace:
> > > 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  wrote:

From: Pasi Kärkkäinen 
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Boris Derzhavets" 
Cc: [e-mail], [e-mail], "Mark Schloesser" 
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  wrote:
>
> From: Boris Derzhavets 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Mark Schloesser" 
> Cc: [e-mail], [e-mail]
> 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  wrote:
>
> From: Boris Derzhavets 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Mark Schloesser" 
> Cc: [e-mail], [e-mail]
> 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  wrote:
>
> From: Mark Schloesser 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: [e-mail]
> Date: Tuesday, September 8, 2009, 8:13 AM
>
> Top commit in my checkout is:
>
> commit 3b316bf67dcbe550e648703475e811fc0cedc705
> Merge: 226206a 27a3a52
> Author: Jeremy Fitzhardinge 
> 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  wrote:
> >
> > From: Mark Schloesser 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Boris Derzhavets" 
> > Cc: [e-mail], [e-mail]
> > 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
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
> -----Inline Attachment Follows-----
>
> --
> Fedora-xen mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
> _______________________________________________
> Xen-devel mailing list
> [e-mail]
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
[e-mail]
http://lists.xensource.com/xen-devel

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

[Pasi Kärkkäinen]

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  wrote:
>
> From: Pasi Kärkkäinen 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: [e-mail], [e-mail], "Mark Schloesser" 
> 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  wrote:
> >
> > From: Boris Derzhavets 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Mark Schloesser" 
> > Cc: [e-mail], [e-mail]
> > 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  wrote:
> >
> > From: Boris Derzhavets 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Mark Schloesser" 
> > Cc: [e-mail], [e-mail]
> > 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  wrote:
> >
> > From: Mark Schloesser 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Boris Derzhavets" 
> > Cc: [e-mail]
> > Date: Tuesday, September 8, 2009, 8:13 AM
> >
> > Top commit in my checkout is:
> >
> > commit 3b316bf67dcbe550e648703475e811fc0cedc705
> > Merge: 226206a 27a3a52
> > Author: Jeremy Fitzhardinge 
> > 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  wrote:
> > >
> > > From: Mark Schloesser 
> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > > To: "Boris Derzhavets" 
> > > Cc: [e-mail], [e-mail]
> > > 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
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-xen
> >
> > -----Inline Attachment Follows-----
> >
> > --
> > Fedora-xen mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-xen
> >
> > _______________________________________________
> > Xen-devel mailing list
> > [e-mail]
> > http://lists.xensource.com/xen-devel
>
> Xen-devel mailing list
> [e-mail]
> http://lists.xensource.com/xen-devel

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

[Boris Derzhavets]

8 GB Ram. I will check dom0_mem=?

Boris.

--- On Tue, 9/8/09, Pasi Kärkkäinen  wrote:

From: Pasi Kärkkäinen 
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Boris Derzhavets" 
Cc: "Mark Schloesser" , [e-mail], [e-mail]
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  wrote:
>
> From: Pasi Kärkkäinen 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: [e-mail], [e-mail], "Mark Schloesser" 
> 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  wrote:
> >
> > From: Boris Derzhavets 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Mark Schloesser" 
> > Cc: [e-mail], [e-mail]
> > 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  wrote:
> >
> > From: Boris Derzhavets 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Mark Schloesser" 
> > Cc: [e-mail], [e-mail]
> > 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  wrote:
> >
> > From: Mark Schloesser 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Boris Derzhavets" 
> > Cc: [e-mail]
> > Date: Tuesday, September 8, 2009, 8:13 AM
> >
> > Top commit in my checkout is:
> >
> > commit 3b316bf67dcbe550e648703475e811fc0cedc705
> > Merge: 226206a 27a3a52
> > Author: Jeremy Fitzhardinge 
> > 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  wrote:
> > >
> > > From: Mark Schloesser 
> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > > To: "Boris Derzhavets" 
> > > Cc: [e-mail], [e-mail]
> > > 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
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-xen
> >
> > -----Inline Attachment Follows-----
> >
> > --
> > Fedora-xen mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-xen
> >
> > _______________________________________________
> > Xen-devel mailing list
> > [e-mail]
> > http://lists.xensource.com/xen-devel
>
> Xen-devel mailing list
> [e-mail]
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
[e-mail]
http://lists.xensource.com/xen-devel

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

[Boris Derzhavets]

System boots up with dom0_mem=4096M.

Boris.

--- On Tue, 9/8/09, Pasi Kärkkäinen  wrote:

From: Pasi Kärkkäinen 
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Boris Derzhavets" 
Cc: [e-mail], [e-mail], "Mark Schloesser" 
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  wrote:
>
> From: Pasi Kärkkäinen 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: [e-mail], [e-mail], "Mark Schloesser" 
> 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  wrote:
> >
> > From: Boris Derzhavets 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Mark Schloesser" 
> > Cc: [e-mail], [e-mail]
> > 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  wrote:
> >
> > From: Boris Derzhavets 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Mark Schloesser" 
> > Cc: [e-mail], [e-mail]
> > 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  wrote:
> >
> > From: Mark Schloesser 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Boris Derzhavets" 
> > Cc: [e-mail]
> > Date: Tuesday, September 8, 2009, 8:13 AM
> >
> > Top commit in my checkout is:
> >
> > commit 3b316bf67dcbe550e648703475e811fc0cedc705
> > Merge: 226206a 27a3a52
> > Author: Jeremy Fitzhardinge 
> > 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  wrote:
> > >
> > > From: Mark Schloesser 
> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > > To: "Boris Derzhavets" 
> > > Cc: [e-mail], [e-mail]
> > > 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
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-xen
> >
> > -----Inline Attachment Follows-----
> >
> > --
> > Fedora-xen mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-xen
> >
> > _______________________________________________
> > Xen-devel mailing list
> > [e-mail]
> > http://lists.xensource.com/xen-devel
>
> Xen-devel mailing list
> [e-mail]
> http://lists.xensource.com/xen-devel

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

[Pasi Kärkkäinen]

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  wrote:
>
> From: Pasi Kärkkäinen 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: [e-mail], [e-mail], "Mark Schloesser" 
> 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  wrote:
> >
> > From: Pasi Kärkkäinen 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Boris Derzhavets" 
> > Cc: [e-mail], [e-mail], "Mark Schloesser" 
> > 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  wrote:
> > >
> > > From: Boris Derzhavets 
> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > > To: "Mark Schloesser" 
> > > Cc: [e-mail], [e-mail]
> > > 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  wrote:
> > >
> > > From: Boris Derzhavets 
> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > > To: "Mark Schloesser" 
> > > Cc: [e-mail], [e-mail]
> > > 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  wrote:
> > >
> > > From: Mark Schloesser 
> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > > To: "Boris Derzhavets" 
> > > Cc: [e-mail]
> > > Date: Tuesday, September 8, 2009, 8:13 AM
> > >
> > > Top commit in my checkout is:
> > >
> > > commit 3b316bf67dcbe550e648703475e811fc0cedc705
> > > Merge: 226206a 27a3a52
> > > Author: Jeremy Fitzhardinge 
> > > 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  wrote:
> > > >
> > > > From: Mark Schloesser 
> > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > > > To: "Boris Derzhavets" 
> > > > Cc: [e-mail], [e-mail]
> > > > 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
> > > [e-mail]
> > > https://www.redhat.com/mailman/listinfo/fedora-xen
> > >
> > > -----Inline Attachment Follows-----
> > >
> > > --
> > > Fedora-xen mailing list
> > > [e-mail]
> > > https://www.redhat.com/mailman/listinfo/fedora-xen
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > [e-mail]
> > > http://lists.xensource.com/xen-devel
> >
> > Xen-devel mailing list
> > [e-mail]
> > http://lists.xensource.com/xen-devel

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

[Boris Derzhavets]

Console drops into the same stack trace in  both cases.

Boris.

--- On Tue, 9/8/09, Pasi Kärkkäinen  wrote:

From: Pasi Kärkkäinen 
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Boris Derzhavets" 
Cc: "Mark Schloesser" , [e-mail], [e-mail]
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  wrote:
>
> From: Pasi Kärkkäinen 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: [e-mail], [e-mail], "Mark Schloesser" 
> 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  wrote:
> >
> > From: Pasi Kärkkäinen 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Boris Derzhavets" 
> > Cc: [e-mail], [e-mail], "Mark Schloesser" 
> > 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] Re: Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem

[Pasi Kärkkäinen]

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  wrote:
>
> From: Pasi Kärkkäinen 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: "Mark Schloesser" , [e-mail], [e-mail]
> 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  wrote:
> >
> > From: Pasi Kärkkäinen 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Boris Derzhavets" 
> > Cc: [e-mail], [e-mail], "Mark Schloesser" 
> > 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  wrote:
> > >
> > > From: Pasi Kärkkäinen 
> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > > To: "Boris Derzhavets" 
> > > Cc: [e-mail], [e-mail], "Mark Schloesser" 
> > > 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] Re: Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem

[Konrad Rzeszutek Wilk]

On Tue, Sep 08, 2009 at 10:22:46PM +0300, Pasi Kärkkäinen wrote:
> 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?

The last set of changes in Jeremy's kernel are a set of patches I sent,
so the problem is most likely caused by my work.

A dmesg from both Xen and Linux kernel would be most helpfull. Also
a lspci -vvv would be nice.

And as Pasi suggested, booting the same kernel without Xen would
be most helpful.
> 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) ?

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

[Jeremy Fitzhardinge]

On 09/08/09 12:34, Konrad Rzeszutek Wilk wrote:
> On Tue, Sep 08, 2009 at 10:22:46PM +0300, Pasi Kärkkäinen wrote:
> > 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?
>
> The last set of changes in Jeremy's kernel are a set of patches I sent,
> so the problem is most likely caused by my work.

Yes, I suspect so.  Last time around, USB was good for highlighting
problems in the swiotlb code.  If there's a problem at 4G then generally
its some physical address being accidentally truncated by an implicit
cast in the middle of an expression.  Or something else.

(Why, yes, I am helpful today.)

J
> A dmesg from both Xen and Linux kernel would be most helpfull. Also
> a lspci -vvv would be nice.
>
> And as Pasi suggested, booting the same kernel without Xen would
> be most helpful.
> > 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) ?
>
> Xen-devel mailing list
> [e-mail]
> http://lists.xensource.com/xen-devel

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

[Boris Derzhavets]

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

From: Pasi Kärkkäinen 
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" 
Cc: "Jeremy Fitzhardinge" , [e-mail], [e-mail]
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  wrote:
>
> From: Pasi Kärkkäinen 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: "Mark Schloesser" , [e-mail], [e-mail]
> 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  wrote:
> >
> > From: Pasi Kärkkäinen 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Boris Derzhavets" 
> > Cc: [e-mail], [e-mail], "Mark Schloesser" 
> > 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  wrote:
> > >
> > > From: Pasi Kärkkäinen 
> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > > To: "Boris Derzhavets" 
> > > Cc: [e-mail], [e-mail], "Mark Schloesser" 
> > > 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
[e-mail]
http://lists.xensource.com/xen-devel

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

[Pasi Kärkkäinen]

On Tue, Sep 08, 2009 at 06:31:29AM -0700, Boris Derzhavets wrote:
> 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

dunno if it makes any difference, but you shouldn't have com1= and console=com1 stuff here if you use it _without_ serial console..

My grub.conf with VGA text console:

title Fedora Xen pv_ops dom0-test (2.6.31-rc8)
        root (hd0,0)
        kernel /xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all
        module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_dom0test-lv01
        module /initrd-2.6.31-rc8.img

-- Pasi
> Usual Grub entry drops console to stack trace.
> Dmesg output is attached.
>
> Boris.
> --- On Tue, 9/8/09, Mark Schloesser  wrote:
>
> From: Mark Schloesser 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: [e-mail]
> Date: Tuesday, September 8, 2009, 8:13 AM
>
> Top commit in my checkout is:
>
> commit 3b316bf67dcbe550e648703475e811fc0cedc705
> Merge: 226206a 27a3a52
> Author: Jeremy Fitzhardinge 
> 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  wrote:
> >
> > From: Mark Schloesser 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Boris Derzhavets" 
> > Cc: [e-mail], [e-mail]
> > 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
> Xen-devel mailing list
> [e-mail]
> http://lists.xensource.com/xen-devel

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

[Boris Derzhavets]

I've just understood.
I cannot remove dom0-mem only.

Thanks
Boris

--- On Tue, 9/8/09, Pasi Kärkkäinen  wrote:

From: Pasi Kärkkäinen 
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Boris Derzhavets" 
Cc: "Mark Schloesser" , [e-mail], [e-mail]
Date: Tuesday, September 8, 2009, 11:26 AM

On Tue, Sep 08, 2009 at 06:31:29AM -0700, Boris Derzhavets wrote:
> 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

dunno if it makes any difference, but you shouldn't have com1= and console=com1 stuff here if you use it _without_ serial console..

My grub.conf with VGA text console:

title Fedora Xen pv_ops dom0-test (2.6.31-rc8)
        root (hd0,0)
        kernel /xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all
        module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_dom0test-lv01
        module /initrd-2.6.31-rc8.img

-- Pasi
> Usual Grub entry drops console to stack trace.
> Dmesg output is attached.
>
> Boris.
> --- On Tue, 9/8/09, Mark Schloesser  wrote:
>
> From: Mark Schloesser 
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" 
> Cc: [e-mail]
> Date: Tuesday, September 8, 2009, 8:13 AM
>
> Top commit in my checkout is:
>
> commit 3b316bf67dcbe550e648703475e811fc0cedc705
> Merge: 226206a 27a3a52
> Author: Jeremy Fitzhardinge 
> 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  wrote:
> >
> > From: Mark Schloesser 
> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> > To: "Boris Derzhavets" 
> > Cc: [e-mail], [e-mail]
> > 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
> Xen-devel mailing list
> [e-mail]
> http://lists.xensource.com/xen-devel