I looked through the phy common code differences with linux master and
nothing jumped out at me that would impact this i350 setup. It would
still be interesting to run that code and see if it works or not when
you get time.
It'd be best to also loop intel in directly since you are a customer
and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230858
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230857
Mark Linimon changed:
What|Removed |Added
Keywords||panic, vimage
Assignee|b.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845
Mark Linimon changed:
What|Removed |Added
Keywords||regression
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845
--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Thu Aug 23 16:52:53 UTC 2018
New revision: 338256
URL: https://svnweb.freebsd.org/changeset/base/338256
Log:
xen/netfront: Ensure curvnet is s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845
Roger Pau Monné changed:
What|Removed |Added
CC||n...@freebsd.org
--
You are re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845
--- Comment #2 from Roger Pau Monné ---
(In reply to Kristof Provost from comment #1)
Thanks! That does indeed seems to solve the issue, it just has a minor typo:
s/vnet/if_vnet/. Would you like to commit it?
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845
Kristof Provost changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228802
Eugene Grosbein changed:
What|Removed |Added
Status|Open|Closed
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228802
--- Comment #26 from h...@restart.be ---
I try with 12.0-ALPHA2 r338128M with a10_timer - see
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229644#c27
The throughput is back to normal :-)
I think this bug is solved.
--
You are receiv
Kevin Bowling wrote:
> Well I took a look at the phy code and actually don't see that we
> abosrbed those commits. I'll try and audit e1000 vs linux in the next
> 24 hours but in the mean time if you could confirm linux-next or the
> like fix or don't fix the phy we can at least know if this is
Well I took a look at the phy code and actually don't see that we
abosrbed those commits. I'll try and audit e1000 vs linux in the next
24 hours but in the mean time if you could confirm linux-next or the
like fix or don't fix the phy we can at least know if this is the
right path or if we need to
I haven't used this hardware before, so I don't if it ever worked. I
only tried 11.2 and it doesn't work. I've also tried Ubuntu 18.04 and it
doesn't work as well. Ubuntu prints the following error:
[ 343.053031] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[ 343.053032] igb:
Great thanks for the info about it not working on Ubuntu too, that
narrows down the problem space considerably.
Can you try that patch on FreeBSD -CURRENT? It should apply with
minimal changes the phy code is shared by multiple OSes. If it works
we can commit.
Regards,
On Thu, Aug 23, 2018 at
14 matches
Mail list logo
