From owner-freebsd-current@freebsd.org Thu Nov 30 08:28:35 2017 Return-Path: Delivered-To: freebsd-current@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 E6384DFCC35 for ; Thu, 30 Nov 2017 08:28:35 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 AEB777B6ED for ; Thu, 30 Nov 2017 08:28:35 +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 125D02603A1; Thu, 30 Nov 2017 09:28:32 +0100 (CET) Subject: Re: panic r326359 To: Masachika ISHIZUKA , freebsd-current@freebsd.org References: <20171129.213725.810459586021929184.ish@amail.plala.or.jp> <20171130.102548.289362648662158746.ish@amail.plala.or.jp> From: Hans Petter Selasky Message-ID: <73623cb8-fd62-7064-3915-8b8efba3df61@selasky.org> Date: Thu, 30 Nov 2017 09:25:48 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171130.102548.289362648662158746.ish@amail.plala.or.jp> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 30 Nov 2017 08:28:36 -0000 On 11/30/17 02:25, Masachika ISHIZUKA wrote: >>> After updating r326359, kernel panic has occure. ( I can boot up >>> but panics within a few minutes.) >>> It was good working up to r325887. >> >> Try to set: >> kern.smp.disabled=1 >> from loader or in /boot/loader.conf > > Thank you for reply, HPS. > > It seems good working by 'set kern.smp.disabled=1' on loader prompt. > > # Another panic has occure: > # Panic String: ufs_dirbad: /: bad dir ino 4334201 at offset 5120: mangled entry > # > # I think that had damaged internal SSD at last panic. > # I repaired SSD by fsdb according to > # http://phaq.phunsites.net/2007/07/01/ufs_dirbad-panic-with-mangled-entries-in-ufs/ > # and now work well. > Issue should be fixed by: https://svnweb.freebsd.org/changeset/base/326376 --HPS