lkml.org 
[lkml]   [1997]   [Jul]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subject2.1.44+ and ppc/glibc
OK well,

right now i am using 2.1.43 for powerpc (pmac) without any noticable
problems. i do get an oddity in my /var/log/messages:

keys kernel: KERNEL! Task: c3548000, PC: c0118038, bad area! - Addr: 260
keys kernel: NIP: C0118038, MSR: 00009932, DAR: 00000260, DSISR: 40000000, FRAME: c3549c90
keys kernel: TASK = c3548000[366] 'sh'
keys kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000260
keys kernel: current->tss.pg_tables = c354a000
keys kernel: *pde = c3547000
keys kernel: *pte = 00000000
keys kernel: VFS: Close: file count is 0

anyhow when the 2.1.44 patch first came out i applied it, made all the
necessary ppc changes (since the patches dont usually cover the asm-ppc
and pmac only files) and got it to build ok. when i tried to boot it this
is what happens:

INIT: version 2.70 booting
Activating swap partitions
-a: error in loading shared libraries
-a: cannot open shared object file: No such file or directory
keys: error in loading shared libraries
keys: cannot open shared object file: No such file or directory
hostname: (none)
Checking root filesystems
-V: error in loading shared libraries
-V: cannot open shared object file: No such file or directory

*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D for normal startup):

so then i type in the root password maybe 20 or 30 lines come up and then
the system reboots to do that all over again. i can only catch the first
line where it says something like "usage: ld.so blah blah blah". after
this i just boot my old 2.1.43 kernel and everything is back to normal. ii
am pretty sure i made all the necessary file system changes, and since it
compiles without any warnings that shouldnt be there i am assuming maybe
it is a glibc problem? i know that it is recommended to use libc 5.4.33,
but i do not have that option. was anything changed in 2.1.44 that would
break glibc 1.0 support? i am using redhat 4.2 w/ the glibc-0.961212
packages and other than this i have not had many problems with it. i have
also been keeping up with the 2.1.45 development and have re-tested the
kernel with each of the pre-patches and finally patch-2.1.45. same thing.
any ideas?


Matt McLean

(___) (__)
(o o) /oo\################
/------\ / (__) keys \ /################\
/ ____O (oo) \/ ################ |
| / /----\----\/ keys@keys.got.net ################ |
/\oo===| / || keys@insomnia.net ################ |
| || *||^-----|| ################
* ^^ ^^ ^^ | | | |
^ ^ ^ ^


\
 
 \ /
  Last update: 2005-03-22 13:39    [W:0.037 / U:0.148 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site