lpfc driver needs to be updated.

[Dick Kennedy]

The current lpfc driver for release 1404 is at 8.3.43 The current upstream driver is at 10.5.0.0 this bug is to report all of the required changes/patches needed to get that driver up to that level.

[Brian Fromme (brianfromme)]

Hi Dick. Thanks for creating this bug. As soon as you have the list of patches, please drop them in a Comment on this bug.

 cheers,
 Brian

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1439327

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Dick Kennedy (dick-kennedy)]

Brian,
I don't know if I already asked you this or not, but if we push more patches upstream this week we will not have commit IDs for them until they are pulled into either James Bottomely or Christoph's or Linus tree, will you accept a patch if we only have the scsi misc mailing list url for it?
Thanks

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Brian Fromme
Sent: Wednesday, April 01, 2015 1:48 PM
To: Dick Kennedy
Subject: [Bug 1439327] Re: lpfc driver needs to be updated.

Hi Dick. Thanks for creating this bug. As soon as you have the list of patches, please drop them in a Comment on this bug.

 cheers,
 Brian

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1439327

Title:
  lpfc driver needs to be updated.

Status in linux package in Ubuntu:
  New

Bug description:
  The current lpfc driver for release 1404 is at 8.3.43 The current
  upstream driver is at 10.5.0.0 this bug is to report all of the
  required changes/patches needed to get that driver up to that level.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1439327/+subscriptions

[Brian Fromme (brianfromme)]

We prefer not to pick patches straight from the scsi ml list, but rather to see the patches at least integrated into a subsystem maintainer's tree first. If they are bug fixes, etc, please make sure they are CC'd to upstream stable and we would naturally pick them up in our SRU process when we pull patches from the stable v3.19.x tree.

[Walt Esker (walt-esker)]

OK. The challenge for us will be to see how fast we can do the development work, create the Upstream patch set, get James or Christoph to pull it in as it relates to your timeline for getting a solution from Emulex for the 14.04.03 release.

I guess we will take it one step at a time and communicate our progress on getting the Upstream patch pushed to the scsi misc list and then we can track the progress together.

Walt

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Brian Fromme
Sent: Wednesday, April 01, 2015 4:29 PM
To: Walt Esker
Subject: [Bug 1439327] Re: lpfc driver needs to be updated.

We prefer not to pick patches straight from the scsi ml list, but rather to see the patches at least integrated into a subsystem maintainer's tree first. If they are bug fixes, etc, please make sure they are CC'd to upstream stable and we would naturally pick them up in our SRU process when we pull patches from the stable v3.19.x tree.

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1439327

Title:
  lpfc driver needs to be updated.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The current lpfc driver for release 1404 is at 8.3.43 The current
  upstream driver is at 10.5.0.0 this bug is to report all of the
  required changes/patches needed to get that driver up to that level.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1439327/+subscriptions

[Leann Ogasawara (leannogasawara)]

Thanks. I've confirmed all of the patches listed in comment #6 are indeed already included in our v3.19 based kernel for Vivid. The Vivid kernel will be introduced back into 14.04 in our 14.04.3 point release so these will naturally be included there as well. Do keep us posted on any additional patches still making their way upstream.

-----
8698a745d800c59cd5a576398bdeccd578ac66f1
v3.16-rc1~24^2~64
-----
fd10ccfa8dfe740f61471b212c200fbdb5de82f5
v3.18-rc1~140^2^2~134
-----
4f871e1b27a7c7254ead541ad6405f339790b6c5
v3.18-rc1~140^2^2~144
-----
8c50d25c0edd8ec05a7e069c23f6ac2e50c898b1
v3.18-rc1~140^2^2~135
-----
eb01656688edd686a80c89281043fe6f2b2af6ff
v3.18-rc1~140^2^2~136
-----
a2fc4aefa06d8b57b6728c1787c84fb3d3c86354
v3.18-rc1~140^2^2~137
-----
7ba36effb666831ac3803ca5b8aed371e7d17c4e
v3.18-rc1~140^2^2~138
-----
9bd2bff5e7140beab948ad3934f4039246748a24
v3.18-rc1~140^2^2~139
-----
12838e74f5164054fd7d5f5201a846ebb9755471
v3.18-rc1~140^2^2~140
-----
c62321978f542e82960264f175c9e33d7279bec5
v3.18-rc1~140^2^2~142
-----
dafe8ceaa89577062c2364139997f04a32f77502
v3.18-rc1~140^2^2~143
-----
2f6fa2c911167e7a3fda130689a36f55b39ed86d
v3.18-rc1~140^2^2~141
-----
27f344eb15dd0da80ebec80c7245e8c85043f841
v3.16-rc1~4^2~89
-----
3fb4b161e0eeb5abc1c3bff2b72d784a23321a5b
v3.16-rc1~4^2~1
-----
28d7f3dfda36b55ad9b05034d8526222c7282a9f
v3.16-rc1~4^2~2
-----
12222f4f5e714cab512478fabf45329dac1e6c58
v3.16-rc1~4^2~3
-----
59c5f61fcaccb04e2728cb84c9689b4ca886fa8e
v3.16-rc1~4^2~4
-----
68e814f587700b935f696b9e18403fe6c900a4a1
v3.16-rc1~4^2~5
-----
b857ff33d0a8be47220ebd0e816962c6037216bb
v3.16-rc1~4^2~7
-----
2e61f50490d0ac4fec03b2409ea981dc4c87e4d6
v3.16-rc1~4^2~6
-----
b857ff33d0a8be47220ebd0e816962c6037216bb
v3.16-rc1~4^2~7
-----
98912dda4d287a7bc6f0b7a91cceb0fedd1492f6
v3.16-rc1~4^2~9
-----
f38fa0bb7c4a54dc7eff622adc6fa7cf763d834d
v3.16-rc1~4^2~10
-----
0293635ef6234ae813df95d6b3b93a666c69f33d
v3.16-rc1~4^2~11
-----
db55fba8dc26535d34c00a3b3256da0b48608071
v3.16-rc1~4^2~12
-----
ee62021a11320e972e0218ab73a5a5196b6aa499
v3.16-rc1~4^2~13
-----
07eab624e5cf471450ed7b8c4ba8521e910dc9cf
v3.16-rc1~4^2~14
-----
15367540f95d455c0d9500cae6e856fcfcd010be
v3.15-rc1~136^2~148
-----
2e7063770ecf7d0d17a59eeb476107a4b608003a
v3.15-rc1~136^2~147
-----
bcece5f557d533a85b24cf4f4416c821219fb7b7
v3.16-rc1~4^2~15
-----
6acb3481498a0bd3bac02af7aa5003f0a52bf037
v3.16-rc1~4^2~16
-----
3d53af4d4a198446fcef6d878466094355b7ec38
v3.15-rc1~136^2~149
-----
06918ac56682bea444981c46297147bd5acd02c2
v3.15-rc1~136^2~150
-----
e10b2022f942f8414d9a5c1e717c5f6940948f8e
v3.15-rc1~136^2~151
-----
f9226c20b736916552d623ef632b7152f61dfcc7
v3.15-rc1~136^2~152
-----
76fd07a632483c85ea24f383f02b92fabf468434
v3.15-rc1~136^2~153
-----
6ff8556d5f86681c164fc9d05e617e160f79f264
v3.15-rc1~136^2~154
-----
1ba981fd3ad1f91b8bb205ce6aac6aad45f2fa7a
v3.15-rc1~136^2~155
-----
2a2719d370b2ec31451462f2775986e42cbeb39f
v3.15-rc1~136^2~156
-----
70ecd49d3cff73729bb8c4a8163b1d40542cc25a
v3.15-rc1~136^2~157
-----
15026c9eb61e205b08a60dc4b7fae3689d9f36c5
v3.15-rc1~136^2~158
-----
f6c3bdfb93a71b06d31ad12447acf2cea04b3324
v3.15-rc1~136^2~159
-----
cff261f6bd03612e792e4c8872c6ad049f743863
v3.15-rc1~136^2~160
-----
0976e1a650bd...

[Nikhith (nikhith-kantharaju)]

Hi Brian,

Above patches gone through sanity testing by EVT and driver looks good without any issues.
We didn't include commit ids 8698a745d800c59cd5a576398bdeccd578ac66f1 and 871e1b27a7c7254ead541ad6405f339790b6c5 in testing because they have new API changes that are not supported in 3.13 kernel.

Thanks,
Nikhith.

[Nikhith (nikhith-kantharaju)]

Hi Brian,

 Its 4f871e1b27a7c7254ead541ad6405f339790b6c5 not 871e1b27a7c7254ead541ad6405f339790b6c5.

Thanks,
Nikhith.

[Nikhith (nikhith-kantharaju)]

Hi Brian,

Is it possible to update the lpfc driver version to 10.4.0.105 ? I have attached the header file lpfc_version.h, this includes the new driver version change.

Thanks,
Nikhith

[Brian Fromme (brianfromme)]

Hi Nikhith,

Our kernel freeze date has passed, so I'm not sure if this can happen for the Vivid release. We do have a process, called SRU (Stable Release Update) which will allow us to make changes after the release.

I will let our kernel team weigh in on the timing of all that.

 thanks,
 Brian

[Walt Esker (walt-esker)]

Hi Brian, we are using this bug to track our submission for 14.04 (3.13 kernel). we are using bug 1439612 to track our submission for 14.04.03 (3.19 kernel) submission.

Nikhith's request would be to set the version number for the driver in 14.04 update.

Thanks,
Walt