From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yk0-f179.google.com (mail-yk0-f179.google.com [209.85.160.179]) by dpdk.org (Postfix) with ESMTP id 0E27A9A92 for ; Wed, 11 Feb 2015 02:33:17 +0100 (CET) Received: by mail-yk0-f179.google.com with SMTP id 9so223564ykp.10 for ; Tue, 10 Feb 2015 17:33:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=su2W/m5M1Cag0arQshTt5smHtrPJKeeG/imXOZrOUYw=; b=WNLO4+c2iNtyGKKjmgPOFgKcF3h6WSghgY5sXrt2ova6pfrzjEm7j+f1owdYMZtzPa 07wsfiAu48Yv9Uc67BkdaEXhANpX869TjBZE0NCJiJVqnfI5eSQxGLa52z6itLd7/mK4 JtPHSl9v8J5NVTwOoDe4nqzqXExgg/CHMAi2T/rHFgNdt/zhsp8CAkVgxRWpMOZf77fz UNIf1/vJe9jVQAjg/onuSS1VF+Lz7tEVAPh/2Y2U6V9oZDq1M+HzKM0upFZwKQBx0033 bllLNrFuhstZsv3HykrxWhJCj1swhW9wM0wwwRFHwWVgwFJstP45cxjfNunOrMIW4Knr T6+w== X-Gm-Message-State: ALoCoQmWiRte0qmqN/z+MMwtNvTfCNoX15LZafOrkLQ8HJgHlG9uR/g7YtUOqxMXvV2uUIN61CU/ MIME-Version: 1.0 X-Received: by 10.236.7.39 with SMTP id 27mr749434yho.16.1423618394348; Tue, 10 Feb 2015 17:33:14 -0800 (PST) Received: by 10.170.42.212 with HTTP; Tue, 10 Feb 2015 17:33:14 -0800 (PST) Date: Tue, 10 Feb 2015 19:33:14 -0600 Message-ID: From: Jay Rolette To: Dev Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] kernel: BUG: soft lockup - CPU#1 stuck for 22s! [kni_single:1782] X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2015 01:33:19 -0000 Environment: * DPDK 1.6.0r2 * Ubuntu 14.04 LTS * kernel: 3.13.0-38-generic When we start exercising KNI a fair bit (transferring files across it, both sending and receiving), I'm starting to see a fair bit of these kernel lockups: kernel: BUG: soft lockup - CPU#1 stuck for 22s! [kni_single:1782] Frequently I can't do much other than get a screenshot of the error message coming across the console session once we get into this state, so debugging what is happening is "interesting"... I've seen this on multiple hardware platforms (so not box specific) as well as virtual machines. Are there any known issues with KNI that would cause kernel lockups in DPDK 1.6? Really hoping someone that knows KNI well can point me in the right direction. KNI in the 1.8 tree is significantly different, so it didn't look straight-forward to back-port it, although I do see a few changes that might be relevant. Any suggestions, pointers or other general help for tracking this down? Thanks! Jay