n
> the future.
>
> > -Original Message-
> > From: Brandeburg, Jesse
> > Sent: Tuesday, December 08, 2015 12:36 PM
> > To: Steffen Weber; Skidmore, Donald C; e1000-devel@lists.sourceforge.net
> > Subject: RE: [E1000-devel] ixgbe and using iptables/SYNPR
randeburg, Jesse
> Sent: Tuesday, December 08, 2015 12:36 PM
> To: Steffen Weber; Skidmore, Donald C; e1000-devel@lists.sourceforge.net
> Subject: RE: [E1000-devel] ixgbe and using iptables/SYNPROXY causes
> random system resets
>
> Also because the problem is maybe related to SY
r 08, 2015 12:12 PM
> To: Skidmore, Donald C; e1000-devel@lists.sourceforge.net
> Subject: Re: [E1000-devel] ixgbe and using iptables/SYNPROXY causes
> random system resets
>
> Hi Don,
>
> thank you for the reply.
>
> We've been using the X520 NICs since February 2015 and
;
e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] ixgbe and using iptables/SYNPROXY causes random
system resets
Hi Don,
thank you for the reply.
We've been using the X520 NICs since February 2015 and so far they have
been working fine. A few weeks ago we enabled SYNPROXY an
t; -Original Message-
>> From: Steffen Weber [mailto:steffen.we...@gmail.com]
>> Sent: Tuesday, December 08, 2015 5:03 AM
>> To: e1000-devel@lists.sourceforge.net
>> Subject: Re: [E1000-devel] ixgbe and using iptables/SYNPROXY causes
>> random system resets
&
t.
Thanks,
-Don Skidmore
> -Original Message-
> From: Steffen Weber [mailto:steffen.we...@gmail.com]
> Sent: Tuesday, December 08, 2015 5:03 AM
> To: e1000-devel@lists.sourceforge.net
> Subject: Re: [E1000-devel] ixgbe and using iptables/SYNPROXY causes
> random system resets
>
&g
Hi,
we have exactly the same problem with the combination of SYNPROXY and
X520 NICs. We use Dell PowerEdge R420 servers.
CPU: Intel(R) Xeon(R) CPU E5-2430
NIC: Intel Corporation Ethernet 10G 2P X520 Adapter (rev 01)
Kernel: Linux 4.1.13 with in-tree ixgbe 4.0.1-k
One of those servers with relat
On 2015-06-30 22:33, Christian Ruppert wrote:
On 2015-06-30 21:20, Rustad, Mark D wrote:
Christian,
On Jun 30, 2015, at 1:58 AM, Christian Ruppert wrote:
bad news. It didn't work either. :(
That is too bad.
The system just did a reset tonight and there's nothing useful.
What I did was:
I
On 2015-06-30 22:50, Rustad, Mark D wrote:
> Christian,
>
>> On Jun 30, 2015, at 1:33 PM, Christian Ruppert wrote:
>>
>> We tried Supermicro 5018D-MTF (E3-1281v3), 5017C-MTF (E3-1220L IIRC)
>> and a Workstation PC (i5-4460) with an Asus mainboard (H97M-E) and
>> it's the same everywhere. All S
Christian,
> On Jun 30, 2015, at 1:33 PM, Christian Ruppert wrote:
>
> We tried Supermicro 5018D-MTF (E3-1281v3), 5017C-MTF (E3-1220L IIRC) and a
> Workstation PC (i5-4460) with an Asus mainboard (H97M-E) and it's the same
> everywhere. All Systems do have 32GB RAM, the two Supermicro even ECC
On 2015-06-30 21:20, Rustad, Mark D wrote:
Christian,
On Jun 30, 2015, at 1:58 AM, Christian Ruppert wrote:
bad news. It didn't work either. :(
That is too bad.
The system just did a reset tonight and there's nothing useful.
What I did was:
I removed the console= parameter and therefore I
Christian,
> On Jun 30, 2015, at 1:58 AM, Christian Ruppert wrote:
>
> bad news. It didn't work either. :(
That is too bad.
> The system just did a reset tonight and there's nothing useful.
> What I did was:
> I removed the console= parameter and therefore I added your mentioned
> earlyprintk
On 2015-06-26 20:47, Christian Ruppert wrote:
> On 2015-06-26 19:47, Rustad, Mark D wrote:
>>> On Jun 26, 2015, at 8:42 AM, Christian Ruppert wrote:
>>>
>>> Neither via
>>> kexec/kdump nor via serial console.
>>
>> Did you use the kernel command line option:
>> earlyprintk=ttyS0,115200,keep
e and using iptables/SYNPROXY causes
>> random
>> system resets
>>
>> On 2015-06-26 21:15, Tantilov, Emil S wrote:
>>>> -Original Message-
>>>> From: Christian Ruppert [mailto:id...@qasl.de]
>>>> Sent: Friday, June 26, 2015 8:43 AM
>-Original Message-
>From: Christian Ruppert [mailto:id...@qasl.de]
>Sent: Friday, June 26, 2015 12:34 PM
>To: Tantilov, Emil S
>Cc: e1000-de...@lists.sf.net
>Subject: RE: [E1000-devel] ixgbe and using iptables/SYNPROXY causes random
>system resets
>
>On 2015-06
]
Sent: Friday, June 26, 2015 12:34 PM
To: Tantilov, Emil S
Cc: e1000-de...@lists.sf.net
Subject: Re: [E1000-devel] ixgbe and using iptables/SYNPROXY causes random
system resets
On 2015-06-26 21:15, Tantilov, Emil S wrote:
>> -Original Message-
>> From: Christian Ruppert [ma
On 2015-06-26 21:15, Tantilov, Emil S wrote:
>> -Original Message-
>> From: Christian Ruppert [mailto:id...@qasl.de]
>> Sent: Friday, June 26, 2015 8:43 AM
>> To: e1000-de...@lists.sf.net
>> Subject: [E1000-devel] ixgbe and using iptables/SYNPROXY causes ran
>-Original Message-
>From: Christian Ruppert [mailto:id...@qasl.de]
>Sent: Friday, June 26, 2015 8:43 AM
>To: e1000-de...@lists.sf.net
>Subject: [E1000-devel] ixgbe and using iptables/SYNPROXY causes random
>system resets
>
>Hi,
>
>we have a setup of some
Hi Jacob,
it really might be that but the biggest problem is that the system just
does a reset. There is no dump, no panic or something, it just does a
full reset of the system. I doubt netconsole will help when console
didn't catch anything but I'll give it a try after having tried Marks's
ea
On 2015-06-26 19:47, Rustad, Mark D wrote:
>> On Jun 26, 2015, at 8:42 AM, Christian Ruppert wrote:
>>
>> Neither via
>> kexec/kdump nor via serial console.
>
> Did you use the kernel command line option:
> earlyprintk=ttyS0,115200,keep
>
> That really should be able to capture the error
> On Jun 26, 2015, at 8:42 AM, Christian Ruppert wrote:
>
> Neither via
> kexec/kdump nor via serial console.
Did you use the kernel command line option:
earlyprintk=ttyS0,115200,keep
That really should be able to capture the error messages, which will help a
great deal.
--
Mark Rusta
Hi,
Any chance you have more than just the one line of that one time crash
dump? I assume that you do not, but that would be the most helpful
information. My guess is that null pointer deref is the real issue
going on here...
Maybe try setting up netconsole through a different device and see if
y
Hi,
we have a setup of some E3's with X520 10GE NICs (more details below)
and we also use the iptables SYNPROXY[1][2] extension.
Details:
CPU: Different E3 Models
NICs: 8086:10fb Ethernet controller: Intel Corporation 82599EB
10-Gigabit SFI/SFP+ Network Connection (rev 01) (X520-2 8086:0003)
Ker
23 matches
Mail list logo
