similar to: CentOS-announce Digest, Vol 134, Issue 12

CentOS Errata and Enhancement Advisory 2016:0683 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-0683.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 648b5c1c0dc0890ee3194aad413b0d952e28cc0325247548f24092d2cfef222a tzdata-2016d-1.el6.noarch.rpm

CentOS Errata and Enhancement Advisory 2016:0682 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-0682.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: beb8bae27284f3d614fc06a783956a67bdf4954962014a9e79e6dca337a4d65f kmod-qla2xxx-8.07.00.26.06.8_k-1.el6_7.i686.rpm x86_64:

CentOS Errata and Enhancement Advisory 2016:0683 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-0683.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 54d05bf911d8ee5756581ca4a6f680a17331a8ad81a78a4c2fab444eef4ae4a4 tzdata-2016d-1.el5.i386.rpm

CentOS Errata and Enhancement Advisory 2016:0683 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-0683.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 57d7e4c3f03b35ab0b95808de779bede15909718a3a3c09637ec82e9eb9ad53d tzdata-2016d-1.el7.noarch.rpm

I wanted to post this in case there is a real bug here. The system this is on is running Debian Etch with the Xen packages from Debian Unstable (currently 3.0.2+hg9697-1). I am running all packaged software so this is probably slightly out of date. This is on an HP DL320 G4 with a Pentium D 930 processor. I tried unloading and reloading the qla2xxx module, but rmmod reported it in use, however

> I wanted to post this in case there is a real bug here. > > The system this is on is running Debian Etch with the Xen packages from > Debian Unstable (currently 3.0.2+hg9697-1). I am running all packaged > software so this is probably slightly out of date. It would be interesting to see if this can be repro''ed on a tree built from a recent xen-unstable.hg.

I am trying to dedicate a number of PCI ports to DomU and no success! The PCI devices I am trying to dedicate are QLogic 23xx cards! I am using SUSE 10.1 with latest xen-unstable! I have followed all the instructions given in latest xen 3.0 manual. Like building the backend support in Dom0 Building the frontend support in DomU Using the pciback.hide=(xx:xx.x) in Dom0 command

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

Maybe one of you has experienced something like this before. I have a host running CentOS5.3, x86_64 version with the standard qla2xxx driver. Both ports are recognized and show output in dmesg but they never find my storage device: qla2xxx 0000:07:00.1: LIP reset occured (f700). qla2xxx 0000:07:00.1: LIP occured (f700). qla2xxx 0000:07:00.1: LIP reset occured (f7f7). qla2xxx 0000:07:00.0: LOOP

In waiting, I tried CentOS 8 which was an even bigger bust. I wiped that clean and tried again with Fedora 31. Same darn error "Could not create Target in configFS". Anyone?? Thank you, Steffan Cline steffan at hldns.com 602-793-0014 ?On 1/2/20, 2:00 AM, "CentOS on behalf of Steffan Cline via CentOS" <centos-bounces at centos.org on behalf of centos at centos.org>

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

On Tue, 2018-05-15 at 09:00 -0700, Matthew Wilcox wrote: > diff --git a/drivers/scsi/qla2xxx/qla_target.c b/drivers/scsi/qla2xxx/qla_target.c > index 025dc2d3f3de..cdf671c2af61 100644 > --- a/drivers/scsi/qla2xxx/qla_target.c > +++ b/drivers/scsi/qla2xxx/qla_target.c > @@ -3719,7 +3719,8 @@ void qlt_free_cmd(struct qla_tgt_cmd *cmd) > return; > } >

On Tue, 2018-05-15 at 09:00 -0700, Matthew Wilcox wrote: > diff --git a/drivers/scsi/qla2xxx/qla_target.c b/drivers/scsi/qla2xxx/qla_target.c > index 025dc2d3f3de..cdf671c2af61 100644 > --- a/drivers/scsi/qla2xxx/qla_target.c > +++ b/drivers/scsi/qla2xxx/qla_target.c > @@ -3719,7 +3719,8 @@ void qlt_free_cmd(struct qla_tgt_cmd *cmd) > return; > } >

This is a really long email...my apologies. Hardware platform: Dell Poweredge 1855 (blade), Dual Xeon 2.8 GHz; 12 MB RAM; PERC 4/IM; mirrored 73 GB U320 SCSI; qLogic 2312 PCI Fibre Channel HBAs. OS: (currently) CentOS 4.3, gcc 3.4.5 Software: Xen 3.0.2-2 Attempting to boot off local SCSI RAID (mirror)...not the SAN. I am more of a Solaris person, so forgive me if I don''t know all

hi All, Re below - thanks for the replies to the fsck question. I have run fsck -r /data and this eventually completed with several changes made. Now I am getting the following error from the qla2xxx driver on boot . . . qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort. qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort. . etc . It looks

On Tue, 2018-06-12 at 09:15 -0700, Matthew Wilcox wrote: > On Tue, Jun 12, 2018 at 03:22:42PM +0000, Bart Van Assche wrote: > > On Tue, 2018-05-15 at 09:00 -0700, Matthew Wilcox wrote: > > > diff --git a/drivers/scsi/qla2xxx/qla_target.c b/drivers/scsi/qla2xxx/qla_target.c > > > index 025dc2d3f3de..cdf671c2af61 100644 > > > ---

On Thu, Dec 08, 2016 at 06:38:11AM +0000, Bart Van Assche wrote: > On 12/07/16 21:54, Michael S. Tsirkin wrote: > > On Thu, Dec 08, 2016 at 05:21:47AM +0000, Bart Van Assche wrote: > >> Additionally, there are notable exceptions to the rule that most drivers > >> are endian-clean, e.g. drivers/scsi/qla2xxx. I would appreciate it if it > >> would remain possible

On Tue, Jun 12, 2018 at 03:22:42PM +0000, Bart Van Assche wrote: > On Tue, 2018-05-15 at 09:00 -0700, Matthew Wilcox wrote: > > diff --git a/drivers/scsi/qla2xxx/qla_target.c b/drivers/scsi/qla2xxx/qla_target.c > > index 025dc2d3f3de..cdf671c2af61 100644 > > --- a/drivers/scsi/qla2xxx/qla_target.c > > +++ b/drivers/scsi/qla2xxx/qla_target.c > > @@ -3719,7 +3719,8

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

On 12/07/16 21:54, Michael S. Tsirkin wrote: > On Thu, Dec 08, 2016 at 05:21:47AM +0000, Bart Van Assche wrote: >> Additionally, there are notable exceptions to the rule that most drivers >> are endian-clean, e.g. drivers/scsi/qla2xxx. I would appreciate it if it >> would remain possible to check such drivers with sparse without enabling >> endianness checks. Have you