From nobody@FreeBSD.org  Fri Sep 16 07:59:39 2011
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 28B551065670
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 16 Sep 2011 07:59:39 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22])
	by mx1.freebsd.org (Postfix) with ESMTP id 0DD888FC08
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 16 Sep 2011 07:59:39 +0000 (UTC)
Received: from red.freebsd.org (localhost [127.0.0.1])
	by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p8G7xcsX003086
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 16 Sep 2011 07:59:38 GMT
	(envelope-from nobody@red.freebsd.org)
Received: (from nobody@localhost)
	by red.freebsd.org (8.14.4/8.14.4/Submit) id p8G7xcK5003085;
	Fri, 16 Sep 2011 07:59:38 GMT
	(envelope-from nobody)
Message-Id: <201109160759.p8G7xcK5003085@red.freebsd.org>
Date: Fri, 16 Sep 2011 07:59:38 GMT
From: Christian Marg <marg@rz.tu-clausthal.de>
To: freebsd-gnats-submit@FreeBSD.org
Subject: (Kernel) Log messages garbled/interleaved
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         160760
>Category:       kern
>Synopsis:       (Kernel) Log messages garbled/interleaved
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 16 08:00:19 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     Christian Marg
>Release:        FreeBSD 8.2-RELEASE
>Organization:
Clausthal University of Technology
>Environment:
FreeBSD imhotep.rz.tu-clausthal.de 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18 02:24:46 UTC 2011     root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
On some occasions the kernel logs messages interleaved with each other, which makes them quite unreadable. I've seen it happening on shutdowns - thats why I didn't report it earlier. This time it made its way to our logfiles, so here is  an example (output from dmesg):

=====8<=====8<=====8<=====8<=====
nfs server nas1:/vol/fc600/www-data: not responding
nfs server nas1:/vol/fc600/www-data: not responding
nfs server nas1:/vol/fc600/www-data: not respnofnsd isnegr
ver nas1:/vol/fc600/www-data: not respondinngfs

server nas1:/vol/fc600/www-data: not respnofnsd isnegr
v
er nas1:/vol/fc600/www-data: not respondnifnsg
s
erver nas1:/vol/fc600/www-data: nnofts  serverre snpaosn1d:i/nvgo
l
/fc600/www-data: not responding
<<66>>nnffss  sseerrvveerr  nnaass11:://vvooll//ffcc660000//wwwwww--ddaattaa::  nonto tr ersepsopnodnidnign
g

nfs snefrsv esre rnvaesr1 :n/avso1l://fvco6l0/0f/cw6w0w0-/dwawtwa-:d atan:o t rneostp ornedsipnogn
d
ing
nfs senrfsv ers enravse1r: /vonla/sf1c:6/0v0o/lw/wfwc-6d0a0t/aw:w wn-odta trae:s ponndoitn gr
e
sponding
nfs server nas1n:f/sv oserver nas1:/vol/fc600/www-data: not responding
l/fc600/www-datnaf:s  nsoetr vreers ponnadsi1n:g/
v
ol/fc600/www-data: not responding
nfs server nas1:/vol/fc600/www-data: not rnefssp osnedrivnegr

nas1:/vol/fc600/www-data: not respondinngf
s
 server nas1:/vol/fc600/www-data: nnfost r esersvpeorn dniansg1
:
/vol/fc600/www-data: not responding
nfs server nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-datanfs server nas1:/vol/fc600/www-data: is:  ailsi vael iavgea iang
a
in
nfs server nas1:/vol/fc600/www-data: is alive agnafisn
s
erver nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
nfs sernfs server nas1:/vol/fc600/www-data: is alive again

ver nas1:/vol/fc600/www-data: is alive again
nfs server nas1:/vol/fc600/www-data: is alive again
=====8<=====8<=====8<=====8<=====

>How-To-Repeat:
Unfortunately I just observe this happening from time to time but could never tell how to provoke this behaviour. It seems like some kind of a race condition...
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
