Re: wg destroy hangs

ing to get the interface back up. Was running -current at the time as well as now. On Wed, Oct 4, 2023 at 12:05 PM Alexander Bluhm wrote: > On Wed, Oct 04, 2023 at 10:53:30AM -0400, Sonic wrote: > > When it happened to me back then (2022) I'm pretty sure I did a "down&qu

Re: wg destroy hangs

When it happened to me back then (2022) I'm pretty sure I did a "down" followed by a "delete" and then the "destroy". Have not tried to recreate since then. On Wed, Oct 4, 2023 at 10:31 AM Alexander Bluhm wrote: > On Wed, Oct 04, 2023 at 10:08:01AM -04

Re: wg destroy hangs

See the post: "Uninterruptible D State after ifconfig wg0 destroy" Oct. 31, 2022 in the Bugs archive. On Wed, Oct 4, 2023 at 10:04 AM Sonic wrote: > This goes back a ways, to at least 7.2 in October 2022. > > > On Wed, Oct 4, 2023 at 8:54 AM Kirill Miazine wrote: > &

Re: wg destroy hangs

This goes back a ways, to at least 7.2 in October 2022. On Wed, Oct 4, 2023 at 8:54 AM Kirill Miazine wrote: > Recently on snapshots I have noticed that ifconfig wgN destroy would > just hang there, without any way to get back the control. Power reset > would be the only way to reboot and

Re: em(4) multiqueue

Is this multiqueue support in 7.3 or does it require patching? According to Intel the i211 should have 2 queues but I see no msi-x support in dmesg: em0 at pci1 dev 0 function 0 "Intel I211" rev 0x03: msi, address Thanks. Chris

Re: WireGuard patchset for OpenBSD, rev. 3

Along that line, does wireguard have any problems using alias addresses? It's not a problem with IKEv1 but it is with IKEv2. Thanks! Chris

Re: serious watchdog timeout issues with em driver

On Fri, Nov 20, 2015 at 8:12 AM, Martin Pieuchot wrote: > I just committed a revert to 1.305 keeping the API changes needed for > the driver to build. > > This should bring your stability back, please let us know if that's not > the case. The kernel/driver builds with those

Re: serious watchdog timeout issues with em driver

On Fri, Nov 20, 2015 at 12:37 PM, Mark Kettenis wrote: > Thanks Martin. All is fine now. System booted with no errors and no watchdog timeouts. Thanks to all. Chris

serious watchdog timeout issues with em driver

Have serious problems for over 7 weeks now with em driver, specifically any rev of if_em.c > 1.305. Starting with rev 1.306, released on 2015/09/30 and continuing to -current, watchdog timeouts rue the day. Unfortunately rev 1.305 no longer builds with -current as it appears the patch in rev

Re: em(4) watchdog timeouts

On Wed, Nov 11, 2015 at 9:20 AM, Gregor Best wrote: > I've done some further testing and I think I've narrowed it down to the > "Unlocking em(4) a bit further"-patch [0]. That was the start of it for me. When I could revert to rev 1.305 for if_em.c and rev 1.57 for if_em.h

Re: em(4) watchdog timeouts

On Wed, Nov 4, 2015 at 2:51 PM, Sonic <sonicsm...@gmail.com> wrote: > Is there anything else I can provide to assist in finding a cure for this > issue? Not sure this helps at all but the specific error I get is "em0: watchdog timeout -- resetting". In this case em0 is t

Re: em(4) watchdog timeouts

On Mon, Nov 2, 2015 at 11:19 PM, Sonic <sonicsm...@gmail.com> wrote: > Sorry to report that the diff does not solve the timeout problem here. > > All was working fine with the if_em* versions from 2015/09/29 (I > downgraded to this version per Stuarts post on 10-14): > &quo

Re: em(4) watchdog timeouts

On Mon, Nov 2, 2015 at 2:11 PM, Mark Kettenis wrote: > Can those that are experiencing watchdog timeouts check if the diff > below gets rid of them? Sorry to report that the diff does not solve the timeout problem here. All was working fine with the if_em* versions from