linux-kernel - Re: hid-sensor-hub 001F:8087:0AC2.0002: timeout waiting for response from ISHTP device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <c3bbbd15-fe41-672d-0e99-bd65a5369e1e@molgen.mpg.de>
Date:   Thu, 9 Jun 2022 18:43:43 +0200
From:   Paul Menzel <pmenzel@...gen.mpg.de>
To:     Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
Cc:     Jiri Kosina <jikos@...nel.org>, Even Xu <even.xu@...el.com>,
        Zhang Lixu <lixu.zhang@...el.com>,
        Benjamin Tissoires <benjamin.tissoires@...hat.com>,
        linux-input@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        Dell.Client.Kernel@...l.com
Subject: Re: hid-sensor-hub 001F:8087:0AC2.0002: timeout waiting for response
 from ISHTP device

Dear Srinivas,


Am 18.05.22 um 21:55 schrieb srinivas pandruvada:

> Good news, is that I can get to one 9310 system.

Awesome.

> Manufacturer: Dell Inc.
> Product Name: XPS 13 9310
> 
> I had
> "
> bios_date:12/10/2020
> bios_release:1.2
> bios_vendor:Dell Inc.
> bios_version:1.2.5
> "
> 
> Didn't observe any issue with ISH after multiple suspend/resume
> 
> Update to the latest available from Dell website
> 
> BIOS Information
> 	Vendor: Dell Inc.
> 	Version: 3.6.0
> 	Release Date: 03/17/2022
> 	
> 
> Still no issue.
> 
> I am using
> 5.17.7-200.fc35.x86_64
> 
> So suggest to updated to the latest BIOS from Dell website and
> reproduce.

I had access to the system, and I have not seen that ISHTP message since 
May 16th, 2022 so with the old 2.2.0 and current 3.6.0 system firmware. 
But it also was not always present beforehand, so no idea, if something 
special has to be done (like attach a device) to trigger it.

Until the message shows up again, let’s consider the issue fixed though. 
Thank you for your time.


Kind regards,

Paul