Comment 34 for bug 1770003

------- Comment From <email address hidden> 2018-05-12 08:42 EDT-------
(In reply to comment #42)
>...
>
> After that, the OK kernel follows with:
> [0001:03:00.0]-580e:2: Asynchronous P2P MODE received
> [0001:03:00.0]-18b9:2: Format 1: VP[0] enabled - status 0 - with port id
> 050500.
> [0001:03:00.0]-5875:2: Format 1: Remote WWPN 20:05:00:05:1e:02:da:3e.
>
> While the NOK kernel follows with:
> [0001:03:00.0]-5809:2: LIP occurred (f700)
> [0001:03:00.0]-580c:2: LIP reset occurred (f7f7).
>
> Later, when the OK kernel seems to detect something, as:
> [0001:03:00.0]-289f:2: Device wrap (030a00).
> [0001:03:00.0]-28d8:2: qla24xx_fcport_handle_login 50:05:07:68:02:16:5e:37
> DS 0 LS 7 P 0 fl 3 confl
> [0001:03:00.0]-28bd:2: qla24xx_fcport_handle_login 982
> 50:05:07:68:02:16:5e:37 post gnl
>
> The NOK kernel just prints:
> [0001:03:00.0]-107ff:2: Async-gpnft hdl=2 FC4Type 8.

Looks like the OK kernel completes the FC login, while the NOK kernel does not. I believe there were some extra patches added that may be missing other requirements. Looking at the two different patch lists, I see this:

1) "scsi: qla2xxx: Fixup locking for session deletion" is missing from the NOK kernel.

2) There are 16 added patches to the NOK kernel, which were not be required when we built our test kernel.

It's possible those 16 patches are missing some critical companion patches, but it should not be necessary to add those 16.

I don't think it is any more acceptable for SRU, but I'll bring it up anyway: another option is to do a full qla2xxx driver refresh to version 10.00.00.04-k, plus the "scsi: qla2xxx: Fixup locking for session deletion" patch (a vital fix).