I have found a change between 176 and 177 that looks suspicious:

diff -upr --color 176/linux-source-4.15.0/kernel/module.c 
177/linux-source-4.15.0/kernel/module.c
--- 176/linux-source-4.15.0/kernel/module.c     2022-03-29 19:39:48.000000000 
+0200
+++ 177/linux-source-4.15.0/kernel/module.c     2022-04-14 22:22:50.000000000 
+0200
@@ -3520,22 +3514,13 @@ static noinline int do_init_module(struc
 
-       /*
-        * We need to finish all async code before the module init sequence
-        * is done.  This has potential to deadlock.  For example, a newly
-        * detected block device can trigger request_module() of the
-        * default iosched from async probing task.  Once userland helper
-        * reaches here, async_synchronize_full() will wait on the async
-        * task waiting on request_module() and deadlock.
-        *
-        * This deadlock is avoided by perfomring async_synchronize_full()
-        * iff module init queued any async jobs.  This isn't a full
-        * solution as it will deadlock the same if module loading from
-        * async jobs nests more than once; however, due to the various
-        * constraints, this hack seems to be the best option for now.
-        * Please refer to the following thread for details.
-        *
-        * http://thread.gmane.org/gmane.linux.kernel/1420814
-        */
-       if (!mod->async_probe_requested && (current->flags & PF_USED_ASYNC))
+       /*
+        * We need to finish all async code before the module init sequence
+        * is done. This has potential to deadlock if synchronous module
+        * loading is requested from async (which is not allowed!).
+        *
+        * See commit 0fdff3ec6d87 ("async, kmod: warn on synchronous
+        * request_module() from async workers") for more details.
+        */
+       if (!mod->async_probe_requested)
                async_synchronize_full();

Maybe this is the deadlock we're all running into...?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1973167

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.15.0-177-generic, my machine
  completely freezes on the Ubuntu Welcome screen, i.e. right after
  switching to GUI mode. The mouse pointer is frozen, the keyboard does
  not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows
  no reaction.

  I cannot work with my machine at this point and have to hard reset it.

  Selecting advanced boot options in grub and selecting the previous
  linux kernel 4.15.0-176 makes it work again. So this bad bug was
  introduced with the 4.15.0-177 kernel release.

  I tried removing the nvidia-driver-510 package, presumably making
  Ubuntu use the "nouveau" driver, and with that, I could use the
  welcome screen and log in, but the machine still froze shortly
  afterwards.

  So maybe this is some sort of interference with my GeForce 1080
  graphics card, but it is not specific to the driver used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
  Uname: Linux 4.15.0-176-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  robert     2082 F.... pulseaudio
   /dev/snd/controlC0:  robert     2082 F.... pulseaudio
   /dev/snd/controlC2:  robert     2082 F.... pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 12 13:36:28 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-29 (2386 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Supermicro Super Server
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic 
root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-176-generic N/A
   linux-backports-modules-4.15.0-176-generic  N/A
   linux-firmware                              1.173.21
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago)
  dmi.bios.date: 09/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11SAE
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to