From owner-freebsd-bugs@FreeBSD.ORG Wed Oct 15 17:21:24 2014 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0F53EA00 for ; Wed, 15 Oct 2014 17:21:24 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EAEFE3FE for ; Wed, 15 Oct 2014 17:21:23 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s9FHLNSh072146 for ; Wed, 15 Oct 2014 17:21:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 160760] (Kernel) Log messages garbled/interleaved Date: Wed, 15 Oct 2014 17:21:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 8.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: tilghman@meg.abyt.es X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2014 17:21:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=160760 tilghman@meg.abyt.es changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tilghman@meg.abyt.es --- Comment #1 from tilghman@meg.abyt.es --- This issue has now just occurred to us, as well, on FreeBSD 9.1: -----snip----- <<<<66>n66>n>e>newwnnenffessw wsnfe serrs vsneevefr sr vfrsrervee r fereeefr refnnasearns:/amse:/mnennt/:/mpatn/t/poopoool/l/zosez/ooel:///amaznoe/rtta/poo/rlima/t/rgiezomate//iarmgsaet/igessma: g:eno:s : nnot trote respo rendnsinsgpp oo nd <6ing <>6>tndin respgo n ding newnfs server freenas:/mnt/pool/zoe/art/imagesne:n wenfwsn fsnoervts e rseerverspro fnrdeinenag fs <<6>6>:r/emennnatse:w/m/npnoewnftons f/s lserse/vrpooezrl/ vozoe/fartre/ee/enarimaa rtfreegse:s:n//a s:minmnt/apges: /mnonoott t /prresol/zpoeospnoe/ondiol/dingng a -----snip----- The message fragments seem to be specifically about a constantly mounted NFS server (running FreeNAS). The server on which this occurred also happens to be running under VMware (as is the FreeNAS server). -- You are receiving this mail because: You are the assignee for the bug.