Skip site navigation (1)Skip section navigation (2) 
Date:      Thu, 12 Aug 2004 00:09:57 +0200
From:      "Terrence Koeman" <root@mediamonks.net>
To:        "'Doug White'" <dwhite@gumbysoft.com>
Cc:        'John Baldwin' <jhb@FreeBSD.org>
Subject:   RE: Lock order reversal in 5.2-CURRENT
Message-ID:  <20040812000885.SM01804@manrikigusari>
In-Reply-To: <20040811101859.P99067@carver.gumbysoft.com>
index | next in thread | previous in thread | raw e-mail 

[-- Attachment #1 --]
> -----Original Message-----
> From: owner-freebsd-current@freebsd.org
> [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Doug White
> Sent: Wednesday, August 11, 2004 19:22
> To: Terrence Koeman
> Cc: freebsd-current@FreeBSD.org; 'John Baldwin'
> Subject: RE: Lock order reversal in 5.2-CURRENT
>
> 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?

It's a Promise FastTrak TX2000 with two mirrored 160Gb Maxtor drives.

> > 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.

I thought so too, because multiple weird errors usually point to the hardware.

But I have three identical systems with the only difference being the contents 
of the disks. The other two systems are running 4.10-STABLE with heavy load 
without any problems. I swapped the disks (only the disks) with a working 
system twice now and it locks up just the same.

I think the chance of three systems having the same hardware problem is really 
small, especially because 4.10-STABLE hasn't had a single problem on those 
systems in the couple of months they run.

Maybe 5.2-CURRENT has a specific problem with the hardware in the systems? But 
it's not like it is exotic hardware, they are SuperMicro 1U barebones with a 
Celeron 2600, 512MB of RAM and a FastTrak TX2000.

-- 
Regards,
Terrence Koeman

MediaMonks B.V. (www.mediamonks.com)
Please quote all replies in correspondence. 

[-- Attachment #2 --]
0	*H
010	+0	*H

S0=0ͺVT"rU0
	*H
0_10	UUS10U
VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0
960129000000Z
280801235959Z0_10	UUS10U
VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority00
	*H
0mVa-Hqg޹뷞
8%Fs$]
enVsߴX9knը?14׏4g	NEVixG)6c\-{2{0*/1g0
	*H
L?hC3]Mz36ؕ"6hl|B.?OvJ͠
)"]݁#{%F0yK@<_SH䆴{5{%ӎ?84q0f0Ϡ
O[uj)0
	*H
0_10	UUS10U
VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0
980512000000Z
080512235959Z010U
VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated00
	*H
0ZDUz-Ox6
JoTw*h1ApzKHV-BD\B/;'
]6B3nTOJƚj$e~7jJ	00	`HB05U.0,0*(&$http://crl.verisign.com/pca1.1.1.crl0GU @0>0<`HE0-0++www.verisign.com/repository/RPA0U00U0
	*H
B|ߌyLMU/P^N.^2yeJRը1!l4x		BZъު"!e3 3
>5d$[h|7d
Ž33>>s00
g'Jd(pkD3?0
	*H
010U
VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated0
040204000000Z
050203235959Z010U
VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. by Ref.,LIAB.LTD(c)9810UPersona Not Validated1402U+Digital ID Class 1 - Microsoft Full Service10UTerrence Koeman1"0 	*H
	root@mediamonks.net00
	*H
0Rt?Th i_3x]:C><ظkm
*<JZ5
-Z#yl(aW|I?E4=m/̳X~{!ǝ?e8040	U00U 00`HE00(+https://www.verisign.com/CPS0b+0V0VeriSign, Inc.0=VeriSign's CPS incorp. by reference liab. ltd. (c)97 VeriSign0	`HB00
`HE" 1a9692937cc291a36df017d840c44b1603U,0*0(&$"http://crl.verisign.com/class1.crl0
	*H
&qAq!LlɄ;tsܵN9`0={ޟukgo ?妍,3\D1"g	^FI
<CG/\-e)1>0:0010U
VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validatedg'Jd(pkD3?0	+0	*H
	1	*H
0	*H
	1
040811220955Z0#	*H
	1~W,sH)>ϔ}++0g	*H
	1Z0X0
*H
0*H
0
*H
@0+0
*H
(0+0
*H
0	+710010U
VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validatedg'Jd(pkD3?0*H
	1䠁010U
VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validatedg'Jd(pkD3?0
	*H
Aq8}W[H$<gI>>M6AobYO`2Pg<dX6uH"ȫf.<68Ge9aC1%7*¿:fo%TwE/"k,
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040812000885.SM01804>