https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Jean-Claude MICHOT changed:
What|Removed |Added
CC||j...@michot.fr
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #129 from J.R. Oldroyd ---
Meant to add above that the watchdog timeout hit re1. There had been
occasional timeouts in the log for a few days but no problems. Last night
there was a series of timeouts in short order and re1 st
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
J.R. Oldroyd changed:
What|Removed |Added
CC||f...@opal.com
--- Comment #128 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Mark Linimon changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #127 from v...@fbsd.ru ---
I've ended up switching to igb0:
for the truth - this host is quite old (>10y) if_re worked quite fine for all
these years and started to glitch only after upgrading to 14.0,
driver from ports helped
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #126 from George Mitchell ---
The consensus of the 124 previous comments is use your choice of the
net/realtek-re-kmod or net/realtek-re-kmod198 ports instead. The second has
more of a track record and seems to work every time;
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
mca_...@hotmail.com changed:
What|Removed |Added
CC||mca_...@hotmail.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Petre Rodan changed:
What|Removed |Added
CC||petre.ro...@subdimension.ro
--- Comm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
SlyFox125 changed:
What|Removed |Added
CC||docj...@live.com
--- Comment #123 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #122 from Jan Przybylak ---
I was using the patched driver for a several of years without issue, but it
stopped working earlier this year due to a different bug. I switched back to
the regular driver and it was fine until a few
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Mark Linimon changed:
What|Removed |Added
Flags|mfc-stable13? |
--- Comment #121 from Mark Linimon
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #119 from Nuno Teixeira ---
Same as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724#c117 when
doing restic backup operation such as prune and check.
re0: port
0x3000-0x30ff mem 0xb4204000-0xb4204fff,0xb420-0xb4203
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #120 from Nuno Teixeira ---
(In reply to vova from comment #115)
> what was helped - switchover to the port net/realtek-re-kmod
I will try install re drivers from ports and check if problem persists.
--
You are receiving thi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Michael Osipov changed:
What|Removed |Added
CC||micha...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
dgilb...@eicat.ca changed:
What|Removed |Added
CC||dgilb...@eicat.ca
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #116 from v...@fbsd.ru ---
(In reply to vova from comment #115)
Well ... with if_re from net/realtek-re-kmod also I am loosing connectivity ...
not that often as with in-tree driver, with quite funny results:
1. system timer g
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
v...@fbsd.ru changed:
What|Removed |Added
CC||v...@fbsd.ru
--- Comment #115 from v
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Riccardo Torrini changed:
What|Removed |Added
CC||ricca...@torrini.org
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #113 from Richard Russo ---
(In reply to Mahmoud Al-Qudsi from comment #112)
> In the four years since, there have been no complaints of any regressions or
> other issues caused by using the vendor-patched version of the drive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Mahmoud Al-Qudsi changed:
What|Removed |Added
CC||mqu...@neosmart.net
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Graham Perrin changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #111 from ykla ---
see also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267514
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Michael Osipov changed:
What|Removed |Added
CC||michael.osi...@siemens.com
--- Co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #108 from George Mitchell ---
The port to install is net/realtek-re-kmod, cited in comment #92 and a few
others following.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #107 from ykla ---
I seem to be replying to the wrong bug? My USB NIC is not a realtek but an ASIX
AX88179A, but I have this problem too.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #106 from ykla ---
(In reply to George Mitchell from comment #104)
Which port? Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #105 from László Károlyi ---
(In reply to George Mitchell from comment #104)
FYI, I use the driver from ports since years, without any errors.
It's only the kernel based driver that has this weird phenomenon. Keep using
the por
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
George Mitchell changed:
What|Removed |Added
CC||geo...@m5p.com
--- Comment #104
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
ykla changed:
What|Removed |Added
CC||ykla...@gmail.com
--- Comment #103 from ykl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
mickael.mail...@gmail.com changed:
What|Removed |Added
CC||mickael.mail...@gmail.co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Richard Russo changed:
What|Removed |Added
CC||free...@ruka.org
--- Comment #101
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Kubilay Kocak changed:
What|Removed |Added
Flags|mfc-stable11? |mfc-stable13?
Keywords|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Kubilay Kocak changed:
What|Removed |Added
See Also|https://bugs.freebsd.org/bu |
|gzilla/show_bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Kubilay Kocak changed:
What|Removed |Added
CC||nicko6...@gmail.com
--- Comment #9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Kubilay Kocak changed:
What|Removed |Added
Blocks|227979 |
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #97 from Rich S ---
Correction...
To load the driver (FreeBSD 12.2) from the package repo:
pkg install realtek-re-kmod
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Rich S changed:
What|Removed |Added
CC||richie...@yahoo.com
--- Comment #96 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #95 from j...@bruelltuete.com ---
Might be useful to increase awareness of the vendor driver by adding it to the
man page: https://reviews.freebsd.org/D33677
--
You are receiving this mail because:
You are on the CC list for th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #94 from Chris Hutchinson ---
I'm just going to throw this out there for a couple of
reasons...
1) several people indicated the vendors driver solved
it for them
2) I just bought a realtek card capable of 9k jumbo
frames.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #93 from László Károlyi ---
(In reply to Bob Smith from comment #92)
With FreeBSD 13.0 out, and it having changed its src and ports repository to
git (https://docs.freebsd.org/en/books/handbook/mirrors/#git), the process
changes
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #92 from Bob Smith ---
To possibly save anyone else some time, this is exactly what I did to get the
driver installed on my FreeBSD 12.1 system.
svn checkout https://svn.freebsd.org/base/releng/`uname -r | cut -d'-' -f1,1`
/usr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #91 from László Károlyi ---
(In reply to Alex Dupre from comment #90)
Sad. At least please notify me when you have a working Realtek driver in
GENERIC.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #90 from Alex Dupre ---
(In reply to László Károlyi from comment #89)
There is no plan to replace it, the FreeBSD driver has some features that are
missing in the Realtek one, but Stefan Esser is working to integrate the
change
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #89 from László Károlyi ---
(In reply to László Károlyi from comment #88)
So, today there was another full backup to Bacbkblaze B2. Not a hiccup, not a
kernel message. The system did a stable throughput of 140-150Mbps:
https://i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #88 from László Károlyi ---
(In reply to Konstantin Belousov from comment #83)
One week has passed and still works like a charm. In fact for some reason, I
see it being faster than the GENERIC re0 drivers, I see bigger throughpu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #87 from Eugene Grosbein ---
(In reply to Konstantin Belousov from comment #83)
> On my 16G machine I got the issue in approximately 1 week of uptime.
Should it help increasing kern.ipc.nmbjumbo9 and/or kern.ipc.nmbjumbo16?
-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #86 from Eugene Grosbein ---
(In reply to László Károlyi from comment #85)
Yes. But, if you use GENERIC of RELEASE0pX then you don't need to keep source
trees at each server. Just compile the module once for major FreeBSD branc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #85 from László Károlyi ---
(In reply to Eugene Grosbein from comment #84)
I'd like to have this in the GENERIC kernel, at least as some kind of a
configurable option in loader.conf, so that I won't have to recompile the ports
m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #84 from Eugene Grosbein ---
(In reply to Konstantin Belousov from comment #83)
How about using 4096 by default with a notice in pkg-message for users
requiring larger MTU?
--
You are receiving this mail because:
You are on th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #83 from Konstantin Belousov ---
(In reply to László Károlyi from comment #82)
These numbers does not matter. On my 16G machine I got the issue in
approximately 1 week of uptime.
The port (not the stock vendor driver) has the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #82 from László Károlyi ---
(In reply to Eugene Grosbein from comment #81)
I have 64GB ram in the server with 54G being wired right now, so I don't think
such a condition will occur at my machine.
--
You are receiving this mai
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #81 from Eugene Grosbein ---
(In reply to László Károlyi from comment #79)
You should monitor this driver's work in the long run. AFAIK this drivers uses
9KB mbufs unconditionally no matter if MTU is 1500 or more, so in the lon
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #80 from Eugene Grosbein ---
(In reply to László Károlyi from comment #78)
> There were no "module_register" errors in the dmesg
This is a messages from loader. Loader messages do not get to kernel dmesg
buffer.
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #79 from László Károlyi ---
So, I have tested today, and the results are great.
I hit my server hard with transferring a 72GB file to an SMB mount on the local
network, and then I copied that file over from the SMB mount to bac
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #78 from László Károlyi ---
(In reply to Eugene Grosbein from comment #76)
Alright, it seems I managed to start my server with the newly compiled driver:
re0: port 0xd000-0xd0ff mem
0xf7204000-0xf7204fff,0xf720-0xf7203fff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #77 from László Károlyi ---
(In reply to Eugene Grosbein from comment #76)
Thanks. I'll make some adjustments and will touch base later.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #76 from Eugene Grosbein ---
Sorry, it's releng/12.1 for 12.1-RELEASE-pX.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #75 from Eugene Grosbein ---
(In reply to László Károlyi from comment #71)
> Additional information, I used the stable/12 branch to check out for the
> kernel sources:
> svn checkout https://svn.FreeBSD.org/base/stable/12 /usr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #74 from Eugene Grosbein ---
(In reply to László Károlyi from comment #70)
> but there's another, different error:
> https://i.imgur.com/TsSqp1g.png
You have mixup of incompatible kernel and module binaries.
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #73 from László Károlyi ---
(In reply to Eugene Grosbein from comment #72)
Hey Eugene,
that is what I did. See #71 and #70.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #72 from Eugene Grosbein ---
(In reply to László Károlyi from comment #68)
> I get no overriding message in dmesg
Loader messages do not get to the dmesg buffer. Instead, use "kldstat -v" to
verify that module is loaded. And y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #71 from László Károlyi ---
(In reply to Alex Dupre from comment #69)
Additional information, I used the stable/12 branch to check out for the kernel
sources:
svn checkout https://svn.FreeBSD.org/base/stable/12 /usr/src/
--
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #70 from László Károlyi ---
(In reply to Alex Dupre from comment #69)
I followed the instructions but the module still won't load.
I've fired up a virtual machine to test locally with the same
patchlevel/kernel/compiled module,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #69 from Alex Dupre ---
(In reply to László Károlyi from comment #68)
If you followed the pkg-message instructions you should simply see the
following lines in dmegs:
re0: port 0xe000-0xe0ff mem
0x91104000-0x91104fff,0x911000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #68 from László Károlyi ---
(In reply to Alex Dupre from comment #67)
I just tried to load the compiled driver with the GENERIC kernel, doesn't seem
to work.
I get no overriding message in dmesg, and when I try to load the modu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #67 from Alex Dupre ---
I've commited the vendor driver to the ports tree, with additional improvements
and instructions to load it with the stock GENERIC kernel:
https://svnweb.freebsd.org/ports?view=revision&revision=542324
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #66 from D ---
(In reply to Ralf Wostrack from comment #43)
I tested your patch and it didn't help me - watchdog timeout still happened
during some hours after boot.
I also tested increased kern.ipc.nmbjumbop and kern.ipc.nmbcl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Eugene Grosbein changed:
What|Removed |Added
Assignee|yong...@freebsd.org |n...@freebsd.org
Sta
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #64 from Alex Dupre ---
Just to let you know that Realtek just released a new version of the driver:
v196.04
I haven't tried it yet, it looks like they added WOL support, too.
If loading the module from the loader overrides th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #63 from László Károlyi ---
(In reply to Eugene Grosbein from comment #62)
Glad to hear that.
Now I only need a source where I can compile and load from, and I'll be gone
load testing for a while on my gigabit connected bare me
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #62 from Eugene Grosbein ---
(In reply to Andriy Gapon from comment #60)
I've just checked it out with 11.4-RELEASE/amd64 in Virtualbox adding
if_re_load="YES" to /boot/loader.conf and booting GENERIC kernel.
First, loader suc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #61 from Eugene Grosbein ---
(In reply to Andriy Gapon from comment #60)
If stand-alone module is loaded by loader, which one is registered -
stand-alone or built in the kernel?
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #60 from Andriy Gapon ---
(In reply to Eugene Grosbein from comment #58)
If it works, then I think that it happens by accident and may be unreliable.
It's not possible to add a module (in the sense of module_t) if a module with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Kubilay Kocak changed:
What|Removed |Added
Summary|[re] if_re watchdog timeout |if_re(4): watchdog timeout
75 matches
Mail list logo
