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.
Sergei Vyshenski wrote:> 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 fxp0This is fairly normal -- the system message buffer contents aren't static. On a system with a long uptime, you might see nothing but arp messages, or core dump messages, etc. That's why /var/run/dmesg.boot exists.
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