it's sad, but still the problem remains. during the week, in the absence of any
significant network load, mbufs increased from 650 to ~1100. i am informing you
because you will be tempted to write off the problem, for example, to a single
faulty hardware. but maybe this is not an igc problem,
Hi David,
Here are all the outputs you mentioned. Hopefully something will improve
our understanding of this story.
David Gwynne writes:
> Ofails are the sum of output errors and queue drops. Can you figure
> out which one it is with netstat -I igc0 -e and netstat -I igc0 -d?
% netstat -I
> On 30 Nov 2022, at 14:36, Greg Steuck wrote:
>
> Greg Steuck writes:
>
>> The watched kettle never boiled. No more crashes in over two weeks
>> (instead of two in the first week). I tried a loop of alternating iperf3
>> tcp and udp to no ill effect. I still see the growth in the metrics I
Greg Steuck writes:
> The watched kettle never boiled. No more crashes in over two weeks
> (instead of two in the first week). I tried a loop of alternating iperf3
> tcp and udp to no ill effect. I still see the growth in the metrics I
> reported, yet the system remained stable.
>
> I applied
I also was not able to recreate the issues I initially saw w/ high
traffic on 7.2 after I re-upgraded. I can't explain it but openbsd 7.2
igc has been solid for about 1.5 weeks now, no patches.
On Tue, Nov 22, 2022 at 11:21 PM Greg Steuck wrote:
>
> The watched kettle never boiled. No more
The watched kettle never boiled. No more crashes in over two weeks
(instead of two in the first week). I tried a loop of alternating iperf3
tcp and udp to no ill effect. I still see the growth in the metrics I
reported, yet the system remained stable.
I applied the patch below and am still
no, they don't grow anymore. apparently, the initial growth is associated with
network services(tor, i2pd and the like), which do not immediately gain full
force. using iperf also does not cause mbufs to grow
thx! you're the best ^.^
> Does this help?
> mbuhl
> Index: dev/pci/if_igc.c
> ===
> RCS file: /cvs/src/sys/dev/pci/if_igc.c,v
> retrieving revision 1.9
> diff -u -p -r1.9 if_igc.c
> --- dev/pci/if_igc.c2 Jun 2022 07:41:17 - 1.9
> +++
Hi Greg, Hi Joe,
dlg@ hinted to me that the ring might overwrite it's own starting
position with the current code.
Does this help?
mbuhl
Index: dev/pci/if_igc.c
===
RCS file: /cvs/src/sys/dev/pci/if_igc.c,v
retrieving revision 1.9
I have had (somewhat) similar sounding issues with igc and 7.2
immediately after upgrading. I am able to reproduce it reliably by
running an iperf3 test to another machine on the network. Within a few
seconds the NIC will stop working. No traffic, no ping. No errors in
dmesg or syslog.
The issue
Greg Steuck writes:
> My router has become unstable since upgrading from 7.1-stable to
> 7.2. After several days of uptime the machine gets into a state where
> some applications (unbound & dhcpd) report ENOBUFS (No buffer space
> available). At that time the machine is pingable over all the
>
11 matches
Mail list logo
