Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: r8169 hang on 4.18
To:     Heiner Kallweit <hkallweit1@gmail.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        netdev@vger.kernel.org
References: <332fecce-3fab-1c92-1558-67a1d90d6372@odi.ch>
 <680acec6-f610-7f9d-5aa2-a03e878354d1@gmail.com>
 <4584fb8e-32f8-7375-8481-fe35c3cf693e@odi.ch>
 <9fb89abb-917a-44b6-5dff-9c4a0ed1fd6b@gmail.com>
From:   =?UTF-8?Q?Ortwin_Gl=c3=bcck?= <odi@odi.ch>
Message-ID: <98c29c26-b898-8b79-f4bd-00399d5e9f06@odi.ch>
Date:   Wed, 26 Sep 2018 17:17:17 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <9fb89abb-917a-44b6-5dff-9c4a0ed1fd6b@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


On 25.09.18 20:44, Heiner Kallweit wrote:
> Unfortunately the lspci info doesn't allow to determine the exact chip type.
> Relevant would be the syslog info as you provided it in your first mail:
> r8169 0000:07:00.0 eth4: RTL8168h/8111h, 50:9a:4c:2e:92:be, XID 54100800, IRQ 16
> Are the chips on the extension card the same as the on-board chip?

They are different: G and H versions.

[    1.696997] r8169 0000:03:00.0 eth0: RTL8168g/8111g at 0x        (ptrval), 00:0a:cd:31:60:1f, XID 
0c000800 IRQ 17
[    1.712910] r8169 0000:04:00.0 eth1: RTL8168g/8111g at 0x        (ptrval), 00:0a:cd:31:60:20, XID 
0c000800 IRQ 18
[    1.724969] r8169 0000:05:00.0 eth2: RTL8168g/8111g at 0x        (ptrval), 00:0a:cd:31:60:21, XID 
0c000800 IRQ 19
[    1.736923] r8169 0000:06:00.0 eth3: RTL8168g/8111g at 0x        (ptrval), 00:0a:cd:31:60:22, XID 
0c000800 IRQ 16
[    1.753031] r8169 0000:07:00.0 eth4: RTL8168h/8111h at 0x        (ptrval), 50:9a:4c:2e:92:be, XID 
14100800 IRQ 16

I am going to try your patch against 4.18.10 and report back!

Thanks,

Ortwin