mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: <dev@aaront.org>
Cc: "Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
	"Saarinen, Jani" <jani.saarinen@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: REGRESSION on linux-next (next-20251201)
Date: Wed, 3 Dec 2025 14:40:54 +0530	[thread overview]
Message-ID: <a22915de-fa1b-40bb-9950-8a8552466225@intel.com> (raw)

Hello Aaron,

Hope you are doing well. I am Chaitanya from the linux graphics team in 
Intel.

This mail is regarding a regression we are seeing in our CI runs[1] on
linux-next repository.

Since the version next-20251201 [2], we are seeing the following regression

`````````````````````````````````````````````````````````````````````````````````
Starting subtest: load
(i915_module_load:1280) igt_debugfs-CRITICAL: Test assertion failure 
function igt_debugfs_path, file ../lib/igt_debugfs.c:121:
(i915_module_load:1280) igt_debugfs-CRITICAL: Failed assertion: debugfs_root
(i915_module_load:1280) igt_debugfs-CRITICAL: Last errno: 2, No such 
file or directory
Subtest load failed.
`````````````````````````````````````````````````````````````````````````````````

I see some other drivers also failing to create their debugfs entries.

`````````````````````````````````````````````````````````````````````````````````
[    0.134437] pinctrl core: failed to create debugfs directory
[    3.488263] intel-lpss 0000:00:15.0: Failed to create debugfs entries
[    3.563494] intel-lpss 0000:00:15.1: Failed to create debugfs entries
[    3.631076] intel-lpss 0000:00:15.2: Failed to create debugfs entries
[    3.697366] intel-lpss 0000:00:15.3: Failed to create debugfs entries
[    3.764351] intel-lpss 0000:00:19.0: Failed to create debugfs entries
[    3.841824] intel-lpss 0000:00:19.1: Failed to create debugfs entries
[    3.909492] nvme0: failed to create debugfs directory
[    3.937845] nvme0n1: failed to create debugfs directory
[    5.636042] pinctrl core: failed to create debugfs directory for 
INTC105E:00
[  177.973628] cec: Failed to create debugfs cec dir
`````````````````````````````````````````````````````````````````````````````````
Detailed log can be found in [3].

After bisecting the tree, the following patch [4] seems to be the first 
"bad" commit

`````````````````````````````````````````````````````````````````````````````````````````````````````````
commit f278809475f6835b56de78b28dc2cc0c7e2c20a4
Author: Aaron Thompson dev@aaront.org
Date:   Thu Nov 20 10:26:33 2025 +0000

     debugfs: Remove broken no-mount mode
`````````````````````````````````````````````````````````````````````````````````````````````````````````

We also verified that if we revert the patch the issue is not seen.

Could you please check why the patch causes this regression and provide 
a fix if necessary?

Thank you.

Regards

Chaitanya

[1]
https://intel-gfx-ci.01.org/tree/linux-next/combined-alt.html?
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20251201
[3]
https://intel-gfx-ci.01.org/tree/linux-next/next-20251201/bat-arlh-2/igt@i915_module_load@load.html
[4] 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20251201&id=f278809475f6835b56de78b28dc2cc0c7e2c20a4

             reply	other threads:[~2025-12-03  9:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03  9:10 Borah, Chaitanya Kumar [this message]
2025-12-03 19:31 ` Aaron Thompson

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=a22915de-fa1b-40bb-9950-8a8552466225@intel.com \
    --to=chaitanya.kumar.borah@intel.com \
    --cc=dev@aaront.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suresh.kumar.kurmi@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®