https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200420
--- Comment #7 from Arcadiy Ivanov ---
There appears to be some indication that the X11SBA series has a hardware bug
in a PCI-E controller supplying igb1-4 (not affecting igb1).
See https://sourceforge.net/p/e1000/bugs/502/
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200420
--- Comment #8 from Arcadiy Ivanov ---
*not affecting igb0
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
Mark Linimon changed:
What|Removed |Added
Keywords||regression
Assignee|freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
Steven Hartland changed:
What|Removed |Added
CC||s...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
--- Comment #2 from Kristjan ---
lagg0: flags=8843 metric 0 mtu 1500
ether b0:83:fe:e5:fa:82
inet 172.21.50.2 netmask 0xff00 broadcast 172.21.50.255
nd6 options=29
media: Ethernet autoselect
statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
--- Comment #3 from Steven Hartland ---
and for bxe0 / bxe1?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.free
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
--- Comment #4 from Kristjan ---
bxe0: flags=8843 metric 0 mtu 1500
ether b0:83:fe:e5:fa:82
nd6 options=29
media: Ethernet autoselect (10Gbase-SR )
status: active
bxe1: flags=8843 metric 0 mtu 1500
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
--- Comment #5 from Steven Hartland ---
That looks odd, no options= for the nic's.
Can you try something silly, assign a private IP to the bxe0 and see if that
changes things?
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211962
--- Comment #5 from Matt Joras ---
The changeset I authored for Isilon has been committed by davidcs. Hopefully
this will alleviate the issues in the PR.
https://svnweb.freebsd.org/base?view=revision&revision=307578
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
--- Comment #6 from Steven Hartland ---
Looks like it may be an old issues see:
https://forums.freenas.org/index.php?threads/lacp-lagg-issues-with-9-3.26227/
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
--- Comment #7 from Kristjan ---
Nothing changes and it seems to be the same problem yes. laggproto loadbalance
is working fine.
LACP was also working in 10.3 so something between 10.3 and 11.0 changed that.
--
You are receiving this mail
Reviving a thread from June,2015...
My brand-spanking new XPS 13 has a dongle for the Thunderbolt port that
implements a RTL8153, which
is recognized by my system (FreeBSD 11.0-RELEASE-p1 #8: Tue Oct 18 22:57:49 PDT
2016):
Oct 19 07:11:01 TWE6 kernel: ugen1.3: at usbus1
Oct 19 07:11:02 TWE6
On 10/19/16 20:06, David Horwitt wrote:
Reviving a thread from June,2015...
My brand-spanking new XPS 13 has a dongle for the Thunderbolt port that
implements a RTL8153, which
is recognized by my system (FreeBSD 11.0-RELEASE-p1 #8: Tue Oct 18
22:57:49 PDT 2016):
Oct 19 07:11:01 TWE6 kernel: uge
Hi!
I got this panic in a bhyve VM, which was just compiling stuff
and had two ssh sessions open. It has static network configuration,
one interfaces, one IP address, IPv4 only and it sees only hardware
address of the host. So it is minimal possible configuration. It
runs with INVARIANTS.
As
On Wed, Oct 19, 2016 at 02:29:14PM -0700, Gleb Smirnoff wrote:
T> Hi!
T>
T> I got this panic in a bhyve VM, which was just compiling stuff
T> and had two ssh sessions open. It has static network configuration,
T> one interfaces, one IP address, IPv4 only and it sees only hardware
T> address of
> On Wed, Oct 19, 2016 at 02:29:14PM -0700, Gleb Smirnoff wrote:
> T> Hi!
> T>
> T> I got this panic in a bhyve VM, which was just compiling stuff
> T> and had two ssh sessions open. It has static network configuration,
> T> one interfaces, one IP address, IPv4 only and it sees only hardware
>
On Wed, Oct 19, 2016 at 07:26:44PM -0500, Mike Karels wrote:
M> > On Wed, Oct 19, 2016 at 02:29:14PM -0700, Gleb Smirnoff wrote:
M> > T> Hi!
M> > T>
M> > T> I got this panic in a bhyve VM, which was just compiling stuff
M> > T> and had two ssh sessions open. It has static network configuration
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
Kubilay Kocak changed:
What|Removed |Added
Keywords||crash
URL|
On 19/10/2016 3:23 AM, Cassiano Peixoto wrote:
> Hi guys,
>
> I have some update about this issue. After my last email i had 3 crashes.
> Two of them had the same message on kernel debug:
>
> (kgdb) list *0x8228c918
> 0x8228c918 is in trim_map_seg_compare
> (/usr/src/sys/cddl/cont
> On Wed, Oct 19, 2016 at 07:26:44PM -0500, Mike Karels wrote:
> M> > On Wed, Oct 19, 2016 at 02:29:14PM -0700, Gleb Smirnoff wrote:
> M> > T> Hi!
> M> > T>
> M> > T> I got this panic in a bhyve VM, which was just compiling stuff
> M> > T> and had two ssh sessions open. It has static network c
On Thu, Oct 20, 2016 at 12:32:17AM -0500, Mike Karels wrote:
M> > On Wed, Oct 19, 2016 at 07:26:44PM -0500, Mike Karels wrote:
M> > M> > On Wed, Oct 19, 2016 at 02:29:14PM -0700, Gleb Smirnoff wrote:
M> > M> > T> Hi!
M> > M> > T>
M> > M> > T> I got this panic in a bhyve VM, which was just comp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #17 from Kubilay Kocak ---
(In reply to Eugene Grosbein from comment #14)
The initial report is fine to be classified against the port. Once the root
cause(s) is confirmed, implicated or identified, a dependent (Depends On) sub
22 matches
Mail list logo
