From owner-freebsd-net@FreeBSD.ORG Sun Nov 28 15:01:47 2010 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91A2A106566C; Sun, 28 Nov 2010 15:01:47 +0000 (UTC) (envelope-from cperciva@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 672078FC15; Sun, 28 Nov 2010 15:01:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oASF1lSo072000; Sun, 28 Nov 2010 15:01:47 GMT (envelope-from cperciva@freefall.freebsd.org) Received: (from cperciva@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oASF1lsC071996; Sun, 28 Nov 2010 15:01:47 GMT (envelope-from cperciva) Date: Sun, 28 Nov 2010 15:01:47 GMT Message-Id: <201011281501.oASF1lsC071996@freefall.freebsd.org> To: cperciva@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-xen@FreeBSD.org From: cperciva@FreeBSD.org Cc: Subject: Re: kern/148780: [panic] mtx_lock() of spin mutex (null) @ /usr/src/sys/net/netisr.c:830 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2010 15:01:47 -0000 Synopsis: [panic] mtx_lock() of spin mutex (null) @ /usr/src/sys/net/netisr.c:830 Responsible-Changed-From-To: freebsd-net->freebsd-xen Responsible-Changed-By: cperciva Responsible-Changed-When: Sun Nov 28 14:59:04 UTC 2010 Responsible-Changed-Why: This is actually a FreeBSD/Xen bug. Somehow the pcpu data is being mangled in the presence of VM pressure; the panic shows up in netisr because netisr looks up a per-cpu data structure (and locks it, hence the locking assertion). http://www.freebsd.org/cgi/query-pr.cgi?pr=148780