From owner-freebsd-current@freebsd.org Sat Aug 11 13:30:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91290106C9E2 for ; Sat, 11 Aug 2018 13:30:13 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 28D437CB83; Sat, 11 Aug 2018 13:30:12 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id E71EE26036B; Sat, 11 Aug 2018 15:30:10 +0200 (CEST) Subject: Re: panic after ifioctl/if_clone_destroy To: Roman Bogorodskiy Cc: Matthew Macy , freebsd-current@freebsd.org References: <20180805153556.GA1957@kloomba> <8acc8f27-29f2-d4c1-7473-f7053b14e7ad@selasky.org> <911d520a-4eb5-02b4-a119-3663a7537e6a@selasky.org> <24743f03-8af2-4106-653d-3bfd13d910c9@selasky.org> <20180811074407.GA6299@kloomba> From: Hans Petter Selasky Message-ID: <983b03f2-928d-852e-325e-1d03b394e591@selasky.org> Date: Sat, 11 Aug 2018 15:29:48 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20180811074407.GA6299@kloomba> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Aug 2018 13:30:13 -0000 On 8/11/18 9:44 AM, Roman Bogorodskiy wrote: > Hans Petter Selasky wrote: > >> On 08/06/18 21:43, Matthew Macy wrote: >>> The struct thread is typesafe. The problem is that the link is no longer >>> typesafe now that it’s not part of the thread. Thanks for pointing this >>> out. I’ll commit a fix later today. >>> >> >> Is there a patch yet? >> >> --HPS >> > > This was committed in: > > https://svnweb.freebsd.org/changeset/base/337525 > > However, I've just updated to r337595, and it still panics. Not sure if > that's related to the original issue though: > > (kgdb) #0 doadump (textdump=0) at pcpu.h:230 > #1 0xffffffff8043ddfb in db_dump (dummy=, > dummy2=, dummy3=, > dummy4=) at /usr/src/sys/ddb/db_command.c:574 > #2 0xffffffff8043dbc9 in db_command (cmd_table=) > at /usr/src/sys/ddb/db_command.c:481 > #3 0xffffffff8043d944 in db_command_loop () > at /usr/src/sys/ddb/db_command.c:534 > #4 0xffffffff80440b6f in db_trap (type=, > code=) at /usr/src/sys/ddb/db_main.c:252 > #5 0xffffffff80bdef83 in kdb_trap (type=9, code=0, tf=) > at /usr/src/sys/kern/subr_kdb.c:693 > #6 0xffffffff8107aee1 in trap_fatal (frame=0xfffffe00760dc8a0, eva=0) > at /usr/src/sys/amd64/amd64/trap.c:906 > #7 0xffffffff8107a3bd in trap (frame=0xfffffe00760dc8a0) at counter.h:87 > #8 0xffffffff81054d05 in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:232 > #9 0xffffffff80ded513 in inp_gcmoptions (ctx=0xfffff80003079f20) > at epoch_private.h:188 > #10 0xffffffff80bd9cba in epoch_call_task (arg=) > at /usr/src/sys/kern/subr_epoch.c:507 > #11 0xffffffff80bdd0a9 in gtaskqueue_run_locked (queue=0xfffff800035be900) > at /usr/src/sys/kern/subr_gtaskqueue.c:332 > #12 0xffffffff80bdce28 in gtaskqueue_thread_loop (arg=) > at /usr/src/sys/kern/subr_gtaskqueue.c:507 > #13 0xffffffff80b530c4 in fork_exit ( > callout=0xffffffff80bdcda0 , > arg=0xfffffe00061a4038, frame=0xfffffe00760dcac0) > at /usr/src/sys/kern/kern_fork.c:1057 > #14 0xffffffff81055cde in fork_trampoline () > at /usr/src/sys/amd64/amd64/exception.S:990 > #15 0x0000000000000000 in ?? () > Current language: auto; currently minimal > (kgdb) > > Full core.txt is here: https://people.freebsd.org/~novel/misc/core.20180811.txt > > Roman Bogorodskiy > What is the full panic message? Are you loading // unloading any network modules? --HPS