Dave Jones - Thu, Jun 02 2005 15:01:20 -0400: > On Thu, Jun 02, 2005 at 08:55:40PM +0200, Christoph Franke wrote: > > Dave Jones - Thu, Jun 02 2005 14:25:48 -0400: > > > > > Is it repeatable ? Does it behave again if you boot with > > > exec-shield=0 ? or exec-shield-randomize=0 ? > > > > Yes, it is repeatable, teamspeak segfaults on every start. Ntpd > > segfaults on both build -30 and -31 during boot, but can be restarted > > afterwards. Will try a boot with exec-shield=0 tomorrow morning and pass > > through the results. > > Ok. Oh, staring on teamspeak I didn't instantly see the old fellow came up again with the -31 build (booted with "exec-shield=0"). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caadde8(0000003000000a88). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caaddf0(0000000000000003). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caaddf8(00007fffffffff54). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade00(00007fffffffff55). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade08(00007fffffffff56). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade18(00007fffffffff57). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade20(00007fffffffff58). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade28(00007fffffffff59). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade30(00007fffffffff5a). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade38(00007fffffffff5b). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade48(0000000000000010). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade50(00000000078bfbff). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade58(0000000000000006). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade60(0000000000001000). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade68(0000000000000011). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade70(0000000000000064). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade78(0000000000000003). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade80(0000000000400040). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade88(0000000000000004). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade90(0000000000000038). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caade98(0000000000000005). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caadea0(0000000000000009). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caadea8(0000000000000007). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caadeb8(0000000000000008). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caadec8(0000000000000009). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caaded0(0000000000417b10). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caaded8(000000000000000b). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caadee8(000000000000000c). Jun 3 07:20:02 sun kernel: mm/memory.c:109: bad pmd ffff81007caadef8(000000000000000d). Jun 3 07:20:03 sun kernel: mm/memory.c:109: bad pmd ffff81007caadf08(000000000000000e). Jun 3 07:20:03 sun kernel: mm/memory.c:109: bad pmd ffff81007caadf18(0000000000000017). Jun 3 07:20:03 sun kernel: mm/memory.c:109: bad pmd ffff81007caadf28(000000000000000f). Jun 3 07:20:03 sun kernel: mm/memory.c:109: bad pmd ffff81007caadf30(00007fffffffff49). Jun 3 07:20:03 sun kernel: mm/memory.c:109: bad pmd ffff81007caadf48(0034365f36387800). Along with the "memory.c bad pmd" issue I keep getting these message again: Usage: ld.so [OPTION]... EXECUTABLE-FILE [ARGS-FOR-PROGRAM...] You have invoked `ld.so', the helper program for shared library executables. This program usually lives in the file `/lib/ld.so', and special directives in executable files using ELF shared libraries tell the system's program loader to load the helper program from this file. This helper program loads the shared libraries needed by the program executable, prepares the program to run, and runs it. You may invoke this helper program directly from the command line to load and run an ELF executable file; this is like executing that file itself, but always uses this helper program from the file you specified, instead of the helper program file specified in the executable file you run. This is mostly of use for maintainers to test new versions of this helper program; chances are you did not intend to run this program. --list list all dependencies and how they are resolved --verify verify that given object really is a dynamically linked object we can handle --library-path PATH use given PATH instead of content of the environment variable LD_LIBRARY_PATH --inhibit-rpath LIST ignore RUNPATH and RPATH information in object names in LIST This occures during compilation of programs as well as on a cronjob renicing some processes and is always parallel to the memory.c log entries. The older builds all showed up with this, -30 didn't but -31 does again. Regards Christoph -- | GnuPG Public Key: http://www.thefranke.net/public.asc | | The BOFH Archive at: http://bofh.ntk.net/Bastard.html | | Registered Linux User: 250439 - http://counter.li.org |
Attachment:
signature.asc
Description: Digital signature
