From owner-freebsd-stable@FreeBSD.ORG Fri Sep 12 16:54:08 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93AD316A4BF for ; Fri, 12 Sep 2003 16:54:08 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id E966243F75 for ; Fri, 12 Sep 2003 16:54:07 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from mail.robbins.dropbear.id.au (210.50.86.106) by smtp01.syd.iprimus.net.au (7.0.018) id 3F4C093C003AEB98; Sat, 13 Sep 2003 09:54:06 +1000 Received: by mail.robbins.dropbear.id.au (Postfix, from userid 1000) id 152B3C8BD; Sat, 13 Sep 2003 09:54:03 +1000 (EST) Date: Sat, 13 Sep 2003 09:54:03 +1000 From: Tim Robbins To: Sergei Vyshenski Message-ID: <20030912235403.GA4576@dilbert.robbins.dropbear.id.au> References: <5.1.0.14.2.20030913015611.00a75180@vivaldi.pn.sinp.msu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.0.14.2.20030913015611.00a75180@vivaldi.pn.sinp.msu.ru> User-Agent: Mutt/1.4.1i cc: freebsd-stable@freebsd.org Subject: Re: fxp damages dmesg? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2003 23:54:08 -0000 On Sat, Sep 13, 2003 at 02:04:59AM +0400, Sergei Vyshenski wrote: > Motherboard ASUS CUSL2-C with 815EP chipset and > two Intel 82559 Pro/100 Ethernet cards > exibits the following. > > dmesg reports usual text only a few seconds after reboot. > Later it displays a single line with a fragment of ipfw log, e.g. > > 167 213.131.11.152 in via fxp0 > > which seems to change with each new activity of ipfw. > Files /var/log/dmesg.today and /var/log/dmesg.yesterday > rotate daily as usual and contain similar single line. > The file /var/run/dmesg.boot still has usual text of dmesg. > > This started not long before 4.9-PRERELEASE > No crushes at any CPU or network load, and no sane error messages. This bug has been around for quite a while, and has been reported (at least) as early as 4.2-R. I think it was fixed in 5.0-current, but I don't remember the details. Tim