Bug 36928 – setiathome crashes hard in 3-5 minutes

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Mark Knecht 2003-12-31 20:04:57 UTC]

Running setiathome on my Gentoo box causes a hard crash in 3-5 minutes. Mouse and keybaord are locked. I have to do a hard reset.

Reproducible: Always
Steps to Reproduce:
1. bash-2.05b$ !/opt/setiathome/setiathome -verbose

Actual Results:  
Hard crash

Expected Results:  
Should run like the Energizer Bunny

I think this is possibly a gcc-3.3.2 problem, but no proof. This machine ran
setiathome for 6 months and only recently started doing this. I've also tried
extra cooling and two kernels.

Wizard root # emerge info
Portage 2.0.49-r18 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r8, 2.4.22-gentoo-r2)
=================================================================
System uname: 2.4.22-gentoo-r2 i686 AMD Athlon(TM) XP 2600+
Gentoo Base System version 1.4.3.10
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-mcpu=athlon-xp -O3 -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-mcpu=athlon-xp -O3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X aalib alsa apm arts avi berkdb bonobo cdr crypt cups encode esd
foomaticdb gdbm gif gnome gpm gtk gtk2 gtkhtml guile imlib jack jack-caps
jack-tmpfs java jpeg kde libg++ libwww mad mikmod motif mozilla mpeg ncurses nls
oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang
spell ssl svga tcltk tcpd truetype x86 xml2 xmms xv zlib video_cards_radeon"

Wizard root #

[Comment 1 SpanKY 2003-12-31 23:07:06 UTC]

try out app-benchmarks/cpuburn ?

[Comment 2 Mark Knecht 2004-01-01 06:48:24 UTC]

Good call. It segfaults in about 30 seconds. Always with code 139. I need to find out what that means, but clearly there is a problem here. I don't think it's heat as I can reboot and it fails in about the same amount of time every time.

Probably not a setiathome problem. Go ahead and close/delete this bug.

Thanks!

[Comment 3 SpanKY 2004-01-01 16:21:16 UTC]

g'luck tracking it down ;)