NetBSD Problem Report #46313

From billc@netbsd.org  Sun Apr  8 23:59:34 2012
Return-Path: <billc@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id 36AC763B9FE
	for <gnats-bugs@gnats.NetBSD.org>; Sun,  8 Apr 2012 23:59:34 +0000 (UTC)
Message-Id: <20120408235947.B5D2F52F8@admin.warped.com>
Date: Sun,  8 Apr 2012 17:59:47 -0600 (MDT)
From: billc@netbsd.org (Charlie Root)
To: gnats-bugs@gnats.NetBSD.org
Subject: xen instance throws evtchn_do_event: handler 0xffffffff80120c17 didn't lower ipl 8 7

>Number:         46313
>Category:       port-xen
>Synopsis:       xen instance throws evtchn_do_event: handler 0xffffffff80120c17 didn't lower ipl 8 7
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bouyer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 09 00:00:00 +0000 2012
>Closed-Date:    Sun Apr 13 02:26:47 +0000 2014
>Last-Modified:  Sun Apr 13 02:26:47 +0000 2014
>Originator:     Charlie Root
>Release:        NetBSD 6.0_BETA
>Organization:

>Environment:


System: NetBSD admin.warped.com 6.0_BETA NetBSD 6.0_BETA (XEN3_DOMU) amd64
Architecture: x86_64
Machine: amd64

root@epsilon:/etc/xen/configs# xm info
host                   : epsilon
release                : 2.6.32-5-xen-amd64
version                : #1 SMP Thu Nov 3 05:42:31 UTC 2011
machine                : x86_64
nr_cpus                : 8
nr_nodes               : 2
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2133
hw_caps                : bfebfbff:2c100800:00000000:00001f40:029ee3ff:00000000:00000001:00000000
virt_caps              : hvm hvm_directio
total_memory           : 24566
free_memory            : 5132
node_to_cpu            : node0:0-3
                         node1:4-7
node_to_memory         : node0:799
                         node1:4333
node_to_dma32_mem      : node0:52
                         node1:0
max_node_id            : 1
xen_major              : 4
xen_minor              : 0
xen_extra              : .1
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
xen_commandline        : placeholder
cc_compiler            : gcc version 4.4.5 (Debian 4.4.5-8) 
cc_compile_by          : waldi
cc_compile_domain      : debian.org
cc_compile_date        : Sun Nov  6 09:42:15 CET 2011
xend_config_format     : 4

>Description:

Apr  8 15:15:23 admin /netbsd: evtchn_do_event: handler 0xffffffff80120c17 didn't lower ipl 8 7

This is also repeatable with running Xen under VMWare with linux dom0 and amd64 domu (my original testbed).

>How-To-Repeat:
I get this during cvs checkout of pkgsrc or building a package (might be disk or net related?)

>Fix:


>Release-Note:

>Audit-Trail:

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: port-xen-maintainer@NetBSD.org, gnats-admin@NetBSD.org,
        netbsd-bugs@NetBSD.org
Subject: Re: port-xen/46313: xen instance throws evtchn_do_event: handler
 0xffffffff80120c17 didn't lower ipl 8 7
Date: Thu, 12 Apr 2012 20:16:31 +0200

 On Mon, Apr 09, 2012 at 12:00:01AM +0000, Charlie Root wrote:
 > >Description:
 > 	
 > Apr  8 15:15:23 admin /netbsd: evtchn_do_event: handler 0xffffffff80120c17 didn't lower ipl 8 7
 > 
 > This is also repeatable with running Xen under VMWare with linux dom0 and amd64 domu (my original testbed).

 This is a known issue. The problem is that a interrupt handler (most
 likely something called from hardclock() called from the clock interrupt
 handler) failed returns at a higher IPL than it was called. I've never
 took time to investigate further.
 The message is annoying but harmless because the Xen interrupt code will
 restore the right IPL. But I think the underlying bug is real and may
 cause problems on other ports ...

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

billc:
NetBSD glurmo.warped.com 6.0_RC1 NetBSD 6.0_RC1 (XEN3_DOMU) #1: Wed Aug 22 08:45:51 MDT 2012  root@glurmo.warped.com:/usr/build/netbsd-6_amd64/obj/sys/arch/amd64/compile/XEN3_DOMU amd64

Linux epsilon 2.6.32-5-xen-amd64 #1 SMP Sun May 6 08:57:29 UTC 2012 x86_64 GNU/Linux

Note the address area:

NetBSD domU: evtchn_do_event: handler 0xffffffff80120079 didn't lower ipl 8 7

Linux dom0:
[1283486.131390] INFO: task umount:12278 blocked for more than 120 seconds.
[1283486.131454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[1283486.131543] umount        D 0000000000000002     0 12278  11379 0x00000000
[1283486.131553]  ffff8805e0394db0 0000000000000282 00000007b1d09d08 ffff8801b1d09db0
[1283486.131564]  0000000000000000 0000000000000000 000000000000f9e0 ffff8801b1d09fd8
[1283486.131574]  0000000000015780 0000000000015780 ffff8805e0392350 ffff8805e0392648
[1283486.131584] Call Trace:
[1283486.131601]  [<ffffffff8100e635>] ? xen_force_evtchn_callback+0x9/0xa
[1283486.131609]  [<ffffffff8100ecf2>] ? check_events+0x12/0x20
[1283486.131618]  [<ffffffff81040e42>] ? check_preempt_wakeup+0x0/0x268
[1283486.131627]  [<ffffffff81109843>] ? bdi_sched_wait+0x0/0xe
[1283486.131633]  [<ffffffff8110984c>] ? bdi_sched_wait+0x9/0xe
[1283486.131646]  [<ffffffff8130e09a>] ? _spin_unlock_irqrestore+0xd/0xe
[1283486.131654]  [<ffffffff8130d2e7>] ? __wait_on_bit+0x41/0x70
[1283486.131660]  [<ffffffff81040e42>] ? check_preempt_wakeup+0x0/0x268
[1283486.131666]  [<ffffffff81109843>] ? bdi_sched_wait+0x0/0xe
[1283486.131673]  [<ffffffff8130d381>] ? out_of_line_wait_on_bit+0x6b/0x77
[1283486.131683]  [<ffffffff810660c0>] ? wake_bit_function+0x0/0x23
[1283486.131689]  [<ffffffff811098c4>] ? sync_inodes_sb+0x73/0x12a
[1283486.131698]  [<ffffffff8110d479>] ? __sync_filesystem+0x4b/0x70
[1283486.131718]  [<ffffffff810f205a>] ? generic_shutdown_super+0x21/0xfa
[1283486.131725]  [<ffffffff8100ecdf>] ? xen_restore_fl_direct_end+0x0/0x1
[1283486.131733]  [<ffffffff810f2155>] ? kill_block_super+0x22/0x3a
[1283486.131740]  [<ffffffff810f2825>] ? deactivate_super+0x60/0x77
[1283486.131749]  [<ffffffff81105198>] ? sys_umount+0x2dc/0x30b
[1283486.131756]  [<ffffffff81011b42>] ? system_call_fastpath+0x16/0x1b

---

Responsible-Changed-From-To: port-xen-maintainer->bouyer
Responsible-Changed-By: bouyer@NetBSD.org
Responsible-Changed-When: Tue, 03 Dec 2013 20:58:58 +0000
Responsible-Changed-Why:
I'll handle it


State-Changed-From-To: open->Analyzed
State-Changed-By: bouyer@NetBSD.org
State-Changed-When: Tue, 03 Dec 2013 20:58:58 +0000
State-Changed-Why:
See http://mail-index.netbsd.org/source-changes/2013/12/03/msg049694.html
will request a pullup in a few days.


State-Changed-From-To: Analyzed->Pending-pullups
State-Changed-By: bouyer@NetBSD.org
State-Changed-When: Tue, 10 Dec 2013 21:26:26 +0000
State-Changed-Why:
pullup-6 #995
pullup-5 #1890


State-Changed-From-To: Pending-pullups->pending-pullups
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Wed, 11 Dec 2013 14:42:28 +0000
State-Changed-Why:
lowercase


State-Changed-From-To: pending-pullups->closed
State-Changed-By: snj@NetBSD.org
State-Changed-When: Sun, 13 Apr 2014 02:26:47 +0000
State-Changed-Why:
Pulled up.


>Unformatted:
 From: billc@netbsd.org
 Reply-To: billc@netbsd.org
 X-send-pr-version: 3.95




 20120407 daily on nyftp

Home	PR Database Search