https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #59 from Eugene Grosbein ---
(In reply to Ralf Wostrack from comment #43)
Can you attach your change in a form of "diff -u" for unpatched and patched
versions of the source file?
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #58 from Eugene Grosbein ---
(In reply to Alex Dupre from comment #57)
I'm sure Readme.txt was created long time ago. OTOH, this may be
driver-dependent.
For example, this works for Intel gigabit drivers (em and igb):
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #57 from Alex Dupre ---
(In reply to Eugene Grosbein from comment #54)
This is new to me. I was quite sure that you cannot load a module if it's
already compiled into the kernel. The realtek driver Readme.txt in fact says
that
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #56 from László Károlyi ---
(In reply to Eugene Grosbein from comment #54)
Assuming it doesn't need a custom kernel compiled, I'm willing to test this on
my server, in hopes of this thing picking up some speed.
Can someone
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #55 from László Károlyi ---
(In reply to Chris Hutchinson from comment #53)
I think others have stated that the bigger the values are, the better. My
values are way bigger than these so I don't think this helps. But thanks
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Eugene Grosbein changed:
What|Removed |Added
CC||eu...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #53 from Chris Hutchinson ---
(In reply to László Károlyi from comment #48)
Hello,
FWIW One of the servers I'm running with the
stock FreeBSD re driver, is currently handling
pf tables totaling more than 72 million addresses.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #52 from Alex Dupre ---
The if_re driver is built into the GENERIC kernel, so that won't work. You need
to build a new GENERIC kernel without the built-in re driver to be able to use
the module version.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #51 from Ralf Wostrack ---
(In reply to László Károlyi from comment #50)
Iam using the GENERIC Kernel as well.
You only need to checkout the src of your installed version.
After that, patch if_re.c in /usr/src/sys/dev/re
with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #50 from László Károlyi ---
(In reply to Ralf Wostrack from comment #49)
Hi Ralf,
thanks for your response. I've seen the corrected drivers posted in here.
My problem is, getting that working involves kernel recompilation,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #49 from Ralf Wostrack ---
(In reply to László Károlyi from comment #48)
Hi László,
please follow comment #43 in the thread.
its a small code change which solves the issue.
Its working for me since months.
my freebsd server
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #48 from László Károlyi ---
The situation got worse today when the monthly full backup started to shut down
re0 by watchdog, and PF started to overwhelm itself.
My box became unreachable, when connecting a console, all I could
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Konstantin Belousov changed:
What|Removed |Added
CC||k...@freebsd.org
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Jan Przybylak changed:
What|Removed |Added
CC||jplx...@gmail.com
--- Comment #46
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
László Károlyi changed:
What|Removed |Added
CC||las...@karolyi.hu
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #44 from Chris Hutchinson ---
(In reply to Bob Smith from comment #42)
The ideal number will vary by card (model/brand/...)
We only ever experienced the watchdog(8) problem on
any of our RealTek cards on FreeBSD-11.x. We have
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Ralf Wostrack changed:
What|Removed |Added
CC||ralf.wostr...@gmx.de
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #42 from Bob Smith ---
(In reply to Chris Hutchinson from comment #40)
Could you share what specific values worked for you? My default values seem
pretty high on FreeBSD 12.1.
kern.ipc.nmbjumbop: 496998
kern.ipc.nmbclusters:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Artem Viklenko changed:
What|Removed |Added
CC||ar...@viklenko.net
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #40 from Chris Hutchinson ---
With my setup shown just above this comment.
I was able to overcome the watchdog timeouts,
and related problems by bumping up the values
of both
kern.ipc.nmbjumbop
and
kern.ipc.nmbclusters
In doing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Chris Hutchinson changed:
What|Removed |Added
CC||portmas...@bsdforge.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Bob Smith changed:
What|Removed |Added
CC||b...@novanet.org
--- Comment #38 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
George changed:
What|Removed |Added
CC||gosha-n...@yandex.ru
--- Comment #37
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #35 from Alex Dupre ---
I don't think I've ever said this issue is good :-)
What I said is that in my environment when I switched to 11.2-RELEASE it was
happening less frequently. With the FreeBSD driver is easy to detect it,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #35 from Alex Dupre ---
I don't think I've ever said this issue is good :-)
What I said is that in my environment when I switched to 11.2-RELEASE it was
happening less frequently. With the FreeBSD driver is easy to detect it,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #34 from zjk ---
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #33 from zjk ---
Created attachment 196815
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196815=edit
System load average and usage - monitorix
--
You are receiving this mail because:
You are on the CC list for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #32
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Igor Zabelin changed:
What|Removed |Added
CC||ig...@yandex.ru
--- Comment #31
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Palle Girgensohn changed:
What|Removed |Added
Blocks||227979
Referenced Bugs:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #30 from Alex Dupre ---
Surely you won't get the watchdog timeout error with the driver taken from the
realtek website, it's been commented out from the source code, so it's not a
real clue.
Said so, with 11.0 and 11.1 I've
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #29 from zjk ---
The following configuration is very promising:
- kernel 11.2-RELEASE recompiled together,
- re driver v. 1.93 (from realtek site).
Effect:
- NO (absolutely none) watchdog timeout,
- FULL speed in both
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #28 from Alex Dupre ---
I still see a few watchdog errors in the logs, but I'm unable to trigger them
voluntarily, even with very high traffic. While before it was enough to run a
single speed test to drop the connection, now I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #27 from zjk ---
After upgrading several machines to 11.2 and all-night tests: nothing better,
still a watchdog fault.
zjk
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #26 from Alex Dupre ---
After upgrading to 11.2-RELEASE the problem seems disappeared on my machine.
Looking at dmesg the only difference is the missing of the following line at
boot:
re0: turning off MSI enable bit.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #25 from zjk ---
hw.re.msi_disable hw.re.msix_disable
I tested this solution for a few days (it already exists somewhere on the
internet).
There is no visible effect (on my computers) - network is closing very
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #24 from Alex Dupre ---
Disabling MSI/MSI-X was proposed as solution in the past. I've just tried again
to be sure, it helps, but the issue doesn't disappear completely. With it I can
successfully run the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Arto Pekkanen changed:
What|Removed |Added
CC||aks...@gmail.com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Mateusz Piotrowski <0...@freebsd.org> changed:
What|Removed |Added
Keywords||needs-patch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Dirk Meyer changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
Rodney W. Grimes changed:
What|Removed |Added
CC|
41 matches
Mail list logo