The following reply was made to PR port-i386/35507; it has been noted by GNATS.

From: "Thomas Feddersen" <thomas.feddersen@t-online.de>
To: <gnats-bugs@NetBSD.org>, <port-i386-maintainer@netbsd.org>,
	<gnats-admin@netbsd.org>, <netbsd-bugs@netbsd.org>
Cc: 
Subject: RE: port-i386/35507: dmesg garbled / corrupted
Date: Tue, 30 Jan 2007 16:48:39 +0100

 > -----Original Message-----
 > From: Pavel Cahyna [mailto:pavel@NetBSD.org]
 > Sent: Monday, January 29, 2007 1:05 PM
 > To: port-i386-maintainer@netbsd.org; gnats-admin@netbsd.org;=20
 > netbsd-bugs@netbsd.org; thomas.feddersen@t-online.de
 > Subject: Re: port-i386/35507: dmesg garbled / corrupted=20
 >=20
 >  Please see if this commit:
 > =20
 >  http://mail-index.netbsd.org/source-changes/2007/01/06/0050.html
 > =20
 >  fixes your problem.
 > =20
 >  You could try a newer kernel from autobuilds.=20
 
 Dear Pavel,
 
 I downloaded a kernel from the main (HEAD) branch,
 
 # uname -a
 NetBSD Ximus.feddersen.xx 4.99.9 NetBSD 4.99.9 (GENERIC.MPACPI) #0: Sun =
 Jan
 21 19:06:43 UTC 2007
 builds@b0.netbsd.org:/home/builds/ab/HEAD/i386/200701200000Z-obj/home/bui=
 lds
 /ab/HEAD/src/sys/arch/i386/compile/GENERIC.MPACPI i386
 #
 
 and: Problem solved! Output from "dmesg" and "messages" are not =
 corrupted.
 Will ths fix be pulled into the 4.0 release?
 
 Thank you for your quick response.=20
 Kind regards
 Thomas