On Fri, Dec 07, 2012 at 12:49:18PM -0800, Garrett Cooper wrote:
G I can't seem to create a lagg'ed interface on HEAD with ixgbe
G (it's failing when creating a cloned interface), whereas creating it
G on 9.1-STABLE built from a couple weeks ago just worked. Ideas?
Have you recompiled the
Hi there,
I'm trying to install a new pf/altq router. I needed to use 9.1-rc3 due to
RAID driver issues.
Everything works find on my quad port intel card (igb), but when I try to
load my ruleset I get the following error :
pfctl: igb0 : driver does not support ALTQ
altq(4) states that igb is
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
On Mon, Dec 10, 2012 at 2:03 AM, Gleb Smirnoff gleb...@freebsd.org wrote:
On Fri, Dec 07, 2012 at 12:49:18PM -0800, Garrett Cooper wrote:
G I can't seem to create a lagg'ed interface on HEAD with ixgbe
G (it's failing when creating a cloned interface), whereas creating it
G on 9.1-STABLE
On Mon, Dec 10, 2012 at 8:03 AM, Garrett Cooper yaneg...@gmail.com wrote:
On Mon, Dec 10, 2012 at 2:03 AM, Gleb Smirnoff gleb...@freebsd.org wrote:
On Fri, Dec 07, 2012 at 12:49:18PM -0800, Garrett Cooper wrote:
G I can't seem to create a lagg'ed interface on HEAD with ixgbe
G (it's
On Mon, Dec 10, 2012 at 8:11 AM, Garrett Cooper yaneg...@gmail.com wrote:
On Mon, Dec 10, 2012 at 8:03 AM, Garrett Cooper yaneg...@gmail.com wrote:
On Mon, Dec 10, 2012 at 2:03 AM, Gleb Smirnoff gleb...@freebsd.org wrote:
On Fri, Dec 07, 2012 at 12:49:18PM -0800, Garrett Cooper wrote:
G I
The following reply was made to PR kern/174311; it has been noted by GNATS.
From: Garrett Cooper yaneg...@gmail.com
To: bug-follo...@freebsd.org, yaneg...@gmail.com
Cc:
Subject: Re: kern/174311: [em][lagg] Can#39;t create lagg on recent CURRENT
(2012.12.05)
Date: Mon, 10 Dec 2012 08:20:34
Synopsis: [em][lagg] Can't create lagg on recent CURRENT (2012.12.05)
State-Changed-From-To: open-closed
State-Changed-By: delphij
State-Changed-When: Mon Dec 10 16:48:43 UTC 2012
State-Changed-Why:
Closed per submitter request: it seems to be an ABI mismatch
between kernel and module.
--- On Mon, 12/10/12, Clément Hermann (nodens) nodens2...@gmail.com wrote:
From: Clément Hermann (nodens) nodens2...@gmail.com
Subject: igb and ALTQ in 9.1-rc3
To: freebsd-net@freebsd.org
Date: Monday, December 10, 2012, 6:03 AM
Hi there,
I'm trying to install a new pf/altq router. I
I noticed this while checking the logs on one of my test boxes
after restarting the network. Any idea where I should start looking
into this (has IPv6 enabled but wasn't using it, em/cxgbe/ixgbe
interfaces with the ixgbe interfaces lagged previously, but now not)?
It looks suspiciously like
Le 10/12/2012 23:09, Barney Cordoba a écrit :
--- On Mon, 12/10/12, Clément Hermann (nodens) nodens2...@gmail.com wrote:
altq(4) states that igb is supported. There are some
references to altq in
if_igb.c (include opt_altq in an ifdef), but they are not in
the em driver
(though my ruleset
9216 sounds like a jumbo frame mbuf. So the NIC is writing to an mbuf
after it's finalised/freed.
I have a similar bug showing up on ath(4) RX. :(
adrian
On 10 December 2012 14:22, Garrett Cooper yaneg...@gmail.com wrote:
I noticed this while checking the logs on one of my test boxes
On Mon, Dec 10, 2012 at 3:10 PM, Adrian Chadd adr...@freebsd.org wrote:
9216 sounds like a jumbo frame mbuf. So the NIC is writing to an mbuf
after it's finalised/freed.
I have a similar bug showing up on ath(4) RX. :(
Compile with DEBUG_MEMGUARD in the kernel configuration, and then set
On 10 December 2012 15:18, m...@freebsd.org wrote:
On Mon, Dec 10, 2012 at 3:10 PM, Adrian Chadd adr...@freebsd.org wrote:
9216 sounds like a jumbo frame mbuf. So the NIC is writing to an mbuf
after it's finalised/freed.
I have a similar bug showing up on ath(4) RX. :(
Compile with
On Mon, Dec 10, 2012 at 3:21 PM, Adrian Chadd adr...@freebsd.org wrote:
On 10 December 2012 15:18, m...@freebsd.org wrote:
On Mon, Dec 10, 2012 at 3:10 PM, Adrian Chadd adr...@freebsd.org wrote:
9216 sounds like a jumbo frame mbuf. So the NIC is writing to an mbuf
after it's finalised/freed.
On Mon, Dec 10, 2012 at 05:37:17PM -0800, Garrett Cooper wrote:
On Mon, Dec 10, 2012 at 3:21 PM, Adrian Chadd adr...@freebsd.org wrote:
On 10 December 2012 15:18, m...@freebsd.org wrote:
On Mon, Dec 10, 2012 at 3:10 PM, Adrian Chadd adr...@freebsd.org wrote:
9216 sounds like a jumbo frame
Le 11/12/2012 00:31, Jack Vogel a écrit :
UH, maybe asking the owner of the driver would help :)
Indeed. I just assumed anyone on the mailing list would be more
knowledgeable than I am. Sorry about that.
... and no, I've never been aware of doing anything to stop supporting
altq
so you
On Mon, Dec 10, 2012 at 03:18:45PM -0800, m...@freebsd.org wrote:
m On Mon, Dec 10, 2012 at 3:10 PM, Adrian Chadd adr...@freebsd.org wrote:
m 9216 sounds like a jumbo frame mbuf. So the NIC is writing to an mbuf
m after it's finalised/freed.
m
m I have a similar bug showing up on ath(4) RX. :(
On Mon, Dec 10, 2012 at 03:31:19PM -0800, Jack Vogel wrote:
J UH, maybe asking the owner of the driver would help :)
J
J ... and no, I've never been aware of doing anything to stop supporting altq
J so you wouldn't see any commits. If there's something in the altq code or
J support (which I have
19 matches
Mail list logo
