Bug 106848

Summary: hangs, not erasing, and more
Product: [Retired] Red Hat Linux Beta Reporter: Ted Kaczmarek <tedkaz>
Component: rpmAssignee: Jeff Johnson <jbj>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: beta1   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-10-19 11:21:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ted Kaczmarek 2003-10-11 22:16:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031003
Epiphany/1.0.1

Description of problem:
The dreaded hang is back.
rpm -q always return nothing on first attempt after a boot.
rpm -e fails, kill -9 and removing __db*'s not making a difference.
rpm --rebuilddb fails

Version-Release number of selected component (if applicable):
rpm-4.2.1-0.30 2.4.22-1.2088.nptl

How reproducible:
Sometimes

Steps to Reproduce:
1.Boot Fedora with kernel 2.4.22-1.2088.nptl
2. Open terminal, rpm -q
3. rpm -e
    

Actual Results:  Doesn't query on first attempt, erase not working and rebuilddb
not working.

Expected Results:  rpm -q works on first attempt, erase doesn't hang, rebuilddb
doesn't hang.

Additional info:

It seems work ok when erasing single packages, but multiple packages kill it
almost every time. Then after a while I can erase two packages, but then rpm -q
will fail again. I have yet to succesfully erase three packages with this
kernel/rpm version.
futex(0x403a8fb0, FUTEX_WAIT, 0, NULL

Hope this is helpful.

Comment 1 Jeff Johnson 2003-10-13 15:47:52 UTC
I need more details to even attempt a guess. AFAIK rpm is
doing the same job as always for thousands of people.

So what's different about your box?

Comment 2 Ted Kaczmarek 2003-10-19 11:21:46 UTC
After having filesystem issues and fsck'ing it, this problem has not been
happening anymore. Vlose this baby out, and I will make a note to myself to stay
away from the 2.6.0-test.X kernels :-)

Ted