From owner-freebsd-questions@FreeBSD.ORG  Fri Sep 11 10:51:03 2009
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 09DBB1065670
	for <freebsd-questions@freebsd.org>;
	Fri, 11 Sep 2009 10:51:03 +0000 (UTC)
	(envelope-from bruce@cran.org.uk)
Received: from muon.cran.org.uk (muon.cran.org.uk [66.246.138.153])
	by mx1.freebsd.org (Postfix) with ESMTP id D5C8B8FC15
	for <freebsd-questions@freebsd.org>;
	Fri, 11 Sep 2009 10:51:02 +0000 (UTC)
Received: from unknown (87-194-158-129.bethere.co.uk [87.194.158.129])
	(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	by muon.cran.org.uk (Postfix) with ESMTPSA id F118881C4;
	Fri, 11 Sep 2009 10:51:01 +0000 (UTC)
Date: Fri, 11 Sep 2009 11:51:10 +0100
From: Bruce Cran <bruce@cran.org.uk>
To: Alex R <alex@mailinglist.ahhyes.net>
Message-ID: <20090911115110.000076ce@unknown>
In-Reply-To: <4AA86C90.7030908@mailinglist.ahhyes.net>
References: <4AA86C90.7030908@mailinglist.ahhyes.net>
X-Mailer: Claws Mail 3.7.1 (GTK+ 2.16.0; i586-pc-mingw32msvc)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject: Re: 7.2-RELEASE/amd64 - weird stuff in dmesg
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 10:51:03 -0000

On Thu, 10 Sep 2009 13:03:44 +1000
Alex R <alex@mailinglist.ahhyes.net> wrote:

> Hi everyone,
> 
> I was wondering whether anyone could shed some light on the following 
> messages I am seeing in dmesg:
> 
> --------------------
> 
> <<33>>aarrpp::  uunnkknnoowwnn  hhaarrddwwaarree  aaddddress format
> (0x0000) ress format (0x0000)
> arp: unakrnpo:w nu nhkanrodwwna rhea raddwdarrees sa dfdorremsast  
> f(o0rxm0a0t0 0()0
> x
> 0000)
> a<rp:3 u>anrkpn:o wunn khnaorwdnw ahraer dawdadrree sasd dfroersmsa
> tf o(r0mxat0 0(00x000)0
> 0
> )
> arp: unknown hardware address format (0xarp:0 7u0n0k)n
> o
> wn hardware address format (0x0700)
> aarrpp::  uunnkknnoowwnn  hhaarrddwwaarree  aaddddrreessss  
> ffoorrmmaatt  ((00xx00770000))
> 
> --------------------------
> 
> Any ideas whats with the jumbled/double letters? Is there something 
> wrong with the machine or is it a bug in the OS? I have seen similar 
> symptoms on SMP enabled boxes when shutting down if 2 processes call 
> kprintf() or printf() at the same time, it results in garbled output.


> Should i turn a blind eye to this?

Yes :)
It's a known issue that the kernel printf isn't locked so messages get
mixed up like that.    In 8.0 the PRINTF_BUFR_SIZE option has been
added which should fix it.

-- 
Bruce