similar to: CentOS-announce Digest, Vol 145, Issue 6

CentOS Errata and Enhancement Advisory 2017:0518 Upstream details at : https://rhn.redhat.com/errata/RHEA-2017-0518.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ed979c3e0264765971802dcf126c98649e278f5c5fddd224d72e80b461826169 kmod-redhat-megaraid_sas-07.700.00.00-rh1.el7_3.x86_64.rpm Source:

CentOS Errata and Security Advisory 2017:0498 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0498.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d845221ad2fdad1633ee7d41dfaa75654c0297b15d097a5a86548cd0377f91c7 thunderbird-45.8.0-1.el5.centos.i386.rpm x86_64:

CentOS Errata and Security Advisory 2017:0498 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0498.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a0b3b41571f8e3bcd493b4e7eb723f6fb71e6a34ffa76411937bcdb12e89a0d6 thunderbird-45.8.0-1.el7.centos.x86_64.rpm Source:

Hello, I noticed the default megaraid_sas driver version in upstream Linux 2.6.32.25 is pretty old, version 4.01, and it seems to be very buggy. It fails to bring up disks and boot fails. Many people have reported this issue on various hardware using LSI RAID adapters, and on various Dell servers (R310/R410/R510/R710) using Dell PERC H700 RAID adapters (which are rebranded LSI adapters).

Hello, I noticed the default megaraid_sas driver version in upstream Linux 2.6.32.25 is pretty old, version 4.01, and it seems to be very buggy. It fails to bring up disks and boot fails. Many people have reported this issue on various hardware using LSI RAID adapters, and on various Dell servers (R310/R410/R510/R710) using Dell PERC H700 RAID adapters (which are rebranded LSI adapters).

CentOS Errata and Security Advisory 2017:0498 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0498.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0692c96015dfc1686339c2ee2ec069b28d368e34384fdbd0e7e8b0d096a4a29f thunderbird-45.8.0-1.el6.centos.i686.rpm x86_64:

Hi List, I''ve testet a bunch of kernel- and module versions with megaraid_sas and xen for months now. With 2.6.18.8 kernel and v00.00.03.01 megaraid_sas module there seem to be sometimes strange and unreproduceable segmentation faults up to kernel panics under heave i/o load. With 2.6.24-19-xen kernel from Ubuntu and v00.00.03.10 megaraid_sas it seemed stable. But I was able to

Hi to all I have a supermicro server with LSI 3108 with - 2x300GB SAS spin drive in raid1 (virtual drive 0) - 2x300GB SAS spin drive in raid1 (virtual drive 1) - 2x200GB Intel SSD DC S3710 drives configured as JBOD in LSI bios In the IPMI storage health status eveything looks fine until I boot into Centos 7.1 (unfortunatelly I didn't try other OS, but also I'm not interested in other)

CentOS Errata and Enhancement Advisory 2014:0893 Upstream details at : https://rhn.redhat.com/errata/RHEA-2014-0893.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ba8d66aa82c1aabaf23f0635284306d4715a9580baea9ceded32ba4887cb882e kmod-megaraid_sas-06.803.01.00_rh1-1.el6_5.i686.rpm x86_64:

Hi all, this patchset implements an emulation for the megaraid_sas HBA. It provides emulates an LSI MegaRAID SAS 8708EM2 HBA, ie presenting to the guest a virtual SCSI adapter. Internally it is using aio for read/write requests and either SG_IO or SCSI command emulation for everything else. The reason for choosing the megaraid_sas HBA and not, say, implementing a virtio scsi interface is

Hi all, this patchset implements an emulation for the megaraid_sas HBA. It provides emulates an LSI MegaRAID SAS 8708EM2 HBA, ie presenting to the guest a virtual SCSI adapter. Internally it is using aio for read/write requests and either SG_IO or SCSI command emulation for everything else. The reason for choosing the megaraid_sas HBA and not, say, implementing a virtio scsi interface is

I have installed the xen 3.1.0 x86_64 tarball compiled for RHEL5 on a RHEL5 system. The system in question was able to boot with the xen kernel that came with RHEL5. I untarred the tarball, and did cd /boot mkinitrd /boot/initrd-2.6.18-xen.img 2.6.18-xen The command exited properly and made a initrd image. The machine booted with a grub.conf entry like this: title Xen 3.1.0 root

Hi all, I try to install CentOS 4.3 for X64_64 on a new Dell PowerEdge 2950. I have two problems: 1. After booting from CD I pressed 'return' to start installation (BIOS-support for USB-keyboard works). After probing the hardware my USB-Keyboard is not working anymore. Dell removed ALL PS/2-Interfaces so I have to use USB. When I start installation with 'linux noprobe' the

CentOS Errata and Enhancement Advisory 2016:1780 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1780.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3f942683663a5acf3ec76fbc4da33363451ff5778ea1da2dec382806510af15f kmod-megaraid_sas-06.811.02.00-1.el7_2.x86_64.rpm Source:

CentOS Errata and Enhancement Advisory 2018:1670 Upstream details at : https://access.redhat.com/errata/RHEA-2018:1670 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a795c66044e67414a963d7531c1ce960850b788b1cb1fe63db95ed1159f18a9c kmod-redhat-megaraid_sas-07.702.06.00_rh2_dup7.5-1.el7_5.x86_64.rpm Source:

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

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

CentOS Errata and Enhancement Advisory 2018:1670 Upstream details at : https://access.redhat.com/errata/RHEA-2018:1670 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) Source: b243c283592e002f31d604f12edbbfdd26a188f335f2751b92ad129045e79172 kmod-redhat-megaraid_sas-07.702.06.00_rh2_dup7.5-1.el7_5.src.rpm -- Johnny Hughes

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

I use xen 4.0(dom0 is suse11.sp1,2.6.32 x86_64) on Dell R710 with PERC H700 RAID adapter. --Intel(R) Xeon(R) CPU E5620 @ 2.40GHz --8 CPU cores. --Memory 64G --RAID5 4.5T When I dedicated (pin) a CPU core only for dom0 use. (I specify "dom0_max_vcpus=1 dom0_vcpus_pin" options for Xen) I got dom0 kernel panic error(pin-1-5.30.bmp) When I pin 2 core to dom0, the dom0 system can boot up,