My guess is that sysctl kern.version got corrupted during its
generation at build time somewhere.  Possibly a type casting issue or
overflow of some sort where ?^M is coming out as the text?

Again, just a guess.

_Matt

On 12/14/05, Geert Hendrickx <ghen@netbsd.org> wrote:
> Hi,
>
> one of my machines always produces a garbled dmesg: it begins with a lot =
of
> ^M characters, the end is truncated (it shows more  devices on the screen
> during boot), and again followed by a sequence of ^M (see attachment).  I
> see this both in dmesg(8) and in /var/run/dmesg.boot.  Any idea what coul=
d
> be causing this?  The machine is a pentium4 EM64T running 3.0_RC6/i386.
>
>         Geert
>
>
>