* Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable [not found] <4AA12398.1010300@rwth-aachen.de> @ 2009-09-04 18:02 ` Boris Derzhavets 2009-09-04 20:09 ` Jeremy Fitzhardinge 2009-09-05 10:14 ` Boris Derzhavets 0 siblings, 2 replies; 18+ messages in thread From: Boris Derzhavets @ 2009-09-04 18:02 UTC (permalink / raw) To: fedora-xen, Mark Schloesser; +Cc: xen-devel [-- Attachment #1.1: Type: text/plain, Size: 2289 bytes --] I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. However, attempt to load kernel under Xen 3.4.1 drops into stack trace and hangs on both F11 and Ubuntu 9.10. Old 2.6.31-rc6's .config file has been used without any changes. I can't set up serial console in meantime. Boris --- On Fri, 9/4/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: From: Mark Schloesser <mark.schloesser@rwth-aachen.de> Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: fedora-xen@redhat.com Date: Friday, September 4, 2009, 10:26 AM Hey guys, I sadly had no luck fixing my X problem. The system seems to run fine and as the subject says I moved from 3.4.1-3 to xen-unstable. As I am already doing fairly bleeding-edge stuff here I thought this would probably make most sense. As I only have an nvs290 gfx card available right now I can't check if this is the problem. But I'll try to get my hands on some other cards for next week. Today I read through a lot of mailing list archives and PDFs trying to dig deeper into the IOMMU/PCI passthrough stuff and I want to give the graphics passthrough situation a shot myself. Sadly it is very confusing to read about the different setups and hardware environments with both positive and negative results. Also the patchsets and versions everybody is talking about do not make it any easier :) My current questions would be: - is the combination of JF git kernel with xen-unstable the right way to go for this setup? Or should I perhaps use older xen version and apply some patchset? I think some of those patches were applied in xen-unstable already but I am not quite sure... - does anyone have hints or clarification regarding the Xorg problem on dom0? As I said there are no eye-catching log entries or errors except the Xorg backtrace at the end of the log file (posted to list before). This happens regardless of which driver I enable (vesa/nv/nouveau). The nvidia binary driver compiles without problems and seems to come up but only gives me a black screen and also locks the vtys. Thanks to the great help, reports and instructions Boris and others! Mark -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen [-- Attachment #1.2: Type: text/html, Size: 2956 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-04 18:02 ` [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable Boris Derzhavets @ 2009-09-04 20:09 ` Jeremy Fitzhardinge 2009-09-05 10:14 ` Boris Derzhavets 1 sibling, 0 replies; 18+ messages in thread From: Jeremy Fitzhardinge @ 2009-09-04 20:09 UTC (permalink / raw) To: Boris Derzhavets; +Cc: Mark Schloesser, xen-devel, fedora-xen On 09/04/09 11:02, Boris Derzhavets wrote: > I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. > However, attempt to load kernel under Xen 3.4.1 drops > into stack trace and hangs on both F11 and Ubuntu 9.10. > Old 2.6.31-rc6's .config file has been used without any changes. > I can't set up serial console in meantime. > What's the stack trace? Even of a photo of it may give some clues. Needless to say, it does work for me with current xen-unstable; there shouldn't be any new hypervisor version dependencies. J ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-04 18:02 ` [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable Boris Derzhavets 2009-09-04 20:09 ` Jeremy Fitzhardinge @ 2009-09-05 10:14 ` Boris Derzhavets 2009-09-06 15:09 ` [Xen-devel] " Mark Schloesser 1 sibling, 1 reply; 18+ messages in thread From: Boris Derzhavets @ 2009-09-05 10:14 UTC (permalink / raw) To: fedora-xen, Mark Schloesser; +Cc: xen-devel [-- Attachment #1.1: Type: text/plain, Size: 2978 bytes --] Mark, Could you share your .config for JF's 2.6.31-rc8 which loads under Xen Unstable. Looks like i miss some point tuning kernel. Thanks. Boris. --- On Fri, 9/4/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen.de> Cc: xen-devel@lists.xensource.com Date: Friday, September 4, 2009, 2:02 PM I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. However, attempt to load kernel under Xen 3.4.1 drops into stack trace and hangs on both F11 and Ubuntu 9.10. Old 2.6.31-rc6's .config file has been used without any changes. I can't set up serial console in meantime. Boris --- On Fri, 9/4/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: From: Mark Schloesser <mark.schloesser@rwth-aachen.de> Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: fedora-xen@redhat.com Date: Friday, September 4, 2009, 10:26 AM Hey guys, I sadly had no luck fixing my X problem. The system seems to run fine and as the subject says I moved from 3.4.1-3 to xen-unstable. As I am already doing fairly bleeding-edge stuff here I thought this would probably make most sense. As I only have an nvs290 gfx card available right now I can't check if this is the problem. But I'll try to get my hands on some other cards for next week. Today I read through a lot of mailing list archives and PDFs trying to dig deeper into the IOMMU/PCI passthrough stuff and I want to give the graphics passthrough situation a shot myself. Sadly it is very confusing to read about the different setups and hardware environments with both positive and negative results. Also the patchsets and versions everybody is talking about do not make it any easier :) My current questions would be: - is the combination of JF git kernel with xen-unstable the right way to go for this setup? Or should I perhaps use older xen version and apply some patchset? I think some of those patches were applied in xen-unstable already but I am not quite sure... - does anyone have hints or clarification regarding the Xorg problem on dom0? As I said there are no eye-catching log entries or errors except the Xorg backtrace at the end of the log file (posted to list before). This happens regardless of which driver I enable (vesa/nv/nouveau). The nvidia binary driver compiles without problems and seems to come up but only gives me a black screen and also locks the vtys. Thanks to the great help, reports and instructions Boris and others! Mark -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -----Inline Attachment Follows----- _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel [-- Attachment #1.2: Type: text/html, Size: 4349 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Xen-devel] Re: Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-05 10:14 ` Boris Derzhavets @ 2009-09-06 15:09 ` Mark Schloesser 2009-09-06 15:49 ` Re: [Fedora-xen] " Boris Derzhavets 0 siblings, 1 reply; 18+ messages in thread From: Mark Schloesser @ 2009-09-06 15:09 UTC (permalink / raw) To: Boris Derzhavets; +Cc: xen-devel, fedora-xen [-- Attachment #1.1: Type: text/plain, Size: 3694 bytes --] Boris, actually I used your config. The same config as I used for -rc6 build. Works just fine for me - but I did not try booting with 3.4.1, only with xen-unstable. Mark Boris Derzhavets wrote: > Mark, > Could you share your .config for JF's 2.6.31-rc8 which loads under Xen Unstable. > Looks like i miss some point tuning kernel. > > Thanks. > Boris. > > --- On Fri, 9/4/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > From: Boris Derzhavets <bderzhavets@yahoo.com> > Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > Cc: xen-devel@lists.xensource.com > Date: Friday, September 4, 2009, 2:02 PM > > I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. > However, attempt to load kernel under Xen 3.4.1 drops > into stack trace and hangs on both F11 and Ubuntu 9.10. > Old 2.6.31-rc6's .config file has been used without any changes. > I can't set up serial console in meantime. > > Boris > > --- On Fri, 9/4/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: fedora-xen@redhat.com > Date: Friday, September 4, 2009, 10:26 AM > > Hey guys, > > I sadly had no luck fixing my X problem. The system seems to run fine > and as the subject says I moved > from 3.4.1-3 to xen-unstable. As I am > already doing fairly bleeding-edge stuff here I thought this would > probably make most sense. > > As I only have an nvs290 gfx card available right now I can't check if > this is the problem. But I'll try to get my hands on some other cards > for next week. > > Today I read through a lot of mailing list archives and PDFs trying to > dig deeper into the IOMMU/PCI passthrough stuff and I want to give the > graphics passthrough situation a shot myself. Sadly it is very confusing > to read about the different setups and hardware environments with both > positive and negative results. Also the patchsets and versions everybody > is talking about do not make it any easier :) > > My current questions would be: > - is the combination of JF git kernel with xen-unstable the right way to > go for this setup? Or should I perhaps use older xen version and apply > some patchset? I think some of those > patches were applied in > xen-unstable already but I am not quite sure... > > - does anyone have hints or clarification regarding the Xorg problem on > dom0? As I said there are no eye-catching log entries or errors except > the Xorg backtrace at the end of the log file (posted to list before). > This happens regardless of which driver I enable (vesa/nv/nouveau). The > nvidia binary driver compiles without problems and seems to come up but > only gives me a black screen and also locks the vtys. > > > Thanks to the great help, reports and instructions Boris and others! > > Mark > > > -----Inline Attachment Follows----- > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > -----Inline Attachment Follows----- > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 260 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --] ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-06 15:09 ` [Xen-devel] " Mark Schloesser @ 2009-09-06 15:49 ` Boris Derzhavets 2009-09-06 16:17 ` [Xen-devel] " Mark Schloesser 0 siblings, 1 reply; 18+ messages in thread From: Boris Derzhavets @ 2009-09-06 15:49 UTC (permalink / raw) To: Mark Schloesser; +Cc: xen-devel, fedora-xen [-- Attachment #1.1: Type: text/plain, Size: 17705 bytes --] I tried to build and load on F12 rawhide with the most recent gcc,glibc and kernel (fedoras). So, xen was installed via xen-3.4.1-3.src.rpm along with libvirt ( via rawhide again). Please, let me know your environment for successful build and load rc8 under Xen 3.5. Boris. BTW Please,be advised :- ********** Quote:- ********** >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; Now kernel gets built, but still fails to load under either Xen 3.5 or Xen 3.4.1. Stack traces differ on C2D E8400 (Xen 3.4.1) and Q9550 (Xen 3.5 unstable )boxes. On the last box :- do_one_initcall + 0x37/0x1a0 kernel_init + 0x164/0x1ba child_rip + 0xa/0x20 ? int_ret_from_sys_call 0x7/0x16 ? retint_restore_arg + 0x5/0x6 ? child_rip 0x0/0x20 Two last commands are the same on the first box. Previous differ. Boris. P.S. I cannot buy or order 20 m of NUL modem cable. Just 2.5 m . That's all --- On Sat, 9/5/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: [Xen-devel] Re: Errors when build 2.6.31-rc8 To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: "Xen-devel" <xen-devel@lists.xensource.com> 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 --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: From: Mark Schloesser <mark.schloesser@rwth-aachen.de> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: fedora-xen@redhat.com, xen-devel@lists.xensource.com Date: Sunday, September 6, 2009, 11:09 AM Boris, actually I used your config. The same config as I used for -rc6 build. Works just fine for me - but I did not try booting with 3.4.1, only with xen-unstable. Mark Boris Derzhavets wrote: > Mark, > Could you share your .config for JF's 2.6.31-rc8 which loads under Xen Unstable. > Looks like i miss some point tuning kernel. > > Thanks. > Boris. > > --- On Fri, 9/4/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > From: Boris Derzhavets <bderzhavets@yahoo.com> > Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen..de> > Cc: xen-devel@lists.xensource.com > Date: Friday, September 4, 2009, 2:02 PM > > I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. > However, attempt to load kernel under Xen 3.4.1 drops > into stack trace and hangs on both F11 and Ubuntu 9.10. > Old 2.6.31-rc6's .config file has been used without any changes. > I can't set up serial console in meantime. > > Boris > > --- On Fri, 9/4/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: fedora-xen@redhat.com > Date: Friday, September 4, 2009, 10:26 AM > > Hey guys, > > I sadly had no luck fixing my X problem. The system seems to run fine > and as the subject says I moved > from 3.4.1-3 to xen-unstable. As I am > already doing fairly bleeding-edge stuff here I thought this would > probably make most sense. > > As I only have an nvs290 gfx card available right now I can't check if > this is the problem. But I'll try to get my hands on some other cards > for next week. > > Today I read through a lot of mailing list archives and PDFs trying to > dig deeper into the IOMMU/PCI passthrough stuff and I want to give the > graphics passthrough situation a shot myself. Sadly it is very confusing > to read about the different setups and hardware environments with both > positive and negative results. Also the patchsets and versions everybody > is talking about do not make it any easier :) > > My current questions would be: > - is the combination of JF git kernel with xen-unstable the right way to > go for this setup? Or should I perhaps use older xen version and apply > some patchset? I think some of those > patches were applied in > xen-unstable already but I am not quite sure... > > - does anyone have hints or clarification regarding the Xorg problem on > dom0? As I said there are no eye-catching log entries or errors except > the Xorg backtrace at the end of the log file (posted to list before). > This happens regardless of which driver I enable (vesa/nv/nouveau). The > nvidia binary driver compiles without problems and seems to come up but > only gives me a black screen and also locks the vtys. > > > Thanks to the great help, reports and instructions Boris and others! > > Mark > > > -----Inline Attachment Follows----- > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > -----Inline Attachment Follows----- > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel [-- Attachment #1.2: Type: text/html, Size: 22417 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply related [flat|nested] 18+ messages in thread
* Re: [Xen-devel] Re: Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-06 15:49 ` Re: [Fedora-xen] " Boris Derzhavets @ 2009-09-06 16:17 ` Mark Schloesser 2009-09-06 16:41 ` Re: [Fedora-xen] " Boris Derzhavets 0 siblings, 1 reply; 18+ messages in thread From: Mark Schloesser @ 2009-09-06 16:17 UTC (permalink / raw) To: Boris Derzhavets; +Cc: xen-devel, fedora-xen [-- Attachment #1.1: Type: text/plain, Size: 18740 bytes --] 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 Boris Derzhavets wrote: > I tried to build and load on F12 rawhide with the most recent > gcc,glibc and kernel (fedoras). So, xen was installed via > xen-3.4.1-3.src.rpm along with libvirt ( via rawhide again). Please, > let me know your environment for successful build and load rc8 under > Xen 3.5. > > Boris. > BTW > Please,be advised :- > > ********** > Quote:- > ********** > >> 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; > > Now kernel gets built, but still fails to load under either Xen 3.5 or Xen > 3.4.1. > Stack traces differ on C2D E8400 (Xen 3.4.1) and Q9550 (Xen 3.5 unstable )boxes. > On the last box :- > > do_one_initcall + 0x37/0x1a0 > kernel_init + 0x164/0x1ba > child_rip + 0xa/0x20 > ? int_ret_from_sys_call 0x7/0x16 > ? retint_restore_arg + 0x5/0x6 > ? child_rip 0x0/0x20 > > Two last > commands are the same on the first box. Previous differ. > > Boris. > P.S. I cannot buy or order 20 m of NUL modem cable. > Just 2.5 m . That's all > > --- On Sat, 9/5/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: > > From: Jeremy Fitzhardinge <jeremy@goop.org> > Subject: [Xen-devel] Re: Errors when build 2.6.31-rc8 > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: "Xen-devel" <xen-devel@lists.xensource.com> > 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 > > > --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: fedora-xen@redhat.com, xen-devel@lists.xensource.com > Date: Sunday, September 6, 2009, 11:09 AM > > Boris, > > actually I used your config. The same config as I used for -rc6 build. > Works just fine for me - but I did not try booting with 3.4.1, only with > xen-unstable. > > Mark > > > Boris Derzhavets wrote: >> Mark, >> Could you share your .config for JF's 2.6.31-rc8 which loads under Xen Unstable. >> Looks like i miss some point tuning kernel. >> >> Thanks. >> Boris. >> >> --- On Fri, 9/4/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: >> >> From: Boris Derzhavets <bderzhavets@yahoo.com> >> Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable >> To: fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen..de> >> Cc: xen-devel@lists.xensource.com >> Date: Friday, September 4, 2009, 2:02 PM >> >> I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. >> However, attempt to load kernel under Xen 3.4.1 drops >> into stack trace and hangs on both F11 and Ubuntu 9.10. >> Old 2.6.31-rc6's .config file has been used without any changes. >> I can't set up serial console in meantime. >> >> Boris >> >> --- On Fri, 9/4/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: >> >> From: Mark Schloesser <mark.schloesser@rwth-aachen.de> >> Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable >> To: fedora-xen@redhat.com >> Date: Friday, September 4, 2009, 10:26 AM >> >> Hey guys, >> >> I sadly had no luck fixing my X problem. The system seems to run fine >> and as the subject says I moved >> from 3.4.1-3 to xen-unstable. As I am >> already doing fairly bleeding-edge stuff here I thought this would >> probably make most sense. >> >> As I only have an nvs290 gfx card available right now I can't check if >> this is the problem. But I'll try to get my hands on some other cards >> for next week. >> >> Today I read through a lot of mailing list archives and PDFs trying to >> dig deeper into the IOMMU/PCI passthrough stuff and I want to give the >> graphics passthrough situation a shot myself. Sadly it is very confusing >> to read about the different setups and hardware environments with both >> positive and negative results. Also the patchsets and versions everybody >> is talking about do not make it any easier :) >> >> My current questions would be: >> - is the combination of JF git kernel with xen-unstable the right way to >> go for this setup? Or should I perhaps use older xen version and apply >> some patchset? I think some of those >> patches were applied in >> xen-unstable already but I am not quite sure... >> >> - does anyone have hints or clarification regarding the Xorg problem on >> dom0? As I said there are no eye-catching log entries or errors except >> the Xorg backtrace at the end of the log file (posted to list before). >> This happens regardless of which driver I enable (vesa/nv/nouveau). The >> nvidia binary driver compiles without problems and seems to come up but >> only gives me a black screen and also locks the vtys. >> >> >> Thanks to the great help, reports and instructions Boris and others! >> >> Mark >> >> >> -----Inline Attachment Follows----- >> >> -- >> Fedora-xen mailing list >> Fedora-xen@redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> >> >> >> >> >> >> -----Inline Attachment Follows----- >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > > > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 260 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --] ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-06 16:17 ` [Xen-devel] " Mark Schloesser @ 2009-09-06 16:41 ` Boris Derzhavets 0 siblings, 0 replies; 18+ messages in thread From: Boris Derzhavets @ 2009-09-06 16:41 UTC (permalink / raw) To: Mark Schloesser; +Cc: xen-devel, fedora-xen [-- Attachment #1.1: Type: text/plain, Size: 19294 bytes --] Thanks. --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: From: Mark Schloesser <mark.schloesser@rwth-aachen.de> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com 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 Boris Derzhavets wrote: > I tried to build and load on F12 rawhide with the most recent > gcc,glibc and kernel (fedoras). So, xen was installed via > xen-3.4.1-3.src.rpm along with libvirt ( via rawhide again). Please, > let me know your environment for successful build and load rc8 under > Xen 3.5. > > Boris. > BTW > Please,be advised :- > > ********** > Quote:- > ********** > >> 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; > > Now kernel gets built, but still fails to load under either Xen 3.5 or Xen > 3.4.1. > Stack traces differ on C2D E8400 (Xen 3.4.1) and Q9550 (Xen 3.5 unstable )boxes. > On the last box :- > > do_one_initcall + 0x37/0x1a0 > kernel_init + 0x164/0x1ba > child_rip + 0xa/0x20 > ? int_ret_from_sys_call 0x7/0x16 > ? retint_restore_arg + 0x5/0x6 > ? child_rip 0x0/0x20 > > Two last > commands are the same on the first box. Previous differ. > > Boris. > P.S. I cannot buy or order 20 m of NUL modem cable. > Just 2.5 m . That's all > > --- On Sat, 9/5/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: > > From: Jeremy Fitzhardinge <jeremy@goop.org> > Subject: [Xen-devel] Re: Errors when build 2.6.31-rc8 > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: "Xen-devel" <xen-devel@lists.xensource.com> > 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 > > > --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: fedora-xen@redhat.com, xen-devel@lists.xensource.com > Date: Sunday, September 6, 2009, 11:09 AM > > Boris, > > actually I used your config. The same config as I used for -rc6 build. > Works just fine for me - but I did not try booting with 3.4.1, only with > xen-unstable. > > Mark > > > Boris Derzhavets wrote: >> Mark, >> Could you share your .config for JF's 2.6.31-rc8 which loads under Xen Unstable. >> Looks like i miss some point tuning kernel. >> >> Thanks. >> Boris. >> >> --- On Fri, 9/4/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: >> >> From: Boris Derzhavets <bderzhavets@yahoo.com> >> Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable >> To: fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen..de> >> Cc: xen-devel@lists.xensource.com >> Date: Friday, September 4, 2009, 2:02 PM >> >> I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. >> However, attempt to load kernel under Xen 3.4.1 drops >> into stack trace and hangs on both F11 and Ubuntu 9.10. >> Old 2.6.31-rc6's .config file has been used without any changes. >> I can't set up serial console in meantime. >> >> Boris >> >> --- On Fri, 9/4/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: >> >> From: Mark Schloesser <mark.schloesser@rwth-aachen.de> >> Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable >> To: fedora-xen@redhat.com >> Date: Friday, September 4, 2009, 10:26 AM >> >> Hey guys, >> >> I sadly had no luck fixing my X problem. The system seems to run fine >> and as the subject says I moved >> from 3.4.1-3 to xen-unstable. As I am >> already doing fairly bleeding-edge stuff here I thought this would >> probably make most sense. >> >> As I only have an nvs290 gfx card available right now I can't check if >> this is the problem. But I'll try to get my hands on some other cards >> for next week. >> >> Today I read through a lot of mailing list archives and PDFs trying to >> dig deeper into the IOMMU/PCI passthrough stuff and I want to give the >> graphics passthrough situation a shot myself. Sadly it is very confusing >> to read about the different setups and hardware environments with both >> positive and negative results. Also the patchsets and versions everybody >> is talking about do not make it any easier :) >> >> My current questions would be: >> - is the combination of JF git kernel with xen-unstable the right way to >> go for this setup? Or should I perhaps use older xen version and apply >> some patchset? I think some of those >> patches were applied in >> xen-unstable already but I am not quite sure... >> >> - does anyone have hints or clarification regarding the Xorg problem on >> dom0? As I said there are no eye-catching log entries or errors except >> the Xorg backtrace at the end of the log file (posted to list before). >> This happens regardless of which driver I enable (vesa/nv/nouveau). The >> nvidia binary driver compiles without problems and seems to come up but >> only gives me a black screen and also locks the vtys. >> >> >> Thanks to the great help, reports and instructions Boris and others! >> >> Mark >> >> >> -----Inline Attachment Follows----- >> >> -- >> Fedora-xen mailing list >> Fedora-xen@redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> >> >> >> >> >> >> -----Inline Attachment Follows----- >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > > > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel [-- Attachment #1.2: Type: text/html, Size: 25898 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Xen-devel] Re: Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
@ 2009-09-08 13:31 Boris Derzhavets
2009-09-08 15:20 ` Re: [Fedora-xen] " Boris Derzhavets
2009-09-08 15:26 ` Pasi Kärkkäinen
0 siblings, 2 replies; 18+ messages in thread
From: Boris Derzhavets @ 2009-09-08 13:31 UTC (permalink / raw)
To: Mark Schloesser; +Cc: xen-devel, fedora-xen
[-- Attachment #1.1: Type: text/plain, Size: 2457 bytes --]
I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:-
title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)
root (hd1,0)
kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1
module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen
module /initrd-2.6.31-rc8.img
Then disconnected NUL modem cable and loaded Dom0 via :
title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)
root (hd1,0)
kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1
module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen
module /initrd-2.6.31-rc8.img
Usual Grub entry drops console to stack trace.
Dmesg output is attached.
Boris.
--- On Tue, 9/8/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote:
From: Mark Schloesser <mark.schloesser@rwth-aachen.de>
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: fedora-xen@redhat.com
Date: Tuesday, September 8, 2009, 8:13 AM
Top commit in my checkout is:
commit 3b316bf67dcbe550e648703475e811fc0cedc705
Merge: 226206a 27a3a52
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date: Thu Sep 3 16:25:12 2009 -0700
Mark
Boris Derzhavets wrote:
> Yep ;)
>
> Please, run
> # git log|more
> in linux-2.6-xen ( obtained via git clone).
> I am wondering what was the top commit for good build 2.6.31-rc8
> I am trying to bisect.
>
> Boris.
>
>
> --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote:
>
> From: Mark Schloesser <mark.schloesser@rwth-aachen.de>
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com
> 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
>
>
>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 3704 bytes --]
[-- Attachment #2: dmesg.log.gz --]
[-- Type: application/x-gzip, Size: 11693 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-08 13:31 [Xen-devel] " Boris Derzhavets @ 2009-09-08 15:20 ` Boris Derzhavets 2009-09-08 15:45 ` Boris Derzhavets 2009-09-08 15:26 ` Pasi Kärkkäinen 1 sibling, 1 reply; 18+ messages in thread From: Boris Derzhavets @ 2009-09-08 15:20 UTC (permalink / raw) To: Mark Schloesser; +Cc: xen-devel, fedora-xen [-- Attachment #1.1: Type: text/plain, Size: 3298 bytes --] That's a working grub entry : title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) root (hd1,0) kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen module /initrd-2.6.31-rc8.img B. --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com Date: Tuesday, September 8, 2009, 9:31 AM I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) root (hd1,0) kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen module /initrd-2.6.31-rc8.img Then disconnected NUL modem cable and loaded Dom0 via : title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) root (hd1,0) kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen module /initrd-2.6.31-rc8.img Usual Grub entry drops console to stack trace. Dmesg output is attached. Boris. --- On Tue, 9/8/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: From: Mark Schloesser <mark.schloesser@rwth-aachen.de> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: fedora-xen@redhat.com Date: Tuesday, September 8, 2009, 8:13 AM Top commit in my checkout is: commit 3b316bf67dcbe550e648703475e811fc0cedc705 Merge: 226206a 27a3a52 Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Date: Thu Sep 3 16:25:12 2009 -0700 Mark Boris Derzhavets wrote: > Yep ;) > > Please, run > # git log|more > in linux-2.6-xen ( obtained via git clone). > I am wondering what was the top commit for good build 2.6.31-rc8 > I am trying to bisect. > > Boris. > > > --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > Date: Sunday, September 6, 2009, 12:17 PM > > I am on standard F11, using a fresh install and then updated all > packages before doing anything xen related. Xen build was done with > current xen-unstable checkout using only "xen" and "tools" build > targets. I have no libvirt or libvirt-preview currently. My Xorg still > does not want to come up btw :) > > Do you need anything else? > > Mark > > > > > > > -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen [-- Attachment #1.2: Type: text/html, Size: 4831 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-08 15:20 ` Re: [Fedora-xen] " Boris Derzhavets @ 2009-09-08 15:45 ` Boris Derzhavets 2009-09-08 16:17 ` Pasi Kärkkäinen 0 siblings, 1 reply; 18+ messages in thread From: Boris Derzhavets @ 2009-09-08 15:45 UTC (permalink / raw) To: Mark Schloesser; +Cc: xen-devel, fedora-xen [-- Attachment #1.1: Type: text/plain, Size: 4136 bytes --] 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 <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com Date: Tuesday, September 8, 2009, 11:20 AM That's a working grub entry : title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) root (hd1,0) kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen module /initrd-2.6.31-rc8.img B. --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com Date: Tuesday, September 8, 2009, 9:31 AM I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) root (hd1,0) kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen module /initrd-2.6.31-rc8.img Then disconnected NUL modem cable and loaded Dom0 via : title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) root (hd1,0) kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen module /initrd-2.6.31-rc8.img Usual Grub entry drops console to stack trace. Dmesg output is attached. Boris. --- On Tue, 9/8/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: From: Mark Schloesser <mark.schloesser@rwth-aachen.de> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: fedora-xen@redhat.com Date: Tuesday, September 8, 2009, 8:13 AM Top commit in my checkout is: commit 3b316bf67dcbe550e648703475e811fc0cedc705 Merge: 226206a 27a3a52 Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Date: Thu Sep 3 16:25:12 2009 -0700 Mark Boris Derzhavets wrote: > Yep ;) > > Please, run > # git log|more > in linux-2.6-xen ( obtained via git clone). > I am wondering what was the top commit for good build 2.6.31-rc8 > I am trying to bisect. > > Boris. > > > --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > Date: Sunday, September 6, 2009, 12:17 PM > > I am on standard F11, using a fresh install and then updated all > packages before doing anything xen related. Xen build was done with > current xen-unstable checkout using only "xen" and "tools" build > targets. I have no libvirt or libvirt-preview currently. My Xorg still > does not want to come up btw :) > > Do you need anything else? > > Mark > > > > > > > -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen [-- Attachment #1.2: Type: text/html, Size: 6350 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-08 15:45 ` Boris Derzhavets @ 2009-09-08 16:17 ` Pasi Kärkkäinen 2009-09-08 17:38 ` Boris Derzhavets 0 siblings, 1 reply; 18+ messages in thread From: Pasi Kärkkäinen @ 2009-09-08 16:17 UTC (permalink / raw) To: Boris Derzhavets; +Cc: xen-devel, fedora-xen, Mark Schloesser On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > Finally, > > title Xen 3.4.1 Fedora 12 (2.6.31-rc8 ) (/dev/sdb1) > > root (hd1,0) > > kernel /xen-3.4.1.gz dom0_mem=1024M > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > module /initrd-2.6.31-rc8.img > > I have to specify dom0_mem, otherwise stack trace. > Hmm... what kind of stack trace you get without dom0_mem specified? -- Pasi > > --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > From: Boris Derzhavets <bderzhavets@yahoo.com> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > Date: Tuesday, September 8, 2009, 11:20 AM > > That's a working grub entry : > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > root (hd1,0) > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen > module /initrd-2.6.31-rc8.img > > B. > > --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > From: Boris Derzhavets <bderzhavets@yahoo.com> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > Date: Tuesday, September 8, 2009, 9:31 > AM > > I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > root (hd1,0) > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen > module /initrd-2.6.31-rc8.img > > Then disconnected NUL modem cable and loaded Dom0 via : > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > root (hd1,0) > kernel /xen-3.4.1.gz > dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen > module /initrd-2.6.31-rc8.img > > Usual > Grub entry drops console to stack trace. > Dmesg output is attached. > > Boris. > --- On Tue, 9/8/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: fedora-xen@redhat.com > Date: Tuesday, September 8, 2009, 8:13 AM > > Top commit in my checkout is: > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > Merge: 226206a 27a3a52 > Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> > Date: Thu Sep 3 16:25:12 2009 > -0700 > > Mark > > > Boris Derzhavets wrote: > > Yep ;) > > > > Please, run > > # git log|more > > in linux-2.6-xen ( obtained via git clone). > > I am wondering what was the top commit for good build 2.6.31-rc8 > > I am trying to bisect. > > > > Boris. > > > > > > --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > Date: Sunday, September 6, 2009, 12:17 PM > > > > I am on standard F11, using a fresh install and then updated all > > packages > before doing anything xen related. Xen build was done with > > current xen-unstable checkout using only "xen" and "tools" build > > targets. I have no libvirt or libvirt-preview currently. My Xorg still > > does not want to come up btw :) > > > > Do you need anything else? > > > > Mark > > > > > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > -----Inline Attachment Follows----- > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-08 16:17 ` Pasi Kärkkäinen @ 2009-09-08 17:38 ` Boris Derzhavets 2009-09-08 17:47 ` Pasi Kärkkäinen 0 siblings, 1 reply; 18+ messages in thread From: Boris Derzhavets @ 2009-09-08 17:38 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: Mark Schloesser, xen-devel, fedora-xen [-- Attachment #1.1: Type: text/plain, Size: 6040 bytes --] 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 <pasik@iki.fi> wrote: From: Pasi Kärkkäinen <pasik@iki.fi> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen.de> Date: Tuesday, September 8, 2009, 12:17 PM On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > Finally, > > title Xen 3.4.1 Fedora 12 (2.6.31-rc8 ) (/dev/sdb1) > > root (hd1,0) > > kernel /xen-3.4.1.gz dom0_mem=1024M > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > module /initrd-2.6.31-rc8.img > > I have to specify dom0_mem, otherwise stack trace. > Hmm... what kind of stack trace you get without dom0_mem specified? -- Pasi > > --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > From: Boris Derzhavets <bderzhavets@yahoo.com> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > Date: Tuesday, September 8, 2009, 11:20 AM > > That's a working grub entry : > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > root (hd1,0) > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen > module /initrd-2.6.31-rc8.img > > B. > > --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > From: Boris Derzhavets <bderzhavets@yahoo.com> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > Date: Tuesday, September 8, 2009, 9:31 > AM > > I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > root (hd1,0) > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen > module /initrd-2.6.31-rc8.img > > Then disconnected NUL modem cable and loaded Dom0 via : > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > root (hd1,0) > kernel /xen-3.4.1.gz > dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen > module /initrd-2.6.31-rc8.img > > Usual > Grub entry drops console to stack trace. > Dmesg output is attached. > > Boris. > --- On Tue, 9/8/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: fedora-xen@redhat.com > Date: Tuesday, September 8, 2009, 8:13 AM > > Top commit in my checkout is: > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > Merge: 226206a 27a3a52 > Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> > Date: Thu Sep 3 16:25:12 2009 > -0700 > > Mark > > > Boris Derzhavets wrote: > > Yep ;) > > > > Please, run > > # git log|more > > in linux-2.6-xen ( obtained via git clone). > > I am wondering what was the top commit for good build 2.6.31-rc8 > > I am trying to bisect. > > > > Boris. > > > > > > --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > Date: Sunday, September 6, 2009, 12:17 PM > > > > I am on standard F11, using a fresh install and then updated all > > packages > before doing anything xen related. Xen build was done with > > current xen-unstable checkout using only "xen" and "tools" build > > targets. I have no libvirt or libvirt-preview currently. My Xorg still > > does not want to come up btw :) > > > > Do you need anything else? > > > > Mark > > > > > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > -----Inline Attachment Follows----- > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel [-- Attachment #1.2: Type: text/html, Size: 11078 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-08 17:38 ` Boris Derzhavets @ 2009-09-08 17:47 ` Pasi Kärkkäinen 2009-09-08 18:13 ` Boris Derzhavets 2009-09-08 18:46 ` Boris Derzhavets 0 siblings, 2 replies; 18+ messages in thread From: Pasi Kärkkäinen @ 2009-09-08 17:47 UTC (permalink / raw) To: Boris Derzhavets; +Cc: Mark Schloesser, xen-devel, fedora-xen On Tue, Sep 08, 2009 at 10:38:08AM -0700, Boris Derzhavets wrote: > Call trace: OK. How much memory you have? Does it happen with dom0_mem=2048M? Does it happen with dom0_mem=4096M? -- Pasi > > > > > > > > usb_hc_died + ..... > > > > usb_add_hcd +..... > > > > usb_hcd_pci_probe + .... > > > > do_work_for_cpu + ..... > > > > local_pci_probe + ... > > > > do_work_for_cpu +..... > > > > kthread +..... > > > > child_rip+.... > > > > restore_args + ..... > > > > child_rip + ..... > > > > Code : > . . . . > > > > . . . . > > > > > > > > RIP [<ffff...c7>] usb_kick_khubd + 0x10/0x25 > > > > RSP < ffff ... e0> > > > > CR2: 00000...098 > > > > > > > > ---[ end trace 8219......]---- > > > > > > > > uhci_hcd 0000:00:1a:0 host controller process error, something bad > > > > happened ! > > > > uhci_hcd 0000:00:1a:0 host controller halted , very bad > > > > uhci_hcd 0000:00:1a:0 HC died, cleaning up > > > --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > From: Pasi Kärkkäinen <pasik@iki.fi> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > Date: Tuesday, September 8, 2009, 12:17 PM > > On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > > Finally, > > > > title Xen 3.4.1 Fedora 12 (2.6.31-rc8 ) (/dev/sdb1) > > > > root (hd1,0) > > > > kernel /xen-3.4.1.gz dom0_mem=1024M > > > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > > > module /initrd-2.6.31-rc8.img > > > > I have to specify dom0_mem, otherwise stack trace. > > > > Hmm... what kind of stack trace you get without dom0_mem specified? > > -- Pasi > > > > > --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > > > From: Boris Derzhavets <bderzhavets@yahoo.com> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > Date: Tuesday, September 8, 2009, 11:20 AM > > > > That's a working grub entry : > > > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > > root (hd1,0) > > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen > > module /initrd-2.6.31-rc8.img > > > > B. > > > > --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > > > From: Boris Derzhavets <bderzhavets@yahoo.com> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > Date: Tuesday, September 8, 2009, 9:31 > > AM > > > > I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- > > > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > > root (hd1,0) > > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen > > module /initrd-2.6.31-rc8.img > > > > Then disconnected NUL modem cable and loaded Dom0 via : > > > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > > root (hd1,0) > > kernel /xen-3.4.1.gz > > dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen > > module /initrd-2.6.31-rc8.img > > > > Usual > > Grub entry drops console to stack trace. > > Dmesg output is attached. > > > > Boris. > > --- On Tue, 9/8/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > Cc: fedora-xen@redhat.com > > Date: Tuesday, September 8, 2009, 8:13 AM > > > > Top commit in my checkout is: > > > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > > Merge: 226206a 27a3a52 > > Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> > > Date: Thu Sep 3 16:25:12 2009 > > -0700 > > > > Mark > > > > > > Boris Derzhavets wrote: > > > Yep ;) > > > > > > Please, run > > > # git log|more > > > in linux-2.6-xen ( obtained via git clone). > > > I am wondering what was the top commit for good build 2.6.31-rc8 > > > I am trying to bisect. > > > > > > Boris. > > > > > > > > > --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > > > > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > > Date: Sunday, September 6, 2009, 12:17 PM > > > > > > I am on standard F11, using a fresh install and then updated all > > > packages > > before doing anything xen related. Xen build was done with > > > current xen-unstable checkout using only "xen" and "tools" build > > > targets. I have no libvirt or libvirt-preview currently. My Xorg still > > > does not want to come up btw :) > > > > > > Do you need anything else? > > > > > > Mark > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > > > -- > > Fedora-xen mailing list > > Fedora-xen@redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > > -----Inline Attachment Follows----- > > > > -- > > Fedora-xen mailing list > > Fedora-xen@redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > > > ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-08 17:47 ` Pasi Kärkkäinen @ 2009-09-08 18:13 ` Boris Derzhavets 2009-09-08 18:46 ` Boris Derzhavets 1 sibling, 0 replies; 18+ messages in thread From: Boris Derzhavets @ 2009-09-08 18:13 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: xen-devel, fedora-xen, Mark Schloesser [-- Attachment #1.1: Type: text/plain, Size: 7228 bytes --] 8 GB Ram. I will check dom0_mem=? Boris. --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@iki.fi> wrote: From: Pasi Kärkkäinen <pasik@iki.fi> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: "Mark Schloesser" <mark.schloesser@rwth-aachen.de>, xen-devel@lists.xensource.com, fedora-xen@redhat.com Date: Tuesday, September 8, 2009, 1:47 PM On Tue, Sep 08, 2009 at 10:38:08AM -0700, Boris Derzhavets wrote: > Call trace: OK. How much memory you have? Does it happen with dom0_mem=2048M? Does it happen with dom0_mem=4096M? -- Pasi > > > > > > > > usb_hc_died + ..... > > > > usb_add_hcd +..... > > > > usb_hcd_pci_probe + .... > > > > do_work_for_cpu + ..... > > > > local_pci_probe + ... > > > > do_work_for_cpu +..... > > > > kthread +..... > > > > child_rip+.... > > > > restore_args + ..... > > > > child_rip + ..... > > > > Code : > . . . . > > > > . . . . > > > > > > > > RIP [<ffff...c7>] usb_kick_khubd + 0x10/0x25 > > > > RSP < ffff ... e0> > > > > CR2: 00000...098 > > > > > > > > ---[ end trace 8219......]---- > > > > > > > > uhci_hcd 0000:00:1a:0 host controller process error, something bad > > > > happened ! > > > > uhci_hcd 0000:00:1a:0 host controller halted , very bad > > > > uhci_hcd 0000:00:1a:0 HC died, cleaning up > > > --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > From: Pasi Kärkkäinen <pasik@iki.fi> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > Date: Tuesday, September 8, 2009, 12:17 PM > > On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > > Finally, > > > > title Xen 3.4.1 Fedora 12 (2.6.31-rc8 ) (/dev/sdb1) > > > > root (hd1,0) > > > > kernel /xen-3.4.1.gz dom0_mem=1024M > > > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > > > module /initrd-2.6.31-rc8.img > > > > I have to specify dom0_mem, otherwise stack trace. > > > > Hmm... what kind of stack trace you get without dom0_mem specified? > > -- Pasi > > > > > --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > > > From: Boris Derzhavets <bderzhavets@yahoo.com> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > Date: Tuesday, September 8, 2009, 11:20 AM > > > > That's a working grub entry : > > > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > > root (hd1,0) > > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen > > module /initrd-2.6.31-rc8.img > > > > B. > > > > --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > > > From: Boris Derzhavets <bderzhavets@yahoo.com> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > Date: Tuesday, September 8, 2009, 9:31 > > AM > > > > I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- > > > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > > root (hd1,0) > > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen > > module /initrd-2.6.31-rc8.img > > > > Then disconnected NUL modem cable and loaded Dom0 via : > > > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > > root (hd1,0) > > kernel /xen-3.4.1.gz > > dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen > > module /initrd-2.6.31-rc8.img > > > > Usual > > Grub entry drops console to stack trace. > > Dmesg output is attached. > > > > Boris. > > --- On Tue, 9/8/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > Cc: fedora-xen@redhat.com > > Date: Tuesday, September 8, 2009, 8:13 AM > > > > Top commit in my checkout is: > > > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > > Merge: 226206a 27a3a52 > > Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> > > Date: Thu Sep 3 16:25:12 2009 > > -0700 > > > > Mark > > > > > > Boris Derzhavets wrote: > > > Yep ;) > > > > > > Please, run > > > # git log|more > > > in linux-2.6-xen ( obtained via git clone). > > > I am wondering what was the top commit for good build 2.6.31-rc8 > > > I am trying to bisect. > > > > > > Boris. > > > > > > > > > --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > > > > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > > Date: Sunday, September 6, 2009, 12:17 PM > > > > > > I am on standard F11, using a fresh install and then updated all > > > packages > > before doing anything xen related. Xen build was done with > > > current xen-unstable checkout using only "xen" and "tools" build > > > targets. I have no libvirt or libvirt-preview currently. My Xorg still > > > does not want to come up btw :) > > > > > > Do you need anything else? > > > > > > Mark > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > > > -- > > Fedora-xen mailing list > > Fedora-xen@redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > > -----Inline Attachment Follows----- > > > > -- > > Fedora-xen mailing list > > Fedora-xen@redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > > > _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel [-- Attachment #1.2: Type: text/html, Size: 13430 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-08 17:47 ` Pasi Kärkkäinen 2009-09-08 18:13 ` Boris Derzhavets @ 2009-09-08 18:46 ` Boris Derzhavets 2009-09-08 18:49 ` Pasi Kärkkäinen 1 sibling, 1 reply; 18+ messages in thread From: Boris Derzhavets @ 2009-09-08 18:46 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: Mark Schloesser, xen-devel, fedora-xen [-- Attachment #1.1: Type: text/plain, Size: 7087 bytes --] System boots up with dom0_mem=4096M. Boris. --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@iki.fi> wrote: From: Pasi Kärkkäinen <pasik@iki.fi> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen.de> Date: Tuesday, September 8, 2009, 1:47 PM On Tue, Sep 08, 2009 at 10:38:08AM -0700, Boris Derzhavets wrote: > Call trace: OK. How much memory you have? Does it happen with dom0_mem=2048M? Does it happen with dom0_mem=4096M? -- Pasi > > > > > > > > usb_hc_died + ..... > > > > usb_add_hcd +..... > > > > usb_hcd_pci_probe + .... > > > > do_work_for_cpu + ..... > > > > local_pci_probe + ... > > > > do_work_for_cpu +..... > > > > kthread +..... > > > > child_rip+.... > > > > restore_args + ..... > > > > child_rip + ..... > > > > Code : > . . . . > > > > . . . . > > > > > > > > RIP [<ffff...c7>] usb_kick_khubd + 0x10/0x25 > > > > RSP < ffff ... e0> > > > > CR2: 00000...098 > > > > > > > > ---[ end trace 8219......]---- > > > > > > > > uhci_hcd 0000:00:1a:0 host controller process error, something bad > > > > happened ! > > > > uhci_hcd 0000:00:1a:0 host controller halted , very bad > > > > uhci_hcd 0000:00:1a:0 HC died, cleaning up > > > --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > From: Pasi Kärkkäinen <pasik@iki.fi> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > Date: Tuesday, September 8, 2009, 12:17 PM > > On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > > Finally, > > > > title Xen 3.4.1 Fedora 12 (2.6.31-rc8 ) (/dev/sdb1) > > > > root (hd1,0) > > > > kernel /xen-3.4.1.gz dom0_mem=1024M > > > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > > > module /initrd-2.6.31-rc8.img > > > > I have to specify dom0_mem, otherwise stack trace. > > > > Hmm... what kind of stack trace you get without dom0_mem specified? > > -- Pasi > > > > > --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > > > From: Boris Derzhavets <bderzhavets@yahoo.com> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > Date: Tuesday, September 8, 2009, 11:20 AM > > > > That's a working grub entry : > > > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > > root (hd1,0) > > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen > > module /initrd-2.6.31-rc8.img > > > > B. > > > > --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > > > From: Boris Derzhavets <bderzhavets@yahoo.com> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > Date: Tuesday, September 8, 2009, 9:31 > > AM > > > > I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- > > > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > > root (hd1,0) > > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen > > module /initrd-2.6.31-rc8.img > > > > Then disconnected NUL modem cable and loaded Dom0 via : > > > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > > root (hd1,0) > > kernel /xen-3.4.1.gz > > dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen > > module /initrd-2.6.31-rc8.img > > > > Usual > > Grub entry drops console to stack trace. > > Dmesg output is attached. > > > > Boris. > > --- On Tue, 9/8/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > Cc: fedora-xen@redhat.com > > Date: Tuesday, September 8, 2009, 8:13 AM > > > > Top commit in my checkout is: > > > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > > Merge: 226206a 27a3a52 > > Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> > > Date: Thu Sep 3 16:25:12 2009 > > -0700 > > > > Mark > > > > > > Boris Derzhavets wrote: > > > Yep ;) > > > > > > Please, run > > > # git log|more > > > in linux-2.6-xen ( obtained via git clone). > > > I am wondering what was the top commit for good build 2.6.31-rc8 > > > I am trying to bisect. > > > > > > Boris. > > > > > > > > > --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > > > > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > > Date: Sunday, September 6, 2009, 12:17 PM > > > > > > I am on standard F11, using a fresh install and then updated all > > > packages > > before doing anything xen related. Xen build was done with > > > current xen-unstable checkout using only "xen" and "tools" build > > > targets. I have no libvirt or libvirt-preview currently. My Xorg still > > > does not want to come up btw :) > > > > > > Do you need anything else? > > > > > > Mark > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > > > -- > > Fedora-xen mailing list > > Fedora-xen@redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > > -----Inline Attachment Follows----- > > > > -- > > Fedora-xen mailing list > > Fedora-xen@redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > > > [-- Attachment #1.2: Type: text/html, Size: 13104 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-08 18:46 ` Boris Derzhavets @ 2009-09-08 18:49 ` Pasi Kärkkäinen 2009-09-08 19:14 ` Boris Derzhavets 0 siblings, 1 reply; 18+ messages in thread From: Pasi Kärkkäinen @ 2009-09-08 18:49 UTC (permalink / raw) To: Boris Derzhavets; +Cc: Mark Schloesser, xen-devel, fedora-xen On Tue, Sep 08, 2009 at 11:46:05AM -0700, Boris Derzhavets wrote: > System boots up with dom0_mem=4096M. > Does it boot up with dom0_mem=4097M ? How about dom0_mem=6144M ? -- Pasi > Boris. > > --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > From: Pasi Kärkkäinen <pasik@iki.fi> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > Date: Tuesday, September 8, 2009, 1:47 PM > > On Tue, Sep 08, 2009 at 10:38:08AM -0700, Boris Derzhavets wrote: > > Call trace: > > > OK. How much memory you have? > > Does it happen with dom0_mem=2048M? Does it happen with dom0_mem=4096M? > > -- Pasi > > > > > > > > > > > usb_hc_died + ..... > > > > > usb_add_hcd +..... > > > > > usb_hcd_pci_probe + .... > > > > > do_work_for_cpu + ..... > > > > > local_pci_probe + ... > > > > > do_work_for_cpu +..... > > > > > kthread +..... > > > > > child_rip+.... > > > > > restore_args + ..... > > > > > child_rip + ..... > > > > > Code : > > . . . . > > > > > . . . . > > > > > > > > > > RIP [<ffff...c7>] usb_kick_khubd + 0x10/0x25 > > > > > RSP < ffff ... e0> > > > > > CR2: 00000...098 > > > > > > > > > > ---[ end trace 8219......]---- > > > > > > > > > > uhci_hcd 0000:00:1a:0 host controller process error, something bad > > > > > happened ! > > > > > uhci_hcd 0000:00:1a:0 host controller halted , very bad > > > > > uhci_hcd 0000:00:1a:0 HC died, cleaning up > > > > > > --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > > > From: Pasi Kärkkäinen <pasik@iki.fi> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > > Date: Tuesday, September 8, 2009, 12:17 PM > > > > On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > > > Finally, > > > > > > title Xen 3.4.1 Fedora 12 (2.6.31-rc8 ) (/dev/sdb1) > > > > > > root (hd1,0) > > > > > > kernel /xen-3.4.1.gz dom0_mem=1024M > > > > > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > > > > > module /initrd-2.6.31-rc8.img > > > > > > I have to specify dom0_mem, otherwise stack trace. > > > > > > > Hmm... what kind of stack trace you get without dom0_mem specified? > > > > -- Pasi > > > > > > > > --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > > > > > From: Boris Derzhavets <bderzhavets@yahoo.com> > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > > Date: Tuesday, September 8, 2009, 11:20 AM > > > > > > That's a working grub entry : > > > > > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > > > root (hd1,0) > > > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all > > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen > > > module /initrd-2.6.31-rc8.img > > > > > > B. > > > > > > --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > > > > > From: Boris Derzhavets <bderzhavets@yahoo.com> > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > > Date: Tuesday, September 8, 2009, 9:31 > > > AM > > > > > > I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- > > > > > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > > > root (hd1,0) > > > kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 > > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen > > > module /initrd-2.6.31-rc8.img > > > > > > Then disconnected NUL modem cable and loaded Dom0 via : > > > > > > title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) > > > root (hd1,0) > > > kernel /xen-3.4.1.gz > > > dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 > > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen > > > module /initrd-2.6.31-rc8.img > > > > > > Usual > > > Grub entry drops console to stack trace. > > > Dmesg output is attached. > > > > > > Boris. > > > --- On Tue, 9/8/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > > > > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > > Cc: fedora-xen@redhat.com > > > Date: Tuesday, September 8, 2009, 8:13 AM > > > > > > Top commit in my checkout is: > > > > > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > > > Merge: 226206a 27a3a52 > > > Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> > > > Date: Thu Sep 3 16:25:12 2009 > > > -0700 > > > > > > Mark > > > > > > > > > Boris Derzhavets wrote: > > > > Yep ;) > > > > > > > > Please, run > > > > # git log|more > > > > in linux-2.6-xen ( obtained via git clone). > > > > I am wondering what was the top commit for good build 2.6.31-rc8 > > > > I am trying to bisect. > > > > > > > > Boris. > > > > > > > > > > > > --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > > > > > > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > > > Date: Sunday, September 6, 2009, 12:17 PM > > > > > > > > I am on standard F11, using a fresh install and then updated all > > > > packages > > > before doing anything xen related. Xen build was done with > > > > current xen-unstable checkout using only "xen" and "tools" build > > > > targets. I have no libvirt or libvirt-preview currently. My Xorg still > > > > does not want to come up btw :) > > > > > > > > Do you need anything else? > > > > > > > > Mark > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > > > > > -- > > > Fedora-xen mailing list > > > Fedora-xen@redhat.com > > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > > > > > -- > > > Fedora-xen mailing list > > > Fedora-xen@redhat.com > > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > > > > > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.xensource.com > > > http://lists.xensource.com/xen-devel > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > > > > > > > > > > > ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-08 18:49 ` Pasi Kärkkäinen @ 2009-09-08 19:14 ` Boris Derzhavets 0 siblings, 0 replies; 18+ messages in thread From: Boris Derzhavets @ 2009-09-08 19:14 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: xen-devel, fedora-xen, Mark Schloesser [-- Attachment #1.1: Type: text/plain, Size: 3152 bytes --] Console drops into the same stack trace in both cases. Boris. --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@iki.fi> wrote: From: Pasi Kärkkäinen <pasik@iki.fi> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: "Mark Schloesser" <mark.schloesser@rwth-aachen.de>, xen-devel@lists.xensource.com, fedora-xen@redhat.com Date: Tuesday, September 8, 2009, 2:49 PM On Tue, Sep 08, 2009 at 11:46:05AM -0700, Boris Derzhavets wrote: > System boots up with dom0_mem=4096M. > Does it boot up with dom0_mem=4097M ? How about dom0_mem=6144M ? -- Pasi > Boris. > > --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > From: Pasi Kärkkäinen <pasik@iki.fi> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > Date: Tuesday, September 8, 2009, 1:47 PM > > On Tue, Sep 08, 2009 at 10:38:08AM -0700, Boris Derzhavets wrote: > > Call trace: > > > OK. How much memory you have? > > Does it happen with dom0_mem=2048M? Does it happen with dom0_mem=4096M? > > -- Pasi > > > > > > > > > > > usb_hc_died + ..... > > > > > usb_add_hcd +..... > > > > > usb_hcd_pci_probe + .... > > > > > do_work_for_cpu + ..... > > > > > local_pci_probe + ... > > > > > do_work_for_cpu +..... > > > > > kthread +..... > > > > > child_rip+.... > > > > > restore_args + ..... > > > > > child_rip + ..... > > > > > Code : > > . . . . > > > > > . . . . > > > > > > > > > > RIP [<ffff...c7>] usb_kick_khubd + 0x10/0x25 > > > > > RSP < ffff ... e0> > > > > > CR2: 00000...098 > > > > > > > > > > ---[ end trace 8219......]---- > > > > > > > > > > uhci_hcd 0000:00:1a:0 host controller process error, something bad > > > > > happened ! > > > > > uhci_hcd 0000:00:1a:0 host controller halted , very bad > > > > > uhci_hcd 0000:00:1a:0 HC died, cleaning up > > > > > > --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > > > From: Pasi Kärkkäinen <pasik@iki.fi> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com, "Mark Schloesser" <mark.schloesser@rwth-aachen.de> > > 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 [-- Attachment #1.2: Type: text/html, Size: 5793 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-08 13:31 [Xen-devel] " Boris Derzhavets 2009-09-08 15:20 ` Re: [Fedora-xen] " Boris Derzhavets @ 2009-09-08 15:26 ` Pasi Kärkkäinen 2009-09-08 15:47 ` Boris Derzhavets 1 sibling, 1 reply; 18+ messages in thread From: Pasi Kärkkäinen @ 2009-09-08 15:26 UTC (permalink / raw) To: Boris Derzhavets; +Cc: xen-devel, fedora-xen, Mark Schloesser 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 <mark.schloesser@rwth-aachen.de> wrote: > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: fedora-xen@redhat.com > Date: Tuesday, September 8, 2009, 8:13 AM > > Top commit in my checkout is: > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > Merge: 226206a 27a3a52 > Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> > Date: Thu Sep 3 16:25:12 2009 -0700 > > Mark > > > Boris Derzhavets wrote: > > Yep ;) > > > > Please, run > > # git log|more > > in linux-2.6-xen ( obtained via git clone). > > I am wondering what was the top commit for good build 2.6.31-rc8 > > I am trying to bisect. > > > > Boris. > > > > > > --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > 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 > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable 2009-09-08 15:26 ` Pasi Kärkkäinen @ 2009-09-08 15:47 ` Boris Derzhavets 0 siblings, 0 replies; 18+ messages in thread From: Boris Derzhavets @ 2009-09-08 15:47 UTC (permalink / raw) To: Pasi Kärkkäinen; +Cc: xen-devel, fedora-xen, Mark Schloesser [-- Attachment #1.1: Type: text/plain, Size: 3321 bytes --] I've just understood. I cannot remove dom0-mem only. Thanks Boris --- On Tue, 9/8/09, Pasi Kärkkäinen <pasik@iki.fi> wrote: From: Pasi Kärkkäinen <pasik@iki.fi> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: "Mark Schloesser" <mark.schloesser@rwth-aachen.de>, xen-devel@lists.xensource.com, fedora-xen@redhat.com 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 <mark.schloesser@rwth-aachen.de> wrote: > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > Cc: fedora-xen@redhat.com > Date: Tuesday, September 8, 2009, 8:13 AM > > Top commit in my checkout is: > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > Merge: 226206a 27a3a52 > Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> > Date: Thu Sep 3 16:25:12 2009 -0700 > > Mark > > > Boris Derzhavets wrote: > > Yep ;) > > > > Please, run > > # git log|more > > in linux-2.6-xen ( obtained via git clone). > > I am wondering what was the top commit for good build 2.6.31-rc8 > > I am trying to bisect. > > > > Boris. > > > > > > --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser@rwth-aachen.de> wrote: > > > > From: Mark Schloesser <mark.schloesser@rwth-aachen.de> > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com > > 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 > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel [-- Attachment #1.2: Type: text/html, Size: 5541 bytes --] [-- Attachment #2: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2009-09-08 19:14 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <4AA12398.1010300@rwth-aachen.de>
2009-09-04 18:02 ` [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable Boris Derzhavets
2009-09-04 20:09 ` Jeremy Fitzhardinge
2009-09-05 10:14 ` Boris Derzhavets
2009-09-06 15:09 ` [Xen-devel] " Mark Schloesser
2009-09-06 15:49 ` Re: [Fedora-xen] " Boris Derzhavets
2009-09-06 16:17 ` [Xen-devel] " Mark Schloesser
2009-09-06 16:41 ` Re: [Fedora-xen] " Boris Derzhavets
2009-09-08 13:31 [Xen-devel] " Boris Derzhavets
2009-09-08 15:20 ` Re: [Fedora-xen] " Boris Derzhavets
2009-09-08 15:45 ` Boris Derzhavets
2009-09-08 16:17 ` Pasi Kärkkäinen
2009-09-08 17:38 ` Boris Derzhavets
2009-09-08 17:47 ` Pasi Kärkkäinen
2009-09-08 18:13 ` Boris Derzhavets
2009-09-08 18:46 ` Boris Derzhavets
2009-09-08 18:49 ` Pasi Kärkkäinen
2009-09-08 19:14 ` Boris Derzhavets
2009-09-08 15:26 ` Pasi Kärkkäinen
2009-09-08 15:47 ` Boris Derzhavets
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.