usb/144387: if_run panic

Hans Petter Selasky hselasky at c2i.net
Tue Mar 2 21:50:03 UTC 2010


The following reply was made to PR usb/144387; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky at c2i.net>
To: freebsd-usb at freebsd.org
Cc: Alexander Kuznetsov <skritku at gmail.com>,
 freebsd-gnats-submit at freebsd.org
Subject: Re: usb/144387: if_run panic
Date: Tue, 2 Mar 2010 22:44:11 +0100

 On Monday 01 March 2010 12:50:27 Alexander Kuznetsov wrote:
 > >Number:         144387
 > >Category:       usb
 > >Synopsis:       if_run panic
 > >Confidential:   no
 > >Severity:       non-critical
 > >Priority:       low
 > >Responsible:    freebsd-usb
 > >State:          open
 > >Quarter:
 > >Keywords:
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Mon Mar 01 12:00:06 UTC 2010
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Alexander Kuznetsov
 > >Release:        9.0-CURRENT (both i386 and amd64)
 > >Organization:
 > >Environment:
 > >Description:
 > 
 > if_run causes kernel panic
 > 
 > run0: device timeout
 > panic: mutex run0 not owned at
 >  /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/run/if_run.c:3376 cpuid
 >  = 0
 > KDB: enter: panic
 > [ thread pid 0 tid 100068 ]
 > Stopped at kdb_enter+0x3d: movq $0,0x6b5b30(%rip)
 > db>bt
 > Tracing pid 0 tid 100068 td 0xffffff000252d000
 > kdb_enter() at kdb_enter+0x3d
 > panic() at panic+0x17b
 > _mtx_assert() at _mtx_assert+0xdc
 > run_usb_timeout_cb() at run_usb_timeout_cb+0x35
 > taskqueue_run() at taskqueue_run+0x91
 > taskqueue_thread_loop() at taskqueue_thread_loop+0x3f
 > fork_exit() at fork_exit+0x12a
 > fork_trampoline() at fork_trampoline+0xe
 > --- trap 0, rip = 0, rsp = 0xffffff80001bcd30, rbp = 0 ---
 > db>
 > 
 > >How-To-Repeat:
 > 
 > # kldload if_run
 > # ifconfig wlan create wlandev run0 wlanmode hostap
 > # ifconfig wlan0 ssid test
 > # ifconfig wlan0 inet 192.168.0.10
 > [panic after some seconds]
 > 
 > >Fix:
 > >
 > >
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 
 This is a know issue which has been fixed, but not committed to -current yet.
 
 --HPS


More information about the freebsd-usb mailing list