Date: Thu, 23 Jan 2014 17:49:25 +0100 From: =?utf-8?Q?Hans_Petter_Selasky?= <hans.petter.selasky@bitfrost.no> To: =?utf-8?Q?Thomas_Hoffmann?= <trh411@gmail.com>, =?utf-8?Q?freebsd-current?= <freebsd-current@freebsd.org> Subject: RE: lock order reversals w/ backtrace Message-ID: <zarafa.52e14815.6aa6.633e23667a81a1c3@mail.lockless.no> In-Reply-To: <CAB7-odngiUKR9H1anXSLAm-g7_NiSAV6a_2XKWvZ_zY0R2sgOg@mail.gmail.com> References: <CAB7-odngiUKR9H1anXSLAm-g7_NiSAV6a_2XKWvZ_zY0R2sgOg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,=0D=0A=0D=0ACan you see if you can snap some keywords of the backtrace= s, like usb_xxx usbdx_xxx cam scsi or something like that.=0D=0A=0D=0AEls= e I believe there are some sysctl options to prevent the final reboot som= ehow so that you can write down the messages.=0D=0A=0D=0A--HPS=0D=0A=20=0D= =0A-----Original message-----=0D=0A> From:Thomas Hoffmann <trh411@gmail.c= om <mailto:trh411@gmail.com> >=0D=0A> Sent: Thursday 23rd January 2014 17= :15=0D=0A> To: freebsd-current <freebsd-current@freebsd.org <mailto:freeb= sd-current@freebsd.org> >=0D=0A> Subject: lock order reversals w/ backtra= ce=0D=0A>=20=0D=0A> A few days ago I started running 11.0-CURRENT at r260= 971 for the first time.=0D=0A>=20=0D=0A> The last couple of times I shutd= own my system I noticed 2 or 3 short "lock=0D=0A> order reversal" message= s with accompanying backtraces scroll by. Do these=0D=0A> messages repres= ent a problem that I should report or can I ignore them as=0D=0A> debug i= n nature=3F If I should report them, how or where do these messages=0D=0A= > get logged=3F I can find no reference to them in syslog or anywhere els= e upon=0D=0A> my subsequent reboot.=0D=0A>=20=0D=0A> I also had a couple = of these messages pop up the other day while=0D=0A> mounting/umounting US= B thumb drives. I did not think anything of them at=0D=0A> the time as th= e mounts/umounts completed successfully.=0D=0A>=20=0D=0A> Please advise. = Thanks.=0D=0A>=20=0D=0A> -Tom=0D=0A> ____________________________________= ___________=0D=0A> freebsd-current@freebsd.org <mailto:freebsd-current@fr= eebsd.org> mailing list=0D=0A> http://lists.freebsd.org/mailman/listinfo= /freebsd-current <http://lists.freebsd.org/mailman/listinfo/freebsd-curre= nt>=20=0D=0A> To unsubscribe, send any mail to "freebsd-current-unsubscri= be@freebsd.org <mailto:freebsd-current-unsubscribe@freebsd.org> "=0D=0A>=20= =0D=0A=0D=0A From owner-freebsd-current@FreeBSD.ORG Thu Jan 23 17:11:14 2014 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 42BE6393 for <freebsd-current@freebsd.org>; Thu, 23 Jan 2014 17:11:14 +0000 (UTC) Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com [IPv6:2607:f8b0:400c:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EE4A6146A for <freebsd-current@freebsd.org>; Thu, 23 Jan 2014 17:11:13 +0000 (UTC) Received: by mail-ve0-f173.google.com with SMTP id oz11so1285251veb.32 for <freebsd-current@freebsd.org>; Thu, 23 Jan 2014 09:11:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ewBZuJOMa1nfvWCmOC9MHRyp2rS1Iw+ZB5Q6vgtekBE=; b=SyjdGZnm2PQkkGQcd0HQAmrFUydKRqffBgJG8KMirpLbvsokgXNOqeouJ2CsqTofm7 6zgvlYqQh4laEkLhxgY1LbdAZhacjNpH3pOjEWi6r6NxQuU8F/FpfImD8Qh2iSou412w 9qspQThVEH2DFRHS52Ay/WM4SfwT5XGQ7aIVGp+jHHASpbH/tVV7CbVD2iNNUCRGKz+C 2BaIsbH2bJWkCKP9ASq0G3ElFSBYq5Tye0TR72GSooiB4UdJmbBMSQMg7ok0rUuDl7c+ iwEAICf0pmLnYAeoHzdR9bdFhrSbILZU77+7G/iL3UIdClAM8AhvlLgz//Ju9vfU0Sv9 cSng== MIME-Version: 1.0 X-Received: by 10.220.193.70 with SMTP id dt6mr5037390vcb.17.1390497073172; Thu, 23 Jan 2014 09:11:13 -0800 (PST) Received: by 10.220.168.135 with HTTP; Thu, 23 Jan 2014 09:11:13 -0800 (PST) In-Reply-To: <alpine.BSF.2.00.1401230947460.76961@wonkity.com> References: <52E09F68.8020804@UToledo.edu> <1390486224478-5879039.post@n5.nabble.com> <alpine.BSF.2.00.1401230748450.76961@wonkity.com> <CAB7-od=jH_eiWoMWEFZ_CzDCrBdHonx3se1YkPX75Zwo-y_R+w@mail.gmail.com> <CAN6yY1t6NYyZvnE0Q40is17Y6DKs9B2CCCq4rSmOhjD3sWyczQ@mail.gmail.com> <alpine.BSF.2.00.1401230947460.76961@wonkity.com> Date: Thu, 23 Jan 2014 12:11:13 -0500 Message-ID: <CAB7-odmU3QFu0yriro_Kb+YZfH7_HzkZrdz7sFJyPhR_AdGctA@mail.gmail.com> Subject: Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release. From: Thomas Hoffmann <trh411@gmail.com> To: Warren Block <wblock@wonkity.com>, freebsd-current <freebsd-current@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: Jakub Lach <jakub_lach@mailplus.pl> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 23 Jan 2014 17:11:14 -0000 On Thu, Jan 23, 2014 at 11:52 AM, Warren Block <wblock@wonkity.com> wrote: > On Thu, 23 Jan 2014, Kevin Oberman wrote: > > On Thu, Jan 23, 2014 at 7:47 AM, Thomas Hoffmann <trh411@gmail.com> >> wrote: >> On Thu, Jan 23, 2014 at 9:56 AM, Warren Block <wblock@wonkity.com> >> wrote: >> > >> > >> > Using -DNOCLEAN with an existing /usr/obj can go even faster than >> ccache: >> > less than two minutes for a buildworld on my frequently updated >> i5/SSD >> > system, sometimes less than one minute. >> >> >> Can you elaborate on this, please? I always clear my /usr/obj before >> starting a buildworld, which takes 2 hours to run on my system. Are you >> saying if I do "make -DNOCLEAN buildworld" I do not have to clear /usr/obj >> first >> > > Yes. Removing /usr/obj is a faster way of doing 'make clean', mostly. > > > AND my buildworld will run faster >> > > Yes, because make will see that many/most files have already been built. > > (AND with no downside)? >> > > Well... mostly. :) > > I noticed that after 10.0-RELEASE, uname on my system still said > "PRERELEASE". That code had not been rebuilt because make did not see it > as needing a rebuild. You can still delete /usr/obj and run a full > buildworld from scratch every so often. > > I should give credit to bdrewery@ for reminding me about -DNOCLEAN when I > was whining about ccache not working on 10.0. It turned out to be a better > solution. > Hmm, I particularly like your suggestion of running a full buildworld periodically. With two hour buildworlds (from scratch) I was planning on rebuilding every couple of weeks. If using -DNOCLEAN can significantly reduce my buildworld time, I'll rebuild weekly and do a full build every fourth week. I'm anxious to give this approach a go and see how much time I can save on the buildworlds. Thanks for the info and tips. -Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?zarafa.52e14815.6aa6.633e23667a81a1c3>