Re: warning - receiver ring buffer overrun

[Chris Zakelj <c.zakelj@ieee.org>]

Nick Holland wrote:

>  well, no dmesg or anything else about your system...or what speed
>  your link is or or or...

Sorry, Nick.  My bad on that.  The link is a residential ADSL, 1.5M/384k.
dmesg...

osiris# cat /var/run/dmesg.boot
OpenBSD 3.4 (GENERIC) #18: Wed Sep 17 03:34:47 MDT 2003
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel 486DX (486-class)
real mem  = 66699264 (65136K)
avail mem = 55980032 (54668K)
using 839 buffers containing 3436544 bytes (3356K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 05/05/91
pcibios at bios0 function 0x1a not configured
bios0: ROM list: 0xc0000/0x8000 0xd8000/0x4000
isa0 at mainbus0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
vga0 at isa0 port 0x3b0/48 iomem 0xa0000/131072
wsdisplay0 at vga0: console (80x25, vt100 emulation), using wskbd0
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
wdc0 at isa0 port 0x1f0/8 irq 14
wd0 at wdc0 channel 0 drive 0: <QUANTUM BIGFOOT2550A>
wd0: 8-sector PIO, LBA, 2457MB, 4994 cyl, 16 head, 63 sec, 5033952 sectors
wd0(wdc0:0:0): using BIOS timings
we0: changing IRQ 9 to 3
we0 at isa0 port 0x280/32 iomem 0xd0000/16384 irq 3: WD8013EPC (16-bit)
we0: address 00:00:c0:93:8d:b3
we0: changing IRQ 10 to 11
we1 at isa0 port 0x300/32 iomem 0xcc000/8192 irq 11: SMC8416T (16-bit)
we1: address 00:e0:29:16:31:93
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
sysbeep0 at pcppi0
lpt2 at isa0 port 0x3bc/4: polled
npx0 at isa0 port 0xf0/16: using exception 16
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask 4040 netmask 4848 ttymask 484a
pctr: no performance counters in CPU
dkcsum: wd0 matched BIOS disk 80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
arplookup: unable to enter address for 172.16.0.1
osiris#

>  Does the ring buffer overrun error even cause you problems? A lot of
>  OpenBSD driver messages are more informative than serious distress.
>  Packets get lost in networks -- the entire system is designed to
>  tolerate it and deal with it. If they are not causing actual
>  problems, just turn off the monitor, problem solved. 8)

I'm honestly not sure...  I do know, however, that I've been getting an 
awful lot of time-out and "document contains no data" errors, as well as 
non-functional javascripts while browsing, that magically "go away" when 
i connect the system directly with the USB port.  I've also been unable 
to get rid of that annoying 'arplookup' error, which I think is an 
artifact of how the DSL modem tries to handle DMZ stuff :(  For what 
it's worth, I did a "pass in quick all"/"pass out quick all" on my 
/etc/pf.conf just to make sure I hadn't screwed something up there.