| View previous topic :: View next topic |
| Author |
Message |
jhardin
n00b
Joined: 12 Oct 2005
Posts: 59
|
 Posted: Sun Jul 19, 2009 4:59 am Post subject: Bus errors killing emerge |
 |
|
Folks:
Something is fishy. I've started experiencing bus errors in various programs at various times.
Worst of all, I'm getting bus errors in emerge, so I am kinda stuck for rebuilding packages...
For example:
| Code: | mercury linux # emerge debianutils
Calculating dependencies ... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/debianutils-3.1.3
* debianutils_3.1.3.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking debianutils_3.1.3.tar.gz to /var/tmp/portage/sys-apps/debianutils-3.1.3/work
* Applying debianutils-2.31-no-bs-namespace.patch ... [ ok ]
>>> Source unpacked in /var/tmp/portage/sys-apps/debianutils-3.1.3/work
>>> Compiling source in /var/tmp/portage/sys-apps/debianutils-3.1.3/work/debianutils-3.1.3 ...
/usr/lib/portage/bin/ebuild.sh: line 2124: 27975 Bus error ( exec 9>&-; ebuild_main; if ! hasq "$EBUILD_SH_ARGS" clean help info nofetch; then
umask 002; save_ebuild_env | filter_readonly_variables > "$T/environment"; chown portage:portage "$T/environment" >&/dev/null; chmod g+w "$T/environment" >&/dev/null;
fi; exit 0 )
* The ebuild phase 'compile' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
>>> Failed to emerge sys-apps/debianutils-3.1.3, Log file:
>>> '/var/tmp/portage/sys-apps/debianutils-3.1.3/temp/build.log'
mercury linux # emerge sed
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/sed-4.2
* sed-4.2.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking sed-4.2.tar.bz2 to /var/tmp/portage/sys-apps/sed-4.2/work
* Applying sed-4.1.5-alloca.patch ... [ ok ]
>>> Source unpacked in /var/tmp/portage/sys-apps/sed-4.2/work
>>> Compiling source in /var/tmp/portage/sys-apps/sed-4.2/work/sed-4.2 ...
/usr/lib/portage/bin/ebuild.sh: line 2124: 28219 Bus error ( exec 9>&-; ebuild_main; if ! hasq "$EBUILD_SH_ARGS" clean help info nofetch; then
umask 002; save_ebuild_env | filter_readonly_variables > "$T/environment"; chown portage:portage "$T/environment" >&/dev/null; chmod g+w "$T/environment" >&/dev/null;
fi; exit 0 )
* The ebuild phase 'compile' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
>>> Failed to emerge sys-apps/sed-4.2, Log file:
>>> '/var/tmp/portage/sys-apps/sed-4.2/temp/build.log'
|
| Code: | mercury ~ # gcc-config -l
[1] sparc-unknown-linux-gnu-4.1.2 *
[2] sparc-unknown-linux-gnu-4.3.2
[3] sparc64-unknown-linux-gnu-4.1.2
[4] sparc64-unknown-linux-gnu-4.3.3 *
|
Might the mismatch between GCC versions be a factor? If so, how do I recover given that emerge is dying?
| Code: | mercury ~ # emerge --info
Portage 2.1.6.13 (default/linux/sparc/2008.0, gcc-4.1.2, glibc-2.8_p20080602-r1, 2.6.20-gentoo-r4 sparc64)
=================================================================
System uname: Linux-2.6.20-gentoo-r4-sparc64-sun4u-with-glibc2.0
Timestamp of tree: Sat, 18 Jul 2009 06:45:02 +0000
app-shells/bash: 3.2_p39
dev-lang/python: 2.4.6, 2.5.4-r2
dev-python/pycrypto: 2.0.1-r6
sys-apps/baselayout: 1.12.11.1
sys-apps/sandbox: 1.6-r2
sys-devel/autoconf: 2.13, 2.63
sys-devel/automake: 1.7.9-r1, 1.9.6-r2, 1.10.2
sys-devel/binutils: 2.18-r3
sys-devel/gcc-config: 1.4.1
sys-devel/libtool: 1.5.26
virtual/os-headers: 2.6.27-r2
ACCEPT_KEYWORDS="sparc"
CBUILD="sparc-unknown-linux-gnu"
CFLAGS="-O2 -mcpu=ultrasparc -pipe"
CHOST="sparc-unknown-linux-gnu"
CONFIG_PROTECT="/etc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-O2 -mcpu=ultrasparc -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="http://gentoo.osuosl.org/ http://ftp.ucsb.edu/pub/mirrors/linux/gentoo/"
LDFLAGS="-Wl,-O1"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"
USE="acl apache2 bash-completion berkdb bzip2 clearpasswd cli cracklib crypt cups dri fortran ftp gcc64 gdbm gpm hal iconv imap isdnlog jpeg jpeg2k libwww mbox memlimit midi mime mudflap ncurses nls nptl nptlonly openmp pam pcre perl php png posix pppd python readline reflection samba session sharedmem sockets sparc spell spl ssl sysfs syslog sysvipc tcpd threads tiff truetype unicode xinetd xml xorg zlib" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES=" access actions alias asis auth auth_anon auth_basic auth_dbm auth_digest authn_anon authn_dbd authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache case-filter-in case_filter cern-meta cgi cgid charset-lite dav dav-fs dav_fs dav_lock dbd deflate dir disk-cache disk_cache echo env expires ext-filter ext_filter file-cache file_cache filter headers ident imagemap imap include info log_config logio mem-cache mem_cache mime mime-magic mime_magic negotiation proxy proxy-connect proxy-ftp proxy-http proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so speling status unique-id unique_id userdir usertrack vhost-alias vhost_alias " ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="fbdev glint mach64 mga r128 radeon sunbw2 suncg14 suncg3 suncg6 sunffb sunleo tdfx voodoo"
Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
|
I have not upgraded any packages in the last week, and these problems just started happening a couple of days ago. Given that bus errors are generally due to programming bugs in aligning data, how likely is this to be a hardware-related problem?
I am a little reluctant to try rebooting at the moment.
Any suggestions for how to recover from this? I do have another sparc64 box, but it's not at all the same versions of packages. For example, it is still on gcc-3.4.6
Thanks for any help. |
|
| Back to top |
|
 |
armin76
Retired Dev
Joined: 24 Apr 2006
Posts: 174
|
| Posted: Sat Oct 03, 2009 6:09 pm Post subject: |
|
|
| Thats kinda strange...i can see you're using stable, and i can tell you that definitely it works okay for me. |
|
| Back to top |
|
|
jhardin
n00b
Joined: 12 Oct 2005
Posts: 59
|
| Posted: Sat Oct 03, 2009 7:17 pm Post subject: |
|
|
I'm beginning to think there are marginal spots on my root filesystem. I'll emerge glibc or ncurses or something else, and after a few days one or two binary files in the package start failing "equery k" checks. Hopefully it's not the drive that's dying...
Anyway, I'm fortunate enough to have another Gentoo SPARC box that I can copy glibc from if it rots. That let me recover enough to be able to run emerge. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gentoo on Sparc
