Linux-RISC-V Archive on lore.kernel.org
 help / color / Atom feed
* MACB in 4.20-rc2
@ 2018-11-14 16:32 schwab
  2018-11-14 16:32 ` Andreas Schwab
  2018-11-14 21:08 ` emil.renner.berthing
  0 siblings, 2 replies; 4+ messages in thread
From: schwab @ 2018-11-14 16:32 UTC (permalink / raw)
  To: linux-riscv

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.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab at suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

^ permalink raw reply	[flat|nested] 4+ messages in thread

* MACB in 4.20-rc2
  2018-11-14 16:32 MACB in 4.20-rc2 schwab
@ 2018-11-14 16:32 ` Andreas Schwab
  2018-11-14 21:08 ` emil.renner.berthing
  1 sibling, 0 replies; 4+ messages in thread
From: Andreas Schwab @ 2018-11-14 16:32 UTC (permalink / raw)
  To: linux-riscv

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.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

^ permalink raw reply	[flat|nested] 4+ messages in thread

* MACB in 4.20-rc2
  2018-11-14 16:32 MACB in 4.20-rc2 schwab
  2018-11-14 16:32 ` Andreas Schwab
@ 2018-11-14 21:08 ` emil.renner.berthing
  2018-11-14 21:08   ` Emil Renner Berthing
  1 sibling, 1 reply; 4+ messages in thread
From: emil.renner.berthing @ 2018-11-14 21:08 UTC (permalink / raw)
  To: linux-riscv

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: MACB in 4.20-rc2
  2018-11-14 21:08 ` emil.renner.berthing
@ 2018-11-14 21:08   ` Emil Renner Berthing
  0 siblings, 0 replies; 4+ messages in thread
From: Emil Renner Berthing @ 2018-11-14 21:08 UTC (permalink / raw)
  To: schwab; +Cc: linux-riscv

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-11-14 16:32 MACB in 4.20-rc2 schwab
2018-11-14 16:32 ` Andreas Schwab
2018-11-14 21:08 ` emil.renner.berthing
2018-11-14 21:08   ` Emil Renner Berthing

Linux-RISC-V Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-riscv/0 linux-riscv/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-riscv linux-riscv/ https://lore.kernel.org/linux-riscv \
		linux-riscv@lists.infradead.org infradead-linux-riscv@archiver.kernel.org
	public-inbox-index linux-riscv


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.infradead.lists.linux-riscv


AGPL code for this site: git clone https://public-inbox.org/ public-inbox