Date: Wed, 18 Dec 2013 22:45:57 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: r259072 is not a happy camper... Message-ID: <75109.1387406757@critter.freebsd.dk> In-Reply-To: <201312181458.20649.jhb@freebsd.org> References: <27325.1386444776@critter.freebsd.dk> <201312131620.25107.jhb@freebsd.org> <55350.1387010679@critter.freebsd.dk> <201312181458.20649.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <201312181458.20649.jhb@freebsd.org>, John Baldwin writes: >> >Does it get a crashdump if you try? >> >> No :-( >> >> There may be a connection to unclean UFS filesystems (SU + TRIM, no J). > >Is this reproducible? Not really. It seems to happen at random, usually shortly after boot and as I mentioned, there is some indications of it being related to munged filesystems. Amongst these indications: Booting single-user and running fsck (without -p) almost always prevents it from happening until after next crash, and I think all the backtraces I've see have been UFS or maybe even WITNESS+UFS related. If it is WITNESS related, the serial console is obviously a prime suspect... But all that said, I havn't seen it for a couple of days... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?75109.1387406757>