Kris Kennaway wrote: > Christoph Friedrichs wrote: >> Hi Guys, >> >> I?m relatively new with my freebsd -current box and actual >> experiencing problems with starting kdm and portupgrade. Everytime I >> do so the kdm-bin log explodes with this error messages: >> >> Fatal error 'Cannot allocate red zone for initial thread' at line 382 >> in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) >> Fatal error 'Cannot allocate red zone for initial thread' at line 382 >> in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) >> Fatal error 'Cannot allocate red zone for initial thread' at line 382 >> in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) >> >> I googled this problem and found something concering some ruby >> packages. I did a manual rebuild of >> >> ruby-1.8.6_2,1 >> perl-5.8.8 >> ruby18-bdb-0.6.2 >> db41-4.1.25_4 >> portupgrade-2.3.1,2 >> >> With this rebuild problems with portupgrade were solved but kdm keeps >> refusing to start with same error messages. In UPDATING I found this: >> >> 20071009: >> Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and >> WITHOUT_LIBTHR are set. >> >> Does this probably have something to do with this? > > Did you update from an older release of FreeBSD? > > Kris > > Yes I did an update from an older release. I previously installed PC-BSD 1.4 which is running a FreeBSD 6 Stable under hood. Actual im running root_at_helix# uname -a FreeBSD helix 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Tue Oct 30 09:45:09 CET 2007 root_at_helix:/usr/obj/usr/src/sys/SELFMADE i386 ChristophReceived on Wed Oct 31 2007 - 06:12:18 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:20 UTC