Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 52472 - kernel-2.6.7-rc2 :: a lot of segment faults
Summary: kernel-2.6.7-rc2 :: a lot of segment faults
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-30 08:59 UTC by Selecter
Modified: 2004-07-12 02:01 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Selecter 2004-05-30 08:59:12 UTC
I am not sure whether it is a new kernel bug so I post it in here.

Recently I have compiled glibc-2.3.2 with NTPL support based on linux-headers-2.6.5 and also I have compiled kernel-2.6.7-rc2.

Running 2.6.7-rc2 version I get a lot of seg. faults: cups daemon, evolution, mozilla, emerge, epiphany etc. Running kde apps like konqueror and konsole with no problems.

Running gentoo-dev-sources-2.6.5 everything is O.K.

Reproducible: Always
Steps to Reproduce:




//gdb 6.0 
$ gdb evolution 
(no debugging symbols found)...Using host libthread_db library 
"/lib/libthread_db.so.1". 
(gdb) run 
Starting program: /usr/bin/evolution 
Program received signal SIGSEGV, Segmentation fault. 
0x40010b28 in ?? () 
 
$ gdb /usr/lib/mozilla/mozilla-bin 
(no debugging symbols found)...Using host libthread_db library 
"/lib/libthread_db.so.1". 
(gdb) run 
Starting program: /usr/lib/mozilla/mozilla-bin 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)...  
Program received signal SIGSEGV, Segmentation fault. 
0x40010b28 in realloc () from /lib/ld-linux.so.2
Comment 1 Tim Yamin (RETIRED) gentoo-dev 2004-06-01 03:27:08 UTC
Can you please try development-sources-2.6.6 so we can isolate what kernel version you got this problem in? Thanks!
Comment 2 Selecter 2004-06-02 02:56:20 UTC
I think this is NPTL troubles. All software needs to be recompiled to use nptl without worries.
Comment 3 Selecter 2004-06-19 00:26:26 UTC
It is still happening. I cannot get rid of it :( I disabled nptl, but it's not use.

(gdb) run
Starting program: /usr/bin/evolution
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.

Program received signal SIGSEGV, Segmentation fault.
0x4000ec58 in ?? ()
(gdb) where
#0  0x4000ec58 in ?? ()
#1  0x40007217 in ?? ()
#2  0x64eacf19 in ?? ()
#3  0x4136a267 in ?? ()
#4  0x400124fc in ?? ()
#5  0x08052144 in ?? ()
#6  0x00000020 in ?? ()
Comment 4 Selecter 2004-06-19 00:29:49 UTC
I forgot to mention that:

1. If I compile __ANY__ new kernel and then run it - the same story with seg. faults happens.

2. Sometimes this all thing dissapears after some minutes on running machine.
Comment 5 Tim Yamin (RETIRED) gentoo-dev 2004-06-19 03:03:21 UTC
Can you do a ``FEATURES="nostrip" emerge glibc'' [ Use NPTL if you wish ] so GDB backtraces work properly? Also; can you please merge 2.6.6 headers before merging glibc again? Thanks...
Comment 6 Selecter 2004-06-19 04:09:11 UTC
Ok I will do it. But I will not use NPTL and especialy 2.6.6 headers (I use 2.4.21). Is that ok?
Comment 7 Selecter 2004-06-19 05:23:59 UTC
Recompiled glibc just like you said - didn't work.
Comment 8 Tim Yamin (RETIRED) gentoo-dev 2004-06-19 05:52:11 UTC
So you mean if you run a backtrace you still get the:

"warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code."

... message, or do you mean that you still get the segmentation faults? This doesn't look like a kernel bug to me since I've been running 2.6.7-rcX with 2.6 headers and NPTL and I haven't had any issues. Reassigning to toolchain@gentoo.org.

One suggestion is to reboot - that solved a few issues when I migrated over to NPTL and I was getting various Segmentation Faults before I rebooted.
Comment 9 Selecter 2004-06-19 12:17:24 UTC
The warning is gone (thanks for the tip) but seg faults - no. And yes - this is not kernel bug. I don't have any ideas what to do :( It seems I will have to rebuild whole system from scratch.
Comment 10 Travis Tilley (RETIRED) gentoo-dev 2004-07-11 15:26:41 UTC
do you still get this problem? also, have you run memtest86 lately?
Comment 11 Selecter 2004-07-12 02:01:47 UTC
I reinstalled gentoo from scratch, sorry.