Re: Software caused connection abort (53) squid 4.6 on OpenBSD 6.5

2019-05-24 Thread wrh
I have applied that diff to my system and will post once I know the results. Thank you. On Thu, May 23, 2019 at 11:41 AM Kasak wrote: > Have you seen this https://github.com/squid-cache/squid/pull/404 ? > > 23 мая 2019 г., в 18:12, Marcus MERIGHI написал(а): > > Hello, > > same here. > > I

Software caused connection abort (53) squid 4.6 on OpenBSD 6.5

2019-05-23 Thread wrh
Hello, I have been running into a repeatable error reported by squid 4.6 from packages once the system has been under a steady load for ~12 hours. Example squid cache.log entry: 2019/05/22 15:03:41 kid1| oldAccept FD 18, 0.0.0.0 [ job2]: (53) Software caused connection abort The file descriptor

RS232 Mini PCI Express Serial Card

2016-03-25 Thread wrh
Hello, Can anyone confirm this device works with OpenBSD 5.8 or higher: https://www.startech.com/Cards-Adapters/Serial-Cards-Adapters/2-Port-RS232-Mini-PCI-Express-Serial-Card-16950-UART~MPEX2S952 I do not have one to test, so before purchasing I thought I would ask about it or experience with

Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-29 Thread wrh
4.6 or 4.7 code? -Bill On Tue, Jun 29, 2010 at 10:48 AM, Fridiric URBAN frederic.ur...@ircad.u-strasbg.fr wrote: Le 29/06/2010 14:16, uhu a C)crit : FrC)dC)ric URBANfrederic.urbanat ircad.u-strasbg.fr writes: . I didn't find any bug report yet on the OpenBSD official Website, this

Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-28 Thread wrh
sendbug submitted with 4.7-current. http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6411 -Bill On Thu, Jun 24, 2010 at 4:14 AM, Fridiric URBAN frederic.ur...@ircad.u-strasbg.fr wrote: Le 23/06/2010 12:08, rh...@hushmail.com a C)crit : Thank you for the messages regarding

Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-18 Thread wrh
The same issue here - with different hardware - Supermicro X8DTU and it's built-in dual Intel 82576 nics. Running 4.7-patch. Fails to initialize most of the time at boot (always em1), now and then it works (initializes and gets link after boot). em0 rarely fails to initialize, but also rarely