From owner-freebsd-virtualization@FreeBSD.ORG  Fri Dec 18 09:45:07 2009
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-virtualization@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 4FF44106566C;
	Fri, 18 Dec 2009 09:45:07 +0000 (UTC)
	(envelope-from bzeeb-lists@lists.zabbadoz.net)
Received: from mail.cksoft.de (mail.cksoft.de [IPv6:2001:4068:10::3])
	by mx1.freebsd.org (Postfix) with ESMTP id 0CA608FC12;
	Fri, 18 Dec 2009 09:45:07 +0000 (UTC)
Received: from localhost (amavis.fra.cksoft.de [192.168.74.71])
	by mail.cksoft.de (Postfix) with ESMTP id 6DEE041C7B7;
	Fri, 18 Dec 2009 10:45:06 +0100 (CET)
X-Virus-Scanned: amavisd-new at cksoft.de
Received: from mail.cksoft.de ([192.168.74.103])
	by localhost (amavis.fra.cksoft.de [192.168.74.71]) (amavisd-new,
	port 10024)
	with ESMTP id d-eU5j1Wp-AQ; Fri, 18 Dec 2009 10:45:05 +0100 (CET)
Received: by mail.cksoft.de (Postfix, from userid 66)
	id A1F7141C6A1; Fri, 18 Dec 2009 10:45:05 +0100 (CET)
Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net
	[10.111.66.10])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.int.zabbadoz.net (Postfix) with ESMTP id 7F3EC4448EC;
	Fri, 18 Dec 2009 09:44:17 +0000 (UTC)
Date: Fri, 18 Dec 2009 09:44:17 +0000 (UTC)
From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
X-X-Sender: bz@maildrop.int.zabbadoz.net
To: Julian Elischer <julian@elischer.org>
In-Reply-To: <4B2A7DC3.8000504@elischer.org>
Message-ID: <20091218094256.J86040@maildrop.int.zabbadoz.net>
References: <200912171530.nBHFUDBO087113@freefall.freebsd.org>
	<4B2A7DC3.8000504@elischer.org>
X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Marko Zec <zec@FreeBSD.org>,
	FreeBSD virtualization mailing list <freebsd-virtualization@freebsd.org>
Subject: Re: kern/141696: [rum] [panic] rum(4)+ vimage = kernel panic
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
	<freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>,
	<mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>,
	<mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Dec 2009 09:45:07 -0000

On Thu, 17 Dec 2009, Julian Elischer wrote:

Hi Julian,

> Venture37 wrote:
>> The following reply was made to PR kern/141696; it has been noted by GNATS.
>> 
>> From: Venture37 <venture37@geeklan.co.uk>
>> To: bug-followup@FreeBSD.org, venture37@geeklan.co.uk
>> Cc:  Subject: Re: kern/141696: [rum] [panic] rum(4)+ vimage = kernel panic
>> Date: Thu, 17 Dec 2009 15:25:28 +0000
>>
>>  Photo of the trace output
>>  http://img64.imageshack.us/i/img1517.jpg/
>
> Marko, et al.
>
> looking at this, the crash is in
>
> ifindex_alloc_locked()
> from:
> if_alloc()
> rum_attach()
> device_attach()
> device_probe_and_attach()
> usb_probe_and_attach_sub()
> usb_probe_and_attach()
> uhub_explore()
> usb_bus_explore()
> usb_process()
>
> the question is "where should we load the current vnet?
>
> is it up to the driver (if_rum) or should device_attach assume that the 
> resulting device MIGHT be a network device.

Different question - why is it a problem for rum/usb whne it's not a
problem for all the other physical interfaces like bge, bce, em, ....
or have we just not noticed what happens if we have them as module and
attach at run-time?

/bz

-- 
Bjoern A. Zeeb         It will not break if you know what you are doing.