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 B32C1C43381 for ; Thu, 14 Mar 2019 06:44:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7EFF82184E for ; Thu, 14 Mar 2019 06:44:10 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="cWEts0L1" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727354AbfCNGoJ (ORCPT ); Thu, 14 Mar 2019 02:44:09 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:42051 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726464AbfCNGoI (ORCPT ); Thu, 14 Mar 2019 02:44:08 -0400 Received: by mail-wr1-f68.google.com with SMTP id n9so432822wrr.9 for ; Wed, 13 Mar 2019 23:44:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=g/tGwqPR1IzMIizk+AYmb6pwrNU1xkniXkrXUS8wA9c=; b=cWEts0L1y93jwlty24jbdXodzUaOgn0igxTTSX5pvMsxkFDHlFUVOLOMf45Rh77J0+ 3x7zh3f+GvMMN9EvEE23rAj1nTvqbeCoeZHXjIpazgF77XZ2UAxKB1eiGuF5t+Tqqaqa DjpQnjJxj++tLJ/7ly74FibaqLwifGnXclF83pLvxmYjZ3hjnpjl4qzVqVBsvO/ZcKGb OB4KEI7MC524f4xnLJxk6jBMNcS3Zc26WUnAIvVnOsLPLA3QEAE3wKuGtjA2YvzlNu0r psHRSlMjitr9ON6XAQSiQzU5qAX4cw7mMMn2lfzefdoI2jrloV/UscGoyntuXWGQ60QT 1V/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=g/tGwqPR1IzMIizk+AYmb6pwrNU1xkniXkrXUS8wA9c=; b=HdYaKpZJFAZF5O70iFR53zXVXn3RfFJySepOPgAr1QJId0v6NK59/cBoNO37J45H+l 3LREQ1m3q6OI2dic74OScfqaI/PeR3slmvFPf444N8SxnwL2JLSCqXtGIGhQ1lfOeBnd Fii5MSIROsN2oUj7q0jCWPXUE4rQ17t7kLF6VsEQDMO2lMxXz2V6O0VpAChhfkjsHz1i uYAeDOfWH9vL6sxSYQ526Keg33iqLxQWuxlp61MTEUOaKaPpnAMvGwSJGyt+BtaTzSnT m9HBEPQBtIBDvPUeMVpP3DrMhxcwxqPnGVU+Oo5DVfnMC7PaJZ9LuS43Dz+/PR/1EO7H HnWA== X-Gm-Message-State: APjAAAW3Rw99JLMkT9lqzO0ycHtxyIX1p0zeqULADtermsQ1gblq1lrU BwjPwxlxSwiI1HNwj9RxjuNTFfIb X-Google-Smtp-Source: APXvYqxSkd9umBFYRAyy5B7+Uhf0mL553WGiAmVFBE8laRTL1S6pXfVWGG5p5mSG864M1ei9JemIdA== X-Received: by 2002:a5d:6b43:: with SMTP id x3mr32757290wrw.76.1552545846558; Wed, 13 Mar 2019 23:44:06 -0700 (PDT) Received: from ?IPv6:2003:ea:8bc4:dc00:88f6:308a:5bae:dd1? (p200300EA8BC4DC0088F6308A5BAE0DD1.dip0.t-ipconnect.de. [2003:ea:8bc4:dc00:88f6:308a:5bae:dd1]) by smtp.googlemail.com with ESMTPSA id y140sm5896314wmd.18.2019.03.13.23.44.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Mar 2019 23:44:05 -0700 (PDT) Subject: Re: r8169 driver from kernel 5.0 crashing To: VDR User Cc: netdev@vger.kernel.org References: From: Heiner Kallweit Message-ID: <753b56b8-f1ab-82f5-f9b5-089fbb638989@gmail.com> Date: Thu, 14 Mar 2019 07:43:59 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On 14.03.2019 04:04, VDR User wrote: > Hi Heiner, > > Thanks for your response. Request info follows.. > >>> Hi, after updating to kernel 5.0, the nic driver (r8169) has been >>> crashing whenever I start using heavy traffic on it (for example, >>> xferring large files to the box across my lan). The destination >>> harddrive may be sleeping and need to spin-up, or not, but the box >>> itself does not suspend/hibernate. The nic becomes completely >>> unresponsive and all connections to the box drop. After what I think >>> is several minutes, the connection comes back to life. The problem >>> happens consistently but seemingly not consistently at the same point. >>> For example, I can xfer a few 4gb files and it will crash at around >>> 2-3gb on the first file. The next time it might not crash until 2-3gb >>> on the second file.Prior to kernel 5.0 I was using 4.19.12 and this >>> problem didn't occur. I have since downgraded back to 4.19.12 pending >>> what response this post gets. >>> >> Thanks for the report. Helpful would be: >> - full dmesg output > > Added as attachment. > >> - "lspci -vv" output (as root) for the network card > [...] >> Can you test a recent 4.20 kernel? This would narrow down the number >> of potentially problematic patches. > > I compiled and test 4.20.15 and didn't experience any crashing. I then > switched back to 5.0.0 and this time I had to transfer significantly > more until the crash occured. I'm not sure but it seems like the > crashes happen when there's both outgoing & incoming traffic > simultaneously. Is the dmesg crash info helpful at all? > Thanks for the additional info and for testing 4.20.15. To rule out that the issue is caused by a regression in network or some other subsystem: Can you take the r8169.c from 4.20.15 and test it on top of 5.0? Meanwhile I'll look at the changes in the driver between 4.20 and 5.0. > Thanks, > Derek > Heiner