Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 87787 - system hangs while emerge is "generating GNU info directory index"
Summary: system hangs while emerge is "generating GNU info directory index"
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: x86 Linux
: High blocker (vote)
Assignee: Portage team
Depends on:
Reported: 2005-04-03 07:49 UTC by Pim Nijdam
Modified: 2005-04-11 15:48 UTC (History)
0 users

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


Note You need to log in before you can comment on or make changes to this bug.
Description Pim Nijdam 2005-04-03 07:49:26 UTC
current situation: When doing an emerge (no matter which package), system hangs at "generating GNU info directory index"
whole story:
The admin had set ACCEPT_KEYWORDS="~x86". Only two important masked packages were installed: sysvinit and baselayout-1-11-10-r6. The admin and I have no idea why sysvinit was installed. I suggested to downgrade baselayout, but therefor sysvinit had to be removed. After cleaning sysvinit, system hanged at "generating GNU info directory index" i.e. didn't respond at keyboard or network. So we booted from a gentoo livecd, mounted gentoo, chrooted and did an emerge baselayout. Again, at "generating GNU info directory index" system hanged. However baselayout was installed. According to the logs, last proper emerge was baselayout-1-11-10-r6 and next emerge, coreutils 5-2-1-r6 terminated. 

Reproducible: Always
Steps to Reproduce:
1. emerge <package>
(even when booted from a livecd)
Actual Results:  
emerge installed the package, cleaned old packages (when needed) and printed
"Generating GNU info directory index". LED blinks, indicating io-activity. LED
turns off, system hangs.

Expected Results:  
emerge nicely

strace is not installed, installing it would mean a crash.

emerge info:
Gentoo Base System version 1.4.16
Portage (default-linux/x86/2004.0, gcc-3.3.4, glibc-,
2.6.3-gentoo-r2 i686)
System uname: 2.6.3-gentoo-r2 i686 AMD Athlon(tm) XP 1800+
Python:              dev-lang/python-2.3.4-r1 [2.3.4 (#1, Apr  3 2005, 13:22:45)]
distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ccache version 2.3 [enabled]
dev-lang/python:     2.3.4-r1
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.5, 1.8.5-r3, 1.6.3, 1.7.9-r1, 1.4_p6, 1.9.4
sys-devel/libtool:   1.5.2-r7
virtual/os-headers:  2.4.19-r1, 2.4.22
CFLAGS="-O2 -march=athlon-xp -pipe"
CONFIG_PROTECT="/etc /opt/jetty/etc /usr/X11R6/lib/X11/xkb
/usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config
/usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown
/usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/ /var/bind /var/qmail/alias /var/qmail/control
/var/vpopmail/domains /var/vpopmail/etc"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon-xp -pipe"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
USE="x86 X aalib alsa apache2 apm arts avi berkdb bitmap-fonts cdr crypt cups
curl directfb emboss encode esd fam flac font-server foomaticdb fortran gdbm ggi
gif gnome gpm gstreamer gtk gtk2 guile imagemagick imlib ipv6 jack java jpeg
junit kde ldap libg++ libwww mad mikmod motif mozilla mp3 mpeg mysql ncurses nls
nowin oggvorbis opengl oss pam pda pdflib perl png ppds python qt quicktime
readline ruby samba sdl slang spell ssl svga tcltk tcpd tetex tiff truetype
truetype-fonts type1-fonts xml xml2 xmms xv zlib"
Comment 1 SpanKY gentoo-dev 2005-04-03 09:48:49 UTC
well, you really shouldnt screw with system packages like that

bsaelayout-1.9.x included sysvinit while 1.11.x broke it into a sep package

you should verify that you didnt hose your sysvinit
Comment 2 Pim Nijdam 2005-04-11 15:48:49 UTC
After all It seemed basylayout was proper installed. Most likely it was a hardware problem for several other programs, eupdate (esearch index generator) and knoppix both hanged the system while accesing the same harddisk. Also the system admin admitted few warnings concerning the harddisk were logged in the past.

Thanks for your reply and my apologies for posting this bug-report. That ACCEPT_KEYWORDS somewhat misled me.