From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: tomas.winkler@intel.com, mchehab@kernel.org,
wentong.wu@intel.com, hverkuil-cisco@xs4all.nl,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: v6.8.0-rc6: mei_ace_probe / mei_vsc_probe: do not call blocking ops when !TASK_RUNNING
Date: Thu, 29 Feb 2024 07:30:33 +0000 [thread overview]
Message-ID: <ZeAymVVsI-CNj6Pc@kekkonen.localdomain> (raw)
In-Reply-To: <ZeAwhhW7DSEazs0F@shine.dominikbrodowski.net>
On Thu, Feb 29, 2024 at 08:21:42AM +0100, Dominik Brodowski wrote:
> Hi Sakari,
>
> many thanks, this patch helps. Another issue persists, though:
>
>
> $ dmesg | cut -c16- | grep -E "(mei|vsc)"
> mei_me 0000:00:16.0: enabling device (0000 -> 0002)
> mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops)
> mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops)
> intel_vsc intel_vsc: silicon stepping version is 0:2
> mei intel_vsc-92335fcf-3203-4472-af93-7b4453ac29da: deferred probe pending: (reason unknown)
> mei intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: deferred probe pending: (reason unknown)
You'll probably need the IPU bridge patches from that branch, too. Or you
can try removing the intel-ipu6 driver and modprobing it again.
>
>
> During suspend entry (s2idle), the following messages are emitted:
>
> ACPI Warning: \_SB.PC00.SPI1.SPFD.CVFD.SID: Insufficient arguments - Caller passed 0, method requires 1 (20230628/nsarguments-232)
> intel_vsc intel_vsc: silicon stepping version is 0:2
> PM: Some devices failed to suspend, or early wake event detected
> ACPI Warning: \_SB.PC00.SPI1.SPFD.CVFD.SID: Insufficient arguments - Caller passed 0, method requires 1 (20230628/nsarguments-232)
> intel_vsc intel_vsc: silicon stepping version is 0:2
> vsc-tp spi-INTC1094:00: wakeup firmware failed ret: -110
> vsc-tp spi-INTC1094:00: wakeup firmware failed ret: -110
> intel_vsc intel_vsc: wait fw ready failed: -110
> intel_vsc intel_vsc: hw_start failed ret = -110 fw status =
> intel_vsc intel_vsc: unexpected reset: dev_state = RESETTING fw status =
> ACPI Warning: \_SB.PC00.SPI1.SPFD.CVFD.SID: Insufficient arguments - Caller passed 0, method requires 1 (20230628/nsarguments-232)
> intel_vsc intel_vsc: silicon stepping version is 0:2
I haven't tried suspending. Is this while streaming or not?
--
Sakari Ailus
next prev parent reply other threads:[~2024-02-29 7:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 17:41 v6.8.0-rc6: mei_ace_probe / mei_vsc_probe: do not call blocking ops when !TASK_RUNNING Dominik Brodowski
2024-02-28 18:54 ` Sakari Ailus
2024-02-29 7:21 ` Dominik Brodowski
2024-02-29 7:30 ` Sakari Ailus [this message]
2024-02-29 16:53 ` Dominik Brodowski
2024-03-05 7:32 ` Sakari Ailus
2024-03-05 18:35 ` Dominik Brodowski
2024-03-08 23:45 ` Wu, Wentong
2024-03-09 9:20 ` Dominik Brodowski
2024-03-10 1:33 ` Wu, Wentong
2024-03-10 8:58 ` Dominik Brodowski
2024-03-23 3:50 ` Wu, Wentong
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=ZeAymVVsI-CNj6Pc@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mchehab@kernel.org \
--cc=tomas.winkler@intel.com \
--cc=wentong.wu@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;
as well as URLs for NNTP newsgroup(s).