From owner-freebsd-current@freebsd.org  Wed Apr 19 18:44:27 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FC3FD45897;
 Wed, 19 Apr 2017 18:44:27 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E30B3A17;
 Wed, 19 Apr 2017 18:44:26 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net
 [73.231.226.104])
 by mail.baldwin.cx (Postfix) with ESMTPSA id 24A9410A7DB;
 Wed, 19 Apr 2017 14:44:20 -0400 (EDT)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-current@freebsd.org, jbtakk@iherebuywisely.com
Cc: current <current@freebsd.org>
Subject: Re: new problem?
Date: Wed, 19 Apr 2017 11:17:55 -0700
Message-ID: <3034917.2qhsWDdZ0Z@ralph.baldwin.cx>
User-Agent: KMail/4.14.10 (FreeBSD/11.0-STABLE; KDE/4.14.10; amd64; ; )
In-Reply-To: <E1cxNoK-0000K1-S7@rmmprod05.runbox>
References: <E1cxNoK-0000K1-S7@rmmprod05.runbox>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3
 (mail.baldwin.cx); Wed, 19 Apr 2017 14:44:20 -0400 (EDT)
X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx
X-Virus-Status: Clean
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 18:44:27 -0000

On Sunday, April 09, 2017 06:08:04 PM Jeffrey Bouquet wrote:
> i386_set_ldt: start=-1 num=1 descs=0x38449fac

This message is a harmless debug printf.  Somehow you compiled
sys/i386/i386/sys_machdep.c with 'DEBUG' defined to enable it
though.  (The message is not enabled by default.)
 
> Tons of those, eight at a time, newly spamming /var/log/messages, maybe after a
> fsck_ffs -y the partitions after a crash, that fixed it,
> 
> as in
> df 
> df output, then eight of the above line with the hex values varying only
> ls
> ls output, then eight of the above line with the hex values varying only
> ......................................
> 2nd problem
> persistent LOR in  [several]
> 
> nvidia_os:c:662, 824
>  
> [dmesg only, above, ]
> 
> vfs_mount.c:1277
> ffs_softdep.c:1908
> vfs_subr.c:2600,  2150, 
> ffs_vnops.c:280
> vfs_bio.c:3500
> ufs_dirhash.c:281
> vfs_syscalls.c:3364
> 
> [some above also in dmesg, most in /var/log/messages...

There are several known LORs in the VFS/UFS code that are either false
positives or ones that have effectively been harmless.

-- 
John Baldwin