Date: Fri, 7 Oct 2016 09:42:07 -0700 (PDT) From: Robroy Gregg <robroy@robroygregg.com> To: Vijay Rajah <me@rvijay.me> Cc: freebsd-questions@freebsd.org Subject: Re: isp(4) QLE2462 initiator failure with 10.3-RELEASE Message-ID: <alpine.BSF.2.20.1610070922200.24435@funmax.d.net> In-Reply-To: <0a7120b7-54d2-5afe-5e9a-3681e74d543e@rvijay.me> References: <alpine.BSF.2.20.1610060934270.93488@funmax.d.net> <0a7120b7-54d2-5afe-5e9a-3681e74d543e@rvijay.me>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 7 Oct 2016, Vijay Rajah wrote: > On 10/06/2016 10:50 PM, Robroy Gregg wrote: >> * I've tried physically swapping the isp0 and isp1 HBA port >> connections--the symptom stuck to isp0, even when its I/Os were >> being attempted through the physical connection formerly used >> (successfully) by isp1. > > This might be an indication of an issue with the Motherboard (MB)(more > specifically issue with the PCIE slot -- Since the problem stays with the > slot). Thank you for replying Vijay! Yeah, though isp0 and isp1 are combined on a single card, in the same physical slot, I understand that they act like two separate devices at some level. > Do you have another PCIE (x4 or higher) slot in the motherboard? if so, > can you use that unsued slot to see if that solves the problem. Yes, there are one or two other empty slots to try. The trouble is, this event has happened only once so far, and we haven't been able to figure out what triggered it. So the new slot approach will be conclusive only if the problem happens again, after the slot's been changed. > OR alternatively, Do you have simllar MB's in your inventory or servers using > the same MB's? if so, can you swap the MB's and see if the issues followes > the MB? (meaning, does the issue occur in the swapped server) We do have a second computer that's identical to this one other than having less RAM, and we'll be bringing that one up soon. It'll be interesting to see if the problem happens there. I'm hoping that somebody familiar with isp(4)'s guts may be able to collect information about the card's bizarre state, and make a stab at what may have caused this. Sadly, I think I have to reboot the computer to enable hint.isp.X.debug, which will probably cause the problem to run away and hide indefinitely. I'd also love to know how many other FreeBSD users are having success with similar configurations. Do QLE2462s work flawlessly for other SAN users? It's ironic that people keep quiet both when hardware X works, and when they're not using hardware X at all. It's hard to judge how esoteric our configuration is for FreeBSD. > Hope this helps I really appreciate your reply Vijay; thank you again. Robroy Gregg Salinas, California
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1610070922200.24435>