Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2485679imm; Mon, 24 Sep 2018 05:18:28 -0700 (PDT) X-Google-Smtp-Source: ACcGV61NhsZcPt2ZV/p/xbtXZILNKgOHVET2O6NOAQaCtxzvXl8Kp9wcrtBDMjZxssNanuhLlvVa X-Received: by 2002:a63:8742:: with SMTP id i63-v6mr9286060pge.27.1537791508565; Mon, 24 Sep 2018 05:18:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537791508; cv=none; d=google.com; s=arc-20160816; b=MCSaBAOe/Hgk9W1ns4ErlY5Ts6eTgRxXxb8WTsBsKBFnrjalPTeoh4NRM7JlP0NqH5 8OnUxr9dHYal/XSg0iCvJavPqdbBp3TYL5ptMqwwfEtRMhWuEGmaCmNcKuPgJAuIX0AC 0gm6MSE144jN91CJIenqs0ljQgj4WQrund2NeR3Mg5p0BqQMeiGMXrTLPD5BFyk/u3hc z1UniXwYKAtzOvAbu+CwZyRyo+fNwdhR4Wzp6f8uJq3nX32ajIWTZaVKidGJQbZbE5Va U1XLGZNF06scWii4/r0oXDzugYoOUpA9pV0ATiw2pfFJUcvQCwCeY8ivWggFyd7J3Prs A4Lw== 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=9+4GcaVDIphbUaHHIHHV4tVpVKr8jeJ2PtSuNqKsAHg=; b=ZnQikEPANY6SlqNhdjlpP25/uS3TUzl3zpZ8qTWCRd5z+KfWjpDogzMIklFzh6rwLs yaKWkxiR/B5ygOsMW0lSSTtIjQ+MX4NpK2wSoCejYdMHNfqGJTQ+9WilzEVtUYgJlK7q a9KmZPP4Hz2aatIsHbeVuynn0FC41U8FOdO2In+GgafpNfbZAFGYjS2xNub9SUlT88um CP1/vgjndGCT2/xjBxkWx+W7r38ekk3T9K8cThbWf91qsd9/N5ATR7Q1mTQqouFbzOTh aDGUhG5MlvJ+qu1uYrrKtqk+ZNvOzgVd/oVfW99tcKshFUuhfFspo/hTOJkjiyUrP5XD xpyw== 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 z61-v6si11853320plb.227.2018.09.24.05.18.13; Mon, 24 Sep 2018 05:18:28 -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 S1732367AbeIXSTF (ORCPT + 99 others); Mon, 24 Sep 2018 14:19:05 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:55878 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729919AbeIXSTE (ORCPT ); Mon, 24 Sep 2018 14:19:04 -0400 Received: from localhost (ip-213-127-77-73.ip.prioritytelecom.net [213.127.77.73]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id EE4F8109F; Mon, 24 Sep 2018 12:17:12 +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.14 086/173] mei: ignore not found client in the enumeration Date: Mon, 24 Sep 2018 13:52:00 +0200 Message-Id: <20180924113122.386351142@linuxfoundation.org> X-Mailer: git-send-email 2.19.0 In-Reply-To: <20180924113114.334025954@linuxfoundation.org> References: <20180924113114.334025954@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.14-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 @@ -1140,15 +1140,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;