From robert.j.woodruff at intel.com Thu Feb 26 11:05:49 2009 From: robert.j.woodruff at intel.com (Woodruff, Robert J) Date: Thu, 26 Feb 2009 11:05:49 -0800 Subject: [Wwg] RE: Sun is asking for a response on Bug No.s 1522, 1523 In-Reply-To: References: <1235592409.22158.80.camel@pc.interlinx.bc.ca> <897D8E97-60A7-4FCB-BD6A-45228C3B4912@Sun.COM> Message-ID: <382A478CAD40FA4FB46605CF81FE39F41F1BFD66@orsmsx507.amr.corp.intel.com> Bill, since the bug was submitted as P3 and normal, rather than P1 as critical or blocker, it was probably overlooked as something that had to be fixed in 1.4. I changed the bug to a blocker P1 bug for OFED 1.4.1, and thus should show up on the bug tracking list that gets reviewed in the EWG. In addition to enterring the bug into bugzilla, people may also want to send an email to the maintaner for blocker bugs, so that they know it needs quick attention. It is asigned to Jeff Becker, the NFS/RDMA maintainer. I know that there were some issues with backports for NFS/RDMA in 1.4 and believe he is trying to get these fixed for OFED 1.4.1. woody ________________________________ From: Bill Boas [mailto:Bill.Boas at openfabrics.org] Sent: Thursday, February 26, 2009 10:06 AM To: general at lists.openfabrics.org; ewg at lists.openfabrics.org; wwg at lists.openfabrics.org Cc: 'Peter Jones'; 'Brian J. Murrell'; 'Makia Minich'; Bryon.Neitzel at Sun.COM Subject: Sun is asking for a response on Bug No.s 1522, 1523 Dear OFA Maintainers: Sun has contacted me about these bugs and is asking for priority action to get fixes for them. See the thread below. I'm sending this email to 3 OFA lists because Sun having to contact the Alliance this way raises many questions about how a vendor like Sun or a customer like, say, a Wall St bank gets bugs fixed and where do we, the OFA, publish this information? And if we agree that an OFA maintainer is the right person to fix the bug how does that maintainer learn that and how do they respond? Thank you for responding to this email and to the Sun team using OFED in their products. Bill. Bill Boas Executive Director and Vice Chair OpenFabrics Alliance 510-375-8840 Bill.Boas at openfabrics.org www.openfabrics.org ________________________________ From: Bryon.Neitzel at Sun.COM [mailto:Bryon.Neitzel at Sun.COM] Sent: Wednesday, February 25, 2009 12:20 PM To: Bill Boas Cc: Peter Jones; Brian J. Murrell; Makia Minich Subject: Fwd: OFED 1.4 for NHM chips Hi Bill, I found the bug numbers for the Lustre build issues against OFED 1.4.0 that I mentioned yesterday. Is there any way to bump up the priority on these? This is blocking our ability to deliver our new Vayu (Nehalem+QDR) hardware to our customers, since Mellanox says they'll only support OFED 1.4 with QDR hardware. Thanks, Bryon Begin forwarded message: From: "Brian J. Murrell" > Date: February 25, 2009 1:06:49 PM MST To: Bryon Neitzel > Cc: Peter Jones > Subject: Re: OFED 1.4 for NHM chips On Wed, 2009-02-25 at 12:59 -0700, Bryon Neitzel wrote: Hi Brian, what is the website where these OFED bugs were filed? https://bugs.openfabrics.org/show_bug.cgi?id=1522 https://bugs.openfabrics.org/show_bug.cgi?id=1523 Bill Boas tried to find any OFED bugs opened by Sun yesterday, Yeah. I opened them a number of days ago. Not sure if it matters to anyone, but IMHO, 1523 is the correct future direction and fixing that would implicitly fix 1522. 1523 basically describes separating the "technology preview" that caused this breakage out into it's own independent module so that it does not pollute the OFED core. As such, it might be resisted as it's a "deeper cut" type of fix, but one that removes the sick part rather than trying to continue to bandage it. b. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jeffrey.C.Becker at nasa.gov Thu Feb 26 13:12:38 2009 From: Jeffrey.C.Becker at nasa.gov (Jeff Becker) Date: Thu, 26 Feb 2009 13:12:38 -0800 Subject: [Wwg] Re: Sun is asking for a response on Bug No.s 1522, 1523 In-Reply-To: <382A478CAD40FA4FB46605CF81FE39F41F1BFD66@orsmsx507.amr.corp.intel.com> References: <1235592409.22158.80.camel@pc.interlinx.bc.ca> <897D8E97-60A7-4FCB-BD6A-45228C3B4912@Sun.COM> <382A478CAD40FA4FB46605CF81FE39F41F1BFD66@orsmsx507.amr.corp.intel.com> Message-ID: <49A705C6.3090605@nasa.gov> Hi Woodruff, Robert J wrote: > Bill, since the bug was submitted as P3 and normal, > rather than P1 as critical or blocker, it was probably overlooked as > something > that had to be fixed in 1.4. I changed the bug to a blocker P1 bug for > OFED 1.4.1, > and thus should show up on the bug tracking list that gets reviewed in > the EWG. > > In addition to enterring the bug into bugzilla, people may also want > to send > an email to the maintaner for blocker bugs, so that they know it needs > quick > attention. It is asigned to Jeff Becker, the NFS/RDMA maintainer. > I know that there were some issues with backports for NFS/RDMA in 1.4 and > believe he is trying to get these fixed for OFED 1.4.1. I'm currently finishing up the SLES11 backports for OFED, and I'll work on this when I'm done. Thanks. -jeff > > woody > > > ------------------------------------------------------------------------ > *From:* Bill Boas [mailto:Bill.Boas at openfabrics.org] > *Sent:* Thursday, February 26, 2009 10:06 AM > *To:* general at lists.openfabrics.org; ewg at lists.openfabrics.org; > wwg at lists.openfabrics.org > *Cc:* 'Peter Jones'; 'Brian J. Murrell'; 'Makia Minich'; > Bryon.Neitzel at Sun.COM > *Subject:* Sun is asking for a response on Bug No.s 1522, 1523 > > Dear OFA Maintainers: > > > > Sun has contacted me about these bugs and is asking for priority > action to get fixes for them. See the thread below. > > > > I?m sending this email to 3 OFA lists because Sun having to contact > the Alliance this way raises many questions about how a vendor like > Sun or a customer like, say, a Wall St bank gets bugs fixed and where > do we, the OFA, publish this information? > > > > And if we agree that an OFA maintainer is the right person to fix the > bug how does that maintainer learn that and how do they respond? > > > > Thank you for responding to this email and to the Sun team using OFED > in their products. > > > > Bill. > > > > Bill Boas > > Executive Director and Vice Chair > > OpenFabrics Alliance > > 510-375-8840 > > Bill.Boas at openfabrics.org > > www.openfabrics.org > > > > ------------------------------------------------------------------------ > > *From:* Bryon.Neitzel at Sun.COM [mailto:Bryon.Neitzel at Sun.COM] > *Sent:* Wednesday, February 25, 2009 12:20 PM > *To:* Bill Boas > *Cc:* Peter Jones; Brian J. Murrell; Makia Minich > *Subject:* Fwd: OFED 1.4 for NHM chips > > > > Hi Bill, > > I found the bug numbers for the Lustre build issues against OFED 1.4.0 > that I mentioned yesterday. > > Is there any way to bump up the priority on these? This is blocking > our ability to deliver our new Vayu (Nehalem+QDR) hardware to our > customers, since Mellanox says they'll only support OFED 1.4 with QDR > hardware. > > > > Thanks, > > Bryon > > > > > > Begin forwarded message: > > > > *From: *"Brian J. Murrell" > > > *Date: *February 25, 2009 1:06:49 PM MST > > *To: *Bryon Neitzel > > > *Cc: *Peter Jones > > > *Subject: **Re: OFED 1.4 for NHM chips* > > > > On Wed, 2009-02-25 at 12:59 -0700, Bryon Neitzel wrote: > > Hi Brian, what is the website where these OFED bugs were filed? > > > https://bugs.openfabrics.org/show_bug.cgi?id=1522 > https://bugs.openfabrics.org/show_bug.cgi?id=1523 > > > Bill Boas tried to find any OFED bugs opened by Sun yesterday, > > > Yeah. I opened them a number of days ago. > > Not sure if it matters to anyone, but IMHO, 1523 is the correct future > direction and fixing that would implicitly fix 1522. 1523 basically > describes separating the "technology preview" that caused this breakage > out into it's own independent module so that it does not pollute the > OFED core. As such, it might be resisted as it's a "deeper cut" type of > fix, but one that removes the sick part rather than trying to continue > to bandage it. > > b. > > >