Bug 1219691

Summary: [Hyper-V bare metal][sles15sp6][Build 53.1] Installation Hangs at 'starting udev.... ok' Step
Product: [openSUSE] PUBLIC SUSE Linux Enterprise Server 15 SP6 Reporter: Roy Cai <roy.cai>
Component: KernelAssignee: Kernel Bugs <kernel-bugs>
Status: VERIFIED FIXED QA Contact:
Severity: Normal    
Priority: P5 - None CC: qe-virt, tiwai
Version: unspecified   
Target Milestone: ---   
Hardware: Hyper-V   
OS: Other   
URL: http://openqa.oqa.prg2.suse.org/tests/13456883/modules/welcome/steps/4
Whiteboard:
Found By: openQA Services Priority:
Business Priority: Blocker: Yes
Marketing QA Status: --- IT Deployment: ---
Attachments: installation hangs here
Call trace log when hanging.
boot log

Description Roy Cai 2024-02-08 01:09:53 UTC
Created attachment 872561 [details]
installation hangs here

[Hyper-V baremetal][sles15sp6][Build 53.1] openQA test fails in welcome

## Observation

openQA test in scenario sle-15-SP6-Online-x86_64-default_install_svirt@svirt-hyperv fails in
[welcome](http://openqa.oqa.prg2.suse.org/tests/13456883/modules/welcome/steps/4)

## Reproducible

Fails since (at least) Build [53.1](http://openqa.oqa.prg2.suse.org/tests/13456883) (current job)

## Reproduction Steps
1. Obtain a Windows Server 2016/2019/2022 Bare Metal.
2. Create a virtual machine (G1 or G2) by booting from the DVD ISO SLE-15-SP6-Online-x86_64-Build53.1-Media1.iso.
3. Proceed with the installation process by selecting the default options, just click 'installation'.
4. The installation hangs on the 'starting udev.... ok' step, preventing progression to the next step.
5. Call trace log appears in the serial output.
--------
[   22.404377][  T105] Call Trace:
[   22.414818][  T105]  <TASK>
[   22.423976][  T105]  ? __die_body+0x1a/0x60
[   22.438039][  T105]  ? die_addr+0x38/0x60
[   22.450875][  T105]  ? exc_general_protection+0x154/0x380
[   22.468000][  T105]  ? asm_exc_general_protection+0x22/0x30
[   22.485864][  T105]  ? drm_atomic_helper_dirtyfb+0x9c/0x280
[   22.503988][  T105]  ? __kmem_cache_alloc_node+0x13b/0x300
[   22.523349][  T105]  ? drm_atomic_helper_dirtyfb+0x9c/0x280
[   22.542651][  T105]  ? drm_atomic_state_init+0x5c/0xc0
[   22.560245][  T105]  ? drm_atomic_helper_dirtyfb+0x9c/0x280
[   22.578370][  T105]  __kmalloc+0x4d/0x130
[   22.591361][  T105]  drm_atomic_helper_dirtyfb+0x9c/0x280
[   22.610074][  T105]  drm_fbdev_generic_helper_fb_dirty+0x223/0x2e0
[   22.629284][  T105]  drm_fb_helper_damage_work+0x83/0x160
[   22.646946][  T105]  process_one_work+0x223/0x440
[   22.661681][  T105]  ? __pfx_worker_thread+0x10/0x10
[   22.677145][  T105]  worker_thread+0x2a/0x3b0
[   22.690953][  T105]  ? __pfx_worker_thread+0x10/0x10
[   22.706664][  T105]  kthread+0xdf/0x120
[   22.719450][  T105]  ? __pfx_kthread+0x10/0x10
[   22.733974][  T105]  ret_from_fork+0x29/0x50
[   22.751387][  T105]  </TASK>
[   22.764300][  T105] Modules linked in: nls_cp437(+) af_packet sg st iscsi_ibft iscsi_boot_sysfs sunrpc sd_mod t10_pi crc64_rocksoft_generic intel_uncore_frequency_common isst_if_mbox_msr isst_if_common crc32_pclmul crc64_rocksoft crc64 crc32c_intel ghash_clmulni_intel sha512_ssse3 sr_mod sha256_ssse3 cdrom joydev hv_netvsc(X) hid_generic ata_generic pata_acpi sha1_ssse3 hv_storvsc(X) scsi_transport_fc hv_utils(X) hid_hyperv(X) hyperv_keyboard(X) hv_balloon(X) hyperv_drm aesni_intel ata_piix crypto_simd cryptd pcspkr libata serio_raw hv_vmbus(X) i2c_piix4 floppy button scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod edd squashfs loop ext4 crc16 mbcache jbd2 zram
[   22.977441][  T105] Supported: Yes, External
[   22.993767][  T105] ---[ end trace 0000000000000000 ]---
--------
Please refer attachment.


## Expected result

Last good: [50.2](http://openqa.oqa.prg2.suse.org/tests/13442068) (or more recent)

## Further details

Manual testing has been conducted, and the issue persists, with the installation hanging at the same step as observed in the automated test.

## Workaround
No
Comment 1 Roy Cai 2024-02-08 01:10:46 UTC
Created attachment 872562 [details]
Call trace log when hanging.
Comment 2 Takashi Iwai 2024-02-09 11:21:26 UTC
Likely the result of the memory corruption (bsc#1219692).
The next update should include the fix.
Comment 3 Takashi Iwai 2024-02-13 13:59:02 UTC
The memory corruption bug was fixed in the latest kernel, so I close for now.
Feel free to reopen if the problem still persists.
Comment 4 Roy Cai 2024-02-17 03:13:35 UTC
Created attachment 872813 [details]
boot log
Comment 5 Roy Cai 2024-02-17 03:15:12 UTC
Verified.