From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S938247AbdEYLwO (ORCPT ); Thu, 25 May 2017 07:52:14 -0400 Received: from pindarots.xs4all.nl ([82.161.210.87]:58546 "EHLO pindarots.xs4all.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936230AbdEYLwK (ORCPT ); Thu, 25 May 2017 07:52:10 -0400 Subject: Re: 4.9.28: VIA velocity hang: how to find cause? To: "linux-kernel@vger.kernel.org" References: <0a888df7-ca7e-10dc-d086-fd0277530e67@xs4all.nl> From: Udo van den Heuvel Organization: hierzo Message-ID: Date: Thu, 25 May 2017 13:52:08 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 >> >