<div dir="ltr"><div>Yes, the problem reproduces on my system on udev 253-1. The debug log you requested is attached, I believe. <br></div><div><br></div><div>It seems the main takeaway from it is that my hwdb is missing? But I do have a `/usr/lib/udev/hwdb.bin` and a `/usr/lib/udev/hwdb.d`, and udev 250 picks up that hwdb just fine.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 27 Apr 2023 at 01:23, Michael Biebl <<a href="mailto:biebl@debian.org">biebl@debian.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Control: tags -1 + moreinfo unreproducible<br>
<br>
On Wed, 22 Feb 2023 00:55:21 +1100 Sohum Banerjea <<a href="mailto:sohum@nsb0.net" target="_blank">sohum@nsb0.net</a>> wrote:<br>
> Package: udev<br>
> Version: 252.5-2<br>
> Severity: important<br>
> <br>
> Dear Maintainer,<br>
> <br>
> Since upgrading my system to udev 252 from 250, kernel module autoloading has been broken<br>
> on my machine. I've confirmed that it's exactly a problem with the udev package via zfs<br>
> rollbacks.<br>
> <br>
> The modules themself work fine; I can run:<br>
> <br>
> sudo modprobe coretemp intel_pch_thermal thinkpad_acpi iwlwifi nvidia-current-drm modeset=1 bluetooth snd-hda-intel btusb<br>
> <br>
> and return to a functioning system.<br>
> <br>
> I do not understand how kernel module autoloading is supposed to work, and could not find<br>
> documentation that helped, so I apologise for not having further information. I'm happy to<br>
> do any further investigation that may help.<br>
<br>
Is this problem still reproducible?<br>
Can you provided a verbose debug log?<br>
<br>
<br>
</blockquote></div>