From owner-freebsd-current@FreeBSD.ORG Fri Jan 23 18:33:39 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 785481065673 for ; Fri, 23 Jan 2009 18:33:39 +0000 (UTC) (envelope-from ptice@aldridge.com) Received: from starbase.aldridge.com (starbase.aldridge.com [205.196.186.12]) by mx1.freebsd.org (Postfix) with ESMTP id 3F2EE8FC14 for ; Fri, 23 Jan 2009 18:33:39 +0000 (UTC) (envelope-from ptice@aldridge.com) Received: from corporate.aldridge.com (corporate.aldridge.com [216.139.69.10]) by starbase.aldridge.com (8.14.3/8.14.2) with ESMTP id n0NIWnXL040785; Fri, 23 Jan 2009 12:32:49 -0600 (CST) Content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Fri, 23 Jan 2009 12:28:33 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: UFS/VFS lock order reversal on stock 8.0-200812-AMD64 Thread-Index: Acl9VCdrlOkSkRUXT3Gt9YKpkKDnFQAMr0/h References: <1232712477.89022.7.camel@buffy.york.ac.uk> <1232713174.89022.8.camel@buffy.york.ac.uk> From: "Paul Tice" To: "Gavin Atkinson" , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: RE: UFS/VFS lock order reversal on stock 8.0-200812-AMD64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 18:33:39 -0000 -----Original Message----- From: Gavin Atkinson [mailto:gavin@FreeBSD.org] Sent: Fri 1/23/2009 6:19 AM To: Paul Tice Cc: freebsd-current@FreeBSD.org Subject: Re: UFS/VFS lock order reversal on stock 8.0-200812-AMD64 =20 On Fri, 2009-01-23 at 12:07 +0000, Gavin Atkinson wrote: > On Thu, 2009-01-22 at 21:33 -0600, Paul Tice wrote: > > I'm new, so please advise me (gently?) about list protocol and such = if needed. > >=20 > > Using stock 8.0-CURRENT-200812-amd64, I am getting the messages = below. >=20 > 8.0-CURRENT is essentially the bleeding-edge of FreeBSD, and is where > development happens that has not necessarily proven itself as being > stable. As it is the development branch, it also has a lot of extra > debugging enabled, which is what you are seeing with the "lock order > reversals". >=20 > If you are not running 8-CURRENT for a specific reason (e.g. because = you > are doing FreeBSD OS development work, or you are prepared to help = debug > issues as you encounter them, or similar), you probably shouldn't be > running CURRENT. Stick with 7.1. >I should have also included (in answer to your actual question): >Neither the lock order reversals or the corrupted messages on shutdown >are anything you need worry about. >Gavin I wouldn't have asked if I wasn't willing to help debug (as possible, = and with very little coding knowledge.) I pulled out the 'extra debugging', made world and kernel, and rebooted. Notice the 5th line of da7's drive ID being interleaved with 'SMP: AP = CPU #1 Launched!' I'm fairly sure this is not a good thing, if for no other reason that = 'apparent garbage' in dmesg is not useful. da6 at mpt0 bus 0 target 6 lun 0 da6: Fixed Direct Access SCSI-5 device=20 da6: 300.000MB/s transfers da6: Command Queueing Enabled da6: 715404MB (1465149168 512 byte sectors: 255H 63S/T 91201C) da7 at mpt0 bus 0 target 7 lun 0 da7: Fixed Direct Access SCSI-5 device=20 da7: 300.000MB/s transfers da7: Command Queueing Enabled da7: 715404MB (1465149168 512 bytSeM Ps:e cAtPo rCsP:U 2#515 HL = a6u3nSc/hTe d9!12 01C) SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #5 Launched! Trying to mount root from ufs:/dev/ad20s1a Thank You Paul