Re: [gentoo-user] Re: 6.1.53-gentoo-r1 kernel not booting

[Dale]

Mark Knecht wrote:
>
>
> On Sat, Oct 7, 2023 at 9:18 AM Dale  > wrote:
> 
> >
> > My first kernel, emerge prechecks warned that it wasn't and might or
> might not work.  So, I went back to a version that it claims is
> supported.  I have to say tho, the nvidia site wasn't very helpful. 
> The messages when emerging nvidia-drivers was a lot more help.  That
> said, it does load the drivers.  They are listed with lsmod.  Given
> the kernel is on my main rig, it's harder to test since I don't reboot
> often.  At some point, I may start a thread about it if a update or
> something doesn't fix it.  After all, current kernel is working just
> fine.
> >
> > I just thought it worthwhile to follow this problem since it might
> help or give clues on things to look into.  Might be related, might not.
> >
> Hi Dale,
>
> So assuming I understand your situation, you built nvidia-drivers to
> work with 
> 6.1.55 - but got no GUI. The build told you it might not work and it
> didn't.
>
> You went back to an earlier kernel and it does work.
>
> I don't think you shared what NVidia card is in this machine, and
> I don't think you shared what version of NVidia drivers worked
> with the old kernel and what version didn't work with the new kernel?
>
> - Mark


Actually, I went to the latest version in the tree, 6.5, and got the
message it likely won't work.  I went back to a version the message said
should work, 6.1.  It still doesn't work.  It may be the driver, it may
not be.  I could have left something new out in the kernel that it needs
but I didn't know it.  It could be any number of things.  At some point
when I got time to mess with it, I'm going to boot into the kernel that
doesn't work and save the log files, sddm, Xorg etc.  Then maybe it will
have a clue as to the problem. 

Until then I just want to sort of follow this to see if it might help
with my problem.  If not, oh well. 

Dale

:-)  :-) 

P. S.  My pack of drives arrived early.  Running SMART test on them
now.  :-D

Re: [gentoo-user] Re: 6.1.53-gentoo-r1 kernel not booting

[Mark Knecht]

On Sat, Oct 7, 2023 at 9:18 AM Dale  wrote:

>
> My first kernel, emerge prechecks warned that it wasn't and might or
might not work.  So, I went back to a version that it claims is supported.
I have to say tho, the nvidia site wasn't very helpful.  The messages when
emerging nvidia-drivers was a lot more help.  That said, it does load the
drivers.  They are listed with lsmod.  Given the kernel is on my main rig,
it's harder to test since I don't reboot often.  At some point, I may start
a thread about it if a update or something doesn't fix it.  After all,
current kernel is working just fine.
>
> I just thought it worthwhile to follow this problem since it might help
or give clues on things to look into.  Might be related, might not.
>
Hi Dale,

So assuming I understand your situation, you built nvidia-drivers to work
with
6.1.55 - but got no GUI. The build told you it might not work and it didn't.

You went back to an earlier kernel and it does work.

I don't think you shared what NVidia card is in this machine, and
I don't think you shared what version of NVidia drivers worked
with the old kernel and what version didn't work with the new kernel?

- Mark

Re: [gentoo-user] 6.1.53-gentoo-r1 kernel not booting

[Valmor F. de Almeida]

On 10/7/23 12:13, Valmor F. de Almeida wrote:


On 10/7/23 08:09, Peter Böhm wrote:

Am Samstag, 7. Oktober 2023, 08:28:01 CEST schrieb Valmor de Almeida:



[snip]



For me the following questions would arise:

a) How did you install the kernel 6.1.41 ? (genkernel; dist-kernel; 
manual

approach)


Sorry I described the install for the 6.1.53-gentoo-r1 kernel. The 
install for 6.1.41 was similar but I used the config file from the 
earlier kernel which is 6.1.38 to start make oldconfig.


--
Valmor



manual:
1) portage sync
2) make oldconfig in the new kernel directory for linux-6.1.53-gentoo-r1

• Mitigations for speculative execution vulnerabilities
*
Mitigations for speculative execution vulnerabilities 
(SPECULATION_MITIGATIONS) [Y/n/?] y

   Remove the kernel mapping in user mode (PAGE_TABLE_ISOLATION) [Y/n/?] y
   Avoid speculative indirect branches in kernel (RETPOLINE) [Y/n/?] y
     Enable return-thunks (RETHUNK) [Y/n/?] y
   Enable UNRET on kernel entry (CPU_UNRET_ENTRY) [Y/n/?] y
   Enable IBPB on kernel entry (CPU_IBPB_ENTRY) [Y/n/?] y
   Enable IBRS on kernel entry (CPU_IBRS_ENTRY) [Y/n/?] y

Up to here default is picked automatically; I don't have a choice.
Next, I have tried with and without accepting the NEW features.

   Mitigate speculative RAS overflow on AMD (CPU_SRSO) [Y/n/?] (NEW)
   Mitigate Straight-Line-Speculation (SLS) [N/y/?] n
   Force GDS Mitigation (GDS_FORCE_MITIGATION) [N/y/?] (NEW)

3) make menuconfig
4) make && make modules_install
5) make install
6) grub-mkconfig -o /boot/grub/grub.cfg
7) reboot


b) Did you make any kernel configuration changes in your 6.1.41 ?

no; I use what is in /boot

->  ls /boot/
config-6.1.41-gentoo grub/    System.map-6.1.41-gentoo 
vmlinuz-6.1.41-gentoo
config-6.1.53-gentoo-r1  lost+found/  System.map-6.1.53-gentoo-r1 
vmlinuz-6.1.53-gentoo-r1



c) Do you use a bootmanager ? (which ?; grub, refind ?)


I use grub-2

*  sys-boot/grub
   Latest version available: 2.06-r9
   Latest version installed: 2.06-r9



d) How did you update to 6.1.53 ? (every step)


-> revdep-rebuild --ignore
-> emerge --depclean
-> eclean distfiles
-> eclean packages
-> emerge @preserved-rebuild
-> emerge --sync
-> etc-update
-> env-update
(run a script to source profile)
-> emerge -vp --update --newuse --deep --tree --with-bdeps=y @world
check conflicts etc., fetch files, then run without -vp



To better understand your system, I would look at the output of
"parted -l" (complete),
"dmesg" (complete),
"lspci -k" and
"emerge --info"
(after you have booted 6.1.41).

To clarify all this here via the mailing list might be difficult; 
therefore I

would suggest to create a thread in our Gentoo support forum:


I will give it shot.



https://forums.gentoo.org/

(I am there also; but we have also a lot of great experts there)

If you create a thread in our forum, then please use wgetpaste for big 
files:

https://wiki.gentoo.org/wiki/Wgetpaste

Greetings,
Peter



Thanks,
--
Valmor

Re: [gentoo-user] Re: 6.1.53-gentoo-r1 kernel not booting

[Dale]

Mark Knecht wrote:
>
>
> On Sat, Oct 7, 2023 at 9:01 AM Dale  > wrote:
> >
> > Peter Böhm wrote:
> > > Am Samstag, 7. Oktober 2023, 14:42:48 CEST schrieb Nuno Silva:
> > >
> > >> I'm not sure it's fair to say it'll be easier in the webforum. [...]
> > > I think everything has its advantages and disadvantages. I
> suggested the forum
> > > because there are also some Gentoo developers active there. If a
> problem
> > > requires several different experts (because I don't know
> everything either)
> > > it's certainly faster and easier there than here. I would also like to
> > > emphasize that it was only a suggestion.
> > >
> > >> It is worth it mentioning the issue there, though, as somebody
> there who
> > >> is not reading this list might know what is going on.
> > > I am one of the moderators of the forum and therefore read every
> new thread
> > >
> > > ;-)
> >
> > I haven't been following all of this thread but I recently built a
> > kernel 6.1.55 and it boots fine but no GUI.  I made sure the symlink is
> > pointing to the right kernel, re-emerged nvidia-drivers and such but
> > still no joy.  If a thread is started there, could someone post a link
> > here?  I'd like to follow this to see if anything helps me with my
> > issue, although it is different, it may have a similar solution.
> >
> > Dale
> >
> > :-)  :-)
>
> Have you triple checked the NVidia site to make sure your
> new kernel is actually supported by the driver you're building.
>
> Sometimes they are delayed by a bit.
>
> HTH,
> Mark


My first kernel, emerge prechecks warned that it wasn't and might or
might not work.  So, I went back to a version that it claims is
supported.  I have to say tho, the nvidia site wasn't very helpful.  The
messages when emerging nvidia-drivers was a lot more help.  That said,
it does load the drivers.  They are listed with lsmod.  Given the kernel
is on my main rig, it's harder to test since I don't reboot often.  At
some point, I may start a thread about it if a update or something
doesn't fix it.  After all, current kernel is working just fine. 

I just thought it worthwhile to follow this problem since it might help
or give clues on things to look into.  Might be related, might not. 

Dale

:-)  :-) 

Re: [gentoo-user] 6.1.53-gentoo-r1 kernel not booting

[Valmor F. de Almeida]

On 10/7/23 08:09, Peter Böhm wrote:

Am Samstag, 7. Oktober 2023, 08:28:01 CEST schrieb Valmor de Almeida:


-> mount /dev/nvme0n1p4 /mnt/gentoo
mout: /mnt/gentoo: can't read superblock on /dev/nvme0n1p4.


Maybe we need to dig a little deeper. Maybe you are using LVM (or have an
encrypted root partition; or both).


No LVM, and no encryption.




-> dmesg

[snip]
nvme nvme0: controller is down; will reset: 
nvme nvme0: Does your device have a faulty power saving mode enabled?
[snip]
EXT4-fs (nvme0n1p4): unable to read superblock

I am still able to boot with the old kernel 6-1-41-gentoo.
Does this mean I may have a hardware problem with the NVMe drive?


I dont think you have a hardware problem because with 6.41 you have no
problems.


It seems like it:

->  smartctl --health /dev/nvme0n1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.41-gentoo] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED




For me the following questions would arise:

a) How did you install the kernel 6.1.41 ? (genkernel; dist-kernel; manual
approach)


manual:
1) portage sync
2) make oldconfig in the new kernel directory for linux-6.1.53-gentoo-r1

• Mitigations for speculative execution vulnerabilities
*
Mitigations for speculative execution vulnerabilities 
(SPECULATION_MITIGATIONS) [Y/n/?] y

  Remove the kernel mapping in user mode (PAGE_TABLE_ISOLATION) [Y/n/?] y
  Avoid speculative indirect branches in kernel (RETPOLINE) [Y/n/?] y
Enable return-thunks (RETHUNK) [Y/n/?] y
  Enable UNRET on kernel entry (CPU_UNRET_ENTRY) [Y/n/?] y
  Enable IBPB on kernel entry (CPU_IBPB_ENTRY) [Y/n/?] y
  Enable IBRS on kernel entry (CPU_IBRS_ENTRY) [Y/n/?] y

Up to here default is picked automatically; I don't have a choice.
Next, I have tried with and without accepting the NEW features.

  Mitigate speculative RAS overflow on AMD (CPU_SRSO) [Y/n/?] (NEW)
  Mitigate Straight-Line-Speculation (SLS) [N/y/?] n
  Force GDS Mitigation (GDS_FORCE_MITIGATION) [N/y/?] (NEW)

3) make menuconfig
4) make && make modules_install
5) make install
6) grub-mkconfig -o /boot/grub/grub.cfg
7) reboot


b) Did you make any kernel configuration changes in your 6.1.41 ?

no; I use what is in /boot

->  ls /boot/
config-6.1.41-gentoo grub/System.map-6.1.41-gentoo 
vmlinuz-6.1.41-gentoo
config-6.1.53-gentoo-r1  lost+found/  System.map-6.1.53-gentoo-r1 
vmlinuz-6.1.53-gentoo-r1



c) Do you use a bootmanager ? (which ?; grub, refind ?)


I use grub-2

*  sys-boot/grub
  Latest version available: 2.06-r9
  Latest version installed: 2.06-r9



d) How did you update to 6.1.53 ? (every step)


-> revdep-rebuild --ignore
-> emerge --depclean
-> eclean distfiles
-> eclean packages
-> emerge @preserved-rebuild
-> emerge --sync
-> etc-update
-> env-update
(run a script to source profile)
-> emerge -vp --update --newuse --deep --tree --with-bdeps=y @world
check conflicts etc., fetch files, then run without -vp



To better understand your system, I would look at the output of
"parted -l" (complete),
"dmesg" (complete),
"lspci -k" and
"emerge --info"
(after you have booted 6.1.41).

To clarify all this here via the mailing list might be difficult; therefore I
would suggest to create a thread in our Gentoo support forum:


I will give it shot.



https://forums.gentoo.org/

(I am there also; but we have also a lot of great experts there)

If you create a thread in our forum, then please use wgetpaste for big files:
https://wiki.gentoo.org/wiki/Wgetpaste

Greetings,
Peter



Thanks,
--
Valmor

Re: [gentoo-user] Re: 6.1.53-gentoo-r1 kernel not booting

[Mark Knecht]

On Sat, Oct 7, 2023 at 9:01 AM Dale  wrote:
>
> Peter Böhm wrote:
> > Am Samstag, 7. Oktober 2023, 14:42:48 CEST schrieb Nuno Silva:
> >
> >> I'm not sure it's fair to say it'll be easier in the webforum. [...]
> > I think everything has its advantages and disadvantages. I suggested
the forum
> > because there are also some Gentoo developers active there. If a problem
> > requires several different experts (because I don't know everything
either)
> > it's certainly faster and easier there than here. I would also like to
> > emphasize that it was only a suggestion.
> >
> >> It is worth it mentioning the issue there, though, as somebody there
who
> >> is not reading this list might know what is going on.
> > I am one of the moderators of the forum and therefore read every new
thread
> >
> > ;-)
>
> I haven't been following all of this thread but I recently built a
> kernel 6.1.55 and it boots fine but no GUI.  I made sure the symlink is
> pointing to the right kernel, re-emerged nvidia-drivers and such but
> still no joy.  If a thread is started there, could someone post a link
> here?  I'd like to follow this to see if anything helps me with my
> issue, although it is different, it may have a similar solution.
>
> Dale
>
> :-)  :-)

Have you triple checked the NVidia site to make sure your
new kernel is actually supported by the driver you're building.

Sometimes they are delayed by a bit.

HTH,
Mark

Re: [gentoo-user] Re: 6.1.53-gentoo-r1 kernel not booting

[Dale]

Peter Böhm wrote:
> Am Samstag, 7. Oktober 2023, 14:42:48 CEST schrieb Nuno Silva:
>
>> I'm not sure it's fair to say it'll be easier in the webforum. [...]
> I think everything has its advantages and disadvantages. I suggested the forum
> because there are also some Gentoo developers active there. If a problem
> requires several different experts (because I don't know everything either)
> it's certainly faster and easier there than here. I would also like to
> emphasize that it was only a suggestion.
>
>> It is worth it mentioning the issue there, though, as somebody there who
>> is not reading this list might know what is going on.
> I am one of the moderators of the forum and therefore read every new thread
>
> ;-)

I haven't been following all of this thread but I recently built a
kernel 6.1.55 and it boots fine but no GUI.  I made sure the symlink is
pointing to the right kernel, re-emerged nvidia-drivers and such but
still no joy.  If a thread is started there, could someone post a link
here?  I'd like to follow this to see if anything helps me with my
issue, although it is different, it may have a similar solution. 

Dale

:-)  :-) 

Re: [gentoo-user] Re: 6.1.53-gentoo-r1 kernel not booting

[Peter Böhm]

Am Samstag, 7. Oktober 2023, 14:42:48 CEST schrieb Nuno Silva:

> I'm not sure it's fair to say it'll be easier in the webforum. [...]

I think everything has its advantages and disadvantages. I suggested the forum
because there are also some Gentoo developers active there. If a problem
requires several different experts (because I don't know everything either)
it's certainly faster and easier there than here. I would also like to
emphasize that it was only a suggestion.

> It is worth it mentioning the issue there, though, as somebody there who
> is not reading this list might know what is going on.

I am one of the moderators of the forum and therefore read every new thread

;-)

[gentoo-user] Re: 6.1.53-gentoo-r1 kernel not booting

[Nuno Silva]

On 2023-10-07, Peter Böhm wrote:

> Am Samstag, 7. Oktober 2023, 08:28:01 CEST schrieb Valmor de Almeida:
>
>> -> mount /dev/nvme0n1p4 /mnt/gentoo
>> mout: /mnt/gentoo: can't read superblock on /dev/nvme0n1p4.
>
> Maybe we need to dig a little deeper. Maybe you are using LVM (or have an
> encrypted root partition; or both).
>
>> -> dmesg
>>
>> [snip]
>> nvme nvme0: controller is down; will reset: 
>> nvme nvme0: Does your device have a faulty power saving mode enabled?
>> [snip]
>> EXT4-fs (nvme0n1p4): unable to read superblock
>>
>> I am still able to boot with the old kernel 6-1-41-gentoo.
>> Does this mean I may have a hardware problem with the NVMe drive?
>
> I dont think you have a hardware problem because with 6.41 you have no
> problems.
>
> For me the following questions would arise:
>
> a) How did you install the kernel 6.1.41 ? (genkernel; dist-kernel; manual
> approach)
> b) Did you make any kernel configuration changes in your 6.1.41 ?
> c) Do you use a bootmanager ? (which ?; grub, refind ?)
> d) How did you update to 6.1.53 ? (every step)
>
> To better understand your system, I would look at the output of
> "parted -l" (complete),
> "dmesg" (complete),
> "lspci -k" and
> "emerge --info"
> (after you have booted 6.1.41).
>
> To clarify all this here via the mailing list might be difficult; therefore I
> would suggest to create a thread in our Gentoo support forum:
>
> https://forums.gentoo.org/
>
> (I am there also; but we have also a lot of great experts there)
>
> If you create a thread in our forum, then please use wgetpaste for big files:
> https://wiki.gentoo.org/wiki/Wgetpaste

I'm not sure it's fair to say it'll be easier in the webforum. For the
files, if you go the wgetpaste/"pastebin" route, you can add addresses
to e-mail messages too (although that creates the inconvenience of not
being in the message and requiring a separate fetch).

Does the gentoo webforum actually support *threads*, and not just
*topics*? A lot of webforum software packages seem to support only the
concept of topics, which would mean conversations are actually easier to
navigate via mailing list or network news (i.e. gmane).


It is worth it mentioning the issue there, though, as somebody there who
is not reading this list might know what is going on.


-- 
Nuno Silva

Re: [gentoo-user] 6.1.53-gentoo-r1 kernel not booting

[Peter Böhm]

Am Samstag, 7. Oktober 2023, 08:28:01 CEST schrieb Valmor de Almeida:

> -> mount /dev/nvme0n1p4 /mnt/gentoo
> mout: /mnt/gentoo: can't read superblock on /dev/nvme0n1p4.

Maybe we need to dig a little deeper. Maybe you are using LVM (or have an
encrypted root partition; or both).

> -> dmesg
>
> [snip]
> nvme nvme0: controller is down; will reset: 
> nvme nvme0: Does your device have a faulty power saving mode enabled?
> [snip]
> EXT4-fs (nvme0n1p4): unable to read superblock
>
> I am still able to boot with the old kernel 6-1-41-gentoo.
> Does this mean I may have a hardware problem with the NVMe drive?

I dont think you have a hardware problem because with 6.41 you have no
problems.

For me the following questions would arise:

a) How did you install the kernel 6.1.41 ? (genkernel; dist-kernel; manual
approach)
b) Did you make any kernel configuration changes in your 6.1.41 ?
c) Do you use a bootmanager ? (which ?; grub, refind ?)
d) How did you update to 6.1.53 ? (every step)

To better understand your system, I would look at the output of
"parted -l" (complete),
"dmesg" (complete),
"lspci -k" and
"emerge --info"
(after you have booted 6.1.41).

To clarify all this here via the mailing list might be difficult; therefore I
would suggest to create a thread in our Gentoo support forum:

https://forums.gentoo.org/

(I am there also; but we have also a lot of great experts there)

If you create a thread in our forum, then please use wgetpaste for big files:
https://wiki.gentoo.org/wiki/Wgetpaste

Greetings,
Peter

Re: [gentoo-user] Finally got a SSD drive to put my OS on

[Dale]

Frank Steinmetzger wrote:
> Am Sun, Apr 16, 2023 at 05:26:15PM -0500 schrieb Dale:
>
 I'm wanting to be able to boot something from the hard drive in the
 event the OS itself won't boot.  The other day I had to dig around and
 find a bootable USB stick and also found a DVD.  Ended up with the DVD
 working best.  I already have memtest on /boot.  Thing is, I very rarely
 use it.  ;-)
>>> So in the scenario you are suggesting, is grub working, giving you a
>>> boot choice screen, and your new Gentoo install is not working so
>>> you want to choose Knoppix to repair whatever is wrong with 
>>> Gentoo? 
>> Given I have a 500GB drive, I got plenty of space.  Heck, a 10GB
>> partition each is more than enough for either Knoppix or LiveGUI.  I
>> could even store info on there about drive partitions and scripts that I
>> use a lot.  Jeez, that's a idea. 
> Back in the day, I was annoyed that whenever I needed $LIVE_SYSTEM, I had to 
> reformat an entire USB stick for that. In times when you don’t even get 
> sticks below 8 GB anymore, I found it a waste of material and useful storage 
> space.
>
> And then I found ventoy: https://www.ventoy.net/
>
> It is a mini-Bootloader which you install once to a USB device, kind-of a 
> live system of its own. But when booting it, it dynamically scans the 
> content of its device and creates a new boot menu from it. So you can put 
> many ISOs on one device as simple files, delete them, upgrade them, 
> whatever, and then you can select one to boot from. Plus, the rest of the 
> stick remains usable as storage, unlike sticks that were dd’ed with an ISO.
>
> -- Grüße | Greetings | Salut | Qapla’ Please do not share anything
> from, with or about me on any social network. The four elements:
> earth, air and firewater.

I made a USB stick with Ventoy on it but hadn't had a chance to boot
anything with it until a few days ago. I currently have the following on
ONE USB stick.


CUSTOMRESCUECD-x86_64-0.12.8.iso
KNOPPIX_V9.1DVD-2021-01-25-EN.iso
livegui-amd64-20230402T170151Z.iso
memtest86.iso
systemrescuecd-x86-5.3.2.iso


I'm having trouble with the Custom Rescue one but it could be bad since
all the others work.  CRC does try to boot but then fails.  If one were
to buy a 64GB stick, one could put a LOT of images on there.  Mine is
just a 32GB and look what I got on there. 

Anyone who boots using USB on occasion should really try this thing
out.  It is as easy as Frank says.  You install the Ventoy thing on it
and then just drop the files on there.  After that, it just works.  This
thing is awesome.  Whoever came up with this thing had a really good
slide rule. This one stick replaces five doing it the old way. 

Seriously, try this thing.  Thanks to Frank for posting about it.  I'd
never heard of it. 

Dale

:-)  :-) 

P. S. I put my old Gigabyte 770T mobo back together.  My old video card
died so I had to order one of those.  It also needed a new button
battery.  Now I'm waiting on a pack of hard drives to come in.  I
ordered a pack of five 320GB drives.  For a OS, plenty big enough.  I
also ordered a pair of USB keyboards since all I have laying around is
PS/2 types now.  On my main rig, I put in another 18GB hard drive.  I'm
replacing a 16TB on one VG and plan to use the 16TB on another VG to
replace a 8GB.  That will increase the size of both VGs.  Hopefully next
month I can order the case for the new rig.  Then I get to save up for
CPU, mobo and memory.  Just a little update for those following my puter
escapades.  LOL 

Re: [gentoo-user] 6.1.53-gentoo-r1 kernel not booting

[Valmor de Almeida]

On Wed, Oct 4, 2023 at 11:36 AM Peter Böhm  wrote:
>
> Am Mittwoch, 4. Oktober 2023, 05:42:17 CEST schrieb Valmor F. de Almeida:
>
> > -> cat /proc/cpuinfo
> >
> > processor   : 0
> > vendor_id   : GenuineIntel
> > cpu family  : 6
> > model   : 158
> > model name  : Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
> > stepping: 9
> > microcode   : 0x84
>
> At the moment this is our actual microcode for Intel CPUs:
>
> sys-firmware/intel-microcode-20230808_p20230804
>
> If you look into:
>
> https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/blob/main/
> releasenote.md
>
> You will see that version f4 is actual for your CPU (dec 6-158-9 is hex
> 6-9e-9) instead your version 84.
>
> KBL-G/H/S/X/E3  B0  06-9e-09/2a 00f200f4  
>   Core
> Gen7; Xeon E3 v6
>
> What you can always do:
>
> 1. Boot with our GentooMinimalCD (so you have the new/actual microcode active
> on your CPU)
> 2. Chroot into your system (like you do with a new installation)
> 3. Re-emerge all packages with "emerge -e ..."
>
> After this, if you boot your kernel-6.1.53-r1 you should have no problem.
>
>
I tried to chroot in the installation using the latest GentooMinimalCD
(it does run the linux-6.1.53-gentoo-r1 kernel) but I am unable to
mount the root directory.

-> lsblk
[snip]
nvme0n1  259:0  0  9453.9G0  disk
|--nvme0n1p1  259.0   0   2M   0   part
|--nvme0n1p2. 259.0   0   128M   0   part
|--nvme0n1p3  259.0   01.6G   0   part
|--nvme0n1p4  259.0   0952.2G   0   part

-> swapon /dev/nvme0n1p3
-> mount /dev/nvme0n1p4 /mnt/gentoo
mout: /mnt/gentoo: can't read superblock on /dev/nvme0n1p4.
 dmesg(1) may have more information after failed mount system call.

-> dmesg

[snip]
nvme nvme0: controller is down; will reset: 
nvme nvme0: Does your device have a faulty power saving mode enabled?
[snip]
EXT4-fs (nvme0n1p4): unable to read superblock

I am still able to boot with the old kernel 6-1-41-gentoo.
Does this mean I may have a hardware problem with the NVMe drive?

Thanks for inputs.
--
Valmor