Public bug reported:

After installing the linux-image-6.8.0-57-generic 6.8.0-57.59 package,
builds instantiated from our build server running "npm ci" hang
indefinitely.

On reboot, the reboot process hangs for several minutes, failing to
clean up the leftover processes:

    systemd-shutdown[1]: Waiting for process: 646484 (npm ci)
    INFO: task npm ci:646484 blocked for more than 122 seconds.
          Not tainted 6.8.0-57-generic #59-Ubuntu
    "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    (message repeats several times before system eventually reboots)

Reverting to linux-image-6.8.0-55-generic 6.8.0-55.57 does stop the
problems from occurring.


In the build system I configured npm to do "silly" level logging, and it stops 
after finishing the last download step, before proceeding to the next step, 
i.e. starting the actual build. I do not get any sort of backtrace indicating 
where the process is hanging.

** Affects: linux-meta (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  "npm ci" hangs with linux-generic 6.8.0-57.59

Status in linux-meta package in Ubuntu:
  New

Bug description:
  After installing the linux-image-6.8.0-57-generic 6.8.0-57.59 package,
  builds instantiated from our build server running "npm ci" hang
  indefinitely.

  On reboot, the reboot process hangs for several minutes, failing to
  clean up the leftover processes:

      systemd-shutdown[1]: Waiting for process: 646484 (npm ci)
      INFO: task npm ci:646484 blocked for more than 122 seconds.
            Not tainted 6.8.0-57-generic #59-Ubuntu
      "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
      (message repeats several times before system eventually reboots)

  Reverting to linux-image-6.8.0-55-generic 6.8.0-55.57 does stop the
  problems from occurring.

  
  In the build system I configured npm to do "silly" level logging, and it 
stops after finishing the last download step, before proceeding to the next 
step, i.e. starting the actual build. I do not get any sort of backtrace 
indicating where the process is hanging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2106592/+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