From owner-freebsd-net@freebsd.org Tue May 2 14:39:59 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6ED66D5AA21 for ; Tue, 2 May 2017 14:39:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 5E9B31F0C for ; Tue, 2 May 2017 14:39:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v42EdxOm082766 for ; Tue, 2 May 2017 14:39:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 218886] ifconfig lagg0 destroy will crash the system Date: Tue, 02 May 2017 14:39:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ecin@rabing.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2017 14:39:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218886 --- Comment #5 from Lutz Rabing --- (In reply to Alan Somers from comment #4) Yes, dumpdev=3D"NO" was set in rc.conf. I changed it to AUTO and repeated the crash. There is just a info.0 and vmcore.0: drwxr-x--- 2 root wheel 8 May 2 16:34 . drwxr-xr-x 25 root wheel 25 May 2 18:34 .. -rw-r--r-- 1 root wheel 2 May 2 16:34 bounds -rw------- 1 root wheel 452 May 2 16:34 info.0 lrwxr-xr-x 1 root wheel 6 May 2 16:34 info.last -> info.0 -rw-r--r-- 1 root wheel 5 Nov 11 2014 minfree -rw------- 1 root wheel 1013112832 May 2 16:34 vmcore.0 lrwxr-xr-x 1 root wheel 8 May 2 16:34 vmcore.last -> vmcore.0 # cat info.0 Dump header from device: /dev/gpt/swap2 Architecture: amd64 Architecture Version: 2 Dump Length: 1013112832 Blocksize: 512 Dumptime: Tue May 2 16:33:14 2017 Hostname: core10.omc.net Magic: FreeBSD Kernel Dump Version String: FreeBSD 11.0-RELEASE-p9 #0: Tue Apr 11 08:48:40 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC Panic String: page fault Dump Parity: 3897632610 Bounds: 0 Dump Status: good --=20 You are receiving this mail because: You are the assignee for the bug.=