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 D13D2C43381 for ; Sun, 10 Mar 2019 19:35:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9715B206BA for ; Sun, 10 Mar 2019 19:35:48 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="s3QTXczC" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726848AbfCJTfr (ORCPT ); Sun, 10 Mar 2019 15:35:47 -0400 Received: from mail-wm1-f68.google.com ([209.85.128.68]:35073 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726505AbfCJTfr (ORCPT ); Sun, 10 Mar 2019 15:35:47 -0400 Received: by mail-wm1-f68.google.com with SMTP id y15so2297900wma.0 for ; Sun, 10 Mar 2019 12:35:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=XoLtobmDZgPKK02o3vOHcFT+OnY2Ey05v37IzjmF3no=; b=s3QTXczCwP8Zdth2IuUclfVwJ/MepNTGbMsKRu+v4jjGmpQXT39AujBqn+ASvmI1e2 UEqrS7Qq8GIyBkZBfiiLYwH7aCJcFAbOAuk2sI2MGn3OuDq2idQrCDeasoRk3VNwl0ua 3e6wri05i2e2U5eDGMutl4mBhwsfvlLW+6RNYcmARK8/WZcpDMVKksk08QSOuKer7/6o Bn9TR1H3kIlmtr7N9UI0VLRWUohiN8uIHCgPv83KTl7ioPP/Mt+tqSc+NpetkPv4iUT/ /4Iy7Vg/+uHupdmrR4Z5BE8GjP7N4/tmvkAWOBhUfC7eaL7WTNUapGcbfRyv/kd2MIOK q+FQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=XoLtobmDZgPKK02o3vOHcFT+OnY2Ey05v37IzjmF3no=; b=XfiWVq33uKfJt/xkDXTcnApLpk7UlH7h9Mis4Sc66AH8QDzqgDBNmzPbs9zkfDl3GY up8PP3OBqH1IbSh95Nvk0Ij2QQ/bDkG+cVQ9zw6U4sFZZk7sJHwf1FUPHYCq7vRbMKId pZXgQZHJQ9USmSeQTPphQP0INkY3oujh6fpOtVvCMrbdzV49/ZXdI9XAMtj6Zg+9roKs j+yodmBreI0BG4IvYVHj4U77ns5QPfbei2S1Z2BwbBONi2ZA8tv529/zUA+x3pHDZ59t Yv9PRpa/cRRPF7U4kuST7hIWqgRFOUjYxW6935sWWJgnnpf7p3A9bxUIHIhuUsj1k3Wm gBSA== X-Gm-Message-State: APjAAAXF788DqhtaM6S+hiB0aBkOWVbnslVGd9wnYSUuiN+LkUIAmhG8 GW3TLjNiqK/m0rdVXZlYPYeOK7JB X-Google-Smtp-Source: APXvYqwNQmW4Yo79u13lZSdlJghhI288CPjZOB9MtiRFe6c1tFjPCapqK8kNPv6ejiAr48dZXAvVmg== X-Received: by 2002:a7b:c146:: with SMTP id z6mr14512045wmi.145.1552246544775; Sun, 10 Mar 2019 12:35:44 -0700 (PDT) Received: from ?IPv6:2003:ea:8bf1:e200:c0d3:171b:900:dd4e? (p200300EA8BF1E200C0D3171B0900DD4E.dip0.t-ipconnect.de. [2003:ea:8bf1:e200:c0d3:171b:900:dd4e]) by smtp.googlemail.com with ESMTPSA id l3sm3418969wrt.62.2019.03.10.12.35.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 10 Mar 2019 12:35:44 -0700 (PDT) Subject: Re: r8169 driver from kernel 5.0 crashing To: VDR User , netdev@vger.kernel.org References: From: Heiner Kallweit Message-ID: Date: Sun, 10 Mar 2019 20:35:39 +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 10.03.2019 20:02, VDR User wrote: > 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 any help or assistance on how to proceed! > -Derek > Thanks for the report. Helpful would be: - full dmesg output - "lspci -vv" output (as root) for the network card - ethtool -S output Can you test a recent 4.20 kernel? This would narrow down the number of potentially problematic patches. Heiner