Hello again all,
On 03/11/12 11:37, Chris Boot wrote:
On 02/11/2012 22:24, Nicholas A. Bellinger wrote:
On Fri, 2012-11-02 at 13:58 +0000, Chris Boot wrote:
I have recently acquired a couple of QLE2460 HBAs in order to play
around with the FC target. I have simply strung them together with an
LC-LC fibre pair, and it appears that as soon as I plug the fibre into
both ends the link comes up: I get an entry appearing in
/sys/class/fc_remote_ports/ on both machines that contains correct
information about the node on the other end of the link (WWPNs,
etc...).
You'll want to go ahead and enable ql2xextended_error_logging=0x7fffffff
at modprobe time on both sides to understand what's going on. Note this
will generate a decent amount of ring buffer output. ;)
I've got a log of the target end with that option set. I've posted it
here for now, as it's rather too large for email:
http://www.bootc.net/temp/qla-2012-11-03.log
That's with Windows as an initiator this time. Going into the
SANsurfer tools it appears that it can see the target end, but it has
0 LUNs...
Well, I'm not sure exactly what I did, but it's working now...
I basically did a 'make clean' in my kernel tree, and rebuilt with
gcc-4.6 on a whim (Debian default is gcc-4.7, but Debian build their
kernels with 4.6). There was also a 3.2.x kernel update for Debian which
I installed on the initiator, but that's clearly not what made a
difference as the HBA boot code and Windows both work with the target
now. Consider me very confused.
Obviously now I'll be doing a bunch more testing, and rebooting my
target and initiator a lot to see if it all breaks again.
Cheers,
Chris
--
Chris Boot
bootc@xxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
