On Wed, Jun 28, 2006 at 03:59:18PM +0800, skysbird@gmail.com wrote:
> Hello,Everyone:
>     I Really hope you can help me to solve this problem up.I have a
> Server,and the hardware profile is here:
> Pentinum D 3.00G(dual-core)
> 2*512MB ddr2
> 2*SEAGATE HARDDISK(SATA,160G,RAID1)
> 
> and I had patched to the LBA48 problem with SEAGATE in wd.c,and I
> successfully make the raid1 through the RAIDFRAME
> 
> My problem is here:
> When I just install the NetBSD3.0,and login to my system,type dmesg,and I
> was so surprised to find the output like this:
> [...]
>  ^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?M^?NetBSD
> 3.0 (GENERIC.MPACPI) #0: Tue Jun 27 19:45:59 UTC 2006
>  skysbird@bsdchina.org:/usr/src/sys/arch/i386/compile/GENERIC.MPACPI
> [...]
> 
> Is here anybody can help me ? Why ? Why did so many ^M come out! And I don't
> find something wrong with my system,I can use the system now in gear. but I
> really want to know whether these ^M is the hardware error? I want to solve
> up this problem. I'm waiting your reply online now~.

This is harmless. It's most probably that the bios doesn't initialize the
ram (or doesn't initialize it to 0). The system doesn't clear the boot
message buffer at boot to preserve the messages after a warm boot, in case
the BIOS doesn't rewrite memory after a warm boot.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--