From owner-freebsd-questions@FreeBSD.ORG Tue May 20 02:17:55 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 345CC37B401 for ; Tue, 20 May 2003 02:17:55 -0700 (PDT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id D470D43FA3 for ; Tue, 20 May 2003 02:17:52 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 20 May 2003 10:17:52 +0100 (BST) To: Ciro In-Reply-To: Your message of "Tue, 20 May 2003 04:00:15 EDT." <20030520035715.Q18906-100000@aegir.asgardnet.org> Date: Tue, 20 May 2003 10:17:51 +0100 From: Ian Dowse Message-ID: <200305201017.aa40105@salmon.maths.tcd.ie> cc: freebsd-questions@freebsd.org Subject: Re: Strange log message in daily security run? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2003 09:17:55 -0000 In message <20030520035715.Q18906-100000@aegir.asgardnet.org>, Ciro writes: >Every now and again I'll get the following mess in my nightly security >run email. Is it a bug, bit-rot, or some kind of attack, or none of the >above? Has Anyone run into this mess before? > >aegir.asgardnet.org kernel log messages: .. >^H\^P \^P\^D\^B@\^H\^H\^D \^P\^A \^A@\^B\^H(\^D\^B\M^@\M^@\^P\^B\^H\ >^A\^BCopiright (c) 1992m2002 The FreeB\^SF PrO*ect. Does it just occur within a day or two of a reboot? If so it's nothing to worry about. This can happen if the system memory is not cleared by the BIOS and can get corrupted while rebooting (the memory contents rot away while the DRAM refresh mechanism is disabled). When FreeBSD boots up, it sees what it thinks is an intact message buffer, so it decides not to clear it (sometimes panic messages before a reboot survive, so this can be very useful). The problem has been fixed in -CURRENT by adding a checksum to the message buffer. Ian