Subject: Re: Yum futex lockup upgrading from 4.0 to 4.1 - msg#00016
List: linux.centos.devel
On Fri, 2005-06-17 at 23:34 -0400, seth vidal wrote:
>
> All my previous tests were from a fully upgraded 4.0 machine, and for
>
> those I had no trouble. With this one, a stock 4.0 machine with
>
> no upgrades, yum locked. Might be worth trying to reproduce it.
>
> Another interesting fact is that this was my only machine with SELinux
>
> active, but I'm still betting on a python/yum related problem.
>
>
And you'd lose that bet.
>
>
FUTEX lock happens between the kernel, rpm and bsddb.
>
>
go check out red hat bugzilla to look for the bugs reported on this
>
problem.
>
>
-sv
>
Here is a RH bugzilla entry:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145021
I have not specifically seen this issue yet.
I will see if I can reproduce it though.
signature.asc
Description: This is a digitally signed message part
_______________________________________________
CentOS-devel mailing list
CentOS-devel-IFYaIzF+flcdnm+yROfE0A@xxxxxxxxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos-devel
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
Re: Yum futex lockup upgrading from 4.0 to 4.1
> All my previous tests were from a fully upgraded 4.0 machine, and for
> those I had no trouble. With this one, a stock 4.0 machine with
> no upgrades, yum locked. Might be worth trying to reproduce it.
> Another interesting fact is that this was my only machine with SELinux
> active, but I'm still betting on a python/yum related problem.
And you'd lose that bet.
FUTEX lock happens between the kernel, rpm and bsddb.
go check out red hat bugzilla to look for the bugs reported on this
problem.
-sv
Previous Message by Thread:
click to view message preview
Re: Yum futex lockup upgrading from 4.0 to 4.1
> All my previous tests were from a fully upgraded 4.0 machine, and for
> those I had no trouble. With this one, a stock 4.0 machine with
> no upgrades, yum locked. Might be worth trying to reproduce it.
> Another interesting fact is that this was my only machine with SELinux
> active, but I'm still betting on a python/yum related problem.
And you'd lose that bet.
FUTEX lock happens between the kernel, rpm and bsddb.
go check out red hat bugzilla to look for the bugs reported on this
problem.
-sv