similar to: CESA-2018:1651 Important CentOS 6 kernel Security Update

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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

Brian, Sorry I forgot to switch to plain text. The link is: https://bugs.centos.org/view.php?id=15186# Ed On Saturday, September 8, 2018, 9:56:25 PM EDT, nschehovin--- via CentOS <centos at centos.org> wrote: Brian, There is a kernel bug that seems to affect systems with older Intel processors.? I have a Dell Laptop that on bootup of kernel 2.6.32-754.3.5.el6.x86_64 will

Brian, There is a kernel bug that seems to affect systems with older Intel processors.? I have a Dell Laptop that on bootup of kernel 2.6.32-754.3.5.el6.x86_64 will display a white square in the upper left corner of the screen and halt.? If I roll back to the 2.6.32-696.30.1.el6.x86_64 version kernel all is well. More info at 0015186: Cannot boot with kernel-2.6.32-754.3.5.el6.x86_64 - CentOS

Thank you for your reply, Ed. Do you know if this issue affects CentOS 7.5 and kernels 3.10.0-862? I'm thinking of upgrading to 7.5 in order to support a meteorological project I'm working on. Brian On Sat, Sep 8, 2018 at 10:07 PM, nschehovin--- via CentOS <centos at centos.org > wrote: > Brian, > > Sorry I forgot to switch to plain text. > > The link is: >

Hello, Ever since I updated my CentOS 6 machine from 6.9 to 6.10 Xorg will not start with the 2.6.32-754 kernels. Instead the computer will reboot. This issue does not exist with the 2.6.32-696.30.1 kernel from CentOS 6.9 that I still have on my system. Has anyone else encountered this issue, and if so, how did you rectify it? Thank you for any help. Brian Bernard

I just spent a while trying to debug some weird slowdown issues, and I thought I?d let the mailing list know in case it helps anyone else, or someone has a cleaner solution (or better ways of debugging the real issue). Just by way of context, we have a cluster using Infiniband and CentOS 6 (up to the latest patches as of a couple weeks ago, so 6.9+anything newer) and OpenMPI 3.1.0. Most of the

Restarting one of our named services produces this entry in the system log file: Oct 12 08:47:45 inet08 setroubleshoot: SELinux is preventing /usr/sbin/named from search access on the directory . For complete SELinux messages. run sealert -l 9eabadb9-0e03-4238-bdb8-c5204333a0bf Checking the selinux incident reference shows this: # sealert -l 9eabadb9-0e03-4238-bdb8-c5204333a0bf SELinux is

Hi, # dovecot --version 2.3.3 (dcead646b) # doveinfo Nombre d'utilisateurs : 1151 Sockets IMAP : 4356 Process dovecot/imap : 4357 Process dovecot/imap-login : 1339 Process dovecot/pop3 : 0 Process dovecot/pop3-login : 0 Process dovecot/auth : 1 Process dovecot/auth -w : 2 Process dovecot/anvil : 1 Process

Our domain controllers have run samba 4.4.3 since it was released. We didn't upgrade because it was so stable :) I recently decided that release was too old and upgraded to 4.8.2 (then current). Our domain controllers were crashing on 4.8.2 so I upgraded to 4.8.3 as soon as it was released but this has not resolved the issue. When the issue occurs the DC becomes unresponsive and needs to be

CentOS Errata and Security Advisory CESA-2009:1651 ntp security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2009-1651.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/ntp-4.1.2-6.el3.i386.rpm source: updates/SRPMS/ntp-4.1.2-6.el3.src.rpm You may update your CentOS-3 i386 installations by running the command:

CentOS Errata and Security Advisory CESA-2009:1651 ntp security update for CentOS 3 x86_64: https://rhn.redhat.com/errata/RHSA-2009-1651.html The following updated file has been uploaded and is currently syncing to the mirrors: x86_64: updates/x86_64/RPMS/ntp-4.1.2-6.el3.x86_64.rpm source: updates/SRPMS/ntp-4.1.2-6.el3.src.rpm You may update your CentOS-3 x86_64 installations by running the

CentOS Errata and Bugfix Advisory 2019:1651 Upstream details at : https://access.redhat.com/errata/RHBA-2019:1651 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7afc466120f71f6ba450a9731f9290b69180a1c7b2d8f5e339d1ea4334940289 kernel-2.6.32-754.17.1.el6.i686.rpm

Concerns: R 1.5.0 gui version, Windows (downloaded binary) and Linux (installed from sources). # Load the data from the attached file: kk<-read.table("__filename__", header=1) # attach the data: attach(kk) Snr<-factor(Snr) # fool around with a call to anova.glm(): anova.glm( aov( nFD~Type+size+Modality+Error(Snr/(Type+size+Modality)) ) ) # Error: object nFD not found # Well, I

https://bugzilla.mindrot.org/show_bug.cgi?id=1651 Summary: Possible race condition using local port forwarding with short lived connections Product: Portable OpenSSH Version: 5.2p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh

https://bugzilla.redhat.com/show_bug.cgi?id=1586278 The above bug addresses? a kernel panic if you have a CentOS 7 KVM/QEMU/Libvirt host server running CentOS 6 VMs on an AMD processor machine. If you get this kernel panic: PANIC: early exception 0d rip 10:ffffffff810462b6 error 0 cr2 0 The fix is to change the CentOS 6 VM CPU Type from Opteron_G5 (the default) to Opteron_G3. This was

Hi, we are having a problem with NFS using RDMA protocol over our FDR10 Infiniband network. I previously wrote to NFS mailing list about this, so you may find our discussion there. I have taken some load off the server which was using NFS for backups, and converted it to use SSH, but we are still having critical problems with NFS clients losing connection to the server, causing the clients