Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp3055285ybe; Sun, 15 Sep 2019 06:37:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqyotLJC++TkS3AAxT54WFCLwuZsQYRfdtMxChwFmCz/rXOnY5K6zoLU/EoX10a9lho9eFEG X-Received: by 2002:a17:906:44b:: with SMTP id e11mr43838620eja.26.1568554655524; Sun, 15 Sep 2019 06:37:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568554655; cv=none; d=google.com; s=arc-20160816; b=wlUnIDToMKZI8b/TZQDqZ23aul6HgV9nHJr7Bu9nT6AHKUeu4jOOscVJIE8kVWPwQs Fgo1lcygT4TWRB3zg+nPXUZ/bwp07us+L5sU+lHI6NAteBbbBy6KgBzCXJ+bb+frmdNa F9bhF1Yb/XjxDmIURTjhJpwdj5fEYBMjZ9Nv1Xi6RqXUn2s2k9byLjbXwxqg/rn3PWij yP6bmJHtD3nXeME0LiphSW7TMuZu6T26ZRvwpXOrWiJzLogH1NfzgK3v8el+AsB6I2Ji v4DMKGRjAu2ID/EsS7vFPXUV51Kw64qQtjjlJ97OHaEiKri0ay3QJzzxu2YzzlpMbgQ5 +h3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=2ONh9octt7hrPQetjAA69jtrwBb1nNoc7kuenQgL5+s=; b=fY9t07aNvPRZFXkiQcNakBSzS1X9H28toJdI40IobY4IyYiQMhTTmgmBLGMh6383ML NDHQkDb/NGwmtfT6ZNUkHpNriFNq7N6itdfhNZmgbB7Sfkazu0kSryjc9VyJF7gpmo69 hbS4F60YoPVuxSTpQVPZMGj0swStjvGaDuh0bFC9O92EHz1Yp7wiAWMlyE7/BWABKWEP /aMeo8Ya7CfHAmpwoD1B8/jMsO+Nd9ddzqMR2w6YOfTzbDa7YxNrBNtDvEctqBRCTupt fg7u5OT50Kjbx1FCl++ng+QIc1QlkTOlXVqr1+IUa9BjQLVxxL/Ih2/7aEF69x8BbbDL VfhQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=neutral (body hash did not verify) header.i=@armlinux.org.uk header.s=pandora-2019 header.b=KrX8c7JG; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=armlinux.org.uk Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n4si1871388ejj.132.2019.09.15.06.37.11; Sun, 15 Sep 2019 06:37:35 -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; dkim=neutral (body hash did not verify) header.i=@armlinux.org.uk header.s=pandora-2019 header.b=KrX8c7JG; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=armlinux.org.uk Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730537AbfIOM3v (ORCPT + 99 others); Sun, 15 Sep 2019 08:29:51 -0400 Received: from pandora.armlinux.org.uk ([78.32.30.218]:36718 "EHLO pandora.armlinux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730448AbfIOM3v (ORCPT ); Sun, 15 Sep 2019 08:29:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2019; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=9p2NJ7BXbD4NZDyoxVh3Cv5cepB8PS65/rD5Ce0NUf8=; b=KrX8c7JGi47gemy02Slr+/J2I Gp+EfycmlV+P7bdYQMrEWbtqcLDuOzSbj1JGG17tjfAGeax2abW9RwMmsOagJKPiLZoCzWCS0yLO/ skHja8Lhgeaz1ZO7mxNfWnlmX5ZdLaoZkB1e0BnNk0wYZgeIHdz5QRmH4/qONolqj2QjjGKwfQJ+H pxUsvux0tRGxGMJ1d2fMSqU3COP6SYBs6TpSs1ClB2d565FL9lt/wcy9rafohvBMje86YF//3iaH/ 2+2d1MZzquM+XAyGnAdLPs/a2Zqwiuo6jbQrv5qspFU/G3wAkzzG/YbvT0cxL61VoL+eFf+xNuOB1 53tmQ+uKw==; Received: from shell.armlinux.org.uk ([2002:4e20:1eda:1:5054:ff:fe00:4ec]:39810) by pandora.armlinux.org.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1i9Tes-0006Iq-Jp; Sun, 15 Sep 2019 13:29:38 +0100 Received: from linux by shell.armlinux.org.uk with local (Exim 4.92) (envelope-from ) id 1i9Tej-0007lP-9q; Sun, 15 Sep 2019 13:29:29 +0100 Date: Sun, 15 Sep 2019 13:29:29 +0100 From: Russell King - ARM Linux admin To: Baruch Siach Cc: Andrew Lunn , tinywrkb , Mark Rutland , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Shawn Guo , Sascha Hauer , open list , Rob Herring , NXP Linux Team , Pengutronix Kernel Team , Fabio Estevam , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] ARM: dts: imx6dl: SolidRun: add phy node with 100Mb/s max-speed Message-ID: <20190915122929.GB25745@shell.armlinux.org.uk> References: <20190910155507.491230-1-tinywrkb@gmail.com> <20190910185033.GD9761@lunn.ch> <87muf6oyvr.fsf@tarshish> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87muf6oyvr.fsf@tarshish> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Sep 15, 2019 at 09:30:00AM +0300, Baruch Siach wrote: > Hi Andrew, > > On Tue, Sep 10 2019, Andrew Lunn wrote: > > On Tue, Sep 10, 2019 at 06:55:07PM +0300, tinywrkb wrote: > >> Cubox-i Solo/DualLite carrier board has 100Mb/s magnetics while the > >> Atheros AR8035 PHY on the MicroSoM v1.3 CPU module is a 1GbE PHY device. > >> > >> Since commit 5502b218e001 ("net: phy: use phy_resolve_aneg_linkmode in > >> genphy_read_status") ethernet is broken on Cubox-i Solo/DualLite devices. > > > > Hi Tinywrkb > > > > You emailed lots of people, but missed the PHY maintainers :-( > > > > Are you sure this is the patch which broken it? Did you do a git > > bisect. > > Tinywrkb confirmed to me in private communication that revert of > 5502b218e001 fixes Ethernet for him on effected system. > > He also referred me to an old Cubox-i spec that lists 10/100 Ethernet > only for i.MX6 Solo/DualLite variants of Cubox-i. It turns out that > there was a plan to use a different 10/100 PHY for Solo/DualLite > SOMs. This plan never materialized. All SolidRun i.MX6 SOMs use the same > AR8035 PHY that supports 1Gb. > > Commit 5502b218e001 might be triggering a hardware issue on the affected > Cubox-i. I could not reproduce the issue here with Cubox-i and a Dual > SOM variant running v5.3-rc8. I have no Solo/DualLite variant handy at > the moment. With 5.3 due out today, I'll be updating my systems to that, which will include quite a few variants of the Hummingboard. It looks like one of my Solo Hummingboards (running a fully up to date Fedora 28) has encountered a problem, so needs a reboot... systemd-journald[436]: Failed to retrieve credentials for PID 17906, ignoring: Cannot allocate memory systemd-journald[436]: Failed to open runtime journal: Cannot allocate memory # ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND ... root 436 0.0 5.2 3128140 26392 ? Ss Aug03 1:20 /usr/lib/systemd/systemd-journald # uptime 13:28:41 up 42 days, 19:13, 1 user, load average: 0.00, 0.03, 0.00 Looks like systemd-journald has a rather bad memory leak... #include -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up