https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
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=208205
Kubilay Kocak changed:
What|Removed |Added
CC||n...@freebsd.org
Assigne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Kubilay Kocak changed:
What|Removed |Added
Blocks|227979 |
Referenced Bugs:
https://bugs.f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Rich S changed:
What|Removed |Added
CC||richie...@yahoo.com
--- Comment #39 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
amvandem...@gmail.com changed:
What|Removed |Added
CC||amvandem...@gmail.com
--- C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #37 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 the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #35 from Chris Hutchinson ---
(In reply to ml from comment #34)
For *me*, doubling the values from their defaults
fixed it. I only mentioned it as
1) disabling MSI-X (default solution) reduces
performance -- even significant
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #34 from m...@netfence.it ---
(In reply to Chris Hutchinson from comment #33)
Aren't those value's default proportional to system RAM?
>From a quick survey on my systems I see:
4GB 11.3 123975 247952
16GB 11.3 507532 1015064
3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Chris Hutchinson changed:
What|Removed |Added
CC||portmas...@bsdforge.com
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Ralf Wostrack changed:
What|Removed |Added
CC||ralf.wostr...@gmx.de
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Bug 208205 depends on bug 212283, which changed state.
Bug 212283 Summary: oversized IP datagrams on raw socket with IP_RAWOUTPUT hang
network interface drivers
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212283
What|R
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #31 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
stil
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Palle Girgensohn changed:
What|Removed |Added
Blocks||227979
Referenced Bugs:
https
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- 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 alw
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- 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 direction
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- 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=208205
--- 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 the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #26 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 the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #25 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.
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #24 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 quickly.
But - ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #23 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 google (m-lab) speed te
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Arto Pekkanen changed:
What|Removed |Added
CC||aks...@gmail.com
--- Comment #22 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #21 from Alex Dupre ---
The use of powerd can make the issue more evident / easier to reproduce, but
it's not the root cause.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #20 from Nick ---
I did some additional testing a while back. And it seems on this setup powerD
does nothing to save power. With it on or off the computer still consumed 8
watts. And I guess at that level it's pretty efficient.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Alex Dupre changed:
What|Removed |Added
CC||a...@freebsd.org
Severity|A
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #18 from Dirk Meyer ---
(In reply to Dirk Meyer from comment #17)
pciconf -v -l
hardware1:
re0@pci0:2:0:0: class=0x02 card=0x78161462 chip=0x816810ec rev=0x06
hdr=0x00
vendor = 'Realtek Semiconductor Co., Ltd.'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Dirk Meyer changed:
What|Removed |Added
CC||din...@freebsd.org
--- Comment #17 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
zjk changed:
What|Removed |Added
CC||z...@wp.pl
--- Comment #16 from zjk ---
The
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #15 from m...@netfence.it ---
Hello.
Just to say that I have a new box which is showing this behaviour: re0 (on
motherboard) locks, while re1 (PCI-X card) is still working.
# pciconf -lv
...
re0@pci0:1:0:0: class=0x02 card=
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #14 from Sean Bruno ---
(In reply to Marc Mach from comment #13)
If someone could identify what is in the Realtek driver that is not in the
FreeBSD base driver, I'm willing to commit it. The diff's are kind of
ridiculous and ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Marc Mach changed:
What|Removed |Added
CC||m...@marc-mach.de
--- Comment #13 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #12 from m...@netfence.it ---
I disabled powerd, but the problem showed up again.
It only happened twice in some months, but it's still a critical problem for
us.
--
You are receiving this mail because:
You are the assignee fo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #11 from c.kw...@gmail.com ---
(In reply to Sean Bruno from comment #8)
Actually you can be right. During boot I always have this LOR:
Sep 7 10:08:26 limbo kernel: lock order reversal:
Sep 7 10:08:26 limbo kernel: 1st 0xf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
m...@netfence.it changed:
What|Removed |Added
CC||m...@netfence.it
--- Comment #10
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #9 from c.kw...@gmail.com ---
(In reply to Sean Bruno from comment #8)
Never checked without pf… I have some LOR regarding pf but hadn't thought pf
could be the one to blame.
To check without pf I need to rewrite all firewall ru
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #8 from Sean Bruno ---
(In reply to c.kworr from comment #7)
Does this happen without pf being used?
--
You are receiving this mail because:
You are the assignee for the bug.
___
fre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
c.kw...@gmail.com changed:
What|Removed |Added
CC||c.kw...@gmail.com
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Sean Bruno changed:
What|Removed |Added
Depends on||212283
Referenced Bugs:
https://bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #6 from Sean Bruno ---
(In reply to Sean Bruno from comment #5)
This machine does *not* run powerd as its a gateway host.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #5 from Sean Bruno ---
We're seeing this on one of our gateways in the FreeBSD cluster at bytemark.
The interface will not come back up unless the machine is rebooted.
FreeBSD igw0.bme.freebsd.org 11.0-ALPHA6 FreeBSD 11.0-ALPH
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #4 from Nick ---
its updated to 10.3-RELEASE-p5 and the issue is still there.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Kubilay Kocak changed:
What|Removed |Added
Keywords||needs-qa
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
--- Comment #2 from Nick ---
here is the output.
[2.3-BETA][r...@pfsense.home.lan]/root: pciconf -lvbc
hostb0@pci0:0:0:0: class=0x06 card=0x22b11849 chip=0x22808086 rev=0x21
hdr=0x00
vendor = 'Intel Corporation'
class
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Sean Bruno changed:
What|Removed |Added
CC||sbr...@freebsd.org
--- Comment #1 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
--
You are
45 matches
Mail list logo
