This is some form of followup on the "em(4) watchdog timeotu on
current/amd64" thread, https://marc.info/?t=14755971446&r=1&w=2 , in
that that thread also discusses stop of traffic.
Hi,
tikun/dchlupacek on CC experienced a similar stop of traffic and no
errors
On 2017-02-03 18:03, Tinker wrote:
On 2016-12-11 05:03, Adam Wolk wrote:
On Wed, Dec 07, 2016 at 10:11:44AM -0700, johnwixard wrote:
I am having the same problem, did you solve it?
/john
[..]
Unfoutnately I don't have any em(4) devices but I think the first step
to diagnose
this would be to
On 2016-12-11 05:03, Adam Wolk wrote:
On Wed, Dec 07, 2016 at 10:11:44AM -0700, johnwixard wrote:
I am having the same problem, did you solve it?
/john
[..]
Unfoutnately I don't have any em(4) devices but I think the first step
to diagnose
this would be to enable debugging output for the em d
On Wed, Dec 07, 2016 at 10:11:44AM -0700, johnwixard wrote:
> I am having the same problem, did you solve it?
>
> /john
>
>
>
> --
> View this message in context:
> http://openbsd-archive.7691.n7.nabble.com/em-4-watchdog-timeotu-on-current-amd64-tp305845p309482.h
I am having the same problem, did you solve it?
/john
--
View this message in context:
http://openbsd-archive.7691.n7.nabble.com/em-4-watchdog-timeotu-on-current-amd64-tp305845p309482.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.
This is current/amd64 on Dell Latitude E5570 (dmesg below).
I am experiencing em(4) watchdog timeouts.
As long as the ethernet cable is in, everything works fine.
But once I disconnect the cable and reconnect,
my em0 will never get a DHCP lease again.
Running 'sh /etc/netstart em0' will result in
6 matches
Mail list logo
