From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-f177.google.com (mail-vc0-f177.google.com [209.85.220.177]) by dpdk.org (Postfix) with ESMTP id 23B919AA6 for ; Wed, 11 Feb 2015 17:25:54 +0100 (CET) Received: by mail-vc0-f177.google.com with SMTP id hy10so1522272vcb.8 for ; Wed, 11 Feb 2015 08:25:53 -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:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=TxbrAnbU0NN16yxtTU/2BqR7wF3G/bVPPt1CmT1vi48=; b=OiKQFSFCUGJqgayCh9PYpaf7KgoyFY2bt6cEFUJUAypIfjOWVLJi2fE9daUki/XZEF AQNsVsmOn9M/PPrb39oW3AY43jZgjZrRfRPpGZGPrWcw/hOjAWIZsVPGhCAoa329uNgu Tt2/t+q3lajwUvSRu7hPF6wjHb5cT51X17fZYulaDLn1tC06BZAoRTNR8dGwakoGXJp6 oMIhTmJjoPy0T4WpzPYTC5C9nB5d5/KwKPnoUKI86Za/JR+Il1zNHzXgJN88QTJUV0HA F70Gbr1vDMtPGW2QPVA1kcl3vl3ZMLd6uKNQttqWzkDCCJJhWUVDPmM6iWCZhNx1VX/c RjBw== X-Gm-Message-State: ALoCoQl2IYPe5+17SHT0QmvAcO52Roh/i8EO3pgP3uxPcgFLdG9J01BIPe254vN/zdXmmITiT8B7 MIME-Version: 1.0 X-Received: by 10.52.53.66 with SMTP id z2mr14258623vdo.75.1423671953554; Wed, 11 Feb 2015 08:25:53 -0800 (PST) Received: by 10.52.177.229 with HTTP; Wed, 11 Feb 2015 08:25:53 -0800 (PST) In-Reply-To: References: Date: Wed, 11 Feb 2015 16:25:53 +0000 Message-ID: From: Alejandro Lucero To: dev Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [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 16:25:54 -0000 Hi Jay, I saw these errors when I worked in the HPC sector. They come usually with a kernel dump for each core in the machine so you can know, after some peering at the kernel code, how the soft lockup triggers. When I did that it was always an issue with the memory. So those times that you can still work on the machine after the problem, look at the kernel messages. I will be glad to look at it. On Wed, Feb 11, 2015 at 1:33 AM, Jay Rolette wrote: > 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 >