On Sat, 2018-10-13 at 10:42 -0400, Laurence Oberman wrote: > On Fri, 2018-10-12 at 17:51 -0700, Bart Van Assche wrote: > > On 10/12/18 1:36 PM, Laurence Oberman wrote: > > > While I have for the longest time used 4.5 as a base for my F/C > > jammer > > > that I use every day here in our lab I recently added more > > jammer > > code > > > so I decided to test this all on latest upstream. > > > > > > Booting the target server on my 4.5 kernel with jammer code is > > > flawless and serves LUNS with no issues and handles the jamming > > also > > > fine. > > > > > > However just building a 4.19.0_rc7+-1 (I left the jammer stuff > > out) > > > its pretty broken. > > > > A large number of patches went upstream between these two kernel > > versions for both the QLogic initiator and target drivers. From the > > logs > > it seems like you were using QLogic hardware at both the initiator > > and > > target side? If so, which kernel version was running at the > > initiator > > side during these tests? 4.5, 4.19-rc7+ or yet another version? > > > > Thanks, > > > > Bart. > > > > > > I had only replied to Bart, this was my reply, reply all now > > Hi Bart > Thank you for always being helpful. > > I am using at the moment RHEL 7.5 for the initiator (based on kernel > 3.10 but of course lots of backports) > The exact same initiator is working fine with the 4.5 and I would not > expect the target to require the same kernel level. > Of course I will try latest upstream on the initiator later and reply > back. > > I was thinking the target should adhere to the standards and support > many types of kernels within reason for the initiator. > > Thanks Changed the Subject to match regression I tested the following: Target upstream 4.19_rc4 Inititiator qla2xxx RHEL7.5 lpfc RHEL7.5 qla2xxx Upstream 4.19_rc4 matching initiatior All 3 are unstable and fail, with tag errors and aborts I am not sure when the issue started so will work on a bisect Oct 15 07:29:52 ml150 kernel: print_req_error: I/O error, dev sdj, sector 128 Oct 15 07:29:52 ml150 kernel: print_req_error: I/O error, dev sds, sector 16 .. .. Oct 15 07:30:11 ml150 kernel: sd 5:0:0:0: [sdi] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK Oct 15 07:30:11 ml150 kernel: sd 5:0:0:0: [sdi] tag#0 CDB: Read(10) 28 00 00 00 03 00 00 01 00 00 Oct 15 07:30:16 ml150 kernel: sd 5:0:0:0: [sdi] tag#1 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK Oct 15 07:30:16 ml150 kernel: sd 5:0:0:0: [sdi] tag#1 CDB: Read(10) 28 00 00 00 00 40 00 00 38 00 Oct 15 07:30:17 ml150 kernel: sd 5:0:1:0: [sdp] tag#0 FAILED Result:
