Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2471328imm; Mon, 24 Sep 2018 05:05:10 -0700 (PDT) X-Google-Smtp-Source: ACcGV60Q17W4sj0cNTOdhIr2YiG20ElXeqnVmSsaPvhgpiL2mqLfXgHfREN0Rx98qxMw5GEA24Wg X-Received: by 2002:a17:902:8a90:: with SMTP id p16-v6mr10573432plo.106.1537790710770; Mon, 24 Sep 2018 05:05:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537790710; cv=none; d=google.com; s=arc-20160816; b=HdtXTGrFH/uw0ikatnQ5PC5/RJyDGa1Q4AItRmZy+zmYrLjuM+B647iHFZQpFPA+UE 9xOLUzcitLzR/D+o+wgwtcWV74uGtfrwcZqFazIhBzT8F0rIPzWbItOQe1Eqwnk06B4k Hwy6NgnBY7AviYpRBsEOC9ke62NLN4HvpI9W56Iq2Hng/r6dyjMVIypU0XAD944usOPj /XqHWmMqFq/MjPvxxUr7JDYATWBTPBbVesBB7ipTWP/PNfR/7GOSx5V00tHncUSxD47u si4TxJb+wUXaDHlfLeMIYFHGqHL0E/0m8vQyUZFgzicrOiNI5KRH/QjE0UbFr4MY1fgM El/w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from; bh=tJQiImt5XHXQ0JXbnfiayJ+jvaj2bJbHNOLzYA/vzAU=; b=m1A1tua7FLAg276GQKdnE6Uv1Giraz8ldB/CGXHg/pLSmcAQ5YUOSgA5XIxGnl858N 5ZG39pmW4z+ZBMjROiN3qKUvDdX6eZeXrfo9e9DwCJHUnmw8eJK0Pwme2dhrTLLPS6DO PV4qg35Er89Uf0++KUJew81pdb0S7SIEux+pWfQRaTJ3n4hLYBdxm4aLU7QCAGtFjufJ nn0fL/93Wd4iUQywHZOjYptZ6BdZDMr1pxKQlNDzS9vb3XQnbI07gRv/VGchw3HKej1P mn0cD2bOrJ/0rRISYrD2/0TGppLmS96Ro572y3PYzIHe66c6TqUQ+UVwIbt7yrI5KJzb 29nA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a11-v6si12857770plp.199.2018.09.24.05.04.55; Mon, 24 Sep 2018 05:05:10 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730928AbeIXSE0 (ORCPT + 99 others); Mon, 24 Sep 2018 14:04:26 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:53748 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729639AbeIXSEZ (ORCPT ); Mon, 24 Sep 2018 14:04:25 -0400 Received: from localhost (ip-213-127-77-73.ip.prioritytelecom.net [213.127.77.73]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id 72D2D106D; Mon, 24 Sep 2018 12:02:38 +0000 (UTC) From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Heiner Kallweit , Alexander Usyskin , Tomas Winkler Subject: [PATCH 4.9 055/111] mei: ignore not found client in the enumeration Date: Mon, 24 Sep 2018 13:52:22 +0200 Message-Id: <20180924113110.406252928@linuxfoundation.org> X-Mailer: git-send-email 2.19.0 In-Reply-To: <20180924113103.337261320@linuxfoundation.org> References: <20180924113103.337261320@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: Alexander Usyskin commit 8d2d8935d30cc2acc57a3196dc10dfa8d5cbcdab upstream. Some of the ME clients are available only for BIOS operation and are removed during hand off to an OS. However the removal is not instant. A client may be visible on the client list when the mei driver requests for enumeration, while the subsequent request for properties will be answered with client not found error value. The default behavior for an error is to perform client reset while this error is harmless and the link reset should be prevented. This issue started to be visible due to suspend/resume timing changes. Currently reported only on the Haswell based system. Fixes: [33.564957] mei_me 0000:00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND [33.564978] mei_me 0000:00:16.0: mei_irq_read_handler ret = -71. [33.565270] mei_me 0000:00:16.0: unexpected reset: dev_state = INIT_CLIENTS fw status = 1E000255 60002306 00000200 00004401 00000000 00000010 Cc: Reported-by: Heiner Kallweit Signed-off-by: Alexander Usyskin Signed-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman --- drivers/misc/mei/hbm.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) --- a/drivers/misc/mei/hbm.c +++ b/drivers/misc/mei/hbm.c @@ -1137,15 +1137,18 @@ int mei_hbm_dispatch(struct mei_device * props_res = (struct hbm_props_response *)mei_msg; - if (props_res->status) { + if (props_res->status == MEI_HBMS_CLIENT_NOT_FOUND) { + dev_dbg(dev->dev, "hbm: properties response: %d CLIENT_NOT_FOUND\n", + props_res->me_addr); + } else if (props_res->status) { dev_err(dev->dev, "hbm: properties response: wrong status = %d %s\n", props_res->status, mei_hbm_status_str(props_res->status)); return -EPROTO; + } else { + mei_hbm_me_cl_add(dev, props_res); } - mei_hbm_me_cl_add(dev, props_res); - /* request property for the next client */ if (mei_hbm_prop_req(dev, props_res->me_addr + 1)) return -EIO;