From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: xenstored unsafe lock order detected, xlate_proc_name, evtchn_ioctl, port_user_lock Date: Tue, 20 Jul 2010 20:17:36 +0300 Message-ID: <20100720171736.GK17817@reaktio.net> References: <20100606173355.GS17817@reaktio.net> <4C0BDDB0.3000501@goop.org> <20100606185401.GT17817@reaktio.net> <20100607125803.GD17817@reaktio.net> <4C0D2345.8000200@goop.org> <20100720115350.GW17817@reaktio.net> <4C45CC16.6060409@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <4C45CC16.6060409@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Jul 20, 2010 at 09:17:26AM -0700, Jeremy Fitzhardinge wrote: > On 07/20/2010 04:53 AM, Pasi K=E4rkk=E4inen wrote: > > On Mon, Jun 07, 2010 at 09:50:13AM -0700, Jeremy Fitzhardinge wrote: > > =20 > >> On 06/07/2010 05:58 AM, Pasi K=E4rkk=E4inen wrote: > >> =20 > >>> On Sun, Jun 06, 2010 at 09:54:01PM +0300, Pasi K=E4rkk=E4inen wrote= : > >>> =20 > >>> =20 > >>>> On Sun, Jun 06, 2010 at 10:41:04AM -0700, Jeremy Fitzhardinge wrot= e: > >>>> =20 > >>>> =20 > >>>>> On 06/06/2010 10:33 AM, Pasi K=E4rkk=E4inen wrote: > >>>>> =20 > >>>>> =20 > >>>>>> Hello, > >>>>>> > >>>>>> I just tried the latest xen/stable-2.6.32.x kernel, ie. 2.6.32.1= 5, with Xen 4.0.0, > >>>>>> and I got this: > >>>>>> > >>>>>> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/log-2.6.32.15-pvo= ps-dom0-xen-stable-x86_64.txt > >>>>>> =20 > >>>>>> =20 > >>>>>> =20 > >>>>> Does this help? > >>>>> > >>>>> =20 > >>>>> =20 > >>>> It gave failing hunks so I had to manually apply it to 2.6.32.15,=20 > >>>> but it seems to fix that issue. No "unsafe lock order" messages an= ymore. > >>>> > >>>> =20 > >>>> =20 > >>> Hmm.. it seems I still get this: > >>> =20 > >>> =20 > >> OK, thanks. Let me look at it; that was a first cut patch I did the > >> other day when I noticed the problem, but I hadn't got around to tes= ting > >> it myself. > >> > >> =20 > > I just tried the latest xen/stable-2.6.32.16 (as of today),=20 > > without any additional patches, and I get this: > > =20 >=20 > Is that new? >=20 I think it's the same as earlier.. -- Pasi >=20 > > > > device vif1.0 entered promiscuous mode > > virbr0: topology change detected, propagating > > virbr0: port 1(vif1.0) entering forwarding state > > alloc irq_desc for 1242 on node 0 > > alloc kstat_irqs on node 0 > > alloc irq_desc for 1241 on node 0 > > alloc kstat_irqs on node 0 > > alloc irq_desc for 1240 on node 0 > > alloc kstat_irqs on node 0 > > blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi) > > alloc irq_desc for 1239 on node 0 > > alloc kstat_irqs on node 0 > > vif1.0: no IPv6 routers present > > alloc irq_desc for 1238 on node 0 > > alloc kstat_irqs on node 0 > > ------------[ cut here ]------------ > > WARNING: at kernel/lockdep.c:2323 trace_hardirqs_on_caller+0xb7/0x135= () > > Hardware name: X7SB4/E > > Modules linked in: ipt_MASQUERADE iptable_nat nf_nat bridge stp llc s= unrpc ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 xen_g= ntdev xen_evtchn xenfs e1000e shpchp i2c_i801 pcspkr iTCO_wdt iTCO_vendor= _support serio_raw joydev floppy usb_storage video output aic79xx scsi_tr= ansport_spi radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unl= oaded: scsi_wait_scan] > > Pid: 23, comm: xenwatch Not tainted 2.6.32.16 #6 > > Call Trace: > > [] warn_slowpath_common+0x7c/0x94 > > [] ? _spin_unlock_irq+0x30/0x3c > > [] warn_slowpath_null+0x14/0x16 > > [] trace_hardirqs_on_caller+0xb7/0x135 > > [] trace_hardirqs_on+0xd/0xf > > [] _spin_unlock_irq+0x30/0x3c > > [] add_to_net_schedule_list_tail+0x92/0x9b > > [] netif_be_int+0x38/0xcd > > [] handle_IRQ_event+0x53/0x119 > > [] handle_level_irq+0x7d/0xdf > > [] __xen_evtchn_do_upcall+0xe1/0x16e > > [] xen_evtchn_do_upcall+0x37/0x4c > > [] xen_do_hypervisor_callback+0x1e/0x30 > > [] ? hypercall_page+0x40a/0x100b > > [] ? hypercall_page+0x40a/0x100b > > [] ? notify_remote_via_evtchn+0x1e/0x44 > > [] ? __mutex_lock_common+0x36a/0x37b > > [] ? xs_talkv+0x5c/0x174 > > [] ? xb_write+0x16e/0x18a > > [] ? xs_talkv+0x6a/0x174 > > [] ? kasprintf+0x38/0x3a > > [] ? xs_single+0x3a/0x3c > > [] ? xenbus_read+0x42/0x5b > > [] ? frontend_changed+0x655/0x681 > > [] ? xenbus_otherend_changed+0xe9/0x176 > > [] ? xen_restore_fl_direct_end+0x0/0x1 > > [] ? lock_release+0x198/0x1a5 > > [] ? frontend_changed+0x10/0x12 > > [] ? xenwatch_thread+0x111/0x14c > > [] ? autoremove_wake_function+0x0/0x39 > > [] ? xenwatch_thread+0x0/0x14c > > [] ? kthread+0x7f/0x87 > > [] ? child_rip+0xa/0x20 > > [] ? restore_args+0x0/0x30 > > [] ? child_rip+0x0/0x20 > > ---[ end trace b036c0423b0ee26a ]--- > > alloc irq_desc for 1237 on node 0 > > alloc kstat_irqs on node 0 > > device vif2.0 entered promiscuous mode > > > > > > -- Pasi > > > > =20 >=20