From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
Salvatore Bonaccorso <carnil@debian.org>
Cc: "Sudip Mukherjee" <sudip.mukherjee@codethink.co.uk>,
linux-kernel@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-mm@kvack.org, regressions@lists.linux.dev,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
x86@kernel.org, "Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: BUG: kernel NULL pointer dereference, address: 0000000000000000
Date: Sat, 3 Jan 2026 11:33:47 +0000 [thread overview]
Message-ID: <aVj-mz8vaw53TWtX@debian> (raw)
In-Reply-To: <49cdd663-bcbd-48b4-ac38-77ce94ef0c8d@molgen.mpg.de>
On Sat, Jan 03, 2026 at 12:01:19PM +0600, Paul Menzel wrote:
> Dear Salvatore,
>
>
> Thank you for the follow-up.
>
> Am 03.01.26 um 01:59 schrieb Salvatore Bonaccorso:
>
> > On Mon, Dec 01, 2025 at 05:05:59PM +0100, Paul Menzel wrote:
>
> > > Am 01.12.25 um 14:25 schrieb Sudip Mukherjee:
> > > > On Thu, 27 Nov 2025 at 22:55, Paul Menzel wrote:
> > >
> > > > > Am 27.11.25 um 19:51 schrieb Paul Menzel:
> > > > >
> > > > > > Unfortunately, not reproducible, but starting with Linux 6.18-rc7, I got
> > > > > > the oops below *once*:
<snip>
> >
> > https://bugs.debian.org/1124075
>
> This is
>
> AMD AM5 ASUS ROG STRIX B650-A GAMING WIFI, BIOS 3067 12/10/2024
>
> > https://bugs.debian.org/1124463
>
> This is
>
> Dell Latitude E5470/0VHKV0, BIOS 1.34.3 11/20/2022
>
> > Does it make a difference to cold-boot or reboot into the system?
>
> I only did cold boots, and I am not able to reproduce it anymore, and wrote
> it off to some hardware issue – despite the system working fine otherwise.
>
> I am adding the x86 folks, and regression lists.
Thanks Salvatore for the Debian bug links.
I had been trying to reproduce this but have not seen it on my machine so far.
But looking at the traces from the Debian bugs and the trace from Paul, my best
guess is that its happening because the low level driver, parport_pc in these
cases, has not completed setting up the hardware.
When 'lp' starts registering, parport driver will check if there is any port,
if no ports are found then it will try to load the low level module.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/parport/share.c?h=v6.19-rc3#n198
As mentioned in the comment request_module() is not trying to load a real module
and it depends on the alias. Also, mentioned in the Documentation.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/admin-guide/parport.rst?h=v6.19-rc3#n45
I am not sure why the problem is seen now, but is it possible to test the
below diff please and see if that fixes the issue.
diff --git a/drivers/parport/share.c b/drivers/parport/share.c
index 427abdf3c4c4a..8f45daf7b3825 100644
--- a/drivers/parport/share.c
+++ b/drivers/parport/share.c
@@ -287,8 +287,16 @@ int __parport_register_driver(struct parport_driver *drv, struct module *owner,
*/
ret = bus_for_each_dev(&parport_bus_type, NULL, NULL,
port_detect);
- if (!ret)
+
+ /* Return if no port has been found. The driver has been
+ * registered, so whenever a new port registers
+ * attach_driver_chain() will be called which will then check
+ * all registered drivers.
+ */
+ if (!ret) {
get_lowlevel_driver();
+ return 0;
+ }
mutex_lock(®istration_lock);
if (drv->match_port)
--
Regards
Sudip
prev parent reply other threads:[~2026-01-03 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 18:51 Paul Menzel
2025-11-27 22:55 ` Paul Menzel
2025-12-01 13:25 ` Sudip Mukherjee
2025-12-01 16:05 ` Paul Menzel
2026-01-02 19:59 ` Salvatore Bonaccorso
2026-01-03 6:01 ` Paul Menzel
2026-01-03 11:33 ` Sudip Mukherjee [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=aVj-mz8vaw53TWtX@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=carnil@debian.org \
--cc=dave.hansen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@lists.linux.dev \
--cc=sudip.mukherjee@codethink.co.uk \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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