On 2015-06-30 22:50, Rustad, Mark D wrote:
> Christian,
> 
>> On Jun 30, 2015, at 1:33 PM, Christian Ruppert <id...@qasl.de> 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. And we only have issues in combination with the 
>> mentioned X520 NIC AND the SYNPROXY iptables extension.
> 
> Was the same X520 used in all of those systems? Do you have a
> different X520 to try?
> 

We have about 6 Servers for this setup and any had their own X520 NIC so 
it's the same model but not the same card (physically).

>> mcelog is empty. The 5018D-MTF Event log has nothing either. I checked 
>> for watchdog related settings in the BIOS but that looked good so far. 
>> Also causing a test kernel panic resulted in a proper dump as well as 
>> a valid kernel dump file. I can check the BIOS tomorrow and/or even 
>> make some pictures of each page/tab in case it might help.
> 
> The log you sent confuses me. The first message had a time stamp of
> 320 seconds, and then there is a new kernel booting. Is this the
> crashkernel being started? A kernel running long enough to get to your
> iptables rules should have produced a lot more messages than what I am
> seeing.

The first line was my "echo h > /proc/sysrq-trigger" then long time 
nothing and then there was the reset and it started with the new kernel. 
The earlyprintk options seems to be somewhat silent in comparison with 
the "console=" option (which I replaced by earlyprintk). There are more 
kernel messages, like:
[43424.885011] Peer xx.xx.xx.xx:23191/80 unexpectedly shrunk window 
4088072550:4088072566 (repaired)
[44814.276353] perf interrupt took too long (2547 > 2500), lowering 
kernel.perf_event_max_sample_rate to 50000

Mostly just the shrunk window stuff though, but that's not logged to the 
serial port.

> 
> Can you try running with no crashkernel option and while you are at
> it, please remove the quiet option. The last thing you want when
> troubleshooting is for things to be quiet.
> 

Will do.

> --
> Mark Rustad, Networking Division, Intel Corporation

-- 
Regards,
Christian Ruppert

------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to