Re: [Xen-devel] Re: Errors when build 2.6.31-rc8

[Boris Derzhavets]

Attempt to load 2.6-31-rc8 under Xen 3.4.1 , installed via xen-3.4.1-3.src.rpm along with
libvirt(rawhide) , on top F12 rawhide. yum update gcc,glibc,kernel had been run.

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

2.6.31-rc6 loads fine in same environment under Xen 3.4.1 on top of  F12 rawhide

Boris,

--- On Sat, 9/5/09, Jeremy Fitzhardinge  wrote:

From: Jeremy Fitzhardinge 
Subject: [Xen-devel] Re: Errors when build 2.6.31-rc8
To: "Boris Derzhavets" 
Cc: "Xen-devel" 
Date: Saturday, September 5, 2009, 11:48 AM

On 09/05/09 04:18, Boris Derzhavets wrote:
> After fresh git clone, git checkout tune "make menuconfig" the same
> way as for RC6
>
> When build :-
>
> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:5,
>                   from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
> include/linux/swiotlb.h:48: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:48: warning: its scope is only this definition
> or declaration, which is probably not what you want
> include/linux/swiotlb.h:51: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:63: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:68: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:72: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:76: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:80: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:84: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:89: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:94: warning: ‘enum dma_data_direction’
> declared inside parameter list
> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
>                   from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
> ‘get_dma_ops’:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:29: error:
> dereferencing pointer to incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:32: error:
> dereferencing pointer to incomplete type
> In file included from
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:37,
>                   from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
>                   from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:12: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:11: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_map_single_attrs’:
> include/asm-generic/dma-mapping-common.h:18: error: implicit
> declaration of function ‘valid_dma_direction’
> In file included from
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:37,
>                   from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
>                   from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
> include/asm-generic/dma-mapping-common.h:19: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:31: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:30: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_unmap_single_attrs’:
> include/asm-generic/dma-mapping-common.h:36: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:37: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:43: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:42: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function ‘dma_map_sg_attrs’:
> include/asm-generic/dma-mapping-common.h:52: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:60: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:59: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_unmap_sg_attrs’:
> include/asm-generic/dma-mapping-common.h:66: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:67: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:72: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:72: error: parameter 5
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function ‘dma_map_page’:
> include/asm-generic/dma-mapping-common.h:79: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:86: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:86: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function ‘dma_unmap_page’:
> include/asm-generic/dma-mapping-common.h:91: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:92: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:98: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:98: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_sync_single_for_cpu’:
> include/asm-generic/dma-mapping-common.h:103: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:104: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:111: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:111: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_sync_single_for_device’:
> include/asm-generic/dma-mapping-common.h:116: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:117: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:126: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:126: error: parameter 5
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_sync_single_range_for_cpu’:
> include/asm-generic/dma-mapping-common.h:131: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:132: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:137: error: type of formal
> parameter 4 is incomplete
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:144: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:144: error: parameter 5
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_sync_single_range_for_device’:
> include/asm-generic/dma-mapping-common.h:149: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:150: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:155: error: type of formal
> parameter 4 is incomplete
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:160: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:160: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_sync_sg_for_cpu’:
> include/asm-generic/dma-mapping-common.h:165: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:166: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:173: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:173: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_sync_sg_for_device’:
> include/asm-generic/dma-mapping-common.h:178: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:179: error: dereferencing
> pointer to incomplete type
> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
>                   from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
> ‘dma_mapping_error’:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:42: error:
> dereferencing pointer to incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:43: error:
> dereferencing pointer to incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: At top level:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:60: warning:
> ‘enum dma_data_direction’ declared inside parameter list
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:60: error:
> parameter 4 (‘dir’) has incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
> ‘dma_alloc_coherent_mask’:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:77: error:
> dereferencing pointer to incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:79: error:
> implicit declaration of function ‘DMA_BIT_MASK’
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
> ‘dma_alloc_coherent’:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:114: error:
> implicit declaration of function ‘is_device_dma_capable’
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:117: error:
> dereferencing pointer to incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:120: error:
> dereferencing pointer to incomplete type
> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
>                   from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
> ‘dma_free_coherent’:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:138: error:
> dereferencing pointer to incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:139: error:
> dereferencing pointer to incomplete type
> make[4]: *** [drivers/gpu/drm/ttm/ttm_agp_backend.o] Error 1
> make[3]: *** [drivers/gpu/drm/ttm] Error 2
> make[2]: *** [drivers/gpu/drm] Error 2
> make[1]: *** [drivers/gpu] Error 2
> make: *** [drivers] Error 2

Does this help?

diff --git a/include/linux/swiotlb.h b/include/linux/swiotlb.h
index cb1a663..f4ebffb 100644
--- a/include/linux/swiotlb.h
+++ b/include/linux/swiotlb.h
@@ -2,6 +2,7 @@
 #define __LINUX_SWIOTLB_H

#include <linux/types.h>
+#include <linux/dma-mapping.h>

struct device;
 struct dma_attrs;

J

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

[Xen-devel] Re: Errors when build 2.6.31-rc8

[Boris Derzhavets]

I believe, that some set of CSs from Xen 3.5 has to be included as patches into
xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor.
Otherwise  , F12 release in November won't have suitable Dom0 kernel again.
I would guess 2.6.31-rc6 at best.

Boris.

--- On Sun, 9/6/09, Boris Derzhavets  wrote:

From: Boris Derzhavets 
Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
To: "Jeremy Fitzhardinge" 
Cc: "Xen-devel" , [e-mail]
Date: Sunday, September 6, 2009, 12:56 PM

Attempt to load 2.6-31-rc8 under Xen 3.4.1 , installed via xen-3.4.1-3.src.rpm along with
libvirt(rawhide) , on top F12 rawhide. yum update gcc,glibc,kernel had been run.

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

2.6.31-rc6 loads fine in same environment under Xen 3.4.1 on top of  F12 rawhide

Boris,

[Xen-devel] Re: Errors when build 2.6.31-rc8

[Mr. Teo En Ming (Zhang Enming)]

On 09/07/2009 01:04 AM, Boris Derzhavets wrote:
> I believe, that some set of CSs from Xen 3.5 has to be included as 
> patches into
> xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor.
> Otherwise  , F12 release in November won't have suitable Dom0 kernel 
> again.
> I would guess 2.6.31-rc6 at best.
>
> Boris.
>
> --- On *Sun, 9/6/09, Boris Derzhavets //* wrote:
> From: Boris Derzhavets <[e-mail]>
> Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
> To: "Jeremy Fitzhardinge" <[e-mail]>
> Cc: "Xen-devel" <[e-mail]>, [e-mail]
> Date: Sunday, September 6, 2009, 12:56 PM
>
> Attempt to load 2.6-31-rc8 under Xen 3.4.1 , installed via
> xen-3.4.1-3.src.rpm along with
> libvirt(rawhide) , on top F12 rawhide. yum update gcc,glibc,kernel
> had been run.
>
> 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
>
> 2.6.31-rc6 loads fine in same environment under Xen 3.4.1 on top
> of  F12 rawhide
>
> Boris,
>
>
>
> Xen-devel mailing list
> [e-mail]
> http://lists.xensource.com/xen-devel

I thought Fedora will no longer have dom 0 kernel?

[Xen-devel] Re: Errors when build 2.6.31-rc8

[Pasi Kärkkäinen]

On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> On 09/07/2009 01:04 AM, Boris Derzhavets wrote:
> > I believe, that some set of CSs from Xen 3.5 has to be included as 
> > patches into
> > xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor.
> > Otherwise  , F12 release in November won't have suitable Dom0 kernel 
> > again.
> > I would guess 2.6.31-rc6 at best.
> >
> > Boris.
> >
> > --- On *Sun, 9/6/09, Boris Derzhavets //* wrote:
> >
> > From: Boris Derzhavets 
> >    Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
> >    To: "Jeremy Fitzhardinge" 
> >    Cc: "Xen-devel" , [e-mail]
> >    Date: Sunday, September 6, 2009, 12:56 PM
> >
> > Attempt to load 2.6-31-rc8 under Xen 3.4.1 , installed via
> >    xen-3.4.1-3.src.rpm along with
> >    libvirt(rawhide) , on top F12 rawhide. yum update gcc,glibc,kernel
> >    had been run.
> >
> > 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
> >
> > 2.6.31-rc6 loads fine in same environment under Xen 3.4.1 on top
> >    of  F12 rawhide
> >
> > Boris,
>
> I thought Fedora will no longer have dom 0 kernel?

http://fedoraproject.org/wiki/Features/XenPvopsDom0

"Dom0 status: awaiting upstream kernel support"

-- Pasi

[Xen-devel] Re: Errors when build 2.6.31-rc8

[Boris Derzhavets]

As far as Xen 3.5 tarball will be officially released  kernel supporting Dom0 should be
JF's pvops kernel. When  xen-3.5.0-X.src.rpm and updated libvirt ( next preview)
will become available via F13 rawhide , F12 & F13 rawhide would be ready to go
in text mode as 3.5 Xen Hosts with virt-install&virt-manager available via VNC
connections.  Why wait until Upstream merge ?

Boris

--- On Sun, 9/6/09, Pasi Kärkkäinen  wrote:

From: Pasi Kärkkäinen 
Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
To: "Mr. Teo En Ming (Zhang Enming)" 
Cc: [e-mail], "Xen-devel" , "Jeremy Fitzhardinge" , [e-mail]
Date: Sunday, September 6, 2009, 2:37 PM

On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> On 09/07/2009 01:04 AM, Boris Derzhavets wrote:
> > I believe, that some set of CSs from Xen 3.5 has to be included as 
> > patches into
> > xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor.
> > Otherwise  , F12 release in November won't have suitable Dom0 kernel 
> > again.
> > I would guess 2.6.31-rc6 at best.
> >
> > Boris.
> >
> > --- On *Sun, 9/6/09, Boris Derzhavets //* wrote:
> >
> > From: Boris Derzhavets 
> >     Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
> >     To: "Jeremy Fitzhardinge" 
> >     Cc: "Xen-devel" , [e-mail]
> >     Date: Sunday, September 6, 2009, 12:56 PM
> >
> > Attempt to load 2.6-31-rc8 under Xen 3.4.1 , installed via
> >     xen-3.4.1-3.src.rpm along with
> >     libvirt(rawhide) , on top F12 rawhide. yum update gcc,glibc,kernel
> >     had been run.
> >
> > 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
> >
> > 2.6.31-rc6 loads fine in same environment under Xen 3.4.1 on top
> >     of  F12 rawhide
> >
> > Boris,
>
> I thought Fedora will no longer have dom 0 kernel?

http://fedoraproject.org/wiki/Features/XenPvopsDom0

"Dom0 status: awaiting upstream kernel support"

-- Pasi

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

[Xen-devel] Re: Errors when build 2.6.31-rc8

[Boris Derzhavets]

In other words,  a kind of 3.5 iteration :-

http://bderzhavets.wordpress.com/2009/09/05/setup-xen-3-4-1-libvirt-on-top-f...

Boris.

--- On Mon, 9/7/09, Boris Derzhavets  wrote:

From: Boris Derzhavets 
Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
To: "Pasi Kärkkäinen" 
Cc: "Jeremy Fitzhardinge" , "Xen-devel" , [e-mail]
Date: Monday, September 7, 2009, 12:49 AM

As far as Xen 3.5 tarball will be officially released  kernel supporting Dom0 should be
JF's pvops kernel. When  xen-3.5.0-X.src.rpm and updated libvirt ( next preview)
will become available via F13 rawhide , F12 & F13 rawhide would be ready to go
in text mode as 3.5 Xen Hosts with virt-install&virt-manager available via VNC
connections.  Why wait until Upstream merge ?

Boris

--- On Sun, 9/6/09, Pasi Kärkkäinen  wrote:

From: Pasi Kärkkäinen 
Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
To: "Mr. Teo En Ming (Zhang Enming)" 
Cc: [e-mail], "Xen-devel"
 , "Jeremy Fitzhardinge" , [e-mail]
Date: Sunday, September 6, 2009, 2:37 PM

On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> On 09/07/2009 01:04 AM, Boris Derzhavets wrote:
> > I believe, that some set of CSs from Xen 3.5 has to be included as 
> > patches into
> > xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor.
> > Otherwise  , F12 release in November won't have suitable Dom0 kernel 
> > again.
> > I would guess 2.6.31-rc6 at best.
> >
> > Boris.
> >
> > --- On *Sun, 9/6/09, Boris Derzhavets //* wrote:
> >
> > From: Boris Derzhavets 
> >     Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
> >     To: "Jeremy Fitzhardinge" 
> >     Cc: "Xen-devel" , [e-mail]
> >     Date: Sunday, September 6, 2009, 12:56 PM
> >
> > Attempt to load 2.6-31-rc8 under Xen 3.4.1 , installed via
> >     xen-3.4.1-3.src.rpm along with
> >     libvirt(rawhide) , on top F12 rawhide. yum update

gcc,glibc,kernel
> > had been run.
> >
> > 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
> >
> > 2.6.31-rc6 loads fine in same environment under Xen 3.4.1 on top
> >     of  F12 rawhide
> >
> > Boris,
>
> I thought Fedora will no longer have dom 0 kernel?

http://fedoraproject.org/wiki/Features/XenPvopsDom0

"Dom0 status: awaiting upstream kernel support"

-- Pasi

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

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

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

[Xen-devel] Re: Errors when build 2.6.31-rc8

[Pasi Kärkkäinen]

On Sun, Sep 06, 2009 at 09:49:41PM -0700, Boris Derzhavets wrote:
> As far as Xen 3.5 tarball will be officially released  kernel supporting Dom0 should be
> JF's pvops kernel. When  xen-3.5.0-X.src.rpm and updated libvirt ( next preview)
> will become available via F13 rawhide , F12 & F13 rawhide would be ready to go
> in text mode as 3.5 Xen Hosts with virt-install&virt-manager available via VNC
> connections.  Why wait until Upstream merge ?

Uhm.. sorry I'm a bit confused. If I understood correctly you have a
call trace on your pv_ops dom0 kernel?

Does that only happen with Xen 3.4.1 or what's the problem?

-- Pasi
> Boris
>
> --- On Sun, 9/6/09, Pasi Kärkkäinen  wrote:
>
> From: Pasi Kärkkäinen 
> Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
> To: "Mr. Teo En Ming (Zhang Enming)" 
> Cc: [e-mail], "Xen-devel" , "Jeremy Fitzhardinge" , [e-mail]
> Date: Sunday, September 6, 2009, 2:37 PM
>
> On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> > On 09/07/2009 01:04 AM, Boris Derzhavets wrote:
> > > I believe, that some set of CSs from Xen 3.5 has to be included as 
> > > patches into
> > > xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor.
> > > Otherwise  , F12 release in November won't have suitable Dom0 kernel 
> > > again.
> > > I would guess 2.6.31-rc6 at best.
> > >
> > > Boris.
> > >
> > > --- On *Sun, 9/6/09, Boris Derzhavets //* wrote:
> > >
> > > From: Boris Derzhavets 
> > >     Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
> > >     To: "Jeremy Fitzhardinge" 
> > >     Cc: "Xen-devel" , [e-mail]
> > >     Date: Sunday, September 6, 2009, 12:56 PM
> > >
> > > Attempt to load 2.6-31-rc8 under Xen 3.4.1 , installed via
> > >     xen-3.4.1-3.src.rpm along with
> > >     libvirt(rawhide) , on top F12 rawhide. yum update gcc,glibc,kernel
> > >     had been run.
> > >
> > > 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
> > >
> > > 2.6.31-rc6 loads fine in same environment under Xen 3.4.1 on top
> > >     of  F12 rawhide
> > >
> > > Boris,
> >
> > I thought Fedora will no longer have dom 0 kernel?
>
> http://fedoraproject.org/wiki/Features/XenPvopsDom0
>
> "Dom0 status: awaiting upstream kernel support"
>
> -- Pasi
>
> Xen-devel mailing list
> [e-mail]
> http://lists.xensource.com/xen-devel

[Xen-devel] Re: Errors when build 2.6.31-rc8

[Boris Derzhavets]

Pasi,

I was trying to load the most recent 2.6.31-rc8 under Xen 3.4.1 ( via src.rpm) on F12
rawhide and got stack trace. Jeremy is saying that rc8 works ok under Xen Unstable.
But, Libvirt 0.7.0-6 would obviously have dependencies  on xen-3.4.1 packages.
If i will port Xen 3.5 directly to F12 (F11) it might work with rc8, however Libvirt 0.7.0-6 will be most probably lost again. Libvirt 0.7.0-6 has been built for 3.4.1 Hypervisor ( in my understanding) . That's why i wrote if Xen 3.5 can load rc8, the easiest way to fix
issue is to backport required Xen 3.5 CSs to xen-3.4.1-X(?).src.rpm  and get it resolved before F12 November's release.

Boris

--- On Mon, 9/7/09, Pasi Kärkkäinen  wrote:

From: Pasi Kärkkäinen 
Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
To: "Boris Derzhavets" 
Cc: "Xen-devel" , [e-mail]
Date: Monday, September 7, 2009, 2:57 AM

On Sun, Sep 06, 2009 at 09:49:41PM -0700, Boris Derzhavets wrote:
> As far as Xen 3.5 tarball will be officially released  kernel supporting Dom0 should be
> JF's pvops kernel. When  xen-3.5.0-X.src.rpm and updated libvirt ( next preview)
> will become available via F13 rawhide , F12 & F13 rawhide would be ready to go
> in text mode as 3.5 Xen Hosts with virt-install&virt-manager available via VNC
> connections.  Why wait until Upstream merge ?

Uhm.. sorry I'm a bit confused. If I understood correctly you have a
call trace on your pv_ops dom0 kernel?

Does that only happen with Xen 3.4.1 or what's the problem?

-- Pasi
> Boris
>
> --- On Sun, 9/6/09, Pasi Kärkkäinen  wrote:
>
> From: Pasi Kärkkäinen 
> Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
> To: "Mr. Teo En Ming (Zhang Enming)" 
> Cc: [e-mail], "Xen-devel" , "Jeremy Fitzhardinge" , [e-mail]
> Date: Sunday, September 6, 2009, 2:37 PM
>
> On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> > On 09/07/2009 01:04 AM, Boris Derzhavets wrote:
> > > I believe, that some set of CSs from Xen 3.5 has to be included as 
> > > patches into
> > > xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor.
> > > Otherwise  , F12 release in November won't have suitable Dom0 kernel 
> > > again.
> > > I would guess 2.6.31-rc6 at best.
> > >
> > > Boris.
> > >
> > > --- On *Sun, 9/6/09, Boris Derzhavets //* wrote:
> > >
> > > From: Boris Derzhavets 
> > >     Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
> > >     To: "Jeremy Fitzhardinge" 
> > >     Cc: "Xen-devel" , [e-mail]
> > >     Date: Sunday, September 6, 2009, 12:56 PM
> > >
> > > Attempt to load 2.6-31-rc8 under Xen 3.4.1 , installed via
> > >     xen-3.4.1-3.src.rpm along with
> > >     libvirt(rawhide) , on top F12 rawhide. yum update gcc,glibc,kernel
> > >     had been run.
> > >
> > > 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
> > >
> > > 2.6.31-rc6 loads fine in same environment under Xen 3.4.1 on top
> > >     of  F12 rawhide
> > >
> > > Boris,
> >
> > I thought Fedora will no longer have dom 0 kernel?
>
> http://fedoraproject.org/wiki/Features/XenPvopsDom0
>
> "Dom0 status: awaiting upstream kernel support"
>
> -- Pasi
>
> 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: Errors when build 2.6.31-rc8

[Boris Derzhavets]

I lost one thing. After backport xen-libs-3.4.1 would be updated, hence libvirt might
require another changes as well.
B.

--- On Mon, 9/7/09, Boris Derzhavets  wrote:

From: Boris Derzhavets 
Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
To: "Pasi Kärkkäinen" 
Cc: "Xen-devel" , [e-mail]
Date: Monday, September 7, 2009, 3:25 AM

Pasi,

I was trying to load the most recent 2.6.31-rc8 under Xen 3.4.1 ( via src.rpm) on F12
rawhide and got stack trace. Jeremy is saying that rc8 works ok under Xen Unstable.
But, Libvirt 0.7.0-6 would obviously have dependencies  on xen-3.4.1 packages.
If i will port Xen 3.5 directly to F12 (F11) it might work with rc8, however Libvirt 0.7.0-6 will be most probably lost again. Libvirt 0.7.0-6 has been built for 3.4.1 Hypervisor ( in my understanding) . That's why i wrote if Xen 3.5 can load rc8, the easiest way to fix
issue is to backport required Xen 3.5 CSs to xen-3.4.1-X(?).src.rpm  and get it resolved before F12 November's release.

Boris

--- On Mon, 9/7/09, Pasi Kärkkäinen  wrote:

From: Pasi Kärkkäinen 
Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
To: "Boris Derzhavets" 
Cc: "Xen-devel" , [e-mail]
Date: Monday, September 7, 2009, 2:57 AM

On Sun, Sep 06, 2009 at 09:49:41PM -0700, Boris Derzhavets wrote:
> As far as Xen 3.5 tarball will be officially released  kernel supporting Dom0 should be
> JF's pvops kernel. When  xen-3.5.0-X.src.rpm and updated libvirt ( next preview)
> will become available via F13 rawhide , F12 & F13 rawhide would be ready to go
> in text mode as 3.5 Xen Hosts with virt-install&virt-manager available via VNC
> connections.  Why wait until Upstream merge ?

Uhm.. sorry I'm a bit confused. If I understood correctly you have a
call trace on your pv_ops dom0
 kernel?

Does that only happen with Xen 3.4.1 or what's the problem?

-- Pasi
> Boris
>
> --- On Sun, 9/6/09, Pasi Kärkkäinen  wrote:
>
> From: Pasi Kärkkäinen 
> Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
> To: "Mr. Teo En Ming (Zhang Enming)" 
> Cc: [e-mail], "Xen-devel" , "Jeremy Fitzhardinge"

, [e-mail]
> Date: Sunday, September 6, 2009, 2:37 PM
>
> On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> > On 09/07/2009 01:04 AM, Boris Derzhavets wrote:
> > > I believe, that some set of CSs from Xen 3.5 has to be included as 
> > > patches into
> > > xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor.
> > > Otherwise  , F12 release in November won't have suitable Dom0 kernel 
> > > again.
> > > I would guess 2.6.31-rc6 at best.
> > >
> > > Boris.
> > >
> > > --- On *Sun, 9/6/09, Boris Derzhavets //* wrote:
> > >
> > > From: Boris Derzhavets 
> > >     Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
> > >     To: "Jeremy Fitzhardinge" 
> > >     Cc: "Xen-devel" , [e-mail]
> > >     Date: Sunday, September 6, 2009, 12:56 PM
>
> Attempt to load 2.6-31-rc8 under Xen 3.4.1 , installed via
> > > xen-3.4.1-3.src.rpm along with
> > >     libvirt(rawhide) , on top F12 rawhide. yum update gcc,glibc,kernel
> > >     had been run.
> > >
> > > 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
> > >
> > > 2.6.31-rc6 loads fine in same environment under Xen 3.4.1 on top
> > >     of  F12 rawhide
> > >
> > > Boris,
> > >
> >
> > I thought Fedora will no longer have dom 0 kernel?
>
> http://fedoraproject.org/wiki/Features/XenPvopsDom0
>
> "Dom0 status: awaiting upstream kernel support"
>
> -- Pasi
>
> Xen-devel mailing list
> [e-mail]
> http://lists.xensource.com/xen-devel

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

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

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

[Xen-devel] Re: Errors when build 2.6.31-rc8

[Boris Derzhavets]

I've got the same stack trace on F11 with the most recent "yum update" under Xen Unstable for 2.6.31-rc8 ( top commit 7c62209cde5b13b81685e79b2f9e3757e293aef1)

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

Boris.

[Xen-devel] Re: Errors when build 2.6.31-rc8 / compiles and works OK

[Pasi Kärkkäinen]

On Mon, Sep 07, 2009 at 12:25:33AM -0700, Boris Derzhavets wrote:
> Pasi,
>
> I was trying to load the most recent 2.6.31-rc8 under Xen 3.4.1 ( via src.rpm) on F12
> rawhide and got stack trace. Jeremy is saying that rc8 works ok under Xen Unstable.
> But, Libvirt 0.7.0-6 would obviously have dependencies  on xen-3.4.1 packages.
> If i will port Xen 3.5 directly to F12 (F11) it might work with rc8, however Libvirt 0.7.0-6 will be most probably lost again. Libvirt 0.7.0-6 has been built for 3.4.1 Hypervisor ( in my understanding) . That's why i wrote if Xen 3.5 can load rc8, the easiest way to fix
> issue is to backport required Xen 3.5 CSs to xen-3.4.1-X(?).src.rpm  and get it resolved before F12 November's release.

I just compiled latest 2.6.31-rc8 pv_ops dom0 kernel (commit 7c62209cde5b13b81685e79b2f9e3757e293aef1) and it works for me.

I'm running with xen-3.4.1-3 on Fedora 11 (x86 32bit PAE).

.config for my working kernel: 
http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31-rc8-rebaster-ma...

-- Pasi
> Boris
>
> --- On Mon, 9/7/09, Pasi Kärkkäinen  wrote:
>
> From: Pasi Kärkkäinen 
> Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
> To: "Boris Derzhavets" 
> Cc: "Xen-devel" , [e-mail]
> Date: Monday, September 7, 2009, 2:57 AM
>
> On Sun, Sep 06, 2009 at 09:49:41PM -0700, Boris Derzhavets wrote:
> > As far as Xen 3.5 tarball will be officially released  kernel supporting Dom0 should be
> > JF's pvops kernel. When  xen-3.5.0-X.src.rpm and updated libvirt ( next preview)
> > will become available via F13 rawhide , F12 & F13 rawhide would be ready to go
> > in text mode as 3.5 Xen Hosts with virt-install&virt-manager available via VNC
> > connections.  Why wait until Upstream merge ?
>
> Uhm.. sorry I'm a bit confused. If I understood correctly you have a
> call trace on your pv_ops dom0 kernel?
>
> Does that only happen with Xen 3.4.1 or what's the problem?
>
> -- Pasi
> > Boris
> >
> > --- On Sun, 9/6/09, Pasi Kärkkäinen  wrote:
> >
> > From: Pasi Kärkkäinen 
> > Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
> > To: "Mr. Teo En Ming (Zhang Enming)" 
> > Cc: [e-mail], "Xen-devel" , "Jeremy Fitzhardinge" , [e-mail]
> > Date: Sunday, September 6, 2009, 2:37 PM
> >
> > On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> > > On 09/07/2009 01:04 AM, Boris Derzhavets wrote:
> > > > I believe, that some set of CSs from Xen 3.5 has to be included as 
> > > > patches into
> > > > xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor.
> > > > Otherwise  , F12 release in November won't have suitable Dom0 kernel 
> > > > again.
> > > > I would guess 2.6.31-rc6 at best.
> > > >
> > > > Boris.
> > > >
> > > > --- On *Sun, 9/6/09, Boris Derzhavets //* wrote:
> > > >
> > > > From: Boris Derzhavets 
> > > >     Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
> > > >     To: "Jeremy Fitzhardinge" 
> > > >     Cc: "Xen-devel" , [e-mail]
> > > >     Date: Sunday, September 6, 2009, 12:56 PM
> > > >
> > > > Attempt to load 2.6-31-rc8 under Xen 3.4.1 , installed via
> > > >     xen-3.4.1-3.src.rpm along with
> > > >     libvirt(rawhide) , on top F12 rawhide. yum update gcc,glibc,kernel
> > > >     had been run.
> > > >
> > > > 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
> > > >
> > > > 2.6.31-rc6 loads fine in same environment under Xen 3.4.1 on top
> > > >     of  F12 rawhide
> > > >
> > > > Boris,
> > >
> > > I thought Fedora will no longer have dom 0 kernel?
> >
> > http://fedoraproject.org/wiki/Features/XenPvopsDom0
> >
> > "Dom0 status: awaiting upstream kernel support"
> >
> > -- Pasi
> >
> > Xen-devel mailing list
> > [e-mail]
> > http://lists.xensource.com/xen-devel
>
> Xen-devel mailing list
> [e-mail]
> http://lists.xensource.com/xen-devel