In message <201312181458.20649....@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 p...@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. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
