Hi, portage has freezed during 'emerge portage' emerge is eating my CPU I can not kill emerge, it doesn't respond. 'killall emerge' doesn't fix Reproducible: Always Steps to Reproduce: 1.emerge --sync 2.emerge portage 3. Actual Results: >>> Install portage-2.2_rc31 into /var/tmp/portage/sys-apps/portage-2.2_rc31/image/ category sys-apps patching file make.conf >>> Completed installing portage-2.2_rc31 into /var/tmp/portage/sys-apps/portage-2.2_rc31/image/ strip: i686-pc-linux-gnu-strip --strip-unneeded -R .comment ecompressdir: bzip2 -9 /usr/share/man >>> Installing (1 of 1) sys-apps/portage-2.2_rc31 looks like this... top outputs 6153 root 35 15 32408 28m 2844 R 99 2.9 5:34.24 emerge I can not kill emerge, it doesn't respond. 'killall emerge' doesn't fix emerge --info Portage 2.2_rc31 (default/linux/x86/2008.0, gcc-4.3.3, glibc-2.9_p20081201-r2, 2.6.29-gentoo-r1 i686) ================================================================= System uname: Linux-2.6.29-gentoo-r1-i686-Intel-R-_Core-TM-2_CPU_T5600_@_1.83GHz-with-gentoo-2.0.0 Timestamp of tree: Mon, 20 Apr 2009 13:00:01 +0000 app-shells/bash: 4.0_p17-r1 dev-lang/python: 2.5.4-r2, 2.6.2 sys-apps/baselayout: 2.0.0 sys-apps/openrc: 0.4.3-r2 sys-apps/sandbox: 1.9 sys-devel/autoconf: 2.13, 2.63-r1 sys-devel/automake: 1.5, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.19.1-r1 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6a virtual/os-headers: 2.6.28-r1 ACCEPT_KEYWORDS="x86 ~x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=core2 -mtune=generic -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-O2 -march=core2 -mtune=generic -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks fixpackages parallel-fetch preserve-libs protect-owned sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="en_US.utf8" LC_ALL="en_US.utf8" LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -Wl,--as-needed" LINGUAS="en tr" MAKEOPTS="-j3" 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" PORTDIR_OVERLAY="/usr/local/portage/layman/xfce-dev /usr/local/portage/layman/purak /usr/local/portage/layman/purak" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acl acpi alsa bzip2 cracklib crypt dbus dri expat gdbm gif gpm gtk hal iconv isdnlog jpeg midi mp3 mudflap ncurses nls nptl nptlonly openmp pam pcre perl pppd python readline reflection session slang ssl startup-notification symlink sysfs tcpd tiff truetype type1 unicode usb userlocales vcd x86 xml xorg xscreensaver xv zlib" ALSA_CARDS="snd-hda-intel" 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="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="evdev keyboard mouse synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en tr" USERLAND="GNU" VIDEO_CARDS="nv vesa nvidia" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Could you show 'dmesg | tail -n 20' and 'strace -p pid' for saw what take place when portage freezes ?
(In reply to comment #1) > Could you show 'dmesg | tail -n 20' and 'strace -p pid' for saw what take place > when portage freezes ? > unfortunately, I have been rebooted system because emerge was eating my CPU. This issue appears sometimes. I hope, it appears in the near future.
Next time that it happens, trigger the python debugger by sending the emerge process a SIGUSR1 singal: killall -s SIGUSR1 emerge At the debugger prompt, type these two lines to get a backtrace: s bt The 's' command is necessary in order to step out of the signal handler, and 'bt' displays the backtrace. Please post the backtrace.
I'll do that as soon as the problem appears next. However as described that might take a week or so...
Interestingly, after I delete, the manifest, the digest works. The Manifest hasn't changed, though. I also tried to change the timestamp of the Manifest to an older time using touch but that did not have an effect, either. Could it be that portage caches the ebuilds somewhere and the problem is in the cached ebuild?
please ignore my last two posts, I posted them in the wrong bug. Sorry!!!
Some time has passed. Please comment on this bug and reopen it if it happens again; when you do so, can you provide the instructions from Comment #3? If you can't reopen, as you are perhaps a new user; feel free to start a new bug.
