From owner-freebsd-net@FreeBSD.ORG Thu Dec 17 06:10:02 2009 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 DCE03106566B for ; Thu, 17 Dec 2009 06:10:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CB2A98FC08 for ; Thu, 17 Dec 2009 06:10:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBH6A2Dv039909 for ; Thu, 17 Dec 2009 06:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBH6A2Tt039908; Thu, 17 Dec 2009 06:10:02 GMT (envelope-from gnats) Date: Thu, 17 Dec 2009 06:10:02 GMT Message-Id: <200912170610.nBH6A2Tt039908@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Julian Elischer Cc: Subject: Re: kern/141696: [rum] [panic] rum(4)+ vimage = kernel panic X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Julian Elischer List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 06:10:02 -0000 The following reply was made to PR kern/141696; it has been noted by GNATS. From: Julian Elischer To: bug-followup@FreeBSD.org, venture37@geeklan.co.uk Cc: Subject: Re: kern/141696: [rum] [panic] rum(4)+ vimage = kernel panic Date: Wed, 16 Dec 2009 21:53:50 -0800 almost certainly there is an entry-point/code-path into the networking code from the rum driver that does not set the current vnet context. the easiest way to find this point is to compile in hte kernel debugger, (options ddb and kdb) and then make it happen again. then get a stack packtrace (bt). this will show us exactly what the code path is. There is a small possibility it is a generic path from usb code through usb-based netywork interfaces, as I remember something like htis being fixed in -current but I don't remember exactly the details.. julian