search for: 55.0.9

CentOS Errata and Security Advisory 2007:0937 https://rhn.redhat.com/errata/RHSA-2007-0937.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: kernel-2.6.9-55.0.9.EL.i586.rpm kernel-2.6.9-55.0.9.EL.i686.rpm kernel-devel-2.6.9-55.0.9.EL.i586.rpm kernel-devel-2.6.9-55.0.9.EL.i686.rpm kernel-doc-2.6.9-55.0.9.EL.noarch.rpm

Are the RPMs for the latest GFS kernel module GFS-kernel-2.6.9-72.2.0.8 to be used with the version 2.6.9-55.0.9.EL available ? I tried to compile the Source RPMs available from the Red Hat site but the modules can't be loaded because of invalid module format arising from version magic issues. The syslog shows: node0 kernel: gfs: version magic '2.6.9-55.0.9.ELsmp SMP 686 REGPARM

CentOS Errata and Security Advisory 2007:0937 https://rhn.redhat.com/errata/RHSA-2007-0937.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: kernel-2.6.9-55.0.9.EL.x86_64.rpm kernel-devel-2.6.9-55.0.9.EL.x86_64.rpm kernel-doc-2.6.9-55.0.9.EL.noarch.rpm kernel-largesmp-2.6.9-55.0.9.EL.x86_64.rpm kernel-largesmp-devel-2.6.9-55.0.9.EL.x86_64.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

I've got a Centos 4 box at work, where I noticed a pile of old kernels lying around and no longer needed. I did "rpm -qa | grep -y kernel > list" then edited the list to remove from it the newer kernels, then "yum remove `cat list`". Yum has come up with a list of 71 packages it wants to remove, even though there were only 33 kernel-related RPMs in the list. this

Anyone had any success with or hints for a system based on the Asus P5B-VM DO board, or the Intel Q965 (with its associated Intel GMA 3000 VGA chip) in general? I had to put pci=nommconf in order to get the installer (CentOS 4.5) and the installed system to boot, but I can't get the graphics to work. Following the instructions at the Intel website

CentOS Errata and Security Advisory 2007:0937 https://rhn.redhat.com/errata/RHSA-2007-0937.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/kernel-2.6.9-55.0.9.EL.ia64.rpm updates/ia64/RPMS/kernel-devel-2.6.9-55.0.9.EL.ia64.rpm updates/ia64/RPMS/kernel-largesmp-2.6.9-55.0.9.EL.ia64.rpm

CentOS Errata and Security Advisory 2007:0937 https://rhn.redhat.com/errata/RHSA-2007-0937.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/kernel-2.6.9-55.0.9.EL.s390.rpm updates/s390/RPMS/kernel-devel-2.6.9-55.0.9.EL.s390.rpm s390x: updates/s390x/RPMS/kernel-2.6.9-55.0.9.EL.s390x.rpm

Hi all, Same system as my previous mail - Asus P5N32-E SLI motherboards, CentOS 4 x86_64. The kernel-supplied forcedeth driver works in kernel-smp-2.6.9-55.0.9.EL (both with and without acpi=off), but after upgrading to kernel-smp-2.6.9-67.0.4.EL, networking does not start. After trying dhcp, ifconfig reports 17 dropped TX packets (all other counters are empty). Ethtool reports the same

# rpm -qa | grep kernel-2 | sort kernel-2.6.9-42.0.10.EL kernel-2.6.9-42.0.2.EL kernel-2.6.9-42.0.3.EL kernel-2.6.9-42.0.8.EL kernel-2.6.9-42.EL kernel-2.6.9-55.0.2.EL kernel-2.6.9-55.0.6.EL kernel-2.6.9-55.0.9.EL kernel-2.6.9-55.EL I'm running the most recent kernel available, and I've never had a problem with any past kernels, so I don't believe there's any reason to keep all of

I have this old memory that the kernels used are a hodge podge of backports etc. So for a kernel-smp-2.6.9-55.0.9.EL should I use 0.4.10? Quoted from http://ivtvdriver.org/index.php/Download: The latest stable releases can be found here. Currently this is version 0.4.10 for kernels <= 2.6.15, version 0.6.7 for kernel 2.6.16, version 0.7.4 for kernel 2.6.17, version 0.10.6 for kernels >=

Hi, I''m seeing what can only be described as dismal striped write performance from lustre 1.6.3 clients :-/ 1.6.2 and 1.6.1 clients are fine. 1.6.4rc3 clients (from cvs a couple of days ago) are also terrible. the below shows that the OS (centos4.5/5) or fabric (gigE/IB) or lustre version on the servers doesn''t matter - the problem is with the 1.6.3 and 1.6.4rc3 client kernels

I''m seeing this error message on one of my OSS''s but not the other three. Any idea what is causing it? Oct 25 13:58:56 oss2 kernel: LustreError: 3228:0:(client.c:519:ptlrpc_import_delay_req()) @@@ IMP_INVALID req at f6b13200 x18040/t0 o101->MGS at MGC192.168.0.200@tcp_0:26 lens 176/184 ref 1 fl Rpc:/0/0 rc 0/0 Oct 25 13:58:56 oss2 kernel: LustreError:

Hi all, I'm having issue with my Centos 5.1 /Xen installation. I'm having 2 dom0 running 2.6.18-53.1.4.el5xen (x86_64). These two dom0 are connected to a SAN. These two dom0 hosts multiple domU like Centos 4.5 (2.6.9-55.0.9.ELxenU) and Centos 5.1 (2.6.18-53.1.4.el5xen). These two dom0 run ntpd to synchronize dom0 time. When i start a virtual machine on the first dom0 all seems good, the

Hi, Our environment is: 2.6.9-55.0.9.EL_lustre.1.6.3smp I am getting following errors from two OSS''s ... Nov 7 10:39:51 storage09.beowulf.cluster kernel: LustreError: 23045:0:(client.c:519:ptlrpc_import_delay_req()) @@@ IMP_INVALID req at 00000100b410be00 x4190687/t0 o101->MGS at MGC10.143.245.201@tcp_0:26 lens 232/240 ref 1 fl Rpc:/0/0 rc 0/0 Nov 7 10:39:51

Hi, Our lustre environment is: 2.6.9-55.0.9.EL_lustre.1.6.3smp I would like to change recovery timeout from default value 250s to something longer I tried example from manual: set_timeout <secs> Sets the timeout (obd_timeout) for a server to wait before failing recovery. We performed that experiment on our test lustre installation with one OST. storage02 is our OSS [root at

Hi, We currently have an CentOS 4.5 running Ultra Monkey box serving web requests to two real servers. Info as below : ipvsadm-1.24-6 heartbeat-2.1.2-3.el4.centos CentOS 4.5(kernel-smp-2.6.9-55.0.6.EL) All was working fine this morning until I upgraded our OS and patched the kernel to kernel-smp-2.6.9-55.0.9.EL via YUM(CESA-2007:0937). After that users started complaining that they were

Hello, I have a question concerning the performance of rsync beteen two sites, one in India one in Germany. File exchange between 2 Linux-machines is done using rsync-3.0.5 (typical file size 1.5 GB). Destination machine is: Linux machine1 2.6.9-55.0.9.ELsmp #1 SMP Tue Sep 25 02:16:15 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux Source machine is: Linux machine2 2.6.18-53.el5 #1 SMP Wed Oct 10

Does anyone know if there is a fix for nscd segfaulting after a short period of time. Googling for it came up with one result that suggested deleting the files in /var/db/nscd , but that didn't help. Another result was about run away processes which is not the problem I'm having. They are x86_64 boxes. output from /var/log/messages Oct 9 12:56:38 lyra kernel: nscd[11660]: segfault at

This morning I''ve had both my infiniband and tcp lustre clients hiccup. They are evicted from the server presumably as a result of their high load and consequent timeouts. My question is- why don''t the clients re-connect. The infiniband and tcp clients both give the following message when I type "df" - Cannot send after transport endpoint shutdown (-108). I''ve