mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Jiri Kosina <jikos@kernel.org>, Even Xu <even.xu@intel.com>,
	Zhang Lixu <lixu.zhang@intel.com>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	linux-input@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Dell.Client.Kernel@dell.com
Subject: Re: hid-sensor-hub 001F:8087:0AC2.0002: timeout waiting for response from ISHTP device
Date: Thu, 9 Jun 2022 18:43:43 +0200	[thread overview]
Message-ID: <c3bbbd15-fe41-672d-0e99-bd65a5369e1e@molgen.mpg.de> (raw)
In-Reply-To: <8eb29bb9a817c88e2e9a4a76a10e99bf5504a3b5.camel@linux.intel.com>

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

      reply	other threads:[~2022-06-09 16:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 15:01 Paul Menzel
2022-05-12 23:07 ` srinivas pandruvada
2022-05-18  4:07   ` Paul Menzel
2022-05-18 15:39     ` srinivas pandruvada
2022-05-18 18:06       ` Paul Menzel
2022-05-18 18:48         ` srinivas pandruvada
2022-05-18 19:55         ` srinivas pandruvada
2022-06-09 16:43           ` Paul Menzel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c3bbbd15-fe41-672d-0e99-bd65a5369e1e@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=Dell.Client.Kernel@dell.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=even.xu@intel.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixu.zhang@intel.com \
    --cc=srinivas.pandruvada@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®