Comment # 31 on bug 1187701 from Mathew McBride

Apologies, I got distracted on other projects.

This is still a problem, thankfully it does not exist with the newer kernel on
Leap 15.4.

I have even attempted to bisect this but can't find any obvious cause. I think
it came with this merge:

commit 691336b369202a4fd8d75a0a255a88ef592f00d9
Merge: 30270eafb6d5 2c269e3edad3
Author: Denis Kirjanov <dkirjanov@suse.com>
Date:   Fri May 21 15:57:15 2021 +0300

    Merge branch 'users/dkirjanov/SLE15-SP3-UPDATE/for-next' into
SLE15-SP3-UPDATE

    Merge SLE15-SP2 into SLE15-SP3-UPDATE with a kabi fix from Michal Suchanek

    suse-commit: d970db8f5beecbc55b223922ed9f3d6dbb885814

A kernel compiled on the commit immediately prior (according to Github) -
d4cb7424a2afeb740fd05840619e26de413aed45  "lpfc: Decouple port_template and
vport_template (bsc#185032)" works.

> Might this be an issue with the DTB? Can you please try to boot the broken kernel with a DTB from the good kernel and see whether this makes a difference?

Note that I've grabbed the dmesg's/kernel logs from several different systems,
depending on what was in front of me at the time.

On the Ten64 the DTB is built into the flash and passed to the kernel via EFI,
so the DTB is from a 'good kernel' in that respect. I can try producing a DTB
from the Leap/SLE kernel source if needed.