From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 23:57:04 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC9AD16A41C for ; Mon, 6 Jun 2005 23:57:04 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A0EB43D4C for ; Mon, 6 Jun 2005 23:57:04 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5180151282; Mon, 6 Jun 2005 19:57:03 -0400 (EDT) Date: Mon, 6 Jun 2005 19:57:03 -0400 From: Kris Kennaway To: "Grooms, Matthew" Message-ID: <20050606235703.GA1106@xor.obsecurity.org> References: <28FCC7CB4CF6EA43AF83BCA2096E97D013E555@AUSEX2VS1.seton.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline In-Reply-To: <28FCC7CB4CF6EA43AF83BCA2096E97D013E555@AUSEX2VS1.seton.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: 5.4-RELEASE lockups on amd64 SMP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 23:57:04 -0000 --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 06, 2005 at 06:54:05PM -0500, Grooms, Matthew wrote: > My appologies. With the debug options listed in my previous post ( should= have read 5.4 not 5.3 ), I got a lock order reversal. After a while, it pa= niced and spat out this ... >=20 > lock order reversal > 1st 0xffffffff80752ec0 pf task mtx (pf task mtx) @ contrib/pf/net/if_pfsy= nc.c:1621 > 2nd 0xffffffff8076e9f0 user map (user man) @ vm/vm_map.c:2998 > KDB: stack backtrace: > witness_checkorder() at witness_checkorder+0x654 > _sx_xlock() at _sx_xlock+0x51 > vm_map_lookup() at vm_map_lookup+0x44 > vm_fault() at vm_fault+0xba > trap() at trap+0x1c5 > alltraps_with_regs_pushed() at alltraps_with_regs_pushed+0x5 > pf_state_tree_lan_ext_RB_REMOVE() at pf_state_tree_lan_ext_RB_REMOVE+0x10c > pf_purge_expired_states() at pf_purge_expired_states+0xab > pfsync_input() at ip_input+0x10f > netisr_processqueue() at netisr_processqueue+0x17 > swi_net() at swi_net+0xa8 > ithread_loop() at ithread_loop+0xd9 > fork_exit() at fork_exit+0xc3 > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip =3D 0, rsp =3D 0xffffffffb44f9d00, rbp =3D 0 --- > KDB: enter: withness_ckeckorder > [thread pid 110 tid 100089] > Stopped at kdb_enter+0x2f: nop > db> panic blockable sleep lock (sleep mutex) tty @ kern/kern_event.c:1453 > cpuid =3D 0 > boot() called on cpu#0 > Uptime: 10m40s > Dumping 4864 mB > 16 32 ......... >=20 > After a reboot, I received another panic. >=20 > Tracing pid 603 tid 100140 td 0xffffff012efda500 > kdb_enter() at kdb_enter+02f > panic() at panic+0x249 > ffs_blkfree() at ffs_blkfree+0x483 > indir_trunc() at indir_trunc+0x190 > indir_trunc() at indir_trunc+0x1fb > handle_workitem_freeblocks() at handle_workitem_freeblocks+0x228 > softdep_setup_freeblocks() at softdep_setup_freeblocks+0x730 > ffs_truncate() at ffs_truncate+0x1c9 > ffs_snapshot() at ffs_snapshot+0x717 > ffs_omount() at ffs_omount+0x16e > vfs_domount() at vfs_domount+0x5a0 > mount() at mount+0xd8 > syscall() at syscall+0x1fb > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall(21, FreeBSD ELF64, mount), rip =3D 0800697580, rsp =3D 0x7fff= ffffec58, fbp =3D 0x515b10 --- >=20 > I am guessing this is related to background fsck processes being launched= because it happened consistently until I disabled background fsck and perf= ormed one manually in single user mode. Now I can boot normally into multi = user mode. You may have had disk corruption that was not repaired by bg fsck. Kris --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCpOLOWry0BWjoQKURAmwVAKCWmwXnos1SC8i8uWfPELTdCVRZaQCgy1zm 2YEPkEYFjG11SxkMFTCIYPc= =TrIg -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S--