Hi, * Steve Langasek [2005-08-17]: > > From the backtrace, I would rather guess it's libc-related. > > Actually, I would guess it's kernel-related. > > Per your original report, you are running: > > > Kernel: Linux 2.6.12.4-bar > > This looks like a self-compiled kernel.
It is. > Please check whether this bug occurs with the Debian kernel > packages, or at least check that you have the core CONFIG_SYSVIPC > option enabled in your kernel config. [EMAIL PROTECTED]:~$ grep CONFIG_SYSVIPC /boot/config-`uname -r` CONFIG_SYSVIPC=y [ Installing the debian linux-image-2.6.12-1-powerpc kernel image failed because mkinitrd can't cope with my encrypted root filesystem on /dev/loop1. Don't know if it should either. ] > If neither enabling CONFIG_SYSVIPC in your custom kernel, nor booting a > Debian kernel, fixes this problem for you, *then* we should look at it > as a libc problem. :) Getting a debian kernel to boot on my machine might prove being painful. I use a custom initrd with loop-aes-utils encryption I made before I heard of cryptsetup. I don't know how easy it will be to make it debian-kernel-compliant again. Cheers, Laurent.
signature.asc
Description: Digital signature
