From nobody@FreeBSD.org  Thu Dec 17 03:27:54 2009
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id C7061106566B
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 17 Dec 2009 03:27:54 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id B64738FC0C
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 17 Dec 2009 03:27:54 +0000 (UTC)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id nBH3RsVa071209
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 17 Dec 2009 03:27:54 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id nBH3RssE071208;
	Thu, 17 Dec 2009 03:27:54 GMT
	(envelope-from nobody)
Message-Id: <200912170327.nBH3RssE071208@www.freebsd.org>
Date: Thu, 17 Dec 2009 03:27:54 GMT
From: Sevan Janiyan <venture37@geeklan.co.uk>
To: freebsd-gnats-submit@FreeBSD.org
Subject: rum(4)+ vimage = kernel panic
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         141696
>Category:       kern
>Synopsis:       [rum] [vimage] [panic] rum(4)+ vimage = kernel panic
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-virtualization
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Dec 17 03:30:01 UTC 2009
>Closed-Date:    Sun Jul 14 13:30:49 PDT 2013
>Last-Modified:  Sun Jul 14 13:30:49 PDT 2013
>Originator:     Sevan Janiyan
>Release:        8.0-RELEASE-p1
>Organization:
>Environment:
FreeBSD laptop.somewhere.local 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #5: Thu Dec 17 02:46:51 GMT 2009     root@laptop.somewhere.local:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
When a new kernel is compiled with vimage enabled & sctp disabled, the system panics after the rum driver has loaded, photo of output:
http://img109.imageshack.us/i/c08m.jpg/
The system boots fine if I disable the rum driver in the config & compile a new kernel
>How-To-Repeat:
boot the a kernel with vimage enabled on a system with a ralink chipset card which is supported by rum(4)
>Fix:
compile a new kernel with rum(4) disabled

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-net 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Thu Dec 17 03:59:10 UTC 2009 
Responsible-Changed-Why:  
Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=141696 

From: Julian Elischer <julian@elischer.org>
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

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/

From: Sevan / Venture37 <venture37@gmail.com>
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:27:18 +0000

 Photo of the trace output
 http://img64.imageshack.us/i/img1517.jpg/
Responsible-Changed-From-To: freebsd-net->freebsd-virtualization 
Responsible-Changed-By: gavin 
Responsible-Changed-When: Sat Aug 14 14:28:09 UTC 2010 
Responsible-Changed-Why:  
Over to maintainer(s) 

http://www.freebsd.org/cgi/query-pr.cgi?pr=141696 
Responsible-Changed-From-To: freebsd-virtualization->bz 
Responsible-Changed-By: bz 
Responsible-Changed-When: Mon Aug 30 15:15:24 UTC 2010 
Responsible-Changed-Why:  
I have a work in progress in perforce to fix USB-network device 
drivers, cardbus, ...  and cloned interface.  Track. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=141696 
State-Changed-From-To: open->analyzed 
State-Changed-By: bz 
State-Changed-When: Thu Oct 14 18:02:32 UTC 2010 
State-Changed-Why:  
I have fixes in perforce that depend on more stuff; planning 
on merging soon. Just sorting PRs. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=141696 
Responsible-Changed-From-To: bz->freebsd-virtualization 
Responsible-Changed-By: bz 
Responsible-Changed-When: Thu Nov 18 10:54:38 UTC 2010 
Responsible-Changed-Why:  
MOve it back to the list for the moment.  Easier to have all 
open problems at one single point. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=141696 
State-Changed-From-To: analyzed->closed 
State-Changed-By: rodrigc 
State-Changed-When: Sun Jul 14 13:30:16 PDT 2013 
State-Changed-Why:  
Duplicate of PR 170096 

http://www.freebsd.org/cgi/query-pr.cgi?pr=141696 
>Unformatted:
