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: Wed, 28 Feb 2024 18:54:14 +0000 [thread overview]
Message-ID: <Zd-BVmoFOiCxA632@kekkonen.localdomain> (raw)
In-Reply-To: <Zd9wUv1zSJ59WS8i@shine.dominikbrodowski.net>
Hi Dominik,
On Wed, Feb 28, 2024 at 06:41:38PM +0100, Dominik Brodowski wrote:
> Hi,
>
> thanks for your work getting the Intel IPU6 camera system - such as found
> within my Dell Inc. XPS 9315 - to work with an upstream kernel. Much
> appreciated!
>
> On Linux 6.8.0-rc6+ (as of this morning, HEAD is at cf1182944c7c), though,
> I get the following warning during boot with everything built into the
> kernel:
>
> ------------[ cut here ]------------
> do not call blocking ops when !TASK_RUNNING; state=2 set at [<000000003688dc79>] prepare_to_wait_event+0x54/0x1a0
> WARNING: CPU: 5 PID: 122 at kernel/sched/core.c:10099 __might_sleep+0x59/0x60
> Modules linked in:
> CPU: 5 PID: 122 Comm: kworker/u24:3 Tainted: G T 6.8.0-rc6+ #2
> Hardware name: Dell Inc. XPS 9315/00KRKP, BIOS 1.1.3 05/11/2022
> Workqueue: events_unbound deferred_probe_work_func
> RIP: 0010:__might_sleep+0x59/0x60
The issue should be fixed by this patch:
<URL:https://git.linuxtv.org/sailus/media_tree.git/commit/?h=ipu6&id=e2dc122949ce2efd05910c0c78617534c3258158>.
I've posted to the LKML, too, so hopefully we have it merged soon.
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2024-02-28 18:54 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 [this message]
2024-02-29 7:21 ` Dominik Brodowski
2024-02-29 7:30 ` Sakari Ailus
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=Zd-BVmoFOiCxA632@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).