Re: [dpdk-users] Dell PowerEdge CPU IERR caused by DPDK 16.07

["Norbert Nyakó" <norbert.nyako@gmail.com>]

Hi,

Thank you for your help!
There was also a ”bus fatal error" in the iDRAC / OMSA log and I also
looked at /var/log/* but there was no any suspicious log entry, I
think it because the machine rebooted as soon as the error triggered.
In my opinion it is not hardware fault because we have two machines
with the same configs and both behaves the same, but we tried with the
same network card with a different machine and there was no error.
Also we will try it with a different network card soon.
Since my first mail we updated the BIOS of the machines but it did not
help. Maybe it can be some firmware bug in the server which
incorrectly identifies CPU fault.

Best regards,
Norbert

2016-11-22 7:48 GMT+01:00 Anupam Kapoor <anupam.kapoor@gmail.com>:
>
> On Mon, Nov 21, 2016 at 3:45 PM, Norbert Nyakó <norbert.nyako@gmail.com>
> wrote:
>>
>> As soon as I ran the testpipeline sample application on one of the
>> servers it stops responding  and on the LCD info screen and in the
>> logs CPU IERR error messages appear
>
>
> difficult to *conclusively* conclude that this might be _caused_ by dpdk.
>
> what is the error that you see (not just the fact that you saw a CPU-IERR) ?
> for some more information have a look here:
> http://www.dell.com/support/article/in/en/indhs1/SLN292634. maybe reseating
> memory modules (or some such) on the machine where you see this might fix
> the issue ?
>
> one laborious but possible approach to conclude that this is caused (rather
> than just _triggered_) by dpdk would be to invert machine configuration and
> then retest ?
>
> --
> thanks
> anupam
>
> In the beginning was the lambda, and the lambda was with Emacs, and Emacs
> was the lambda.