On Apr 27, 2012, at 2:07 AM, lini...@freebsd.org wrote:
> Old Synopsis: sosend sometimes return EINVAL with TSO and VLAN on 82599 NIC
> New Synopsis: [netinet] [patch] sosend sometimes return EINVAL with TSO and
> VLAN on 82599 NIC
> http://www.freebsd.org/cgi/query-pr.cgi?pr=167325
I did an an
On Thu, 2012-08-16 at 09:56 -0700, John wrote:
> Hi Folks,
>
>I have an R820 I'm testing. The system seems to boot up fine, but
> no network adapters show up. From pciconf -l :
>
> none4@pci0:1:0:0: class=0x02 card=0x1f5c1028 chip=0x168a14e4
> rev=0x10 hdr=0x00
> none5@pci0:1:0:1:
At Fri, 7 Sep 2012 01:28:16 -0700,
Anuranjan Shukla wrote:
>
>
> >
> >> struct socket {
> >>
> >>int so_fibnum; /* routing domain for this socket */
> >>uint32_t so_user_cookie;
> >> + u_int so_oqueue; /* manage send prioritizing based on
> >>application
> >> needs */
> >
On 9/7/12 4:28 PM, Anuranjan Shukla wrote:
Hi George,
Thanks for taking a look. Some answers/comments below.
Building FreeBSD without the network stack (network stack as a module)
--
This would be interesting for many reasons
On Fri, Sep 07, 2012 at 12:35:53AM -0700, Sean Bruno wrote:
S> Just noted this happened today, running stable/9 ish from august 10th.
S> It looks like I got a good and valid crashdump off of this if anyone is
S> interested.
...
S> --- trap 0xc, rip = 0x80731312, rsp = 0xff846c8977d0, rb
On 07/09/2012 06:22, Brian Stivala wrote:
> Hi,
>
> Can I get an answer regarding the below.
>
> Thanks
>
> Regards,
> Brian Stivala
I assume
http://forum.pfsense.org/index.php?PHPSESSID=d9f0e7e874a14184be2074988f0f4a8a&topic=53277
is you also.
>From the look of it and reading that thread I would s
We've had similar problems with lagg at work, each lagg is made up of
one igb and one em port, sometimes for no apparent reason they seem to
stop passing through traffic. The easiest way we've found to get it
working again is ifconfig down and up on one of the physical
interfaces. This is on 8.1
O
Hi George,
Thanks for taking a look. Some answers/comments below.
>
>> Building FreeBSD without the network stack (network stack as a module)
>> --
>>
>This would be interesting for many reasons, and I think it would be a good
>co
Since I saw other panics on our stable/9 I started poking around and found this
one lying around too.
And, I have a crashdump here as well. Not sure about reproduction, but I see
it happened on two seperate servers
over the course of the day. Here is one of them.
igb0: port 0xe880-0xe89f
me
Just noted this happened today, running stable/9 ish from august 10th.
It looks like I got a good and valid crashdump off of this if anyone is
interested.
igb0: port
0xe880-0xe89f mem
0xfbe6-0xfbe7,0xfbe4-0xfbe5,0xfbeb8000-0xfbebbfff irq 32
at device 0.0 on pci5
igb0: Using MSIX
10 matches
Mail list logo
