From owner-freebsd-bugs@freebsd.org Thu Jan 10 22:49:40 2019 Return-Path: Delivered-To: freebsd-bugs@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 33905149BA1D for ; Thu, 10 Jan 2019 22:49:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C1B3B738E9 for ; Thu, 10 Jan 2019 22:49:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 858FB149BA1B; Thu, 10 Jan 2019 22:49:39 +0000 (UTC) Delivered-To: bugs@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 73F04149BA19 for ; Thu, 10 Jan 2019 22:49:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 12DEB738E3 for ; Thu, 10 Jan 2019 22:49:39 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 532AC302E for ; Thu, 10 Jan 2019 22:49:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0AMncQO051749 for ; Thu, 10 Jan 2019 22:49:38 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0AMncqZ051748 for bugs@FreeBSD.org; Thu, 10 Jan 2019 22:49:38 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 234042] panics on 12.0-RELEASE: swi4: clock(0), instruction pointer 0x0 Date: Thu, 10 Jan 2019 22:49:38 +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: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mandrews@bit0.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@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-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jan 2019 22:49:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234042 --- Comment #9 from Mike Andrews --- All of my systems are dual-stack v4/v6, and the panics happen after a few d= ays of uptime. Not boot-time. If it was boot-time I wouldn't have finished upgrading the whole rack. :) There shouldn't be any churn in the ARP and ND tables -- it's a server rack= and most addresses are statically assigned, and nothing's coming or going. The expire times are at defaults. So the only churn should be re-populating ri= ght after a normal expire. Traffic does get kinda heavy at times though (lots = of HTTPS, lots of NFSv3) though we had a lightly loaded system get it yesterda= y. All the NICs are em(4) -- we have a few systems with igb but none of those = have had the panic yet. No idea if that's relevant or just luck. I put 12.0-p2 on everything overnight last night and one system has paniced since then, so it's not anything that was fixed in that patch. The panics = did not happen on 11.x or 10.x -- this is all new with 12.0. I do now have vmcore images now for many of these, including the 12.0-p2 one from two hours ago. (Initially I didn't have dumps working on geli+gmirror= ed swap. I do now.) --=20 You are receiving this mail because: You are the assignee for the bug.=