[Bug 166724] [re] if_re watchdog timeout

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Sep 3 14:33:14 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724

--- Comment #34 from zjk <zjk7 at wp.pl> ---
A. After longer tests - I must cancel the previous optimistic news. We are
talking about the 11.2-RELEASE + 1.93-realtek driver:

1. Suspensions, computer stops - still occur. They are only shorter - though
still cumbersome. 

See attachment above.

Generally at the beginning the interface works quickly, after some time it
slows down and shows signs of loss.

2. There are still messages about the interface suspension. Because I use lagg
it looks like this:
+ [20445] re1: Interface stopped DISTRIBUTING, possible flapping
+ [48114] re0: Interface stopped DISTRIBUTING, possible flapping

B. Regarding Alex's statements. This is a real problem.
Of course, the "watchdog timeout" message itself is not harmful.
The important thing is that the message in the function follows the reset and
re-initialisation of the interface - this unfortunately results in the loss or
partial destruction of transmitted files / frames (which unfortunately I have
experienced many times).

The application of version 1.93-1.94: is therefore of such a  improvement that
not only does the message disappear (commented out from function - as Alex
correctly writes), but the files are not damaged during the transmission (yet
to be checked!).

Version 11.2-RELEASE - for me it certainly generates hundreds of messages
"watchdog timeout" - but today I do not know if it prevents damage or loss of
transmitted data (to be checked). 
I see:
        /* Cancel pending I/O and free all RX/TX buffers. */
        re_stop(sc);
        /* Put controller into known state. */
        re_reset(sc);
It means: drop, loss transmitted information.

C. However, I will not agree with Alex that it is good. Perhaps it is good for
a laptop, too little for the server. It is still terrible.

D. Test 11.2 + 1.94 - I have not started yet.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-net mailing list