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

[Valmor F. de Almeida]

On 10/8/23 06:34, Neil Bothwick wrote:

On Sat, 7 Oct 2023 12:13:58 -0400, Valmor F. de Almeida wrote:


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.


Those are settings you already have in your existing confid, shown to
give context to the following NEW settings.

You can change them, but with make config, not oldconfig.




After some distractions...
For the record. This problem solved itself with the 6.1.57-gentoo 
kernel. Just used the config from 6.1.41-gentoo in make oldconfig.

Thanks for the help.
--
Valmor

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

[Neil Bothwick]

On Sat, 7 Oct 2023 12:13:58 -0400, Valmor F. de Almeida wrote:

> 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.

Those are settings you already have in your existing confid, shown to
give context to the following NEW settings.

You can change them, but with make config, not oldconfig.


-- 
Neil Bothwick

Love is grand. Divorce is a few grand more.


pgpqMoU9497s1.pgp
Description: OpenPGP digital signature

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] 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] 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] 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

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

[Peter Böhm]

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.

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

[Neil Bothwick]

On Tue, 3 Oct 2023 23:42:17 -0400, Valmor F. de Almeida wrote:

> There may have been a microcode emerge from dependencies; I don't
> emerge directly. I do agree with you: if I try to recompile the working 
> kernel it will not boot. However I am not willing to try just right now 
> and having to troubleshoot a broken system.

Microcode is usually applied as an initramfs, and I think you said you
are not using any.

If you set LOCALVERSION in the kernel config, your existing kernel will
be installed with a new name, so you'll still have the working kernel to
fall back on.


-- 
Neil Bothwick

Taglines are like cars - You get a good one, then someone nicks it.


pgpxE0Vt3LD_M.pgp
Description: OpenPGP digital signature

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

[Valmor F. de Almeida]

On 10/2/23 05:39, Peter Böhm wrote:

If your system is working with your old kernel I dont think it could be a
hardware problem. If your kernel config is the same then I dont think it is a
problem with the kernel.

My questions would be:

Which CPU do you use ? Have you emerged a new microcode for CPU ?

Example: Intel has disabled avx in some CPUs via microcode update. Now some
applications may throw an illegal instruction ... and your problem description
look like that only some programs have a problem. You could test it by
compiling your old kernel again ... you should have then the same problem with
it (of course you backup your old kernel before).

Regards,
Peter



The config file is not the same but I have played with what has changed 
and I don't seem to be able to fix the problem; no boot.


-> 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
cpu MHz : 3680.490
cache size  : 6144 KB

[snip]
There are 8 cores.

There may have been a microcode emerge from dependencies; I don't emerge 
 directly. I do agree with you: if I try to recompile the working 
kernel it will not boot. However I am not willing to try just right now 
and having to troubleshoot a broken system.

Thanks,
--
Valmor

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

[Valmor F. de Almeida]

On 10/2/23 04:44, Lee wrote:

I found this:

https://www.reddit.com/r/Gentoo/comments/168qrbx/gentoosources_6146_kernel_reports_io_error/
 



Lee 


This is probably it.
Thanks.
--
Valmor


On Mon, Oct 2, 2023, 12:14 AM Valmor F. de Almeida > wrote:




On 10/1/23 20:29, Håkon Alstadheim wrote:
 >
 > Den 01.10.2023 21:31, skrev Frank Steinmetzger:
 >> Am Sat, Sep 30, 2023 at 11:25:46PM +0200 schrieb Håkon Alstadheim:
 >>> Den 30.09.2023 22:57, skrev Valmor F. de Almeida:
  Hello,
 
  For a while now (3 weeks or so) I have been upgrading the
linux kernel
  on a Dell XPS laptop starting from 6.1.41-gentoo (which is my
current
  working kernel) to 6.1.53-gentoo-r1. No kernel I have built
since is
  able to boot. I have been following the same method for many
years:
  make
  oldconfig, etc...
 
  The booting error starts at:
 
  [snip]
 
  * INIT: Entering runlevel: 3
  [snip]
  * Starting cronie ...
  * Starting DHCP Client Daemon ...
  * Starting laptop_mode ...
  * Mounting network filesystems ...
  /etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output
error
  /lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
  INIT:
  INIT: cannot execute "/sbin/agetty"
  INIT: cannot execute "/sbin/agetty"
  INIT: cannot execute "/sbin/agetty"
 
 
 >>> Can you show /etc/fstab and the console-log for the entire boot?
 >>> Seems /sbin
 >>> is not readable. You sure you have the kernel modules loaded?
Are you
 >>> using
 >>> an initramfs? If so, does that build without errors ?
 >> The input/output error – to me – indicates a hardware problem.
When you
 >> mounted the FS by hand, can you read ewend? For instance with
md5sum.
 >>
 > except it boots ok with older kernels. When you've eliminated the
 > impossible, whatever remains, however improbable has to be a kernel
 > config change (missing or erroneous and unintended) , or
 > initramfs failing to build/install correctly. Check error output
from
 > your kernel build.
 >

Right it boots with 6.1.41. I started again from the config of 6.1.41
and unset SRSO:

->  diff linux/.config /boot/config-6.1.41-gentoo
3c3
< # Linux/x86 6.1.53-gentoo-r1 Kernel Configuration
---
  > # Linux/x86 6.1.41-gentoo Kernel Configuration
5c5
< CONFIG_CC_VERSION_TEXT="gcc (Gentoo 13.2.1_p20230826 p7) 13.2.1
20230826"
---
  > CONFIG_CC_VERSION_TEXT="gcc (Gentoo 12.3.1_p20230526 p2) 12.3.1
20230526"
7c7
< CONFIG_GCC_VERSION=130201
---
  > CONFIG_GCC_VERSION=120301
455d454
< # CONFIG_CPU_SRSO is not set
457d455
< # CONFIG_GDS_FORCE_MITIGATION is not set
646d643
< CONFIG_ARCH_HAS_CPU_FINALIZE_INIT=y
3136d3132
< CONFIG_VIDEO_V4L2_SUBDEV_API=y
3139,3140d3134
< CONFIG_V4L2_FWNODE=m
< CONFIG_V4L2_ASYNC=m
3236c3230,3233
< CONFIG_VIDEO_CAMERA_SENSOR=y
---
  >
  > #
  > # Camera sensor devices
  > #
3295a3293
  > # end of Camera sensor devices

Still no luck; kernel build has no errors. Boot hangs.
Thanks for the replies. Maybe 6.2 will not have this problem for my
system.
--
Valmor

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

[Peter Böhm]

If your system is working with your old kernel I dont think it could be a
hardware problem. If your kernel config is the same then I dont think it is a
problem with the kernel.

My questions would be:

Which CPU do you use ? Have you emerged a new microcode for CPU ?

Example: Intel has disabled avx in some CPUs via microcode update. Now some
applications may throw an illegal instruction ... and your problem description
look like that only some programs have a problem. You could test it by
compiling your old kernel again ... you should have then the same problem with
it (of course you backup your old kernel before).

Regards,
Peter

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

[Lee]

I found this:

https://www.reddit.com/r/Gentoo/comments/168qrbx/gentoosources_6146_kernel_reports_io_error/


Lee 

On Mon, Oct 2, 2023, 12:14 AM Valmor F. de Almeida 
wrote:

>
>
> On 10/1/23 20:29, Håkon Alstadheim wrote:
> >
> > Den 01.10.2023 21:31, skrev Frank Steinmetzger:
> >> Am Sat, Sep 30, 2023 at 11:25:46PM +0200 schrieb Håkon Alstadheim:
> >>> Den 30.09.2023 22:57, skrev Valmor F. de Almeida:
>  Hello,
> 
>  For a while now (3 weeks or so) I have been upgrading the linux kernel
>  on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
>  working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
>  able to boot. I have been following the same method for many years:
>  make
>  oldconfig, etc...
> 
>  The booting error starts at:
> 
>  [snip]
> 
>  * INIT: Entering runlevel: 3
>  [snip]
>  * Starting cronie ...
>  * Starting DHCP Client Daemon ...
>  * Starting laptop_mode ...
>  * Mounting network filesystems ...
>  /etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
>  /lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
>  INIT:
>  INIT: cannot execute "/sbin/agetty"
>  INIT: cannot execute "/sbin/agetty"
>  INIT: cannot execute "/sbin/agetty"
> 
> 
> >>> Can you show /etc/fstab and the console-log for the entire boot?
> >>> Seems /sbin
> >>> is not readable. You sure you have the kernel modules loaded? Are you
> >>> using
> >>> an initramfs? If so, does that build without errors ?
> >> The input/output error – to me – indicates a hardware problem. When you
> >> mounted the FS by hand, can you read ewend? For instance with md5sum.
> >>
> > except it boots ok with older kernels. When you've eliminated the
> > impossible, whatever remains, however improbable has to be a kernel
> > config change (missing or erroneous and unintended) , or
> > initramfs failing to build/install correctly. Check error output from
> > your kernel build.
> >
>
> Right it boots with 6.1.41. I started again from the config of 6.1.41
> and unset SRSO:
>
> ->  diff linux/.config /boot/config-6.1.41-gentoo
> 3c3
> < # Linux/x86 6.1.53-gentoo-r1 Kernel Configuration
> ---
>  > # Linux/x86 6.1.41-gentoo Kernel Configuration
> 5c5
> < CONFIG_CC_VERSION_TEXT="gcc (Gentoo 13.2.1_p20230826 p7) 13.2.1 20230826"
> ---
>  > CONFIG_CC_VERSION_TEXT="gcc (Gentoo 12.3.1_p20230526 p2) 12.3.1
> 20230526"
> 7c7
> < CONFIG_GCC_VERSION=130201
> ---
>  > CONFIG_GCC_VERSION=120301
> 455d454
> < # CONFIG_CPU_SRSO is not set
> 457d455
> < # CONFIG_GDS_FORCE_MITIGATION is not set
> 646d643
> < CONFIG_ARCH_HAS_CPU_FINALIZE_INIT=y
> 3136d3132
> < CONFIG_VIDEO_V4L2_SUBDEV_API=y
> 3139,3140d3134
> < CONFIG_V4L2_FWNODE=m
> < CONFIG_V4L2_ASYNC=m
> 3236c3230,3233
> < CONFIG_VIDEO_CAMERA_SENSOR=y
> ---
>  >
>  > #
>  > # Camera sensor devices
>  > #
> 3295a3293
>  > # end of Camera sensor devices
>
> Still no luck; kernel build has no errors. Boot hangs.
> Thanks for the replies. Maybe 6.2 will not have this problem for my system.
> --
> Valmor
>
>

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

[Valmor F. de Almeida]

On 10/1/23 20:29, Håkon Alstadheim wrote:


Den 01.10.2023 21:31, skrev Frank Steinmetzger:

Am Sat, Sep 30, 2023 at 11:25:46PM +0200 schrieb Håkon Alstadheim:

Den 30.09.2023 22:57, skrev Valmor F. de Almeida:

Hello,

For a while now (3 weeks or so) I have been upgrading the linux kernel
on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
able to boot. I have been following the same method for many years: 
make

oldconfig, etc...

The booting error starts at:

[snip]

* INIT: Entering runlevel: 3
[snip]
* Starting cronie ...
* Starting DHCP Client Daemon ...
* Starting laptop_mode ...
* Mounting network filesystems ...
/etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
/lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
INIT:
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"


Can you show /etc/fstab and the console-log for the entire boot? 
Seems /sbin
is not readable. You sure you have the kernel modules loaded? Are you 
using

an initramfs? If so, does that build without errors ?

The input/output error – to me – indicates a hardware problem. When you
mounted the FS by hand, can you read ewend? For instance with md5sum.

except it boots ok with older kernels. When you've eliminated the 
impossible, whatever remains, however improbable has to be a kernel 
config change (missing or erroneous and unintended) , or 
initramfs failing to build/install correctly. Check error output from 
your kernel build.




Right it boots with 6.1.41. I started again from the config of 6.1.41 
and unset SRSO:


->  diff linux/.config /boot/config-6.1.41-gentoo
3c3
< # Linux/x86 6.1.53-gentoo-r1 Kernel Configuration
---
> # Linux/x86 6.1.41-gentoo Kernel Configuration
5c5
< CONFIG_CC_VERSION_TEXT="gcc (Gentoo 13.2.1_p20230826 p7) 13.2.1 20230826"
---
> CONFIG_CC_VERSION_TEXT="gcc (Gentoo 12.3.1_p20230526 p2) 12.3.1 20230526"
7c7
< CONFIG_GCC_VERSION=130201
---
> CONFIG_GCC_VERSION=120301
455d454
< # CONFIG_CPU_SRSO is not set
457d455
< # CONFIG_GDS_FORCE_MITIGATION is not set
646d643
< CONFIG_ARCH_HAS_CPU_FINALIZE_INIT=y
3136d3132
< CONFIG_VIDEO_V4L2_SUBDEV_API=y
3139,3140d3134
< CONFIG_V4L2_FWNODE=m
< CONFIG_V4L2_ASYNC=m
3236c3230,3233
< CONFIG_VIDEO_CAMERA_SENSOR=y
---
>
> #
> # Camera sensor devices
> #
3295a3293
> # end of Camera sensor devices

Still no luck; kernel build has no errors. Boot hangs.
Thanks for the replies. Maybe 6.2 will not have this problem for my system.
--
Valmor

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

[Lee]

I found this:

https://www.reddit.com/r/Gentoo/comments/168qrbx/gentoosources_6146_kernel_reports_io_error/


Lee 

On Sun, Oct 1, 2023, 7:56 PM Håkon Alstadheim 
wrote:

>
> Den 01.10.2023 21:31, skrev Frank Steinmetzger:
> > Am Sat, Sep 30, 2023 at 11:25:46PM +0200 schrieb Håkon Alstadheim:
> >> Den 30.09.2023 22:57, skrev Valmor F. de Almeida:
> >>> Hello,
> >>>
> >>> For a while now (3 weeks or so) I have been upgrading the linux kernel
> >>> on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
> >>> working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
> >>> able to boot. I have been following the same method for many years:
> make
> >>> oldconfig, etc...
> >>>
> >>> The booting error starts at:
> >>>
> >>> [snip]
> >>>
> >>> * INIT: Entering runlevel: 3
> >>> [snip]
> >>> * Starting cronie ...
> >>> * Starting DHCP Client Daemon ...
> >>> * Starting laptop_mode ...
> >>> * Mounting network filesystems ...
> >>> /etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
> >>> /lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
> >>> INIT:
> >>> INIT: cannot execute "/sbin/agetty"
> >>> INIT: cannot execute "/sbin/agetty"
> >>> INIT: cannot execute "/sbin/agetty"
> >>>
> >>>
> >> Can you show /etc/fstab and the console-log for the entire boot? Seems
> /sbin
> >> is not readable. You sure you have the kernel modules loaded? Are you
> using
> >> an initramfs? If so, does that build without errors ?
> > The input/output error – to me – indicates a hardware problem. When you
> > mounted the FS by hand, can you read ewend? For instance with md5sum.
> >
> except it boots ok with older kernels. When you've eliminated the
> impossible, whatever remains, however improbable has to be a kernel
> config change (missing or erroneous and unintended) , or
> initramfs failing to build/install correctly. Check error output from
> your kernel build.
>
>

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

[Lee K]

On Mon, Oct 02, 2023 at 02:29:05AM +0200, Håkon Alstadheim wrote:
> 
> Den 01.10.2023 21:31, skrev Frank Steinmetzger:
> > Am Sat, Sep 30, 2023 at 11:25:46PM +0200 schrieb Håkon Alstadheim:
> >> Den 30.09.2023 22:57, skrev Valmor F. de Almeida:
> >>> Hello,
> >>>
> >>> For a while now (3 weeks or so) I have been upgrading the linux kernel
> >>> on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
> >>> working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
> >>> able to boot. I have been following the same method for many years: make
> >>> oldconfig, etc...
> >>>
> >>> The booting error starts at:
> >>>
> >>> [snip]
> >>>
> >>> * INIT: Entering runlevel: 3
> >>> [snip]
> >>> * Starting cronie ...
> >>> * Starting DHCP Client Daemon ...
> >>> * Starting laptop_mode ...
> >>> * Mounting network filesystems ...
> >>> /etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
> >>> /lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
> >>> INIT:
> >>> INIT: cannot execute "/sbin/agetty"
> >>> INIT: cannot execute "/sbin/agetty"
> >>> INIT: cannot execute "/sbin/agetty"
> >>>
> >>>
> >> Can you show /etc/fstab and the console-log for the entire boot? Seems 
> >> /sbin
> >> is not readable. You sure you have the kernel modules loaded? Are you using
> >> an initramfs? If so, does that build without errors ?
> > The input/output error – to me – indicates a hardware problem. When you
> > mounted the FS by hand, can you read ewend? For instance with md5sum.
> >
> except it boots ok with older kernels. When you've eliminated the 
> impossible, whatever remains, however improbable has to be a kernel 
> config change (missing or erroneous and unintended) , or 
> initramfs failing to build/install correctly. Check error output from 
> your kernel build.
> 

I found this: 

https://www.reddit.com/r/Gentoo/comments/168qrbx/gentoosources_6146_kernel_reports_io_error/

-- 
Lee

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

[Håkon Alstadheim]

Den 01.10.2023 21:31, skrev Frank Steinmetzger:

Am Sat, Sep 30, 2023 at 11:25:46PM +0200 schrieb Håkon Alstadheim:

Den 30.09.2023 22:57, skrev Valmor F. de Almeida:

Hello,

For a while now (3 weeks or so) I have been upgrading the linux kernel
on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
able to boot. I have been following the same method for many years: make
oldconfig, etc...

The booting error starts at:

[snip]

* INIT: Entering runlevel: 3
[snip]
* Starting cronie ...
* Starting DHCP Client Daemon ...
* Starting laptop_mode ...
* Mounting network filesystems ...
/etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
/lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
INIT:
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"



Can you show /etc/fstab and the console-log for the entire boot? Seems /sbin
is not readable. You sure you have the kernel modules loaded? Are you using
an initramfs? If so, does that build without errors ?

The input/output error – to me – indicates a hardware problem. When you
mounted the FS by hand, can you read ewend? For instance with md5sum.

except it boots ok with older kernels. When you've eliminated the 
impossible, whatever remains, however improbable has to be a kernel 
config change (missing or erroneous and unintended) , or 
initramfs failing to build/install correctly. Check error output from 
your kernel build.

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

[Frank Steinmetzger]

Am Sat, Sep 30, 2023 at 11:25:46PM +0200 schrieb Håkon Alstadheim:
> 
> Den 30.09.2023 22:57, skrev Valmor F. de Almeida:
> > 
> > Hello,
> > 
> > For a while now (3 weeks or so) I have been upgrading the linux kernel
> > on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
> > working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
> > able to boot. I have been following the same method for many years: make
> > oldconfig, etc...
> > 
> > The booting error starts at:
> > 
> > [snip]
> > 
> > * INIT: Entering runlevel: 3
> > [snip]
> > * Starting cronie ...
> > * Starting DHCP Client Daemon ...
> > * Starting laptop_mode ...
> > * Mounting network filesystems ...
> > /etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
> > /lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
> > INIT:
> > INIT: cannot execute "/sbin/agetty"
> > INIT: cannot execute "/sbin/agetty"
> > INIT: cannot execute "/sbin/agetty"
> > 
> > 
> Can you show /etc/fstab and the console-log for the entire boot? Seems /sbin
> is not readable. You sure you have the kernel modules loaded? Are you using
> an initramfs? If so, does that build without errors ?

The input/output error – to me – indicates a hardware problem. When you 
mounted the FS by hand, can you read ewend? For instance with md5sum.

-- 
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.

“If wishes were horses we’d all be eating steak.” – Jayne, Firefly


signature.asc
Description: PGP signature

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

[Valmor F. de Almeida]

On 10/1/23 07:29, Michael wrote:

On Sunday, 1 October 2023 05:56:02 BST Valmor F. de Almeida wrote:

On 9/30/23 17:25, Håkon Alstadheim wrote:

Den 30.09.2023 22:57, skrev Valmor F. de Almeida:

Hello,

For a while now (3 weeks or so) I have been upgrading the linux kernel
on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
able to boot. I have been following the same method for many years:
make oldconfig, etc...

The booting error starts at:

[snip]

* INIT: Entering runlevel: 3
[snip]
* Starting cronie ...
* Starting DHCP Client Daemon ...
* Starting laptop_mode ...
* Mounting network filesystems ...
/etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
/lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
INIT:
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"


Can you show /etc/fstab and the console-log for the entire boot? Seems
/sbin is not readable. You sure you have the kernel modules loaded? Are
you using an initramfs? If so, does that build without errors ?


Here is fstab:

/dev/nvme0n1p2  /boot   ext2defaults0 2
/dev/nvme0n1p3  noneswapsw  0 0
/dev/nvme0n1p4  /   ext4noatime,discard
 0 1
/dev/cdrom  /mnt/cdrom  autonoauto,user 0 0

I have not changed anything from 6.1.41-gentoo (which compiles and
boots) except updating the config file for compiling the new kernel.
Then I do: make && modules_install. Which runs without errors. After
that: grub-mkconfig -o /boot/grub/grub.cfg.
I am not using initramfs.

I don't know how to save the boot messages; it seems that if I turn on
the logger in openrc, it will log the openrc messages but not sysinit
runlevels?

Thanks,
--
Valmor


I think the error messages you're getting indicate inability to access your
rootfs.  Have you perhaps changed the fs drivers in the latest kernels, from
built in to modules?

Have you diff'ed your 6.1.41-gentoo .config file against the latest kernels'
.config files to see what might have changed/missing?

You can set up a netconsole to check boot time messages:

https://www.kernel.org/doc/Documentation/networking/netconsole.txt
https://wiki.ubuntu.com/Kernel/Netconsole

In summary, build netconsole in the new kernel, or as a module, change GRUB's
default CMDLINE from "quiet splash" to "debug" and add netconsole in the
kernel command line:

netconsole=@/,[PORT]@[DEST_IP]

Then at the destination PC launch netcat/socat/telnet; e.g.

nc -u -l -p [PORT]

and reboot the PC you want to debug with the latest kernel, while watching the
output on the destination PC's terminal with nc.


Here is the diff for the config files:

->  diff config /boot/config-6.1.41-gentoo
3c3
< # Linux/x86 6.1.53-gentoo-r1 Kernel Configuration
---
> # Linux/x86 6.1.41-gentoo Kernel Configuration
5c5
< CONFIG_CC_VERSION_TEXT="gcc (Gentoo 13.2.1_p20230826 p7) 13.2.1 20230826"
---
> CONFIG_CC_VERSION_TEXT="gcc (Gentoo 12.3.1_p20230526 p2) 12.3.1 20230526"
7c7
< CONFIG_GCC_VERSION=130201
---
> CONFIG_GCC_VERSION=120301
455d454
< CONFIG_CPU_SRSO=y
457d455
< # CONFIG_GDS_FORCE_MITIGATION is not set
646d643
< CONFIG_ARCH_HAS_CPU_FINALIZE_INIT=y
3136d3132
< CONFIG_VIDEO_V4L2_SUBDEV_API=y
3139,3140d3134
< CONFIG_V4L2_FWNODE=m
< CONFIG_V4L2_ASYNC=m
3236c3230,3233
< CONFIG_VIDEO_CAMERA_SENSOR=y
---
>
> #
> # Camera sensor devices
> #
3295a3293
> # end of Camera sensor devices

I guess I could explore some of this difference.
I have not changed the way I compile the kernel and I typically try to 
have everything built in (only a few modules).

Thanks for the netconsole info.
--
Valmor

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

[Håkon Alstadheim]

Den 01.10.2023 06:56, skrev Valmor F. de Almeida:

On 9/30/23 17:25, Håkon Alstadheim wrote:


Den 30.09.2023 22:57, skrev Valmor F. de Almeida:


Hello,

For a while now (3 weeks or so) I have been upgrading the linux 
kernel on a Dell XPS laptop starting from 6.1.41-gentoo (which is my 
current working kernel) to 6.1.53-gentoo-r1. No kernel I have built 
since is able to boot. I have been following the same method for 
many years: make oldconfig, etc...


The booting error starts at:

[snip]

* INIT: Entering runlevel: 3
[snip]
* Starting cronie ...
* Starting DHCP Client Daemon ...
* Starting laptop_mode ...
* Mounting network filesystems ...
/etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
/lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
INIT:
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"


Can you show /etc/fstab and the console-log for the entire boot? 
Seems /sbin is not readable. You sure you have the kernel modules 
loaded? Are you using an initramfs? If so, does that build without 
errors ?



Here is fstab:

/dev/nvme0n1p2  /boot   ext2 defaults    0 2
/dev/nvme0n1p3  none    swap sw  0 0
/dev/nvme0n1p4  /   ext4 noatime,discard    0 1
/dev/cdrom  /mnt/cdrom  auto noauto,user 0 0

I have not changed anything from 6.1.41-gentoo (which compiles and 
boots) except updating the config file for compiling the new kernel. 
Then I do: make && modules_install. Which runs without errors. After 
that: grub-mkconfig -o /boot/grub/grub.cfg.

I am not using initramfs.

I can't see anything fishy in fstab, no network-mounts that might have 
failed. From the original message it looks like your network interface 
is not being set up correctly, but you should still be able to boot. 
Also "rmdir: command not found" probably means your PATH does not get 
set, or else you don't have execute permissions on rmdir. Odd  that this 
should be dependent on kernel version. You should go over and verify 
that the transfer of your linux .config went OK. Then verify that the 
new config does in fact enable modules for your network card, and enable 
the necessary settings for your init system (looks like you are using 
openrc?)

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

[Michael]

On Sunday, 1 October 2023 05:56:02 BST Valmor F. de Almeida wrote:
> On 9/30/23 17:25, Håkon Alstadheim wrote:
> > Den 30.09.2023 22:57, skrev Valmor F. de Almeida:
> >> Hello,
> >> 
> >> For a while now (3 weeks or so) I have been upgrading the linux kernel
> >> on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current
> >> working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is
> >> able to boot. I have been following the same method for many years:
> >> make oldconfig, etc...
> >> 
> >> The booting error starts at:
> >> 
> >> [snip]
> >> 
> >> * INIT: Entering runlevel: 3
> >> [snip]
> >> * Starting cronie ...
> >> * Starting DHCP Client Daemon ...
> >> * Starting laptop_mode ...
> >> * Mounting network filesystems ...
> >> /etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
> >> /lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
> >> INIT:
> >> INIT: cannot execute "/sbin/agetty"
> >> INIT: cannot execute "/sbin/agetty"
> >> INIT: cannot execute "/sbin/agetty"
> > 
> > Can you show /etc/fstab and the console-log for the entire boot? Seems
> > /sbin is not readable. You sure you have the kernel modules loaded? Are
> > you using an initramfs? If so, does that build without errors ?
> 
> Here is fstab:
> 
> /dev/nvme0n1p2  /boot   ext2defaults0 2
> /dev/nvme0n1p3  noneswapsw  0 0
> /dev/nvme0n1p4  /   ext4noatime,discard
> 0 1
> /dev/cdrom  /mnt/cdrom  autonoauto,user 0 0
> 
> I have not changed anything from 6.1.41-gentoo (which compiles and
> boots) except updating the config file for compiling the new kernel.
> Then I do: make && modules_install. Which runs without errors. After
> that: grub-mkconfig -o /boot/grub/grub.cfg.
> I am not using initramfs.
> 
> I don't know how to save the boot messages; it seems that if I turn on
> the logger in openrc, it will log the openrc messages but not sysinit
> runlevels?
> 
> Thanks,
> --
> Valmor

I think the error messages you're getting indicate inability to access your 
rootfs.  Have you perhaps changed the fs drivers in the latest kernels, from 
built in to modules?

Have you diff'ed your 6.1.41-gentoo .config file against the latest kernels' 
.config files to see what might have changed/missing?

You can set up a netconsole to check boot time messages:

https://www.kernel.org/doc/Documentation/networking/netconsole.txt
https://wiki.ubuntu.com/Kernel/Netconsole

In summary, build netconsole in the new kernel, or as a module, change GRUB's 
default CMDLINE from "quiet splash" to "debug" and add netconsole in the 
kernel command line:

netconsole=@/,[PORT]@[DEST_IP]

Then at the destination PC launch netcat/socat/telnet; e.g.

nc -u -l -p [PORT]

and reboot the PC you want to debug with the latest kernel, while watching the 
output on the destination PC's terminal with nc.


signature.asc
Description: This is a digitally signed message part.

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

[Valmor F. de Almeida]

On 9/30/23 17:25, Håkon Alstadheim wrote:


Den 30.09.2023 22:57, skrev Valmor F. de Almeida:


Hello,

For a while now (3 weeks or so) I have been upgrading the linux kernel 
on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current 
working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is 
able to boot. I have been following the same method for many years: 
make oldconfig, etc...


The booting error starts at:

[snip]

* INIT: Entering runlevel: 3
[snip]
* Starting cronie ...
* Starting DHCP Client Daemon ...
* Starting laptop_mode ...
* Mounting network filesystems ...
/etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
/lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
INIT:
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"


Can you show /etc/fstab and the console-log for the entire boot? Seems 
/sbin is not readable. You sure you have the kernel modules loaded? Are 
you using an initramfs? If so, does that build without errors ?



Here is fstab:

/dev/nvme0n1p2  /boot   ext2defaults0 2
/dev/nvme0n1p3  noneswapsw  0 0
/dev/nvme0n1p4  /   ext4noatime,discard 
   0 1

/dev/cdrom  /mnt/cdrom  autonoauto,user 0 0

I have not changed anything from 6.1.41-gentoo (which compiles and 
boots) except updating the config file for compiling the new kernel. 
Then I do: make && modules_install. Which runs without errors. After 
that: grub-mkconfig -o /boot/grub/grub.cfg.

I am not using initramfs.

I don't know how to save the boot messages; it seems that if I turn on 
the logger in openrc, it will log the openrc messages but not sysinit 
runlevels?


Thanks,
--
Valmor

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

[Håkon Alstadheim]

Den 30.09.2023 22:57, skrev Valmor F. de Almeida:


Hello,

For a while now (3 weeks or so) I have been upgrading the linux kernel 
on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current 
working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is 
able to boot. I have been following the same method for many years: 
make oldconfig, etc...


The booting error starts at:

[snip]

* INIT: Entering runlevel: 3
[snip]
* Starting cronie ...
* Starting DHCP Client Daemon ...
* Starting laptop_mode ...
* Mounting network filesystems ...
/etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
/lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
INIT:
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"


Can you show /etc/fstab and the console-log for the entire boot? Seems 
/sbin is not readable. You sure you have the kernel modules loaded? Are 
you using an initramfs? If so, does that build without errors ?

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

[Valmor F. de Almeida]

Hello,

For a while now (3 weeks or so) I have been upgrading the linux kernel 
on a Dell XPS laptop starting from 6.1.41-gentoo (which is my current 
working kernel) to 6.1.53-gentoo-r1. No kernel I have built since is 
able to boot. I have been following the same method for many years: make 
oldconfig, etc...


The booting error starts at:

[snip]

* INIT: Entering runlevel: 3
[snip]
* Starting cronie ...
* Starting DHCP Client Daemon ...
* Starting laptop_mode ...
* Mounting network filesystems ...
/etc/init.d/netmount: line 45 /lib/rc/bin/ewend: Input/output error
/lib/rc/sh/rc-cgroup.sh: line 184: rmdir: command not found
INIT:
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"

[snip]

The following kernels all failed to boot: 6.1.46-gentoo, 6.1.53-gentoo, 
6.1.53-gentoo-r1. I am wondering whether this will eventually get fixed 
on later kernels. I have been upgrading kernels on this machine since 
2020 every other week without any kernel problems.


Inputs appreciated.
Thanks,
--
Valmor