From: Andrew Lunn <andrew@lunn.ch>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: netdev@vger.kernel.org, Heiko Stuebner <heiko@sntech.de>,
david.choi@micrel.com, Andy Yan <andy.yan@rock-chips.com>
Subject: Re: Linux kernel hangs if using RV1108 with MSZ8863 switch with two ports connected
Date: Sat, 17 Nov 2018 00:40:44 +0100 [thread overview]
Message-ID: <20181116234044.GA752@lunn.ch> (raw)
In-Reply-To: <CAP9ODKpHzQKC-C8KNbNUB3OGt7_xJyNtWyeYj7C9pwbh=ow0Yg@mail.gmail.com>
On Fri, Nov 16, 2018 at 04:28:29PM -0200, Otavio Salvador wrote:
> Hi,
>
> I have a custom design based on Rockchip RV1108 that uses an MSZ8863
> switch running kernel 4.19.
>
> The dts part is as follows:
>
> &gmac {
> pinctrl-names = "default";
> pinctrl-0 = <&rmii_pins>;
> snps,reset-gpio = <&gpio1 RK_PC1 GPIO_ACTIVE_LOW>;
> snps,reset-active-low;
> clock_in_out = "output";
> status = "okay";
> };
>
> RV1108 GMAC is connected to KSZ8863 port 3 and after kernel boots, I
> can put an Ethernet cable from my router to the uplink port of
> KSZ8863, which makes the RV1108 board and a Linux PC connected to the
> other KSZ8863 port to both get IP addresses.
>
> So in this usecase the setup is working fine.
>
> However, if the RV1108 board boots with both Ethernet cables to the
> KSZ8863 switch connected, then the kernel silently hangs.
Hi Otavio
By silently, you mean it prints nothing at all?
I would try building the kernel with all the lock debugging turned
on. That might find something even with your working case, if there is
a potential deadlock.
If the kernel dies very early, you might need to enable "kernel
low-level debugping print and EARLY_PRINTK, in order to see anything.
Andrew
next prev parent reply other threads:[~2018-11-17 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 18:28 Linux kernel hangs if using RV1108 with MSZ8863 switch with two ports connected Otavio Salvador
2018-11-16 23:40 ` Andrew Lunn [this message]
2018-11-17 21:04 ` Otavio Salvador
2018-11-18 18:12 ` Andrew Lunn
2018-11-18 22:27 ` Heiko Stübner
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=20181116234044.GA752@lunn.ch \
--to=andrew@lunn.ch \
--cc=andy.yan@rock-chips.com \
--cc=david.choi@micrel.com \
--cc=heiko@sntech.de \
--cc=netdev@vger.kernel.org \
--cc=otavio.salvador@ossystems.com.br \
/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;
as well as URLs for NNTP newsgroup(s).