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=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no 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 CBCF2ECE58E for ; Thu, 17 Oct 2019 18:14:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9A72D21835 for ; Thu, 17 Oct 2019 18:14:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2441188AbfJQSOv (ORCPT ); Thu, 17 Oct 2019 14:14:51 -0400 Received: from mx2.suse.de ([195.135.220.15]:34654 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2438601AbfJQSOv (ORCPT ); Thu, 17 Oct 2019 14:14:51 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 83724B3A0; Thu, 17 Oct 2019 18:14:50 +0000 (UTC) Date: Thu, 17 Oct 2019 20:14:46 +0200 From: Daniel Wagner To: Stefan Wahren Cc: Woojung Huh , Andrew Lunn , netdev@vger.kernel.org, UNGLinuxDriver@microchip.com, bcm-kernel-feedback-list@broadcom.com, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org Subject: Re: lan78xx and phy_state_machine Message-ID: <20191017181446.llylehcpu66bpqcn@beryllium.lan> References: <20191014140604.iddhmg5ckqhzlbkw@beryllium.lan> <20191015005327.GJ19861@lunn.ch> <20191015171653.ejgfegw3hkef3mbo@beryllium.lan> <20191016142501.2c76q7kkfmfcnqns@beryllium.lan> <20191016155107.GH17013@lunn.ch> <20191017065230.krcrrlmedzi6tj3r@beryllium.lan> <6f445327-a2bc-fa75-a70a-c117f2205ecd@gmx.net> <20191017174133.e4uhsp77zod5vbef@beryllium.lan> <388beb72-c7e6-745a-ad39-cfbde201f373@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <388beb72-c7e6-745a-ad39-cfbde201f373@gmx.net> User-Agent: NeoMutt/20180716 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > >> Unfortunately, you didn't wrote which kernel version works for you > >> (except of this splat). Only 5.3 or 5.4-rc3 too? > > With v5.2.20 I was able to boot the system. But after this discussion > > I would say that was just luck. The race seems to exist for longer and > > only with my 'special' config I am able to reproduce it. > okay, let me rephrase my question. You said that 5.4-rc3 didn't even > boot in your setup. After applying Andrew's patch, does it boot or is it > a different issue? Yes, with Andrew's patch the initial problem is gone. > >> [1] - https://marc.info/?l=linux-netdev&m=154604180927252&w=2 > >> [2] - https://patchwork.kernel.org/patch/10888797/ > > Indeed, the irq domain code looks suspicious and Marc pointed out that > > is dead wrong. Could we just go with [2] and fix this up? > > Sorry, i cannot answer this question. Sure, I just trying to lobbying :)