I am experiencing random segfaults with kernel 2.6.11 and up. Usualy happens after running for a day or two. Heavy emerging/compiling seems to bring it on faster. It seems that the problem goes away after I disable "Preemtible Kernel" option in the the kernel config. I experienced this problem on G4 Windtunnel as well as on G4 TiBook. Tried gentoo-dev-sources as well as development-sources. Reproducible: Sometimes Steps to Reproduce: No exact steps to reproduce it. Just emerge something heavy like Firefox. Problem should manifest. Actual Results: powerpc-unknown-linux-gnu-gcc -o prmwait.o -c -mtune=G4 -mabi=altivec -pipe -pipe -ansi -pthread -O2 -fPIC -UDEBUG -DMOZILLA_CLIENT=1 -DNDEBUG=1 -DXP_UNIX=1 -D_POSIX_SOURCE=1 -D_BSD_SOURCE=1 -D_SVID_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -DHAVE_FCNTL_FILE_LOCKING=1 -DLINUX=1 -DHAVE_LCHOWN=1 -DHAVE_STRERROR=1 -D_REENTRANT=1 -DFORCE_PR_LOG -D_PR_PTHREADS -UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I/var/tmp/portage/mozilla-firefox-1.0.2/work/mozilla/dist/include/nspr -I../../../pr/include -I../../../pr/include/private prmwait.c prmwait.c: In function `_MW_PollInternal': prmwait.c:599: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions. The bug is not reproducible, so it is likely a hardware or OS problem. distcc[434] ERROR: compile prmwait.c on localhost failed Expected Results: Expect no segfaults. Portage 2.0.51.19 (default-linux/ppc/2004.3, gcc-3.4.3-20050110, glibc-2.3.4.200 41102-r1, 2.6.12-rc1 ppc) ================================================================= System uname: 2.6.12-rc1 ppc 7455, altivec supported Gentoo Base System version 1.6.10 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Feb 28 2005, 01:48:26)] distcc 2.18.3 powerpc-unknown-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] dev-lang/python: 2.3.5 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.90.0.3-r4 sys-devel/libtool: 1.5.14 virtual/os-headers: 2.4.22-r1 ACCEPT_KEYWORDS="ppc ~ppc" AUTOCLEAN="yes" CFLAGS="-O2 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe" CHOST="powerpc-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share /config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kd e/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/q mail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo http://gentoo.osuosl.org http: //www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X alsa apache2 berkdb bitmap-fonts cdr crypt cups curl dba divx4linux dvd d vdread emboss encode esd fam flac font-server fortran gd gdbm gif gpm gtk2 image magick imlib java jpeg junit kde libwww maildir motif mp3 mpeg mysql ncurses nls oggvorbis ooo-kde opengl oss pam perl png ppc python qt readline sdl slang spel l sqlite ssl tcpd tiff truetype truetype-fonts type1-fonts unicode usb xml xml2 xmms xprint xv xvid zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Please attach your "dmesg" output after a few of these crashes have occurred.
Created attachment 56217 [details] dmesg output dmesg output after few gcc segfaults
Comment on attachment 56217 [details] dmesg output Here is a dmesg output after few of those segfaults. Seems to be nothing of use in it. Played around with different options in "Kernel Hacking", still got nothing of any use in dmesg.
Please test 2.6.12-rc2 if you haven't already and file a bug at http://bugzilla.kernel.org if the issue exists there. Please update this bug with the upstream bug URL.
Upstream URL: http://bugzilla.kernel.org/show_bug.cgi?id=4502
Does disabling PREEMPT help? (see upstream bug)
What's the status of this bug? On a recent kernel (say 2.6.21) can you run with preemption and without SMP reliably?
