On 2018-04-20 5:24 AM, Jeroen Roovers wrote:
But later this week I retried the 712/80 with the current Linux
kernel (4.15.x) and Debian userland and the issue hit me again,
although much later and despite the 100 Mbit network switch in
between. Looking at it I could see that the collision indicator was
active on the switch for the port used by the 712/80. I then
configured a singular port of the 1000 Mbit network switch to 10 Mbit
full duplex and attached the 712/80 to it. And then the issue again
seemed to be gone. But trying to install a package or updating the
package cache again quickly triggered it.
You could try setting the internal NIC to half-duplex, or perhaps use a
(passive) 10BASE-T hub instead of a switch if you cannot configure that
internally, on the kernel command line, or doing it in userland is too
late.
From the manual, it seems the 10BASE-T port is half duplex (CSMA/CD).
The MAU
interface is definitely half duplex and the word duplex is not mentioned
in the manual.
The 10BASE-T port probably doesn't support auto negotiation, so you will
need to manually
set the switch port to 10BASE-T half duplex if it doesn't automatically
configure to this mode
when auto negotiation fails.
Some switches support a half-duplex back pressure form of flow control.
Setting the switch port is probably easier than finding a passive 10BASE
hub.
Dave
--
John David Anglin dave.anglin@xxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
