From: Udo van den Heuvel <udovdh@xs4all.nl>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 4.9.28: VIA velocity hang: how to find cause?
Date: Thu, 25 May 2017 13:52:08 +0200 [thread overview]
Message-ID: <d1c7f2ea-cfaa-218b-e08e-b67c47223f49@xs4all.nl> (raw)
In-Reply-To: <c0c37152-5238-5b71-8948-55fdd5db5015@xs4all.nl>
Hello,
Forcing the VIA Velocity interface to 1000 Mbps FDX appears to help a
bit but still the connection stops transferring data after a while.
I added some printk's and in or after velocity_tx_service it ends.
Where should I focus with my debug printk's?
It appears I can reproduce the issue by running a `find /` over ssh to
the box. So perhaps it is an interrupt related issue?
Please help find the root cause.
Kind regards,
Udo
On 24-05-17 15:04, Udo van den Heuvel wrote:
> Hello,
>
> This issue occurs on VIA Epia M910E.
> Both interfaces suffer from this.
> Setting msglvl with ethtool has no effect on the info the driver
> provides on any issues.
> So how to proceed from here?
> If this is a software issue, which I cannot determine, the driver is
> useless in its present state.
>
> Kind regards,
> Udo
>
> On 23-05-17 18:07, Udo van den Heuvel wrote:
>> Hello,
>>
>> I noticed multiple times that VIA velocity interface stop functioning
>> without reason but is revived after and `ifdown ethX; ifup ethX`.
>> No data is transferred until the `fix` is applied.
>> No errors are shown in dmesg or /var/log/messages w.r.t. the interface.
>> How to find the root cause?
>>
>> This is with kernel 4.9.28.
>>
>> Kind regards,
>> Udo
>>
>
next prev parent reply other threads:[~2017-05-25 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 16:07 4.9.28: VIA velocity hang: how to find cause? Udo van den Heuvel
2017-05-24 13:04 ` Udo van den Heuvel
2017-05-25 11:52 ` Udo van den Heuvel [this message]
2017-05-25 12:46 ` Alan Cox
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=d1c7f2ea-cfaa-218b-e08e-b67c47223f49@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox