[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Latest Stretch Cloud kernel won't boot on 64 core Azure VMs



On Mon, Oct 25, 2021 at 03:49:59PM +0000, Matthias Bach wrote:
> 
> For a specific use case we are still running Debian 9.13 on some VMs on Azure. Sadly, we had to notice that the linux-image-4.19.0-0.bpo.18-cloud-amd64 (4.19.208-1~deb9u1) version of linux-4.19 won't boot on 64 core VMs. Specifically, we tested with a variety of E64 and D64 machines. The machines will boot when using less cores. With the previous kernel version (bpo.17-cloud-amd64) this issue did not occur.
> 
> The reason I am reaching out to this mailing list is that following the error-reporting link on packages.debian.org shows me that there is no maintainer for the package, and I shouldn't report bugs to it. Thus, I am hoping that via this list I might find the right set of people that might point me in the proper direction for further investigating this issue.

Kernel packages are maintained by the kernel team, and this should
probably be opened as a bug against the appropriate version of
src:linux.  Only a subset of the kernel team is actively focusing on the
stretch LTS kernels, but the bug report will be visible to them.

> 
> I do have serial console logs of failing machines available and attached one for reference. However, I failed to find any obvious cause for the issue in it.

The log shows the kernel booting with no issues.  However, there's
nothing indicating that it ever actually mounts or pivots to its primary
root filesystem while running in the ramdisk.  It would be interesting
to see the same logs from a version that works, for comparison.

noah

> [    6.522034] Run /init as init process
> Loading, please wait...
> starting version 232
> [    6.704851] SCSI subsystem initialized
> [    6.711614] cryptd: max_cpu_qlen set to 1000
> [    6.713294] hv_vmbus: Vmbus version:4.0
> [    6.718805] hv_vmbus: Unknown GUID: c376c1c3-d276-48d2-90a9-c04748072c60
> [    6.726371] ata_piix 0000:00:07.1: Hyper-V Virtual Machine detected, ATA device ignore set
> [    6.738004] scsi host0: ata_piix
> [    6.740899] AVX2 version of gcm_enc/dec engaged.
> [    6.740946] scsi host1: ata_piix
> [    6.744242] AES CTR mode by8 optimization enabled
> [    6.746911] ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
> [    6.755022] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
> [    6.844687] hv_vmbus: registering driver hv_storvsc
> [    6.850953] scsi host2: storvsc_host_t
> [    6.860565] scsi 2:0:0:0: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
> [    6.867638] scsi host3: storvsc_host_t
> [    6.871551] hv_vmbus: registering driver hv_netvsc
> [    6.877009] scsi 3:0:1:0: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
> [    6.899646] scsi host4: storvsc_host_t
> [    6.902281] blk-mq: reduced tag depth to 10240
> [    7.264531] scsi host5: storvsc_host_t
> [    7.267798] blk-mq: reduced tag depth to 10240
> [    7.708797] hv_netvsc 000d3a22-63bc-000d-3a22-63bc000d3a22 eth0: VF slot 1 added
> [    7.725626] sd 2:0:0:0: [sda] 268435456 512-byte logical blocks: (137 GB/128 GiB)
> [    7.725777] sd 3:0:1:0: [sdb] 3355443200 512-byte logical blocks: (1.72 TB/1.56 TiB)
> [    7.730614] sd 2:0:0:0: [sda] 4096-byte physical blocks
> [    7.730744] sd 2:0:0:0: [sda] Write Protect is off
> [    7.736191] sd 3:0:1:0: [sdb] 4096-byte physical blocks
> [    7.740133] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
> [    7.743668] sd 3:0:1:0: [sdb] Write Protect is off
> [    7.754867]  sda: sda1
> [    7.759809] sd 3:0:1:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA
> [    7.760766] sd 2:0:0:0: [sda] Attached SCSI disk
> [    7.767983]  sdb: sdb1
> [    7.777602] sd 3:0:1:0: [sdb] Attached SCSI disk
> 


Reply to: