Date: Mon, 20 Aug 2007 23:26:59 +0300 From: Nikolay Pavlov <qpadla@gmail.com> To: freebsd-current@freebsd.org Subject: Crash in todays current (panic: bio_caller1 used by the provider ad0s4e) Message-ID: <200708202327.03951.qpadla@gmail.com>
next in thread | raw e-mail | index | archive | help
--nextPart4682400.etQkBxHyO7
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Another one panic caused by geom_journal journal initialization (sorry for=
=20
tautology) at the final stage of EVERY kernel booting process.
I am unable to get a full crashdump because my dump device is not ready at=
=20
that moment.
I see the message:
panic: bio_caller1 used by the provider ad0s4e
And a backtrace like this one:
kdb_enter
panic
g_io_deliver
g_std_done
biodone
g_io_schedule_up
g_up_procbody
fork_exit
fork_trempoline
And the current thread is pid 3 "g_up"
The intresting thing is that i do not have this panic with GENERIC kernel.
My kernel is deffer from it by this lines:
#!commented! options WITNESS_SKIPSPIN
options DEBUG_LOCKS
options DEBUG_VFS_LOCKS
options DIAGNOSTIC=20
=2D-=20
* Best regards, Nikolay Pavlov *
--nextPart4682400.etQkBxHyO7
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQBGyfkX/2R6KvEYGaIRAjMyAKCAFddLIPk6V4Nu7pgHlYftldwN2QCfSR/5
oC+0DxYnLDbqcVD55x8fLaQ=
=xsIM
-----END PGP SIGNATURE-----
--nextPart4682400.etQkBxHyO7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200708202327.03951.qpadla>