Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp3336410ybg; Fri, 25 Oct 2019 02:36:58 -0700 (PDT) X-Google-Smtp-Source: APXvYqyMRa+aB+5Fut8zhsUP4FlNK5Ovm9K/gOnNj8NhqQdQZ+R1Mx7eZ8GmYLjuDXSy8Oikl10n X-Received: by 2002:aa7:d358:: with SMTP id m24mr2841413edr.204.1571996218712; Fri, 25 Oct 2019 02:36:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571996218; cv=none; d=google.com; s=arc-20160816; b=OS+ps3OqtF043W3iDTTo59ALhyM7+oT77g+Q/Co2qs5IVbIMwJxxQRCZd3Wnzt/I7Z b+FSkIjxGRZOr39SHsYxnmtNK+3w8WKhvbnghyg7TB8WldfsLAslD4YfWZD5f1g2GrHx 0F/utI9t+w5gwXLKlIpdrRMTECpuBWvcoVZ/dgUDKJ2QNWvbbZmQE/qytr2veBbL5xCt G5zwbBkSpx8Aov2cfUtcf+6uNy5BYLYVZAVxQmONYbxaChxOh1xMhLt4sD5ZYadocdMX Wf588IAePu2C+hgno7StwU/rr6V7PMb7bqyHqR2lTNl9sFPdDvadIieyL8G2sCAvZMvb kcjA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=EzxqLk+l11YQwxsdVziDenV56pIvcNqPpBhMcF6c66U=; b=cASOpgy5wizZvtFQvMsnU1rAboPqfrzyobtxZDrP5RKF5be+yhH4wvpuh2oEACWJYD GHZyeHAvKoEB2WAEoJ+ihMlYSSQq+8WZUO5+hP6H8MsWpn9PEgvZinZBvKVOoiNrcSUP ptvN1s4emmNpWMOYrIPv4DrOtg9QL6XAmuLnZV2fvcdL+3HcR/snEp+GtsilO7ZqVt0z NYeA42ntMGIkVZbjChhdORXYrcqQf+II7SV/2H7j4dkNaFhp4aYyPNvzbKnB7Jy7PuRa frHbfJsJqcjiImTL5lrzm1cGUsu4NzT5mFrO1V3VDd2V90R6o1HsxPZpVI7IZYebtceu 45yg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p20si846761ejj.394.2019.10.25.02.36.34; Fri, 25 Oct 2019 02:36:58 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2438898AbfJXKnX (ORCPT + 99 others); Thu, 24 Oct 2019 06:43:23 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:53393 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2436873AbfJXKnW (ORCPT ); Thu, 24 Oct 2019 06:43:22 -0400 Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1iNaaL-0003Um-Dg; Thu, 24 Oct 2019 12:43:17 +0200 Date: Thu, 24 Oct 2019 12:43:17 +0200 From: Sebastian Andrzej Siewior To: Daniel Wagner Cc: Jakub Kicinski , UNGLinuxDriver@microchip.com, netdev@vger.kernel.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org, Woojung Huh , Marc Zyngier , Andrew Lunn , Stefan Wahren , Jisheng Zhang , Thomas Gleixner Subject: Re: [PATCH] net: usb: lan78xx: Use phy_mac_interrupt() for interrupt handling Message-ID: <20191024104317.32bp32krrjmfb36p@linutronix.de> References: <20191018082817.111480-1-dwagner@suse.de> <20191018131532.dsfhyiilsi7cy4cm@linutronix.de> <20191022101747.001b6d06@cakuba.netronome.com> <20191023074719.gcov5xfrcvns5tlg@beryllium.lan> <20191023080640.zcw2f2v7fpanoewm@beryllium.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20191023080640.zcw2f2v7fpanoewm@beryllium.lan> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019-10-23 10:06:40 [+0200], Daniel Wagner wrote: > Sebastian suggested to try this here: > > --- a/drivers/net/usb/lan78xx.c > +++ b/drivers/net/usb/lan78xx.c > @@ -1264,8 +1264,11 @@ static void lan78xx_status(struct lan78xx_net *dev, struct urb *urb) > netif_dbg(dev, link, dev->net, "PHY INTR: 0x%08x\n", intdata); > lan78xx_defer_kevent(dev, EVENT_LINK_RESET); > > - if (dev->domain_data.phyirq > 0) > + if (dev->domain_data.phyirq > 0) { > + local_irq_disable(); > generic_handle_irq(dev->domain_data.phyirq); > + local_irq_enable(); > + } > } else > netdev_warn(dev->net, > "unexpected interrupt: 0x%08x\n", intdata); This should should be applied as a regression fix introduced by commit ed194d1367698 ("usb: core: remove local_irq_save() around ->complete() handler") > While this gets rid of the warning, the networking interface is not > really stable: > > [ 43.999628] nfs: server 192.168.19.2 not responding, still trying > [ 43.999633] nfs: server 192.168.19.2 not responding, still trying > [ 43.999649] nfs: server 192.168.19.2 not responding, still trying > [ 43.999674] nfs: server 192.168.19.2 not responding, still trying > [ 43.999678] nfs: server 192.168.19.2 not responding, still trying > [ 44.006712] nfs: server 192.168.19.2 OK > [ 44.018443] nfs: server 192.168.19.2 OK > [ 44.024765] nfs: server 192.168.19.2 OK > [ 44.025361] nfs: server 192.168.19.2 OK > [ 44.025420] nfs: server 192.168.19.2 OK > [ 256.991659] nfs: server 192.168.19.2 not responding, still trying > [ 256.991664] nfs: server 192.168.19.2 not responding, still trying > [ 256.991669] nfs: server 192.168.19.2 not responding, still trying > [ 256.991685] nfs: server 192.168.19.2 not responding, still trying > [ 256.991713] nfs: server 192.168.19.2 not responding, still trying > [ 256.998797] nfs: server 192.168.19.2 OK > [ 256.999745] nfs: server 192.168.19.2 OK > [ 256.999828] nfs: server 192.168.19.2 OK > [ 257.000438] nfs: server 192.168.19.2 OK > [ 257.004784] nfs: server 192.168.19.2 OK Since this does not improve the situation as a whole it might be best to remove the code as suggested by Daniel. Sebastian