Date: Thu, 30 Nov 2017 09:25:48 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Masachika ISHIZUKA <ish@amail.plala.or.jp>, freebsd-current@freebsd.org Subject: Re: panic r326359 Message-ID: <73623cb8-fd62-7064-3915-8b8efba3df61@selasky.org> In-Reply-To: <20171130.102548.289362648662158746.ish@amail.plala.or.jp> References: <20171129.213725.810459586021929184.ish@amail.plala.or.jp> <a80976a8-aa9b-bca4-dea2-c8b4888b3330@selasky.org> <20171130.102548.289362648662158746.ish@amail.plala.or.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?73623cb8-fd62-7064-3915-8b8efba3df61>