Re: panic r326359
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. > > Issue should be fixed by: > https://svnweb.freebsd.org/changeset/base/326376 Thank you, HPS. I updated r326384 and it is good working. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic r326359
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 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic r326359
>>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. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic r326359
On 11/29/17 13:37, 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. # cat /var/crash/info.6 Dump header from device: /dev/gpt/fbswap Architecture: amd64 Architecture Version: 2 Dump Length: 505135104 Blocksize: 512 Compression: none Dumptime: Wed Nov 29 20:22:32 2017 Hostname: carrot.ish.org Magic: FreeBSD Kernel Dump Version String: FreeBSD 12.0-CURRENT #2 r326359: Wed Nov 29 19:06:12 JST 2017 ishiz...@carrot.ish.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC Panic String: Lock if_lagg rmlock not read locked @ /usr/src/sys/net/if_lagg.c:1655 Dump Parity: 971727379 Bounds: 6 Dump Status: good I put vmcore.6.bz2(157mb) in the following. https://www.ish.org/files/vmcore.6.bz2 Try to set: kern.smp.disabled=1 from loader or in /boot/loader.conf Does it still panic? --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
