From owner-freebsd-net@freebsd.org Sun Feb 19 01:39:35 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 9B207CDB590 for ; Sun, 19 Feb 2017 01:39:35 +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 8AFCA1EE3 for ; Sun, 19 Feb 2017 01:39:35 +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 v1J1dZu5045077 for ; Sun, 19 Feb 2017 01:39:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217214] frequent panics in tcp_output/sbsndptr Date: Sun, 19 Feb 2017 01:39:35 +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-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: p-fbsd-bugs@ziemba.us 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: Sun, 19 Feb 2017 01:39:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217214 --- Comment #2 from G. Paul Ziemba --- (In reply to Hiren Panchasara from comment #1) Thank you for your input. Yes, I am running VirtualBox, but just to be clea= r, the panics are occurring on the host system, not the guest. I have rebuilt the kernel with INVARIANTS in hopes of obtaining additional info, but will also see about trying some older versions as you suggest. It's not entirely clear to me that the reboot loop with the non -O2 kernel = is panicinn at the same place. I'm also seeing some startup time panics at line 760 of /usr/src/sys/ufs/ufs/ufs_lookup.c (ufs_dirbad: /v2: bad dir ino 270866706 at offset 1024: mangled entry) in the -O2 kernel. I speculate the= se could be the result of a prior crash leaving the filesystem in an improper state. --=20 You are receiving this mail because: You are the assignee for the bug.=