WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: Xen Still hangs up when insmod xenbus.ko. Re: [Xen-devel] Unmodified

To: Liang Yang <multisyncfe991@xxxxxxxxxxx>
Subject: Re: Xen Still hangs up when insmod xenbus.ko. Re: [Xen-devel] Unmodified_drivers modules broke again for 3.0.4?
From: Kurt Hackel <kurt.hackel@xxxxxxxxxx>
Date: Fri, 26 Jan 2007 18:43:52 -0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Delivery-date: Fri, 26 Jan 2007 18:43:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <BAY125-DAV87729DA9D208116E74A3793BC0@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1168083889.4942.6.camel@xxxxxxxxxxxxxxxxxxxxx> <BAY125-DAV87729DA9D208116E74A3793BC0@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11
Hi,

Just wondering if anyone made any progress on this.  I hit the same
problem when loading xenbus.ko built for RHEL4 U4 and xen 3.0.4.1.  Doesn't
lock up the guest, but the modprobe hangs after it gets into read_reply().

Host is x86_64 running 3.0.4.1 and the standard 2.6.16 dom0.  Guest is
x86_64 hvm with RHEL4 U4.

Here's a stack trace:
modprobe      D 000001006b5f1e58     0  3675   3546                3639
(NOTLB) 
000001006b5f1d58 0000000000000006 000001006b5f1ca8 ffffffffa0158fb0
       000000000000004d ffffffffa0158ff0 0000000000000080
0000000100000000
       00000100759f8030 00000000007766af
Call Trace:
       <ffffffff80138542>{printk+141} 
       <ffffffffa015555e>{:xenbus:read_reply+202}
       <ffffffff80135746>{autoremove_wake_function+0} 
       <ffffffff80135746>{autoremove_wake_function+0}
       <ffffffffa0155870>{:xenbus:xs_talkv+241} 
       <ffffffffa01559c0>{:xenbus:xs_single+95}
       <ffffffffa0155bcc>{:xenbus:xenbus_directory+88} 
       <ffffffffa0157897>{:xenbus:xenbus_probe_devices+67}
       <ffffffff801ea63d>{__up_write+20} 
       <ffffffffa0157dbc>{:xenbus:xenbus_probe+61}
       <ffffffffa016310f>{:xenbus:xenbus_probe_init+271} 
       <ffffffff8014fd37>{sys_init_module+278}
       <ffffffff8011026a>{system_call+126}

I also traced each function entry (within xenbus/) up to the hang:
xenbus_probe_init:864
xenbus_dev_init:366
create_xen_proc_entry:10
xs_init:869
xb_init_comms:200
xenwatch_thread:752
xenbus_probe:803
xenbus_probe_devices:594
xenbus_directory:340
join:302
xs_single:269
xs_talkv:212
xenbus_thread:851
process_msg:790
xb_read:149
xb_write:101
get_output_chunk:77
xb_write:101
get_output_chunk:77
read_reply:128

Looks sort of like it was stuck on the "spin_lock(&xs_state.reply_lock)"
but I don't see any imbalanced usage of the reply_lock in xenbus_xs.c and
I do see the xs_init call which inits the spinlock.

Thanks,
-kurt


On Mon, Jan 08, 2007 at 09:56:00AM -0700, Liang Yang wrote:
> Hi Ian,
> 
> Now I can xen-platform-pci.ko can be loaded after building 
> unmodified_drivers modules with the correct kernel header. Thanks for 
> pointing out.
> 
> However, Xen still hangs up when I try load xenbus.ko module after 
> xen-platform-pci.ko is loaded successfully. The problem remains the same 
> even though I applied the patch you provided and using the latest 
> xen-unstable.hg version.
> 
> Thanks,
> 
> Liang
> 
> ----- Original Message ----- 
> From: "Ian Campbell" <Ian.Campbell@xxxxxxxxxxxxx>
> To: "Liang Yang" <multisyncfe991@xxxxxxxxxxx>
> Cc: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>; "Keir Fraser" 
> <keir@xxxxxxxxxxxxx>; <xen-users@xxxxxxxxxxxxxxxxxxx>
> Sent: Saturday, January 06, 2007 4:44 AM
> Subject: Re: [Xen-devel] Unmodified_drivers modules broke again for 3.0.4?
> 
> 
> >On Fri, 2007-01-05 at 16:51 -0700, Liang Yang wrote:
> >>Hi,
> >>
> >>I tried to load unmodified_drivers modules for vbd device and got error 
> >>when
> >>doing insmod xen-platform-pci.ko in HVM Linux domain:
> >>xen_platform_pci: disagrees about version of symbol struct_module
> >>insmod: error inserting 'xen-platform-pci.ko' : -1 invalid module format.
> >>
> >>I used the same kernel version for HVM Linux kernel and the kernel I was
> >>building unmodified_drivers, i.e. they are both 2.6.16.33. I tested
> >>xen-3.0.4-testing and xen-unstable, all got the same problem. Xen 3.0.2 
> >>with
> >>2.6.16.29 kernel version still works fine.
> >>
> >>Could anyone point out some links to fix this?
> >
> >I needed the patch below when I tried the xen-unstable version
> >yesterday. I don't see how it can be related to the problem you are
> >seeing but with it they work fine for me on RHEL4 and SLES9. I didn't
> >try 2.6.16 but I will on Monday.
> >
> >Are you sure you are building against the correct kernel headers for the
> >kernel you are running?
> >
> >Ian.
> >
> >diff -r d04ff58bbe18 unmodified_drivers/linux-2.6/platform-pci/evtchn.c
> >--- a/unmodified_drivers/linux-2.6/platform-pci/evtchn.c Fri Jan 05 
> >10:40:19 2007 +0000
> >+++ b/unmodified_drivers/linux-2.6/platform-pci/evtchn.c Fri Jan 05 
> >14:40:02 2007 +0000
> >@@ -48,6 +48,12 @@ static struct {
> > void *dev_id;
> > int close; /* close on unbind_from_irqhandler()? */
> >} evtchns[MAX_EVTCHN];
> >+
> >+int irq_to_evtchn_port(int irq)
> >+{
> >+        return irq;
> >+}
> >+EXPORT_SYMBOL_GPL(irq_to_evtchn_port);
> >
> >void mask_evtchn(int port)
> >{
> >
> >
> >
> >_______________________________________________
> >Xen-devel mailing list
> >Xen-devel@xxxxxxxxxxxxxxxxxxx
> >http://lists.xensource.com/xen-devel
> >
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>