similar to: Processes stuck in futex()

Be curious myself as to what info you come up with on the "upgrade via ISO" and "SATA" support questions you posed. Hopefully someone on the list will help you out with a reply to the list. JT > Message: 1 > Date: Sat, 3 Apr 2004 19:47:15 -0800 (PST) > From: Bart Schaefer <schaefer at zanshin.com> > To: centos at caosity.org > Subject: [Centos] Upgrade

The previously noted upgrade-to-4.4 recipe: yum update yum sqlite python-sqlite ; yum update worked more consistently than running "yum upgrade," but it too fell victim to the futex hang. In my limited testing, a reboot of the machine before starting the upgrade gave me a 100% success rate. Given two identical machines, one that had been used for a few days and one that was freshly

Cutting straight to the chase: When, if ever, does the installer offer an option to upgrade an existing installation, rather than wanting to reformat the disks? More details than you may want: I recently acquired a new PC chassis, with no operating system but with a Serial-ATA disk (which I was not expecting when I ordered it). I set the BIOS for legacy IDE mode and installed RedHat 9, then

Today I upgraded to 1.2.0 - and my indexing jobs are now getting hung up. They appear to be waiting on a futex. Not everyone, but every now and then. I'll try to get some diagnostics. /Per Jessen, Z?rich

> On 31 May 2018, at 06:19, via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > When I run "make check-all" with ToT I am seeing what looks like a hang > generating sanitizer tests: > > [...] > [100%] Generating dynamic/Asan-x86_64-calls-Dynamic-Test > make[3]: Leaving directory '/build/debug' > [100%] Built target

When I run "make check-all" with ToT I am seeing what looks like a hang generating sanitizer tests: [...] [100%] Generating dynamic/Asan-x86_64-calls-Dynamic-Test make[3]: Leaving directory '/build/debug' [100%] Built target TAsan-x86_64-calls-Dynamic-Test [100%] Generating default/Asan-x86_64-inline-Test make[3]: Leaving directory '/build/debug' [100%] Built target

I've got CentOS 5 installed on my hp pavilion ze 5300 laptop and the network configuration UI says my wireless NIC has been correctly identified and assigned what appears to be the right Broadcom device driver on eth1. However, the inteface doesn't come up. Google doesn't find anything recent about using Linux with Broadcom except for someone's passing remark that Ubuntu 7 beta

I'd been putting off installing the FX3 packages because of some extensions I use that don't have upgrades. [*] However, when FX1.5 crashed on me today I decided to finally go ahead. Fired up yum and I'm told I have to install a slew of evolution28 library packages in order to install the firefox package. Why? I removed evolution from my system for a reason, and I'd just as

Just to follow-up, I'm now encountering this as well. I'm doing this on Linux. It seems that when linking with the most-recently built clang, the unit tests are taking a while to complete. It's notably not using more than 1 thread, and if using `lld` I would have expected the linker to still be running in parallel. I'm doing this on a debug build, so that might help narrow it

OK, running Samba 3.0.0 on RH9 in a W2K AD environment. MIT Kerberos 1.2.7. Joined the domain with no problem, wbinfo and getent respond perfectly. I can get Kerberos tickets from the W2K domain and browse domain resources from the RH9 box, both with krb tickets and by supplying a password, although using the -k option does not display the "network neighborhood" browse list. However,

I just tried this with CentOS 5.3 as well, and got exactly the same symptoms and dmesg output. (As a point of comparison, Ubunu 8.04 on my work laptop is able to access the drive.) Obviously "not detected" is a misapprehension, though I'm puzzled why "lsusb" doesn't show it. The device is there even though the partition table can't be read. ---------- Forwarded

I'm trying to create a hook that attaches several virtio-scsi disks to a starting vm, and it seems like the hook enters a deadlock while attempting to do so. Is there any workaround around this? Any better way, forking virsh execution somehow? Could anyone explain why this is creating a deadlock in the first place? Isn't libvirt multithreaded? Thanks for the help! Shlomi ### hook

Apologies if I should ask this elsewhere, google search is not helping. I've got a CentOS5 server with lighttpd installed from EPEL, configured for https only (no connections on ports other than 443). I have the latest security updates for openssl, etc. However, when connecting to the server with recent Chrome from Windows or Android, I get the "Your connection is not private"

Most of my desktops are still running CentOS5, but I have installed CentOS6 on a few of them. The users on those desktops are reporting that DNS lookups are slow, and from my brief tests, that does appear to be the case. After some googling, I found a suggestion to disable IPv6, but that didn't help. So I tried to figure out where the delay occurs using strace and ltrace, but that

I'm testing an upgrade of an i686 production machine running 1.4.24.1 to 1.6.0.9. I've installed dahdi-linux-2.1.0.4. But: asterisk -cvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv Asterisk 1.6.0.9, Copyright (C) 1999 - 2008 Digium, Inc. and others. Created by Mark Spencer <markster at digium.com> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.

Hi all, I am using Match directive and internal-sftp to chroot sftp users into their directory. Connection and login works. I can change directories and put/get files. Also logging of the internal sftp-process works (created a /dev/log socket inside the chroot). As soon as I use the 'ls' command, nothing happens and the the process gets stuck. Listing files does work as soon as I remove

I have identical two hypervisors same operating system: Ubuntu 22.04.2 LTS Recently both virsh stopped talking to the libvirtd. Both stopped within a few days of each other. Currently if I run: virsh uri virsh version virsh list # virsh list ..nothing just hangs When I ran strace on these broken machines it get stuck at same spot: strace virsh list ...

I got file conflicts between the sysreport and sos packages on the file /usr/sbin/sysreport. I unchecked sysreport in the package updater UI and the rest of the update is proceedng.

If it wouldn't be too much trouble ... when a kernel security update notice is posted to the announcements list, would it be possible to indicate whether the centosplus kernel is also susceptible to the security issue being patched? I'm running the plus kernel now, and find myself wondering whether I will ever need to back off to the base kernel because of security issues. Or is it

Hi, i just want to ask whether somebody else has this problem of mine and if it can be solved. Many of my ( 30+ ) puppet installation freeze up after some time. The process is waiting for some private futex, but it stays like that forever. This is what strace looks like when the problem occures: [pid 29173] futex(0x3d35ce7a84, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406739,