Date: Sat, 13 Sep 2003 09:54:03 +1000 From: Tim Robbins <tjr@FreeBSD.ORG> To: Sergei Vyshenski <fbsd4@pn.sinp.msu.ru> Cc: freebsd-stable@freebsd.org Subject: Re: fxp damages dmesg? Message-ID: <20030912235403.GA4576@dilbert.robbins.dropbear.id.au> In-Reply-To: <5.1.0.14.2.20030913015611.00a75180@vivaldi.pn.sinp.msu.ru> References: <5.1.0.14.2.20030913015611.00a75180@vivaldi.pn.sinp.msu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030912235403.GA4576>