From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933158AbcLINFp (ORCPT ); Fri, 9 Dec 2016 08:05:45 -0500 Received: from pb-sasl1.pobox.com ([64.147.108.66]:59148 "EHLO sasl.smtp.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932474AbcLINFn (ORCPT ); Fri, 9 Dec 2016 08:05:43 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=subject:to :references:cc:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sasl; b=kmNE1C /rV5MPPmByUJAm9fE73hem4LMteSEuH5dZScb03Q1vYvtWHWNaAtamfhuXIOvCoD Z6SUKav2PrGnxCAB8W4wtCKYlMztY8CXMdmd1gPGfx1dFqokADOJBrblqCFgLvgX osdX0TDxrQC6kXUW2DddXbmr7IxAmCKlSCPvA= Subject: Re: [PATCH net 1/2] r8152: fix the sw rx checksum is unavailable To: Hayes Wang References: <20161125095350.GA20653@kroah.com> <1816ec7e-2733-f4ba-5d30-29dbabd20aad@pobox.com> <20161125.115827.2014848246966159357.davem@davemloft.net> <0835B3720019904CB8F7AA43166CEEB201057793@RTITMBSV03.realtek.com.tw> <0835B3720019904CB8F7AA43166CEEB20105C9EE@RTITMBSV03.realtek.com.tw> Cc: "netdev@vger.kernel.org" , nic_swsd , "linux-kernel@vger.kernel.org" , "linux-usb@vger.kernel.org" From: Mark Lord Message-ID: <80471630-f5fb-1352-9c4f-dffeb129206c@pobox.com> Date: Fri, 9 Dec 2016 08:05:39 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <0835B3720019904CB8F7AA43166CEEB20105C9EE@RTITMBSV03.realtek.com.tw> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 2FB62912-BE10-11E6-B9AF-B2316462E9F6-82205200!pb-sasl1.pobox.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 16-12-08 10:23 PM, Hayes Wang wrote: > Mark Lord > > I find an issue about autosuspend, and it may result in the same > problem with you. I don't sure if this is helpful to you, because > it only occurs when enabling the autosuspend. Thanks. I am using ASIX adapters now. I did try the latest 4.9-rc8, and 4.8.12 kernels with the r8152 dongle yesterday, in hope that perhaps the many EHCI fixes from those kernels might help out. The dongle was unusable with those newer kernels. Most of the time it failed with "Get ether addr fail\n" at startup. On the occasions where it got past that point, it often failed the DHCP negotiation, but this looks more like a bug elsewhere in the kernel, possibly racing against initialization of the random number generators. Adding a 2-second sleep the the r8151 probe function made this error mostly go away. Cheers -- Mark Lord