From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 43DC5C10F0C for ; Thu, 4 Apr 2019 22:11:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0DE7D217D9 for ; Thu, 4 Apr 2019 22:11:31 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="ITogDj38" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731189AbfDDWLa (ORCPT ); Thu, 4 Apr 2019 18:11:30 -0400 Received: from mail-lf1-f44.google.com ([209.85.167.44]:36779 "EHLO mail-lf1-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731187AbfDDWL2 (ORCPT ); Thu, 4 Apr 2019 18:11:28 -0400 Received: by mail-lf1-f44.google.com with SMTP id d18so2951248lfn.3 for ; Thu, 04 Apr 2019 15:11:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iwHoC8t2r+v5RbVW2CYOtHdjNhLo3GkqxlbnYUA3tPU=; b=ITogDj38KoLhjSPhPzSLoAEjB3uO+pEobA1v/5Zs9vNtPa/1ni2a8NfiYB1imkm/em id+niyRePyv5NeXTr7yr9V/JRUoIA1z1hJIeD21PRC507TlyUupczj5l1GUQ4nxDGjFy lznmNtKJ9x8j6Esr6gdGXyHT2tUdayqRM5p/nfvI4yXSlCEd8TgkuYeg7GsLPb2kBPYW D58z6sOTDMZ5Krj+/S8bBD1eanG0lV+F4O0qKFGccjNPIRVcLmFXHftbEsfOOGgHqanP YMouj3UybYiCZxDLg4b7YSYRkcgeZ7ACr8WAcTq6+SiUWzF0lLM7GHnL40MbVxGhUKYD 00pg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iwHoC8t2r+v5RbVW2CYOtHdjNhLo3GkqxlbnYUA3tPU=; b=iu8VoFiMvkJIHC3zU6a3f5S7j1UJlnynckoMsYlWo7vx31KURPoo2fDekB6HnGkJJv otbR8mSsomYbStmMnUZcSsg9vfjsdeFSZB0uh4kguCa8KmyRLzDiZfF4mwiSPZ+/3FgF +Prl2KvKai00nxgPDTLHssyCr+JOLlGjafrMmrCbJOjdGt+ae4VmgK69s3zcnz3Hh63j z/p2VqAy9zli54Jq6EDTuA7pYoMSC8ph7nsEfCSkN6xyKHDWGMYyjFPpOBMpGJalVkq5 AMcNaU+Ugu7TzYyPC+d71W9jqz5Q8YtXT3Q3KZn9cLdtlmn96QOR3i7rFZkyDKfrxPYo dzfg== X-Gm-Message-State: APjAAAVmcogTSmTxMJbxGRK1OTsfvRbGHhKo33SI7kFObQcFimsrSwwC mT8GQDDcwExOPGf3MiDLd4gBDT3LHSR2/BmEk0A= X-Google-Smtp-Source: APXvYqwx3edZJ92qMP9+kENvPo6S3FHecM3WPFWVP2C0AyA8/ztDLcgUgqDL28J6MHEasmHO5vrZk5FIN+RVDRaydbQ= X-Received: by 2002:a19:ed03:: with SMTP id y3mr4526081lfy.30.1554415886515; Thu, 04 Apr 2019 15:11:26 -0700 (PDT) MIME-Version: 1.0 References: <0704f164-aa0a-bcae-a886-a7fc4a4cd52f@gmail.com> <8f910b1339a741cdc780f3948c11a082a8a51b9e.camel@linux.intel.com> <5870baca-9d1b-b75f-6406-4ba0cee1dbe8@gmail.com> <939eb5de-de7e-86ba-d1d9-fac7faa14f2c@gmail.com> In-Reply-To: <939eb5de-de7e-86ba-d1d9-fac7faa14f2c@gmail.com> From: VDR User Date: Thu, 4 Apr 2019 15:11:13 -0700 Message-ID: Subject: Re: r8169 driver from kernel 5.0 crashing - napi_consume_skb To: Heiner Kallweit Cc: netdev@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > > Unfortunately I have to report that the crashing has resurfaced. I'm > > currently using kernel 5.0 with Heiner's fix applied. In the last few > > days I've had the crash occur 4 times now. I'm not sure how to further > > investigate this but I'm guessing a patch that adds more debugging > > output will be needed to track down where exactly things go bad and > > hopefully what exactly is triggering it? In 2 cases there was > > bi-directional traffic, in the other 2 cases there was only incoming > > traffic. In all cases the nic became unresponsive, all connections to > > the box died/timed out. After roughly 10 minutes the nic came back to > > life on its own without my intervention. The odd thing I noticed was > > the dmesg log showing the problem only shows up once in dmesg instead > > of 4 times to coincide with the 4 crashes/freezes. I don't think the > > box reboot itself, and if it did then dmesg should be clean. > > > Instead of having to wait for the issue: Can you trigger it with iperf3 > in either direction? I'm not familiar with iperf3 but installed it and looked up a quick example. I started the iperf3 server on the server and then ran the test on the client a bunch of times. And then also tried the test with the `-d` bi-directional flag. I couldn't get the crash/freeze to trigger though. Is there a certain command line I should run the test with, or anything specific I should do? -Derek