From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 55A6C13C905 for ; Thu, 23 May 2024 06:45:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716446758; cv=none; b=VPuvRGEan8ae5mDZgZBiUHeRxQJYUngiPajB9Wue0EQFF1kfeiR4Q9E0eUfpgghcCWbrrG4eb+DwrOXQO656aDs+SC8/cOfKM4XC24eRoecvkBeRu+IyFI04ochIhTgec/6FwPnBHzSa2QNLx7fV2+9JbshcLmUTrLM4ScpGVkw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716446758; c=relaxed/simple; bh=QOge68Fw0tzENrc52wcXLnWTfYP7hBED4uLrPeCT0dU=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=doG1d6ZFiLmq4I+SZAhMB6oSLVUXZbeJtyfjvbIiAQ3uNCd9dS+WKGyQPdWUjksFAtrDORYzXzdmG9aSi+pYqHhzk1OdS7wlRvCVH4ai5bOoTmf/c+I/X9O6qNfQX2avsU2KE9fclg4fihcSYrfMlyYaBvpzNKRZwLUNiMSz0oA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=jLaCiAsd; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="jLaCiAsd" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1716446756; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yDmW+1GQHZyT/E1Y2bedeCzyZRugpccl1pSBaP9FTL8=; b=jLaCiAsd9rEf9ymSJYSjQtDHW13dZehoOCAkl0qQb9dXQQGwlBZXL7YYtosCPHQl6HJGjG KYujYIPCDx9lTX20ntuuvpLciC/oRRu84aXz5+KwAHoZ/N1m87FeCLLOXI20h47r/30va0 axxgygZ2VtPkZF6zd/Ie0keJIGPIvrc= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-260-37Yvtka0PjOESfXu_snMHA-1; Thu, 23 May 2024 02:45:51 -0400 X-MC-Unique: 37Yvtka0PjOESfXu_snMHA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 79410185A78E; Thu, 23 May 2024 06:45:50 +0000 (UTC) Received: from fedora.redhat.com (unknown [10.39.192.206]) by smtp.corp.redhat.com (Postfix) with ESMTP id F13181C008BB; Thu, 23 May 2024 06:45:47 +0000 (UTC) From: Jose Ignacio Tornos Martinez To: yongqin.liu@linaro.org Cc: davem@davemloft.net, edumazet@google.com, inventor500@vivaldi.net, jtornosm@redhat.com, kuba@kernel.org, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, netdev@vger.kernel.org, pabeni@redhat.com, stable@vger.kernel.org Subject: Re: [PATCH] net: usb: ax88179_178a: fix link status when link is set to down/up Date: Thu, 23 May 2024 08:45:45 +0200 Message-ID: <20240523064546.7017-1-jtornosm@redhat.com> In-Reply-To: References: Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.7 Hello Yongqin, Again, not a lot of information from the logs, but perhaps you coud give me more information for your scenario. Could you try to execute the down interface operation, mac assignment and the up interface operation from command line? That works for me. Maybe some synchronization issue is happening in your boot operation. Could you provide more information about how/when you are doing the commented operations to try to reproduce? Best regards José Ignacio