From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-f179.google.com (mail-io0-f179.google.com [209.85.223.179]) by dpdk.org (Postfix) with ESMTP id 192E8558C for ; Tue, 22 Nov 2016 15:27:57 +0100 (CET) Received: by mail-io0-f179.google.com with SMTP id s15so3935751ioi.2 for ; Tue, 22 Nov 2016 06:27:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=mKOojJPGhvkHfg0hr4MzVr03YAucBEqQEv09CXGnGlY=; b=JVU9W/ideqFTPq8pgrB6H6kQME9jvz0mHqgwp/HanV9KoDsYKqJH5OuUScxirP0K54 3SjGFQUZEZUIuOzcu87HMo+bDI5aF8h8eaQxEr31eNO9WrvCqqlnrit4Np7RJqFzPxcd /HeSt561bkc5H5MM1kdBxJxR0AWP1P6qDhOuDdoyuDI9Ul601sUn17Pv/bv2kX5T8C6i veKSTUr8t5K6klcv481cip6OOzgkgJZ1Kat714e3BbPaY66piCfoYKbBeaxAfOoG/FHx uf2WS7WDtz+U2BNVMT+5mO6ifWg4E1VERsy5KQDOPp06oV3OvilRdLlvIefPWbL24i5f o8VA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=mKOojJPGhvkHfg0hr4MzVr03YAucBEqQEv09CXGnGlY=; b=B5cNHD0J2HSKk7MZTk5HX8Auo/PixJnKbmoJJs+ndBtblzb0dDGNgE0VWuo7+gWbt6 GsTyLBcOnlVAfltw0g1jF8N76OoqxJCa54t0X5plQdEBzfT1ZcxyDviP+Tck6G6O2j59 V2EaL1kgzZdeEA7B8Vtihax5pjJ8BDdQfCc8tOBwATnA9b+IZI7qnzHZ6YW0xnqVJGbQ /g7FAUz+fRGI5VaXTYW2HiasQWQ2P9G2AcjOzltxadELwyuZsDDaHyioBfjo0Wz+uql7 /bG4lKZiBGIp69Cgk+LoJkQkiFLr7NijbU6B7ah2zKWCYWyAceqmMmtWZe5p1xrIn6G1 AYPw== X-Gm-Message-State: AKaTC00HVUTB2sIvzajm/0xcxQnDscztltLXyVKEhsP+E50uFtZS3BmqTXo0w3sl3KPSUQIb9uFgBVJpsuKtqQ== X-Received: by 10.107.133.206 with SMTP id p75mr8028553ioi.175.1479824876261; Tue, 22 Nov 2016 06:27:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.27.14 with HTTP; Tue, 22 Nov 2016 06:27:55 -0800 (PST) In-Reply-To: References: From: =?UTF-8?Q?Norbert_Nyak=C3=B3?= Date: Tue, 22 Nov 2016 15:27:55 +0100 Message-ID: To: Anupam Kapoor Cc: users@dpdk.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-users] Dell PowerEdge CPU IERR caused by DPDK 16.07 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 14:27:57 -0000 Hi, Thank you for your help! There was also a =E2=80=9Dbus fatal error" in the iDRAC / OMSA log and I al= so 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 : > > On Mon, Nov 21, 2016 at 3:45 PM, Norbert Nyak=C3=B3 > 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 reseati= ng > 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 (rath= er > than just _triggered_) by dpdk would be to invert machine configuration a= nd > then retest ? > > -- > thanks > anupam > > In the beginning was the lambda, and the lambda was with Emacs, and Emacs > was the lambda.