init-early.sh used greatest stack depth

so, after compiling a new kernel from gentoo sources (3.2.11) and a restart, my trusty old x60 freezes during boot with the last message being:

init-early.sh used greatest stack depth

hmm

after a little googling, i stumbled across this bug.

so, here is what i did in a nutshell to get my machine back up and running (remember, this is just one fix):
boot off of a minimal install disk
# mount /dev/sda3 /mnt/gentoo
# mount -t proc none /mnt/gentoo/proc
# mount -o bind /dev /mnt/gentoo/dev
# chroot /mnt/gentoo /bin/bash
# env-update
# source /etc/profile

now run fdisk -l to find the path to the boot partition which in my case looks like :

# fdisk -l

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x5f51a82e

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      206847      102400   83  Linux
/dev/sda2          206848     8595455     4194304   82  Linux swap / Solaris
/dev/sda3         8595456   488397167   239900856   83  Linux

now lets mount boot also
# mount /dev/sda1 /boot

now, make your way to /usr/src/linux and vi your .config file
look for:
CONFIG_DEVTMPFS
which in my case said:
# CONFIG_DEVTMPFS is not set
now lets change it to:
CONFIG_DEVTMPFS=y

now, compile your kernel how you normally would and use the new bzImage file.

that fixed my situation, YMMV.

• CONFIG_DEVTMPFS_MOUNT=y
  helps me

  Reply

• Awesome, this fixed the problem for me. Appreciate you taking the time to post this.

  Reply