Tonight I was installing some packages and I got the already known Smart freeze on my Suse 10.0 box. After this: 8:Installing autoconf ################################################################### [ 47%] It freezes. Then I went to another terminal: # strace -f -p 23016 (...) [pid 23070] read(12, 0xbc6b904, 16384) = -1 EAGAIN (Resource temporarily unavailable) [pid 23070] futex(0xbac12f0, FUTEX_WAKE, 1) = 0 [pid 23070] futex(0xbad2f70, FUTEX_WAKE, 1) = 0 [pid 23070] futex(0xbac12f0, FUTEX_WAKE, 1) = 0 [pid 23070] select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout) [pid 23070] futex(0xbac12f0, FUTEX_WAKE, 1) = 0 [pid 23070] futex(0xbac12f0, FUTEX_WAKE, 1) = 0 [pid 23070] read(12, 0xbc6b904, 16384) = -1 EAGAIN (Resource temporarily unavailable) (...) This error repeated over and over for about 30 minutes. After long time waiting, I got this: --- SIGSTOP (Stopped (signal)) @ 0 (0) --- --- SIGSTOP (Stopped (signal)) @ 0 (0) --- And the smart term shows: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/smart/backends/rpm/pm.py", line 253, in _rpmoutthread time.sleep(1) IOError: [Errno 514] Unknown error 514 Then it freezes again, but strace stops and nothing shows after that. I can reproduce it. Whenever I try to install this set of packages: autoconf-2.59-82@i586 libstdc++-devel-4.0.2_20050901-3@i586 automake-1.9.6-2@i586 ncurses-devel-5.4-71@i586 bison-1.875-56@i586 pkgconfig-0.19-6@i586 ctags-2004.11.15-4@i586 slang-devel-1.4.9-127@i586 flex-2.5.4a-297@i586 task-c++-devel-100-1.netmask.suse100@noarch gcc-4.0.2_20050901-3@i586 task-c-devel-100-1.netmask.suse100@noarch gcc-c++-4.0.2_20050901-3@i586 texinfo-4.8-9.2@i586 glib2-devel-2.8.4-3@i586 zlib-devel-1.2.3-3@i586 glibc-devel-2.3.5-40@i686 Unfortunately it freezes randomly. Each time I run this transaction it freezes on a different package. Also, note that task-c-devel and task-c ++-devel don't really exist, they're just two packages I'm porting from Conectiva. Does this help on something? Can someone have an idea of what's going on here? If I understand correctly, it was waiting for an external thread (in this case an rpm thread) that never ended (or did, but smart couldn't see it). # rpm -q smart rpm rpm-python smart-0.40-12.guru.suse100 rpm-4.1.1-222 rpm-python-4.1.1-222 -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % TI+Telecom Analyst <> Linux Specialist % http://mteixeira.webset.net <> http://pmping.sf.net % [D0CE 6BD4 526B B7D1 6F4E 85FA A7A0 1A6F B23A A9EE]