From: Jeroen Roovers <jer@gentoo.org>
To: Frank Scheiner <frank.scheiner@web.de>
Cc: Helge Deller <deller@gmx.de>,
debian-hppa@lists.debian.org,
linux-parisc <linux-parisc@vger.kernel.org>,
Dennis Clarke <dc@oetec.com>
Subject: Re: Ultra5 successful install - PGX64 issues
Date: Fri, 20 Apr 2018 11:24:26 +0200 [thread overview]
Message-ID: <20180420112426.3c8be653@wim.jer> (raw)
In-Reply-To: <103f23dc-0d00-2ca1-fb98-271d1e03ad90@web.de>
On Thu, 19 Apr 2018 21:29:45 +0200
Frank Scheiner <frank.scheiner@web.de> wrote:
> Afterwards I found some older notes about this machine which mention
> no issues during diskless operation with the very same configuration
> (kernel and possibly also userland), which made me wonder, if there's
> maybe an issue between the machine's built-in NIC and my used 1000
> Mbit network switch. And indeed, when connecting another 100 Mbit
> network switch in between the 712/80 and the 1000 Mbit network switch
> the issue seemed to be gone and the machine stayed accessible .
>
> 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.
Kind regards,
jer
next prev parent reply other threads:[~2018-04-20 9:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFC0-0XVQUVHmM+TT4qUK_djRGx-eV+d=5FTpGyjRR40mwAv=Q@mail.gmail.com>
[not found] ` <6a4e3490-dd3e-5832-43be-dba8211ce6e4@physik.fu-berlin.de>
[not found] ` <dd60b1eb-595d-f208-2885-c958a5ff3a4c@blastwave.org>
[not found] ` <16600fdc-6bba-1e2d-f106-560b8ea366c8@physik.fu-berlin.de>
[not found] ` <9671ecea-1353-df1c-ebbd-24a5b7d3008b@oetec.com>
[not found] ` <de1ac156-926a-c187-f15e-2c3da9251c82@web.de>
2018-04-15 8:34 ` Ultra5 successful install - PGX64 issues Helge Deller
2018-04-19 19:29 ` Frank Scheiner
2018-04-20 6:37 ` Helge Deller
2018-04-21 19:12 ` John David Anglin
2018-04-21 22:17 ` Helge Deller
2018-04-21 22:36 ` John David Anglin
2018-04-22 9:06 ` Helge Deller
2018-04-22 19:17 ` Frank Scheiner
2018-04-20 9:24 ` Jeroen Roovers [this message]
2018-04-21 0:22 ` John David Anglin
2018-04-22 19:17 ` Frank Scheiner
2018-04-22 20:10 ` John David Anglin
2018-04-23 13:38 ` Frank Scheiner
2018-04-22 19:17 ` Frank Scheiner
2018-04-08 9:52 Phillip Stevens
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=20180420112426.3c8be653@wim.jer \
--to=jer@gentoo.org \
--cc=dc@oetec.com \
--cc=debian-hppa@lists.debian.org \
--cc=deller@gmx.de \
--cc=frank.scheiner@web.de \
--cc=linux-parisc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.