From: Tom Bogendoerfer <tsbogend@alpha.franken.de>
To: Laura Abbott <labbott@redhat.com>
Cc: isubramanian@apm.com, kchudgar@apm.com, qnguyen@apm.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] xgene: Don't fail probe, if there is no clk resource for SGMII interfaces
Date: Thu, 27 Jul 2017 23:39:15 +0200 [thread overview]
Message-ID: <20170727213915.GA4902@alpha.franken.de> (raw)
In-Reply-To: <22ee6284-7b23-7664-d6cf-23687f09a3be@redhat.com>
On Thu, Jul 27, 2017 at 02:03:42PM -0700, Laura Abbott wrote:
> This change causes boot failures for me on my APM Mustang system running
> Fedora rawhide:
>
> [ 16.669089] Synchronous External Abort: synchronous external abort (0x9600000
> [ 16.669099] Internal error: : 96000010 [#1] SMP
> [ 16.669103] Modules linked in: xgene_enet(+) at803x realtek mdio_xgene xgenes
> [ 16.669127] CPU: 2 PID: 534 Comm: systemd-udevd Not tainted 4.13.0-0.rc1.git1
> [ 16.669128] Hardware name: AppliedMicro X-Gene Mustang Board/X-Gene Mustang 6
> [ 16.669131] task: ffff8003e6f8ce00 task.stack: ffff8003e4fd8000
> [ 16.669144] PC is at xgene_enet_wr_mac+0xa0/0x128 [xgene_enet]
> [ 16.669152] LR is at xgene_enet_wr_mac+0x64/0x128 [xgene_enet]
on the first glance I don't see anything clock related there.
What firmware version is installed on your mustang board ? I saw
ethernet related crashes with mustang boards because the device tree
in firmware was too old for the xgene ethernet driver.
Thoms.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2017-07-27 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 8:57 [PATCH net] xgene: Don't fail probe, if there is no clk resource for SGMII interfaces Thomas Bogendoerfer
2017-07-13 16:22 ` David Miller
2017-07-27 21:03 ` Laura Abbott
2017-07-27 21:39 ` Tom Bogendoerfer [this message]
2017-07-27 22:39 ` Laura Abbott
2017-07-28 14:23 ` Tom Bogendoerfer
2017-07-28 16:42 ` Laura Abbott
2017-07-28 18:40 ` Iyappan Subramanian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170727213915.GA4902@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=isubramanian@apm.com \
--cc=kchudgar@apm.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qnguyen@apm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox