Bug 160760 - (Kernel) Log messages garbled/interleaved
Summary: (Kernel) Log messages garbled/interleaved
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 8.2-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-16 09:00 UTC by Christian Marg
Modified: 2018-05-20 23:51 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Marg 2011-09-16 09:00:19 UTC
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...
Comment 1 tilghman 2014-10-15 17:21:24 UTC
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
<o6>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).
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2018-05-20 23:51:24 UTC
For bugs matching the following conditions:
- Status == In Progress
- Assignee == "bugs@FreeBSD.org"
- Last Modified Year <= 2017

Do
- Set Status to "Open"