ural(4) and panic on sleeping thread (6.1-R)

[John Baldwin]

On Tuesday 01 August 2006 11:58, José M. Fandiño wrote:
> Hello,
> 
> I get a panic each time I try to create an access point
> with the ural driver.
> 
> only by running this commands the machine panic:
> kldload bridge
> sysctl net.link.ether.bridge.enable=1
> net.link.ether.bridge_cfg="rl0,ural0"
> 
> I'm not very familiarized with 'kgdb' so if some developper
> gets interested in this panic I can execute all commands
> they are interested in.
> 
> thank you.
> 
> # kgdb -c /var/crash/vmcore.3 /usr/obj/usr/src/sys/GENERIC/kernel.debug
> [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: 
Undefined symbol "ps_pglobal_lookup"]
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain 
conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-marcel-freebsd".
> 
> Unread portion of the kernel message buffer:
> <6>rl0: promiscuous mode enabled
> Sleeping thread (tid 100079, pid 783) owns a non-sleepable lock
> panic: sleeping thread

In kgdb, do 'proc 783', and then 'where' to get a stack trace of the thread 
that did the wrong thing.   (The thread that panics is just an innocent 
victim that bumped into the miscreant.)

-- 
John Baldwin