Hi Yan Jin,

In order to allow additional upstream mainline kernel developers to
examine the issue, at your earliest convenience, could you please test
the latest mainline kernel, available here -
https://kernel.ubuntu.com/mainline/?C=M;O=D?

Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily 
folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the Bug 
Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

In addition, to keep this issue relevant to upstream, please continue to
test the latest mainline kernel as it becomes available.

Lastly, it is most helpful that after testing of the latest mainline
kernel is complete, you mark this report Status Confirmed.

Thank you for your help,
John Cabaj

-- 
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/2091082

Title:
  Ubuntu 24.10 hangs into initramfs during boot-up sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 24.10 (desktop, Linux version 6.11.0-8-generic / 6.11.0-9-generic) 
hangs into initramfs during boot-up sometimes.
  reproduce steps:
  1. create a Ubuntu VM on an ESXi Host and install Ubuntu 24.10 Desktop as a 
Guest OS
  2. after the installation is finished, to add a new device or remove a 
device, then power on the VM

  expected result:
  The VM can boot up successfully

  actual result:
  The VM hangs into initramfs during boot-up sometimes (~20%)

  dmesg logs:
  ...
  [    3.706178] EXT4-fs (sda2): orphan cleanup on readonly fs
  [    3.706589] EXT4-fs error (device sda2): ext4_orphan_get:1417: comm mount: 
bad orphan inode 1068314
  [    3.706629] ext4_test_bit(bit=3353, block=4194322) = 0
  [    3.707620] EXT4-fs (sda2): recovery complete
  [    3.707629] EXT4-fs error (device sda2): ext4_mark_recovery_complete:6207: 
comm mount: Orphan file not empty on read-only fs.
  [    3.707738] EXT4-fs (sda2): mount failed
  [    3.853152] fbcon: Taking over console
  [    3.900966] Console: switching to colour frame buffer device 128x48
  [   11.496471] workqueue: drm_fb_helper_damage_work hogged CPU for >13333us 4 
times, consider switching to WQ_UNBOUND
  [   11.520471] workqueue: drm_fb_helper_damage_work hogged CPU for >13333us 5 
times, consider switching to WQ_UNBOUND
  [   11.569678] workqueue: drm_fb_helper_damage_work hogged CPU for >13333us 7 
times, consider switching to WQ_UNBOUND
  [   11.661470] workqueue: drm_fb_helper_damage_work hogged CPU for >13333us 
11 times, consider switching to WQ_UNBOUND
  [   16.590462] workqueue: drm_fb_helper_damage_work hogged CPU for >13333us 
19 times, consider switching to WQ_UNBOUND
  ....

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