Re: panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/net/iflib.c:3716

Chalk another review fail up to shuffling patches between git and phab. Sorry for the inconvenience. -M On Wed, Apr 11, 2018 at 10:26 AM, K. Macy wrote: > Actually ctx lock is still a mutex. Just add the STATE_LOCK_INIT line. > -M > > On Wed, Apr 11, 2018 at 10:24 AM, K. Macy

Re: panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/net/iflib.c:3716

Actually ctx lock is still a mutex. Just add the STATE_LOCK_INIT line. -M On Wed, Apr 11, 2018 at 10:24 AM, K. Macy wrote: > Sorry about that. It looks like my review must have been missing a line. > > @@ -4702,8 +4707,8 @@ iflib_register(if_ctx_t ctx) > >

Re: panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/net/iflib.c:3716

Sorry about that. It looks like my review must have been missing a line. @@ -4702,8 +4707,8 @@ iflib_register(if_ctx_t ctx) _iflib_assert(sctx); - CTX_LOCK_INIT(ctx, device_get_nameunit(ctx->ifc_dev)); - + CTX_LOCK_INIT(ctx); + STATE_LOCK_INIT(ctx,

Re: panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/net/iflib.c:3716

On 11.04.2018 20:02, Mark Johnston wrote: >> It appears that r332389 is implicated. > > I'm seeing this too, under bhyve with e1000 emulation. Reverting r332389 > fixes the problem. I have this problem too. And reverting r332389 fixes it. em0@pci0:0:25:0:class=0x02 card=0x20088086

Re: panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/net/iflib.c:3716

On Wed, Apr 11, 2018 at 04:39:58AM -0700, David Wolfskill wrote: > This was running: > > FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #156 > r332399M/332400:1200061: Wed Apr 11 04:17:45 PDT 2018 > r...@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY

panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/net/iflib.c:3716

This was running: FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #156 r332399M/332400:1200061: Wed Apr 11 04:17:45 PDT 2018 r...@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 during boot, after updating from: FreeBSD g1-215.catwhisker.org

r291494 PANIC mtx_lock() of spin mutex @ /usr/src/sys/kern/vfs_subr.c:512

Dump Version String: FreeBSD 11.0-CURRENT #9 r291494: Mon Nov 30 13:21:08 EST 2015 mikej@bsd11:/usr/obj/usr/src/sys/GENERIC Panic String: mtx_lock() of spin mutex @ /usr/src/sys/kern/vfs_subr.c:512 Dump Parity: 2232113789 Bounds: 1 Dump Status: good https://charon.gopai.com

Re: r291494 PANIC mtx_lock() of spin mutex @ /usr/src/sys/kern/vfs_subr.c:512

76 > Blocksize: 512 > Dumptime: Wed Dec 2 12:10:06 2015 > Hostname: bsd11 > Magic: FreeBSD Kernel Dump > Version String: FreeBSD 11.0-CURRENT #9 r291494: Mon Nov 30 > 13:21:08 EST 2015 > mikej@bsd11:/usr/obj/usr/src/sys/GENERIC > Panic String: mtx_lock() of spi

panic: mtx_lock() of spin mutex in ip_output.c

I have a Dell 4150 laptop using dhcp and ntpd on the xl0 interface. I did ifconfig xl0 down and received the following panic (hand transcribed :-( ). panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/netinet/ip_output.c:266 Stack backtrace: backtrace() panic() panic: process 414(ntpd):2

Re: panic: mtx_lock() of spin mutex in ip_output.c

On Fri, Nov 07, 2003 at 11:31:45AM -0800, Steven G. Kargl wrote: I have a Dell 4150 laptop using dhcp and ntpd on the xl0 interface. I did ifconfig xl0 down and received the following panic (hand transcribed :-( ). panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/netinet/ip_output.c

Re: panic: mtx_lock() of spin mutex in ip_output.c

On Friday 07 November 2003 12:54 pm, Steve Kargl wrote: On Fri, Nov 07, 2003 at 11:31:45AM -0800, Steven G. Kargl wrote: I have a Dell 4150 laptop using dhcp and ntpd on the xl0 interface. I did ifconfig xl0 down and received the following panic (hand transcribed :-( ). panic: mtx_lock

Re: panic: mtx_lock() of spin mutex in ip_output.c

:-( ). panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/netinet/ip_output.c:266 Stack backtrace: backtrace() panic() panic: process 414(ntpd):2 Giant but isn't blocked on a mutex Make sure you have rev 1.250 of ip_input.c. Okay. I'll update my source tree. This panic

Re: panic: mtx_lock() of spin mutex

the filedesc lock. The console log has some additional messages anout mutexes, interrupts, before it spirals down an endless loop of xlock already held messages: panic: mtx_lock() of spin mutex D^QR@TR@ ^UV@^D @ /usr/src/sys/kern/kern_descrip.c:485 cpuid = 1; lapic.id = 0200 Debugger(panic

Re: panic: mtx_lock() of spin mutex

in a tcsh, where ~sunhee is on NFS: panic: mtx_lock() of spin mutex D\^QR\M-@\M-TR\M-@ \M^UV\M-@\^D @ /usr/src/sys/kern/kern_descrip.c:485 cpuid = 1; lapic.id = 0200 panic: from debugger cpuid = 1; lapic.id = 0200 boot() called on cpu#1 Uptime: 2m28s pfs_vncache_unload(): 3 entries

Re: panic: mtx_lock() of spin mutex

John, John Baldwin wrote: On 26-Nov-2002 Lars Eggert wrote: #12 0xc02a93e6 in do_dup (td=0xc60a2a80, type=DUP_FIXED, old=-1, new=4, retval=0xc60a2b18) at /usr/src/sys/kern/kern_descrip.c:485 Hmm, old = -1, this might be fixed by a patch I committed today to fix bugs in do_dup(). Please

Re: panic: mtx_lock() of spin mutex

John Baldwin wrote: On 18-Oct-2002 Lars Eggert wrote: John Baldwin wrote: What is line 488 of src/sys/kern/kern_descrip.c? fhold(fp) in do_dup(). Hrm. You can try adding some KASSERT()'s that the reference count of that struct file isn't zero or negative. Did that, and the KASSERT never

Re: panic: mtx_lock() of spin mutex

John Baldwin wrote: On 18-Oct-2002 Lars Eggert wrote: John Baldwin wrote: What is line 488 of src/sys/kern/kern_descrip.c? fhold(fp) in do_dup(). Hrm. You can try adding some KASSERT()'s that the reference count of that struct file isn't zero or negative. fd_refcnt is an u_short,

Re: panic: mtx_lock() of spin mutex

for GDB. Type show warranty for details. This GDB was configured as i386-undermydesk-freebsd... panic: from debugger panic messages: --- panic: mtx_lock() of spin mutex duI\M-@\M-4qI\M-@`\M^NN\M-@\^D @ /usr/src/sys/kern/kern_descrip.c:486 cpuid = 1; lapic.id = 0200 panic: from debugger cpuid = 1

RE: panic: mtx_lock() of spin mutex

of the mutex looks definitly fishy. Let me knowif I can provide more information (tried to get a core dump, but machine hung hard after typing panic.) panic: mtx_lock() of spin mutex $,J@4(J@^@^GN@^D @ /usr/src/sys/kern/kern_descrip.c:488 cpuid = 1; lapic.id = 0200 Debugger(panic) Stopped

Re: panic: mtx_lock() of spin mutex

John Baldwin wrote: What is line 488 of src/sys/kern/kern_descrip.c? fhold(fp) in do_dup(). Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature

Re: panic: mtx_lock() of spin mutex

On 18-Oct-2002 Lars Eggert wrote: John Baldwin wrote: What is line 488 of src/sys/kern/kern_descrip.c? fhold(fp) in do_dup(). Hrm. You can try adding some KASSERT()'s that the reference count of that struct file isn't zero or negative. -- John Baldwin [EMAIL PROTECTED]

panic: mtx_lock() of spin mutex

knowif I can provide more information (tried to get a core dump, but machine hung hard after typing panic.) panic: mtx_lock() of spin mutex $,J@4(J@^@^GN@^D @ /usr/src/sys/kern/kern_descrip.c:488 cpuid = 1; lapic.id = 0200 Debugger(panic) Stopped at Debugger+0x5a: xchgl %ebx,in_Debugger.0

Re: panic: mtx_lock() of spin mutex

Lars Eggert wrote: I'm tracking down a lock order reversal for hsu@, and just came across this other locking panic twice in the last few hours. Found a way to reproduce this at will (shell tab-completion on a filename on an NFS-mounted file system), and managed to get a core dump. Note that

Re: panic: mtx_lock() of spin mutex

Lars Eggert wrote: Note that the panic message makes a lot more sense this time around: Argh; which I maybe should have included in the fist place. Typescript attached. Sorry, Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute typescript Description: