Comment # 11 on bug 1210111 from Dmitry Markov

(In reply to Takashi Iwai from comment #10)
> Hm, is UUID changed with the recent kernels?

How did I not notice this!
indeed, the uuid in the kernel panic screenshot and the current uuid in the
running system are different.
I quote below:

> [werwolf@power] ~  
> ❯ sudo blkid | grep sd
> [sudo] пароль для root: 
> /dev/sdb2: LABEL="ost_root" UUID="23485829-5338-453f-8490-f66f0599321b" UUID_SUB="8f4b4a69-5cbb-43ce-9a30-f511c577756c" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="9da743dc-1990-45f7-a4c9-d3a03363a26e"
> /dev/sdb3: UUID="6b2e5908-4406-4cd5-8da1-bf937ab002c0" TYPE="swap" PARTUUID="37b7ccd3-b8b0-42c3-8f7d-5655da878bda"
> /dev/sda1: LABEL="ost_home" UUID="18f7ab3c-4be3-4f03-ac0d-8211542090f4" UUID_SUB="85b9980d-79dc-4ba2-809c-859bda52503b" BLOCK_SIZE="4096" TYPE="btrfs" PARTLABEL="ost_home" PARTUUID="952d3df3-00b3-4640-8dd0-dfed8ee080b9"
> /dev/sdb1: PARTUUID="cc2fabbb-5679-47ff-aaba-b8142d7d0802"

but I still do not understand how it happened, and what to do now.
Of course, I can manually rewrite the UUID from the kernel panic screen into
notepad, then fix it in fstab and cmdline, but this looks like an attempt to
treat the symptoms and not their causes.