Date: Mon, 6 Apr 2020 15:56:36 +0300 From: Lev Serebryakov <lev@FreeBSD.org> To: Hans Petter Selasky <hps@selasky.org>, Masachika ISHIZUKA <ish@amail.plala.or.jp>, freebsd-current@freebsd.org Subject: Re: r359627 is panicked with 'softdep_setup_blkfree: not free' Message-ID: <80d0492a-d2c3-ab36-54f6-ccf637d9b04a@FreeBSD.org> In-Reply-To: <4094df3d-00d2-4c30-acc2-136f6d02aa63@selasky.org> References: <20200406.174413.600265685809252683.ish@amail.plala.or.jp> <20200406.195118.1912278797281119565.ish@amail.plala.or.jp> <20200406.215032.1194930430950082666.ish@amail.plala.or.jp> <4094df3d-00d2-4c30-acc2-136f6d02aa63@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --jgPEMDC8J9WHunwhmsrmmJVzW3dQ2iCJz Content-Type: multipart/mixed; boundary="6CqfFkzaw7hiz5RXerPeZAegzKTdHXvoN" --6CqfFkzaw7hiz5RXerPeZAegzKTdHXvoN Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 06.04.2020 15:52, Hans Petter Selasky wrote: >>>> =C2=A0=C2=A0 I'm using r359627M. (r359627 with mount_udf2). >>>> =C2=A0=C2=A0 It is panicked with 'softdep_setup_blkfree: not free'. >>>> >>>> =C2=A0=C2=A0 Panic log was stored as follows. >>> >>> =C2=A0=C2=A0 Sorry, this panic was my mistake. >>> =C2=A0=C2=A0 I forgot to update drm-current-kmod. >>> >>> old% pkg info drm-current-kmod >>> [snip] >>> Annotations=C2=A0=C2=A0=C2=A0 : >>> =C2=A0=C2=A0=C2=A0=C2=A0FreeBSD_version: 1300084 <--- old >>> [snip] >>> >>> old# pkg install -f drm-current-kmod >>> new% pkg info drm-current-kmod >>> [snip] >>> Annotations=C2=A0=C2=A0=C2=A0 : >>> =C2=A0=C2=A0=C2=A0=C2=A0FreeBSD_version: 1300088 >>> [snip] >>> >>> =C2=A0=C2=A0 This works fine. >> >> =C2=A0=C2=A0 The panic was occured again. >> =C2=A0=C2=A0 Crash dump was the same. >> =C2=A0=C2=A0 To reinstall drm-current-kmod was not fixed this issue. >> >=20 > Issue probably will go away if you boot to single-user-mode and run fsc= k > -y before booting the system. Regardless, kernel should not panic. I had several panics like this, too. I had some unstable hardware which could turn off due to overheating, and when I had UFS+SU, it could panic in such way after reboot (typically after 5 or 10 minutes of normal work)... I didn't report these panics, as was not enable to collect any meningful information like crashdump or stack, as this system was headless and consoleless. --=20 // Lev Serebryakov --6CqfFkzaw7hiz5RXerPeZAegzKTdHXvoN-- --jgPEMDC8J9WHunwhmsrmmJVzW3dQ2iCJz Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAl6LJwlfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c R49UFg//QAM0CDWDogYPth9lL7poOOjwRCwO3sNKBJtO5tP5SAYryFZdtkFZS09L v1vvRVwvEbGkdUlf0wBRuNGEOUImHCTEZXVso/2RJ9k41EpVT1f34z40q6ABKji7 wfoP3FyCv8aVGrg1qjucDOJ8kadCqIwXyd+1VfibGT5ZwT0f+BZ8mSy1vUazBm4y 0EQknZr/LHDb38AfaERio7GszU3YMJh3JKvLChkT1K/ZjSMRaAyiWNpPUPjPDtvp pBmG77Vzlkag4MKOfYOzS458VeAE6UNyZici6YIlnKGX4vBPasdG5Z7OkSc90ZEW HI9Qng+PzHSk2jrg+GClcN0x94Qfqz3Kax6gr+uvcvYZxKWSIeAwVOWB2eI8N4Q0 8pFvpzKqCkeSJd1GteESlgAVo308aThCQfW2GzMJLTbO6LphetYhpMj1dVyTnXi1 g7fBMIKRSY87OcFJUMR8DwX8NcwB/tyvdQy/RBFF5ZEiEOySS0La2TFgEQHiylE+ 0deLbynM1nLuv38m4P7VwSYmKdP6dTwEaRK4mWP/bLoZ9stdIJMdS+DgFJYb+LG6 g6axCr+TtlLGyxnsAUsvkvZS7ORJqYQrbrHMuj1W4noqJ49babNd/qPtmyGYqZ5h ZJAK1vmQtytn2b1K3FOWuaWy4V1tC90tDxxuXUVawH0v6Vwe7IE= =iFjo -----END PGP SIGNATURE----- --jgPEMDC8J9WHunwhmsrmmJVzW3dQ2iCJz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80d0492a-d2c3-ab36-54f6-ccf637d9b04a>