cmucl *** Sigsegv in page not marked as write protected
Quote:
> >> I'm running cmucl on red hat linux (kernal-2.2.5-22) . The cmucl
> >> version is from the debian package (2.4.20). I'm not sure how that
> >> translates into cmucl release numbers. In any case, I get the
> >> following on startup:
> > All your problems will disappear when you use a newer Kernel.
> > 2.2.5 is rather old and buggy...
> I use 2.2.16 and if I remember right the Memory problems disappeared
> somewhere around 2.2.12.
> If you update, then CMUCL runs fine without "lazy" Option.
My apologies for starting to get away from common lisp with my follow
up question, but maybe someone here using cmucl on linux has been
through something similar before. If not, I'll repost to a linux group
and hope that I can understand the responses there; linux isn't my
native language ;-)
I downloaded the and installed following rpm:
kernel-2.2.17-14.i686.rpm
My previous lilo.conf file looked like this:
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/vmlinuz-2.2.5-22smp
label=linux
root=/dev/sda8
initrd=/boot/initrd-2.2.5-22smp.img
read-only
After making an initrd image like this:
/sbin/mkinitrd initrd-2.2.17-14.img 2.2.17-14
I added the following (as the first image)
image=/boot/vmlinuz-2.2.17-14
label=linux-new
root=/dev/sda8
initrd=/boot/initrd-2.2.17-14.img
read-only
I updated the symbolic links that I found in /boot as follows:
System.map -> System.map-2.2.17-14
module-info -> module-info-2.2.17-14
vmlinuz -> vmlinuz-2.2.17-14
I ran /sbin/lilo and got no error messages.
Now, when I reboot, I get the following:
kernel panic: VFS: unable to mount root fs on 08:08
I got that message in previous attempts without the initrd image and
the relevant line in linux.conf
Does anyone know where I went wrong?
Thanks for any help,
George