Lock order reversal in 5.2-CURRENT

Doug White dwhite at gumbysoft.com
Wed Aug 11 10:21:32 PDT 2004

On Wed, 11 Aug 2004, Terrence Koeman wrote:

> I think something else is wrong, as I get different lock order reversals and
> some other errors that all lockup the box. Earlier I had a corrupted cc
> binary after a buildworld.
> Everything points to a hardware failure somewhere, but I already switched
> the hardware before this happened, I swapped RAID arrays in identical
> machines, and the machine where -CURRENT runs on now was a production server
> that ran 4.9/4.10-STABLE for months under heavy load without any problems
> whatsoever.
> The following is what I got today:
> Second bad
> /: bad dir ino 16110954 at offset 24: mangled entry
> panic: ufs_dirbad: bad dir

Your RAID is doing a really good job of corrupting your data. :)  What
RAID controller and volume layout are you using?
> Fatal trap 18: integer divide fault while in kernel mode

This looks more serious .. you may have a bad CPU, memory, or some other
critical component.

Doug White                    |  FreeBSD: The Power to Serve
dwhite at gumbysoft.com          |  www.FreeBSD.org

More information about the freebsd-current mailing list