From: Emil Renner Berthing <emil.renner.berthing@gmail.com>
To: schwab@suse.de
Cc: linux-riscv@lists.infradead.org
Subject: Re: MACB in 4.20-rc2
Date: Wed, 14 Nov 2018 22:08:47 +0100 [thread overview]
Message-ID: <CANBLGcxSA0GYd+D0Ofe0mAJhGQcqdi-4jCWGWk=EUqnqK-4v1A@mail.gmail.com> (raw)
Message-ID: <20181114210847.A3zWTGMBkq_dbBJR3C8YKgh2Gg_zRCEPiD_ZKcbFNnw@z> (raw)
In-Reply-To: <mvmwopffwlo.fsf@suse.de>
Hi Andreas,
On Wed, 14 Nov 2018 at 17:33, Andreas Schwab <schwab@suse.de> wrote:
>
> It looks like the MACB driver is broken in 4.20-rc2. I can see these
> two messages:
>
> [ 38.530000] macb: GEM doesn't support hardware ptp.
> [ 38.540000] libphy: MACB_mii_bus: probed
>
> but appears to be stuck without ever reaching this message:
>
> [ 38.750000] Microsemi VSC8541 SyncE 10090000.ethernet-ffffffff:00: attached PHY driver [Microsemi VSC8541 SyncE] (mii_bus:phy_addr=10090000.ethernet-ffffffff:00, irq=POLL)
>
> The module never finishes initializing.
That's funny. I _just_ came to the same conclusion.
Here is my bootlog with a backtrace:
http://ix.io/1rTR
..and the code I'm building:
https://github.com/esmil/linux/commits/hfu
I tried reverting Atish' hack, but that's not it.
/Emil
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-11-14 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 16:32 MACB in 4.20-rc2 Andreas Schwab
2018-11-14 16:32 ` Andreas Schwab
2018-11-14 21:08 ` Emil Renner Berthing [this message]
2018-11-14 21:08 ` Emil Renner Berthing
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='CANBLGcxSA0GYd+D0Ofe0mAJhGQcqdi-4jCWGWk=EUqnqK-4v1A@mail.gmail.com' \
--to=emil.renner.berthing@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=schwab@suse.de \
/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).