[Kernel-packages] [Bug 1823037] [NEW] amd_iommu possible data corruption
Public bug reported: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* ** Affects: linux (Ubuntu) Importance: Medium Assignee: Jeff Lane (bladernr) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Jeff Lane (bladernr) Status: New ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Assignee: Jeff Lane (bladernr) Status: New ** Affects: linux (Ubuntu Disco) Importance: Medium Assignee: Jeff Lane (bladernr) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Xenial) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: In Progress Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
related branch https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco/+ref/amd-iommu-cherrypick ** Also affects: linux (Ubuntu Disco) Importance: Medium Assignee: Jeff Lane (bladernr) Status: In Progress ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Jeff Lane (bladernr) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: In Progress Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808437] Re: Unable to obtain an Emulex LPe35000 series adapter firmware dump in 18.04 - impacts end customer supportability
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808437 Title: Unable to obtain an Emulex LPe35000 series adapter firmware dump in 18.04 - impacts end customer supportability Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Bug description: We are unable to obtain a LPe35000 adapter firmware dump in Ubuntu 18.04. This prevents our debugging customer firmware related issues. This patch was missed during upstream and inbox integration. Our testing for months appeared to have succeeded due to invalid test case. Test case have been corrected to validate fw dump was correctly provided. This fix is very straightforward. Reference upstream submit: James Smart 2018-12-10 19:43:42 PST The patch has been pushed upstream: https://marc.info/?l=linux-scsi&m=154449943301058&w=2 Commit is pending from the upstream maintainer. --- Management support for IF_TYPE=6 Symptoms: Firmware dump, loopback, etc are not working on Prism Cause: The driver has a strict check for SLI_INTF_IF_TYPE_2 Fix: Extend the management support for SLI_INTF_IF_TYPE_6 Unit Testing: Ran Onekat and captured firmware dump on Prism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808437] Re: Unable to obtain an Emulex LPe35000 series adapter firmware dump in 18.04 - impacts end customer supportability
** Changed in: linux-aws (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1808437 Title: Unable to obtain an Emulex LPe35000 series adapter firmware dump in 18.04 - impacts end customer supportability Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Invalid Bug description: We are unable to obtain a LPe35000 adapter firmware dump in Ubuntu 18.04. This prevents our debugging customer firmware related issues. This patch was missed during upstream and inbox integration. Our testing for months appeared to have succeeded due to invalid test case. Test case have been corrected to validate fw dump was correctly provided. This fix is very straightforward. Reference upstream submit: James Smart 2018-12-10 19:43:42 PST The patch has been pushed upstream: https://marc.info/?l=linux-scsi&m=154449943301058&w=2 Commit is pending from the upstream maintainer. --- Management support for IF_TYPE=6 Symptoms: Firmware dump, loopback, etc are not working on Prism Cause: The driver has a strict check for SLI_INTF_IF_TYPE_2 Fix: Extend the management support for SLI_INTF_IF_TYPE_6 Unit Testing: Ran Onekat and captured firmware dump on Prism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
Test kernels are up here: https://people.canonical.com/~jlane/testkernels/ Please test each and report back ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827330] Re: [block layer] please pull below upstream patch to Ubuntu 19.04 kernel
Hi Shagun, Could you also try the upstream builds (info below) and make sure the patch resolves the issue: https://wiki.ubuntu.com/Kernel/MainlineBuilds It looks like this landed upstream right after kernel freeze and thus wasn't pulled into Disco. Looks like a matter of just very close timing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827330 Title: [block layer] please pull below upstream patch to Ubuntu 19.04 kernel Status in linux package in Ubuntu: Confirmed Bug description: Doing a lip on lpfc crashes the Ubuntu 19.04 kernel #echo 1> /sys/class/fc_host/host<>/issue_lip Kernel version: Linux version 5.0.0-7-generic (buildd@lcy01-amd64-020) (gcc version 8.3.0 (Ubuntu 8.3.0-2ubuntu1)) Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.338980] BUG: unable to handle kernel NULL pointer dereference at 00b8 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.344517] #PF error: [normal kernel read fault] Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.344523] PGD 0 P4D 0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.351436] device-mapper: multipath: Failing path 129:64. Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352960] RIP: 0010:blk_mq_dispatch_rq_list+0xc8/0x4f0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352962] Code: 45 84 ed 0f 85 21 02 00 00 49 8b 06 83 45 ac 01 49 39 c6 0f 84 2e 02 00 00 4d 8b 3e 80 7d b0 00 4d 8d 67 b8 49 8b 5f c8 75 26 <48> 8b 83 b8 00 00 00 48 8b 40 40 48 8b 40 10 48 85 c0 74 12 48 89 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352963] RSP: 0018:b8c6c7d37d88 EFLAGS: 00010246 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352965] RAX: 9da508c85848 RBX: RCX: 000a Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352966] RDX: RSI: b8c6c7d37e10 RDI: 9da50321c848 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352967] RBP: b8c6c7d37e00 R08: R09: 00646b636f6c626b Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352968] R10: 8080808080808080 R11: 00ddf2c6455b R12: 9da508c85800 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352969] R13: R14: b8c6c7d37e10 R15: 9da508c85848 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352971] FS: () GS:9da51fdc() knlGS: Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352972] CS: 0010 DS: ES: CR0: 80050033 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352973] CR2: 00b8 CR3: 0007a8c0e002 CR4: 007606e0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352974] DR0: DR1: DR2: Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352975] DR3: DR6: fffe0ff0 DR7: 0400 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352976] PKRU: 5554 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.353566] Oops: [#19] SMP PTI Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.403374] CPU: 2 PID: 27111 Comm: kworker/2:2H Tainted: G D 5.0.0-7-generic #8-Ubuntu Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.404046] Hardware name: Dell Inc. PowerEdge R740/07WCGN, BIOS 1.5.6 10/17/2018 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.404861] Workqueue: kblockd blk_mq_run_work_fn Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.405740] RIP: 0010:blk_mq_dispatch_rq_list+0xc8/0x4f0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.406428] Code: 45 84 ed 0f 85 21 02 00 00 49 8b 06 83 45 ac 01 49 39 c6 0f 84 2e 02 00 00 4d 8b 3e 80 7d b0 00 4d 8d 67 b8 49 8b 5f c8 75 26 <48> 8b 83 b8 00 00 00 48 8b 40 40 48 8b 40 10 48 85 c0 74 12 48 89 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.407860] RSP: 0018:b8c6ca4dfd88 EFLAGS: 00010246 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.408624] RAX: 9da509360b48 RBX: RCX: 000a Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.409492] RDX: RSI: b8c6ca4dfe10 RDI: 9da50cc71010 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.410234] RBP: b8c6ca4dfe00 R08: R09: 00646b636f6c626b Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.410980] R10: 8080808080808080 R11: 1000 R12: 9da509360b00 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.411730] R13: R14: b8c6ca4dfe10 R15: 9da509360b48 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.412493] FS: () GS:9da51fa4() knlGS: Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.413283] CS: 0010 DS: ES: CR0: 80050033 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.414045] CR2: 00b8 CR3: 0007a8c0e006 CR
[Kernel-packages] [Bug 1827330] Re: [block layer] please pull below upstream patch to Ubuntu 19.04 kernel
commit fd9c40f64c514bdc585a21e2e33fa5f83ca8811b
Author: Bart Van Assche
Date: Thu Apr 4 10:08:43 2019 -0700
block: Revert v5.0 blk_mq_request_issue_directly() changes
blk_mq_try_issue_directly() can return BLK_STS*_RESOURCE for requests that
have been queued. If that happens when blk_mq_try_issue_directly() is called
by the dm-mpath driver then dm-mpath will try to resubmit a request that is
already queued and a kernel crash follows. Since it is nontrivial to fix
blk_mq_request_issue_directly(), revert the blk_mq_request_issue_directly()
changes that went into kernel v5.0.
This patch reverts the following commits:
* d6a51a97c0b2 ("blk-mq: replace and kill blk_mq_request_issue_directly") #
v5.0.
* 5b7a6f128aad ("blk-mq: issue directly with bypass 'false' in
blk_mq_sched_insert_requests") # v5.0.
* 7f556a44e61d ("blk-mq: refactor the code of issue request directly") #
v5.0.
Cc: Christoph Hellwig
Cc: Ming Lei
Cc: Jianchao Wang
Cc: Hannes Reinecke
Cc: Johannes Thumshirn
Cc: James Smart
Cc: Dongli Zhang
Cc: Laurence Oberman
Cc:
Reported-by: Laurence Oberman
Tested-by: Laurence Oberman
Fixes: 7f556a44e61d ("blk-mq: refactor the code of issue request directly")
# v5.0.
Signed-off-by: Bart Van Assche
Signed-off-by: Jens Axboe
Patch exists in mainline from April 7 (patch landed April 4 but wasn't
pulled into Mainline until April 7) so it's not currently in Disco or
Eoan.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1827330
Title:
[block layer] please pull below upstream patch to Ubuntu 19.04 kernel
Status in linux package in Ubuntu:
Confirmed
Bug description:
Doing a lip on lpfc crashes the Ubuntu 19.04 kernel
#echo 1> /sys/class/fc_host/host<>/issue_lip
Kernel version:
Linux version 5.0.0-7-generic (buildd@lcy01-amd64-020) (gcc version 8.3.0
(Ubuntu 8.3.0-2ubuntu1))
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.338980] BUG: unable to
handle kernel NULL pointer dereference at 00b8
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.344517] #PF error: [normal
kernel read fault]
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.344523] PGD 0 P4D 0
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.351436] device-mapper:
multipath: Failing path 129:64.
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352960] RIP:
0010:blk_mq_dispatch_rq_list+0xc8/0x4f0
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352962] Code: 45 84 ed 0f
85 21 02 00 00 49 8b 06 83 45 ac 01 49 39 c6 0f 84 2e 02 00 00 4d 8b 3e 80 7d
b0 00 4d 8d 67 b8 49 8b 5f c8 75 26 <48> 8b 83 b8 00 00 00 48 8b 40 40 48 8b 40
10 48 85 c0 74 12 48 89
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352963] RSP:
0018:b8c6c7d37d88 EFLAGS: 00010246
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352965] RAX:
9da508c85848 RBX: RCX: 000a
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352966] RDX:
RSI: b8c6c7d37e10 RDI: 9da50321c848
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352967] RBP:
b8c6c7d37e00 R08: R09: 00646b636f6c626b
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352968] R10:
8080808080808080 R11: 00ddf2c6455b R12: 9da508c85800
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352969] R13:
R14: b8c6c7d37e10 R15: 9da508c85848
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352971] FS:
() GS:9da51fdc() knlGS:
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352972] CS: 0010 DS:
ES: CR0: 80050033
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352973] CR2:
00b8 CR3: 0007a8c0e002 CR4: 007606e0
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352974] DR0:
DR1: DR2:
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352975] DR3:
DR6: fffe0ff0 DR7: 0400
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352976] PKRU: 5554
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.353566] Oops: [#19]
SMP PTI
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.403374] CPU: 2 PID: 27111
Comm: kworker/2:2H Tainted: G D 5.0.0-7-generic #8-Ubuntu
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.404046] Hardware name: Dell
Inc. PowerEdge R740/07WCGN, BIOS 1.5.6 10/17/2018
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.404861] Workqueue: kblockd
blk_mq_run_work_fn
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.405740] RIP:
0010:blk_mq_dispatch_rq_list+0xc8/0x4f0
Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.406428] Code: 45 84 ed 0f
85 21 02 00 00 49 8b 06 83 45 ac 01 49 39 c6 0f 84 2e 02 0
[Kernel-packages] [Bug 1827330] Re: [block layer] please pull below upstream patch to Ubuntu 19.04 kernel
This also looks to be in upstream stable as of May 19, so I presume will land in an SRU for Disco at some point. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827330 Title: [block layer] please pull below upstream patch to Ubuntu 19.04 kernel Status in linux package in Ubuntu: Confirmed Bug description: Doing a lip on lpfc crashes the Ubuntu 19.04 kernel #echo 1> /sys/class/fc_host/host<>/issue_lip Kernel version: Linux version 5.0.0-7-generic (buildd@lcy01-amd64-020) (gcc version 8.3.0 (Ubuntu 8.3.0-2ubuntu1)) Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.338980] BUG: unable to handle kernel NULL pointer dereference at 00b8 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.344517] #PF error: [normal kernel read fault] Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.344523] PGD 0 P4D 0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.351436] device-mapper: multipath: Failing path 129:64. Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352960] RIP: 0010:blk_mq_dispatch_rq_list+0xc8/0x4f0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352962] Code: 45 84 ed 0f 85 21 02 00 00 49 8b 06 83 45 ac 01 49 39 c6 0f 84 2e 02 00 00 4d 8b 3e 80 7d b0 00 4d 8d 67 b8 49 8b 5f c8 75 26 <48> 8b 83 b8 00 00 00 48 8b 40 40 48 8b 40 10 48 85 c0 74 12 48 89 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352963] RSP: 0018:b8c6c7d37d88 EFLAGS: 00010246 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352965] RAX: 9da508c85848 RBX: RCX: 000a Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352966] RDX: RSI: b8c6c7d37e10 RDI: 9da50321c848 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352967] RBP: b8c6c7d37e00 R08: R09: 00646b636f6c626b Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352968] R10: 8080808080808080 R11: 00ddf2c6455b R12: 9da508c85800 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352969] R13: R14: b8c6c7d37e10 R15: 9da508c85848 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352971] FS: () GS:9da51fdc() knlGS: Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352972] CS: 0010 DS: ES: CR0: 80050033 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352973] CR2: 00b8 CR3: 0007a8c0e002 CR4: 007606e0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352974] DR0: DR1: DR2: Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352975] DR3: DR6: fffe0ff0 DR7: 0400 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352976] PKRU: 5554 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.353566] Oops: [#19] SMP PTI Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.403374] CPU: 2 PID: 27111 Comm: kworker/2:2H Tainted: G D 5.0.0-7-generic #8-Ubuntu Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.404046] Hardware name: Dell Inc. PowerEdge R740/07WCGN, BIOS 1.5.6 10/17/2018 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.404861] Workqueue: kblockd blk_mq_run_work_fn Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.405740] RIP: 0010:blk_mq_dispatch_rq_list+0xc8/0x4f0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.406428] Code: 45 84 ed 0f 85 21 02 00 00 49 8b 06 83 45 ac 01 49 39 c6 0f 84 2e 02 00 00 4d 8b 3e 80 7d b0 00 4d 8d 67 b8 49 8b 5f c8 75 26 <48> 8b 83 b8 00 00 00 48 8b 40 40 48 8b 40 10 48 85 c0 74 12 48 89 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.407860] RSP: 0018:b8c6ca4dfd88 EFLAGS: 00010246 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.408624] RAX: 9da509360b48 RBX: RCX: 000a Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.409492] RDX: RSI: b8c6ca4dfe10 RDI: 9da50cc71010 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.410234] RBP: b8c6ca4dfe00 R08: R09: 00646b636f6c626b Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.410980] R10: 8080808080808080 R11: 1000 R12: 9da509360b00 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.411730] R13: R14: b8c6ca4dfe10 R15: 9da509360b48 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.412493] FS: () GS:9da51fa4() knlGS: Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.413283] CS: 0010 DS: ES: CR0: 80050033 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.414045] CR2: 00b8 CR3: 0007a8c0e006 CR4: 007606e0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.414814] DR0: DR1: DR2: Apr 8 12:10:38 dhcp-10-123-163-25 ker
[Kernel-packages] [Bug 1827330] Re: [block layer] please pull below upstream patch to Ubuntu 19.04 kernel
Unfortunately, I do not have the hardware to test this. I can load the driver but without an HBA I can't recreate the crash. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827330 Title: [block layer] please pull below upstream patch to Ubuntu 19.04 kernel Status in linux package in Ubuntu: Confirmed Bug description: Doing a lip on lpfc crashes the Ubuntu 19.04 kernel #echo 1> /sys/class/fc_host/host<>/issue_lip Kernel version: Linux version 5.0.0-7-generic (buildd@lcy01-amd64-020) (gcc version 8.3.0 (Ubuntu 8.3.0-2ubuntu1)) Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.338980] BUG: unable to handle kernel NULL pointer dereference at 00b8 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.344517] #PF error: [normal kernel read fault] Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.344523] PGD 0 P4D 0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.351436] device-mapper: multipath: Failing path 129:64. Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352960] RIP: 0010:blk_mq_dispatch_rq_list+0xc8/0x4f0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352962] Code: 45 84 ed 0f 85 21 02 00 00 49 8b 06 83 45 ac 01 49 39 c6 0f 84 2e 02 00 00 4d 8b 3e 80 7d b0 00 4d 8d 67 b8 49 8b 5f c8 75 26 <48> 8b 83 b8 00 00 00 48 8b 40 40 48 8b 40 10 48 85 c0 74 12 48 89 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352963] RSP: 0018:b8c6c7d37d88 EFLAGS: 00010246 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352965] RAX: 9da508c85848 RBX: RCX: 000a Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352966] RDX: RSI: b8c6c7d37e10 RDI: 9da50321c848 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352967] RBP: b8c6c7d37e00 R08: R09: 00646b636f6c626b Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352968] R10: 8080808080808080 R11: 00ddf2c6455b R12: 9da508c85800 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352969] R13: R14: b8c6c7d37e10 R15: 9da508c85848 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352971] FS: () GS:9da51fdc() knlGS: Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352972] CS: 0010 DS: ES: CR0: 80050033 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352973] CR2: 00b8 CR3: 0007a8c0e002 CR4: 007606e0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352974] DR0: DR1: DR2: Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352975] DR3: DR6: fffe0ff0 DR7: 0400 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.352976] PKRU: 5554 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.353566] Oops: [#19] SMP PTI Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.403374] CPU: 2 PID: 27111 Comm: kworker/2:2H Tainted: G D 5.0.0-7-generic #8-Ubuntu Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.404046] Hardware name: Dell Inc. PowerEdge R740/07WCGN, BIOS 1.5.6 10/17/2018 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.404861] Workqueue: kblockd blk_mq_run_work_fn Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.405740] RIP: 0010:blk_mq_dispatch_rq_list+0xc8/0x4f0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.406428] Code: 45 84 ed 0f 85 21 02 00 00 49 8b 06 83 45 ac 01 49 39 c6 0f 84 2e 02 00 00 4d 8b 3e 80 7d b0 00 4d 8d 67 b8 49 8b 5f c8 75 26 <48> 8b 83 b8 00 00 00 48 8b 40 40 48 8b 40 10 48 85 c0 74 12 48 89 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.407860] RSP: 0018:b8c6ca4dfd88 EFLAGS: 00010246 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.408624] RAX: 9da509360b48 RBX: RCX: 000a Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.409492] RDX: RSI: b8c6ca4dfe10 RDI: 9da50cc71010 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.410234] RBP: b8c6ca4dfe00 R08: R09: 00646b636f6c626b Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.410980] R10: 8080808080808080 R11: 1000 R12: 9da509360b00 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.411730] R13: R14: b8c6ca4dfe10 R15: 9da509360b48 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.412493] FS: () GS:9da51fa4() knlGS: Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.413283] CS: 0010 DS: ES: CR0: 80050033 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.414045] CR2: 00b8 CR3: 0007a8c0e006 CR4: 007606e0 Apr 8 12:10:38 dhcp-10-123-163-25 kernel: [ 8673.414814] DR0: DR1: DR2: Apr 8 12:10:38 dhcp-10-12
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
** Description changed: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. - - Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. - This is a clean cherry pick from mainline of - 8aafaaf2212192012f5bae305bb31cdf7681d777 + Treat exclusion ranges as reserved regions in the iommu-core to fix the + problem. + This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 + 3c677d206210f53a4be972211066c0f1cd47fe12 [Test Case] - [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain + 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly [Regression Risk] Only affects the amd_iommu driver: - drivers/iommu/amd_iommu* + drivers/iommu/amd_iommu* -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 3c677d206210f53a4be972211066c0f1cd47fe12 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801574] Re: [cosmic] ipoib ping with large message size failed
Err... nevermind 4.4 anyway. just 5.0 would be interesting to see if this persisted into Disco. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801574 Title: [cosmic] ipoib ping with large message size failed Status in linux package in Ubuntu: Confirmed Bug description: We see that ping over ipoib interface stuck with large packets, this is a new degradation, this test pass on Ubuntu 18.04. After investigating the issue, we see that commit [1] introduce the issue, and it is not an upstream commit, it is canonical commit. Could you please check with the canonical kernel team why they revert that commit? To reproduce the bug, please use ConnectX-3 devices with ipoib connection with 2044 MTU (default) and run command [2]. Is there open Launchpad on it? [1] commit 77a24c313d21e3765b04d90521e9228a9bb6e332 Author: Tyler Hicks Date: Fri Aug 3 21:53:15 2018 + Revert "net: increase fragment memory usage limits" This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It made denial of service attacks on the IP fragment handling easier to carry out. CVE-2018-5391 Signed-off-by: Tyler Hicks Signed-off-by: Stefan Bader [2] ping 13.194.22.1 -I 13.194.23.1 -s 65507 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801574] Re: [cosmic] ipoib ping with large message size failed
Hi Talat, Something else occurs to me, could you list which kernels are affected? Is this correct so far: 4.15: Not affected 4.18: Affected How about 5.0 and perhaps 4.4 (not sure if 4.4 includes support for this though, so that may be not worth investigating.) And for failing kernels, could you provide the full version (per uname)? that helps too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801574 Title: [cosmic] ipoib ping with large message size failed Status in linux package in Ubuntu: Confirmed Bug description: We see that ping over ipoib interface stuck with large packets, this is a new degradation, this test pass on Ubuntu 18.04. After investigating the issue, we see that commit [1] introduce the issue, and it is not an upstream commit, it is canonical commit. Could you please check with the canonical kernel team why they revert that commit? To reproduce the bug, please use ConnectX-3 devices with ipoib connection with 2044 MTU (default) and run command [2]. Is there open Launchpad on it? [1] commit 77a24c313d21e3765b04d90521e9228a9bb6e332 Author: Tyler Hicks Date: Fri Aug 3 21:53:15 2018 + Revert "net: increase fragment memory usage limits" This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It made denial of service attacks on the IP fragment handling easier to carry out. CVE-2018-5391 Signed-off-by: Tyler Hicks Signed-off-by: Stefan Bader [2] ping 13.194.22.1 -I 13.194.23.1 -s 65507 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
** Description changed: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 3c677d206210f53a4be972211066c0f1cd47fe12 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly + These can be picked from my branches here: + Bionic + https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic + Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic + Disco: + https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco + + I do not believe these are necessary for Eoan, 5.1 should already + include them but it's worth verifying that as I started work on this + prior to Eoan's cycle. + [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 3c677d206210f53a4be972211066c0f1cd47fe12 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly These can be picked from my branches here: Bionic https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic Disco: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco I do not believe these are necessary for Eoan, 5.1 should already include them but it's worth verifying that as I started work on this prior to Eoan's cycle. [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
** Description changed:
[Impact]
+ iommu/amd: Reserve exclusion range in iova-domain
If a device has an exclusion range specified in the IVRS table, this region
needs to be reserved in the iova-domain of that device. This hasn't happened
until now and can cause data corruption on data transfered with these devices.
Treat exclusion ranges as reserved regions in the iommu-core to fix the
problem.
- This is a clean cherry pick from mainline of
8aafaaf2212192012f5bae305bb31cdf7681d777
- 3c677d206210f53a4be972211066c0f1cd47fe12
+ iommu/amd: Set exclusion range correctly
+
+ The exlcusion range limit register needs to contain the
+ base-address of the last page that is part of the range, as
+ bits 0-11 of this register are treated as 0xfff by the
+ hardware for comparisons.
+
+ So correctly set the exclusion range in the hardware to the
+ last page which is _in_ the range.
[Test Case]
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
Bionic
- https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
- Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
- Disco:
- https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
+ https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
+ Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
+ Disco:
+ https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
1823037-amd_iommu-cherrypick
- I do not believe these are necessary for Eoan, 5.1 should already
- include them but it's worth verifying that as I started work on this
- prior to Eoan's cycle.
+ Note Disco only required f1cd47fe12 as the first patch was already
+ picked in LP: #1830934
+
+ Not necessary for Eoan, they're in 5.2-rc1.
[Regression Risk]
+ Low,
Only affects the amd_iommu driver:
drivers/iommu/amd_iommu*
** Description changed:
[Impact]
- iommu/amd: Reserve exclusion range in iova-domain
- If a device has an exclusion range specified in the IVRS table, this region
needs to be reserved in the iova-domain of that device. This hasn't happened
until now and can cause data corruption on data transfered with these devices.
-
- Treat exclusion ranges as reserved regions in the iommu-core to fix the
- problem.
-
iommu/amd: Set exclusion range correctly
-
+
+ BugLink: https://bugs.launchpad.net/bugs/1823037
+
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register are treated as 0xfff by the
hardware for comparisons.
-
+
So correctly set the exclusion range in the hardware to the
last page which is _in_ the range.
+
+ Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
+ Signed-off-by: Joerg Roedel
+
+ (cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
+ Signed-off-by: Jeffrey Lane
+
+
+ iommu/amd: Reserve exclusion range in iova-domain
+
+ BugLink: https://bugs.launchpad.net/bugs/1823037
+
+ If a device has an exclusion range specified in the IVRS
+ table, this region needs to be reserved in the iova-domain
+ of that device. This hasn't happened until now and can cause
+ data corruption on data transfered with these devices.
+
+ Treat exclusion ranges as reserved regions in the iommu-core
+ to fix the problem.
+
+ Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
+ Signed-off-by: Joerg Roedel
+ Reviewed-by: Gary R Hook
+
+ (cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
+ Signed-off-by: Jeffrey Lane
[Test Case]
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
Bionic
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
Disco:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
1823037-amd_iommu-cherrypick
Note Disco only required f1cd47fe12 as the first patch was already
picked in LP: #1830934
Not necessary for Eoan, they're in 5.2-rc1.
[Regression Risk]
- Low,
+ Low,
Only affects the amd_iommu driver:
drivers/iommu/amd_iommu*
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
** Description changed:
[Impact]
iommu/amd: Set exclusion range correctly
-
+
BugLink: https://bugs.launchpad.net/bugs/1823037
-
+
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register are treated as 0xfff by the
hardware for comparisons.
-
+
So correctly set the exclusion range in the hardware to the
last page which is _in_ the range.
-
+
Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
Signed-off-by: Joerg Roedel
-
+
(cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
Signed-off-by: Jeffrey Lane
+ iommu/amd: Reserve exclusion range in iova-domain
- iommu/amd: Reserve exclusion range in iova-domain
-
BugLink: https://bugs.launchpad.net/bugs/1823037
-
+
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.
-
+
Treat exclusion ranges as reserved regions in the iommu-core
to fix the problem.
-
+
Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
Signed-off-by: Joerg Roedel
Reviewed-by: Gary R Hook
-
+
(cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
Signed-off-by: Jeffrey Lane
[Test Case]
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
- Bionic
+ Bionic:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
+ b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range
in iova-domain
+ ee4a87e6b7fe7e039c1f02c50c53da63e4270732
+
Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
+ 0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range
in iova-domain
+ fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range
correctly
+
+
Disco:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
1823037-amd_iommu-cherrypick
+ 6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range
correctly
- Note Disco only required f1cd47fe12 as the first patch was already
- picked in LP: #1830934
- Not necessary for Eoan, they're in 5.2-rc1.
+ Note Disco only required f1cd47fe12 as the first patch was already picked in
LP: #1830934
+
+ Not necessary for Eoan as these are already upstream in 5.2-rc1
[Regression Risk]
Low,
Only affects the amd_iommu driver:
drivers/iommu/amd_iommu*
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823037
Title:
amd_iommu possible data corruption
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Status in linux source package in Disco:
In Progress
Bug description:
[Impact]
iommu/amd: Set exclusion range correctly
BugLink: https://bugs.launchpad.net/bugs/1823037
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register are treated as 0xfff by the
hardware for comparisons.
So correctly set the exclusion range in the hardware to the
last page which is _in_ the range.
Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
Signed-off-by: Joerg Roedel
(cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
Signed-off-by: Jeffrey Lane
iommu/amd: Reserve exclusion range in iova-domain
BugLink: https://bugs.launchpad.net/bugs/1823037
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.
Treat exclusion ranges as reserved regions in the iommu-core
to fix the problem.
Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
Signed-off-by: Joerg Roedel
Reviewed-by: Gary R Hook
(cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
Signed-off-by: Jeffrey Lane
[Test Case]
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
co
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
** Description changed:
[Impact]
- iommu/amd: Set exclusion range correctly
-
- BugLink: https://bugs.launchpad.net/bugs/1823037
-
- The exlcusion range limit register needs to contain the
- base-address of the last page that is part of the range, as
- bits 0-11 of this register are treated as 0xfff by the
- hardware for comparisons.
-
- So correctly set the exclusion range in the hardware to the
- last page which is _in_ the range.
-
- Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
- Signed-off-by: Joerg Roedel
-
- (cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
- Signed-off-by: Jeffrey Lane
-
iommu/amd: Reserve exclusion range in iova-domain
BugLink: https://bugs.launchpad.net/bugs/1823037
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.
Treat exclusion ranges as reserved regions in the iommu-core
to fix the problem.
Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
Signed-off-by: Joerg Roedel
Reviewed-by: Gary R Hook
(cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
Signed-off-by: Jeffrey Lane
- [Test Case]
+ iommu/amd: Set exclusion range correctly
+
+ BugLink: https://bugs.launchpad.net/bugs/1823037
+
+ The exlcusion range limit register needs to contain the
+ base-address of the last page that is part of the range, as
+ bits 0-11 of this register are treated as 0xfff by the
+ hardware for comparisons.
+
+ So correctly set the exclusion range in the hardware to the
+ last page which is _in_ the range.
+
+ Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
+ Signed-off-by: Joerg Roedel
+
+ (cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
+ Signed-off-by: Jeffrey Lane
+
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
Bionic:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range
in iova-domain
ee4a87e6b7fe7e039c1f02c50c53da63e4270732
Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range
in iova-domain
fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range
correctly
-
Disco:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
1823037-amd_iommu-cherrypick
6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range
correctly
-
- Note Disco only required f1cd47fe12 as the first patch was already picked in
LP: #1830934
+ Note Disco only required f1cd47fe12 as the first patch was already
+ picked in LP: #1830934
Not necessary for Eoan as these are already upstream in 5.2-rc1
[Regression Risk]
- Low,
- Only affects the amd_iommu driver:
- drivers/iommu/amd_iommu*
+ Low,this adds memory range protection to the driver and has already been
acked upstream.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823037
Title:
amd_iommu possible data corruption
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Status in linux source package in Disco:
In Progress
Bug description:
[Impact]
iommu/amd: Reserve exclusion range in iova-domain
BugLink: https://bugs.launchpad.net/bugs/1823037
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.
Treat exclusion ranges as reserved regions in the iommu-core
to fix the problem.
Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
Signed-off-by: Joerg Roedel
Reviewed-by: Gary R Hook
(cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
Signed-off-by: Jeffrey Lane
iommu/amd: Set exclusion range correctly
BugLink: https://bugs.launchpad.net/bugs/1823037
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register are treated as 0xfff by the
hardware for comparisons.
So corr
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
** Description changed:
[Impact]
iommu/amd: Reserve exclusion range in iova-domain
BugLink: https://bugs.launchpad.net/bugs/1823037
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.
Treat exclusion ranges as reserved regions in the iommu-core
to fix the problem.
Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
Signed-off-by: Joerg Roedel
Reviewed-by: Gary R Hook
(cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
Signed-off-by: Jeffrey Lane
iommu/amd: Set exclusion range correctly
BugLink: https://bugs.launchpad.net/bugs/1823037
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register are treated as 0xfff by the
hardware for comparisons.
So correctly set the exclusion range in the hardware to the
last page which is _in_ the range.
Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
Signed-off-by: Joerg Roedel
(cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
Signed-off-by: Jeffrey Lane
-
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
Bionic:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range
in iova-domain
ee4a87e6b7fe7e039c1f02c50c53da63e4270732
Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range
in iova-domain
fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range
correctly
Disco:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
1823037-amd_iommu-cherrypick
6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range
correctly
Note Disco only required f1cd47fe12 as the first patch was already
picked in LP: #1830934
Not necessary for Eoan as these are already upstream in 5.2-rc1
[Regression Risk]
- Low,this adds memory range protection to the driver and has already been
acked upstream.
+ Low,this adds memory protection to the driver and has already been acked
upstream and tested by Dell for 24 hours with no failures noted.
** Description changed:
[Impact]
iommu/amd: Reserve exclusion range in iova-domain
BugLink: https://bugs.launchpad.net/bugs/1823037
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.
Treat exclusion ranges as reserved regions in the iommu-core
to fix the problem.
Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
Signed-off-by: Joerg Roedel
Reviewed-by: Gary R Hook
(cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
Signed-off-by: Jeffrey Lane
iommu/amd: Set exclusion range correctly
BugLink: https://bugs.launchpad.net/bugs/1823037
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register are treated as 0xfff by the
hardware for comparisons.
So correctly set the exclusion range in the hardware to the
last page which is _in_ the range.
Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
Signed-off-by: Joerg Roedel
(cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
Signed-off-by: Jeffrey Lane
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
Bionic:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range
in iova-domain
- ee4a87e6b7fe7e039c1f02c50c53da63e4270732
+ ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range
correctly
Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
0acc8c0e862b46b12c233abd76593420f4a20
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
** Description changed:
[Impact]
- iommu/amd: Reserve exclusion range in iova-domain
-
- BugLink: https://bugs.launchpad.net/bugs/1823037
-
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.
-
- Treat exclusion ranges as reserved regions in the iommu-core
- to fix the problem.
-
- Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
- Signed-off-by: Joerg Roedel
- Reviewed-by: Gary R Hook
-
- (cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
- Signed-off-by: Jeffrey Lane
-
- iommu/amd: Set exclusion range correctly
-
- BugLink: https://bugs.launchpad.net/bugs/1823037
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register are treated as 0xfff by the
hardware for comparisons.
So correctly set the exclusion range in the hardware to the
last page which is _in_ the range.
-
- Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
- Signed-off-by: Joerg Roedel
-
- (cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
- Signed-off-by: Jeffrey Lane
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
Bionic:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range
in iova-domain
ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range
correctly
Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range
in iova-domain
fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range
correctly
Disco:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
1823037-amd_iommu-cherrypick
6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range
correctly
Note Disco only required f1cd47fe12 as the first patch was already
picked in LP: #1830934
Not necessary for Eoan as these are already upstream in 5.2-rc1
[Regression Risk]
- Low,this adds memory protection to the driver and has already been acked
upstream and tested by Dell for 24 hours with no failures noted.
+ Low,this adds memory protection to the driver and has already been applied
upstream and tested by Dell for 24 hours with no failures noted.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823037
Title:
amd_iommu possible data corruption
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Status in linux source package in Disco:
In Progress
Bug description:
[Impact]
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register are treated as 0xfff by the
hardware for comparisons.
So correctly set the exclusion range in the hardware to the
last page which is _in_ the range.
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
Bionic:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range
in iova-domain
ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range
correctly
Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range
in iova-domain
fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range
correctly
Disco:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
1823037-amd_iommu-cherrypick
6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range
correctly
Note Disco
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
SRU Request submitted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. The exlcusion range limit register needs to contain the base-address of the last page that is part of the range, as bits 0-11 of this register are treated as 0xfff by the hardware for comparisons. So correctly set the exclusion range in the hardware to the last page which is _in_ the range. [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly These can be picked from my branches here: Bionic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic 1823037-amd_iommu-cherrypick b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range in iova-domain ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range correctly Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic 1823037-amd_iommu-cherrypick 0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range in iova-domain fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range correctly Disco: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco 1823037-amd_iommu-cherrypick 6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range correctly Note Disco only required f1cd47fe12 as the first patch was already picked in LP: #1830934 Not necessary for Eoan as these are already upstream in 5.2-rc1 [Regression Risk] Low,this adds memory protection to the driver and has already been applied upstream and tested by Dell for 24 hours with no failures noted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801574] Re: [cosmic] ipoib ping with large message size failed
Hi Tyler, do you have any update for this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801574 Title: [cosmic] ipoib ping with large message size failed Status in linux package in Ubuntu: Confirmed Bug description: We see that ping over ipoib interface stuck with large packets, this is a new degradation, this test pass on Ubuntu 18.04. After investigating the issue, we see that commit [1] introduce the issue, and it is not an upstream commit, it is canonical commit. Could you please check with the canonical kernel team why they revert that commit? To reproduce the bug, please use ConnectX-3 devices with ipoib connection with 2044 MTU (default) and run command [2]. Is there open Launchpad on it? [1] commit 77a24c313d21e3765b04d90521e9228a9bb6e332 Author: Tyler Hicks Date: Fri Aug 3 21:53:15 2018 + Revert "net: increase fragment memory usage limits" This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It made denial of service attacks on the IP fragment handling easier to carry out. CVE-2018-5391 Signed-off-by: Tyler Hicks Signed-off-by: Stefan Bader [2] ping 13.194.22.1 -I 13.194.23.1 -s 65507 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
So I'm a bit confused because I've been told that A: additional patches are necessary to solve the issue, and B: that the issue is solved without those additional patches. When you did the test, were you using the older, failing firmware levels, or have you updated to the patched firmware that is also part of this fix? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819485] Re: AMD Rome : Additional patches
Does this work in Disco w/ 5.0 kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819485 Title: AMD Rome : Additional patches Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839166] Re: Bios is not setting CPU cores to maximum frequency
Moved to correct project ** Project changed: umkl => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839166 Title: Bios is not setting CPU cores to maximum frequency Status in linux package in Ubuntu: Incomplete Bug description: We are hitting below customer issue as explained briefly below. “ UCS C220 M5 Firmware 4.0(2f) - standalone Ubuntu 16.04.5 LTS with 4.15.0-29-generic kernel (HWE) The customer is looking to force the CPU frequency to stay on max value. Ubuntu detects variable speeds (the CPU cores are going down to 800 MHz): Bios is not setting all CPU cores to maximum frequency in Ubuntu. Bios settings are as below. - Disabled Intel speedstep - Disabled TurboBoost - Limited to C0/C1 only with disabled extended states - Disabled P states, or reduced as much as possible - Set profiles to max performance - Control for CPU performance is done via BIOS, not OS - CPU performance is Enterprise The issue is also not seen on another C220 M5SX without NVMe drives running 3.1(3i). Same kernel version for Ubuntu. Downgrading the firmware on one of the affected C220 M5s doesn't resolve the issue.” All the cores are running on max frequency after applying the below command at the OS level: tuned-adm profile latency-performance “ So please let us know is this BIOS or Ubuntu issue? I . will attach logs soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876990] [NEW] zfs modules in Focal kernel taint kernel
Public bug reported:
the ZFS modules in the shipping focal kernel do not contain the intree
flag, and because of that I believe they are the cause of kernel
tainting discovered during 20.04 certification testing.
The output from a recent certification test run for 20.04:
Kernel taint value is 4097
Taint bit value: 0 (proprietary module was loaded)
Taint bit value: 12 (externally-built ('out-of-tree') module was loaded)
Looking into modinfo for everything loaded at the time, it appears that
the ZFS modules are loaded (even though we did not configure any ZFS
filesystems), and that seems to be the root cause of the test failure.
To test this, I checked /proc/sys/kernel/tainted and verified it was
tainted. I then blacklisted all the ZFS related modules and rebooted,
and then checked /proc/sys/kernel/tainted again and the kernel no longer
shows as being tainted.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1876990
Title:
zfs modules in Focal kernel taint kernel
Status in linux package in Ubuntu:
New
Bug description:
the ZFS modules in the shipping focal kernel do not contain the intree
flag, and because of that I believe they are the cause of kernel
tainting discovered during 20.04 certification testing.
The output from a recent certification test run for 20.04:
Kernel taint value is 4097
Taint bit value: 0 (proprietary module was loaded)
Taint bit value: 12 (externally-built ('out-of-tree') module was loaded)
Looking into modinfo for everything loaded at the time, it appears
that the ZFS modules are loaded (even though we did not configure any
ZFS filesystems), and that seems to be the root cause of the test
failure. To test this, I checked /proc/sys/kernel/tainted and
verified it was tainted. I then blacklisted all the ZFS related
modules and rebooted, and then checked /proc/sys/kernel/tainted again
and the kernel no longer shows as being tainted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876990/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877270] Re: Devlink - add RoCE disable kernel support
Moved to kernel package
** Changed in: mstflint (Ubuntu)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: mstflint (Ubuntu)
Status: New => In Progress
** Changed in: mstflint (Ubuntu)
Importance: Undecided => Medium
** Package changed: mstflint (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Assignee: Jeff Lane (bladernr) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877270
Title:
Devlink - add RoCE disable kernel support
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Bug description:
[Impact]
RoCE disable feature was added to the kernel v5.5.
This feature was requested by Mellanox customers that use Ubuntu 20.04,
and it's a very high important to deliver this feature to the customers
in one of ubuntu 20.04 SRU.
[SHORT DESCRIPTION]
RoCE enablement state controls driver support for RoCE traffic.
When RoCE is disabled, there is no gid table, only raw ethernet QPs are
supported and traffic on the well known UDP RoCE port is handled as raw
ethernet traffic.
[Test Case]
To change RoCE enablement state a user must change the driverinit
cmode value and run devlink reload.
User command examples:
- Disable RoCE::
$ devlink dev param set pci/:06:00.0 name enable_roce value false
cmode driverinit
$ devlink dev reload pci/:06:00.0
- Read RoCE enablement state::
$ devlink dev param show pci/:06:00.0 name enable_roce
pci/:06:00.0:
name enable_roce type generic
values:
cmode driverinit value true
[Regression Potential]
This feature shouldn't affect the regression because it's only adding support
for
RoCE enable/disable.
Also,
This feature was tested internally by Mellanox QA teams
those tests logs/results are private unfortunately i can't share it here
[Other Info]
Feature patchset:
94de879c28d8 IB/mlx5: Load profile according to RoCE enablement state
b5a498baf929 IB/mlx5: Rename profile and init methods
cc9defcbb8fa net/mlx5: Handle "enable_roce" devlink param
e90cde0d76f0 net/mlx5: Document flow_steering_mode devlink param
6c7295e13ffd devlink: Add new "enable_roce" generic device param
patctwork:
https://patchwork.ozlabs.org/cover/1192314/
userspace:
No userspace dependency on this. the feature uses the devlink
param functionality which already exists in UB20.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877270/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883229] Re: Ubuntu server installation on S3260M4 server gets failed
** Package changed: checkbox (Ubuntu) => grub (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883229 Title: Ubuntu server installation on S3260M4 server gets failed Status in grub package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Details/Description: - Ubuntu 20.04 fails on S3260 M4 with Gonga Beach in UEFI mode. Os get installed. However, upon rebooting OS never came up. Grub loads only to get hanged in a black screen. No options work later. Unable to collect Installer logs. How to reproduce: -- 1.Update S3260M4 M4 to bios build ucs-s3260-huu-4.1.2S36 2.Deploy Ubuntu 20.04 on S3260 M4. 3.Observe the installation proceeding and after installation OS reboots and loads the kernel and gets hanged on the black screen 4. The same OS works in Legacy mode in C3000 RAID controller card of LSI. Expected behavior: - Ubuntu 20.04 should get deployed in GB/DD-Raid in UEFI mode Screenshots -- Screenshot attached. Please let us know how to collect logs on this scenario Note :With MASS deployment we are able to deploy OS successfully with USFI method. Attached the logs of MASS server in this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1883229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883229] Re: Ubuntu server installation on S3260M4 server gets failed
Try installing 18.04 in the same manner and see if that works. It would be useful to know if this is limited to 20.04 or is more widespread, since you didn't certify this one with 18.04 either. Also, what is a Gonga Beach? Am I correct in guessing that this is the RAID controller? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883229 Title: Ubuntu server installation on S3260M4 server gets failed Status in grub package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Details/Description: - Ubuntu 20.04 fails on S3260 M4 with Gonga Beach in UEFI mode. Os get installed. However, upon rebooting OS never came up. Grub loads only to get hanged in a black screen. No options work later. Unable to collect Installer logs. How to reproduce: -- 1.Update S3260M4 M4 to bios build ucs-s3260-huu-4.1.2S36 2.Deploy Ubuntu 20.04 on S3260 M4. 3.Observe the installation proceeding and after installation OS reboots and loads the kernel and gets hanged on the black screen 4. The same OS works in Legacy mode in C3000 RAID controller card of LSI. Expected behavior: - Ubuntu 20.04 should get deployed in GB/DD-Raid in UEFI mode Screenshots -- Screenshot attached. Please let us know how to collect logs on this scenario Note :With MASS deployment we are able to deploy OS successfully with USFI method. Attached the logs of MASS server in this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1883229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883312] Re: NVMe FC Auto-connect is not working for Ubuntu 20.04
** Description changed: - Jeff, - - Please update Ubuntu 20.04 to from nvme-cli 1.9 to nvme-cli 1.10.1. 1.9 - autoconnect is not working. - - thank you - Laurie - -- + [SUMMARY] Auto-connect is not working for Ubuntu 20.04. However manual nvme discover and connect commands works. root@ubuntu2004:~# uname -a Linux ubuntu2004 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:06:57 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu2004:~# nvme version nvme version 1.9 root@ubuntu2004:~# cat /sys/module/lpfc/version 0:12.6.0.4 root@ubuntu2004:~# cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal root@ubuntu2004:~# + + [IMPACT] + + + + [FIXES] + + Update nvme-cli to 1.10.1 + + [TESTING] + + [REGRESSION RISK] ** Package changed: linux (Ubuntu) => nvme-cli (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883312 Title: NVMe FC Auto-connect is not working for Ubuntu 20.04 Status in nvme-cli package in Ubuntu: New Bug description: [SUMMARY] Auto-connect is not working for Ubuntu 20.04. However manual nvme discover and connect commands works. root@ubuntu2004:~# uname -a Linux ubuntu2004 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:06:57 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu2004:~# nvme version nvme version 1.9 root@ubuntu2004:~# cat /sys/module/lpfc/version 0:12.6.0.4 root@ubuntu2004:~# cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal root@ubuntu2004:~# [IMPACT] [FIXES] Update nvme-cli to 1.10.1 [TESTING] [REGRESSION RISK] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1883312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877270] Re: Devlink - add RoCE disable kernel support
Pushing patches for this bug to this branch:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1877270-pull-roce-disable-from-5.5
** Description changed:
[Impact]
RoCE disable feature was added to the kernel v5.5.
This feature was requested by Mellanox customers that use Ubuntu 20.04,
and it's a very high important to deliver this feature to the customers
in one of ubuntu 20.04 SRU.
[SHORT DESCRIPTION]
RoCE enablement state controls driver support for RoCE traffic.
When RoCE is disabled, there is no gid table, only raw ethernet QPs are
supported and traffic on the well known UDP RoCE port is handled as raw
ethernet traffic.
[Test Case]
To change RoCE enablement state a user must change the driverinit cmode
value and run devlink reload.
User command examples:
- Disable RoCE::
$ devlink dev param set pci/:06:00.0 name enable_roce value false
cmode driverinit
$ devlink dev reload pci/:06:00.0
- Read RoCE enablement state::
$ devlink dev param show pci/:06:00.0 name enable_roce
pci/:06:00.0:
name enable_roce type generic
values:
cmode driverinit value true
[Regression Potential]
This feature shouldn't affect the regression because it's only adding support
for
RoCE enable/disable.
Also,
This feature was tested internally by Mellanox QA teams
those tests logs/results are private unfortunately i can't share it here
[Other Info]
Feature patchset:
- 4383cfcc65e7 net/mlx5: Add devlink reload
+ 4383cfcc65e7 net/mlx5: Add devlink reload
32680da71034 net/mlx5: Remove unneeded variable in mlx5_unload_one
94de879c28d8 IB/mlx5: Load profile according to RoCE enablement state
b5a498baf929 IB/mlx5: Rename profile and init methods
cc9defcbb8fa net/mlx5: Handle "enable_roce" devlink param
e90cde0d76f0 net/mlx5: Document flow_steering_mode devlink param
6c7295e13ffd devlink: Add new "enable_roce" generic device param
- 070c63f20f6c ("net: devlink: allow to change namespaces during
- reload")## This one does not apply cleanly
-
All are in upstream in 5.5, so no pick into Groovy necessary
userspace:
No userspace dependency on this. the feature uses the devlink
param functionality which already exists in UB20.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877270
Title:
Devlink - add RoCE disable kernel support
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Bug description:
[Impact]
RoCE disable feature was added to the kernel v5.5.
This feature was requested by Mellanox customers that use Ubuntu 20.04,
and it's a very high important to deliver this feature to the customers
in one of ubuntu 20.04 SRU.
[SHORT DESCRIPTION]
RoCE enablement state controls driver support for RoCE traffic.
When RoCE is disabled, there is no gid table, only raw ethernet QPs are
supported and traffic on the well known UDP RoCE port is handled as raw
ethernet traffic.
[Test Case]
To change RoCE enablement state a user must change the driverinit
cmode value and run devlink reload.
User command examples:
- Disable RoCE::
$ devlink dev param set pci/:06:00.0 name enable_roce value false
cmode driverinit
$ devlink dev reload pci/:06:00.0
- Read RoCE enablement state::
$ devlink dev param show pci/:06:00.0 name enable_roce
pci/:06:00.0:
name enable_roce type generic
values:
cmode driverinit value true
[Regression Potential]
This feature shouldn't affect the regression because it's only adding support
for
RoCE enable/disable.
Also,
This feature was tested internally by Mellanox QA teams
those tests logs/results are private unfortunately i can't share it here
[Other Info]
Feature patchset:
4383cfcc65e7 net/mlx5: Add devlink reload
32680da71034 net/mlx5: Remove unneeded variable in mlx5_unload_one
94de879c28d8 IB/mlx5: Load profile according to RoCE enablement state
b5a498baf929 IB/mlx5: Rename profile and init methods
cc9defcbb8fa net/mlx5: Handle "enable_roce" devlink param
e90cde0d76f0 net/mlx5: Document flow_steering_mode devlink param
6c7295e13ffd devlink: Add new "enable_roce" generic device param
All are in upstream in 5.5, so no pick into Groovy necessary
userspace:
No userspace dependency on this. the feature uses the devlink
param functionality which already exists in UB20.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877270/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-package
[Kernel-packages] [Bug 1885030] Re: [Intel] Add Error Disconnect Recover support
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885030 Title: [Intel] Add Error Disconnect Recover support Status in intel: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Incomplete Bug description: As per the following PCIe spec ECNs, implement EDR support in Linux kernel and upstream it. https://members.pcisig.com/wg/PCI-SIG/document/14076 https://members.pcisig.com/wg/PCI-SIG/document/12888 Commit ID: Merged 5.7 rc1 20e15e673b05 27005618178e 6d2c89441571 894020fdd88c ac1c8e35a326 aea47413e7ce b5dfbeacf748 b6cf1a42f916 be06c1b42eea e8e5ff2aeec1 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1885030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885030] Re: [Intel] Add Error Disconnect Recover support
** Description changed: As per the following PCIe spec ECNs, implement EDR support in Linux kernel and upstream it. https://members.pcisig.com/wg/PCI-SIG/document/14076 https://members.pcisig.com/wg/PCI-SIG/document/12888 - Commit ID: Merged 5.7 rc1 - 20e15e673b05 27005618178e 6d2c89441571 894020fdd88c ac1c8e35a326 aea47413e7ce b5dfbeacf748 b6cf1a42f916 be06c1b42eea e8e5ff2aeec1 + Patchset (Merged 5.7 mainline): + 894020fdd88c PCI/AER: Rationalize error status register clearing + ac1c8e35a326 PCI/DPC: Add Error Disconnect Recover (EDR) support + aea47413e7ce PCI/DPC: Expose dpc_process_error(), dpc_reset_link() for use by EDR + 20e15e673b05 PCI/AER: Add pci_aer_raw_clear_status() to unconditionally clear Error Status + 27005618178e PCI/DPC: Cache DPC capabilities in pci_init_capabilities() + e8e5ff2aeec1 PCI/ERR: Return status of pcie_do_recovery() + b6cf1a42f916 PCI/ERR: Remove service dependency in pcie_do_recovery() + be06c1b42eea PCI/DPC: Move DPC data into struct pci_dev + 6d2c89441571 PCI/ERR: Update error status after reset_link() + b5dfbeacf748 PCI/ERR: Combine pci_channel_io_frozen cases -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885030 Title: [Intel] Add Error Disconnect Recover support Status in intel: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Incomplete Bug description: As per the following PCIe spec ECNs, implement EDR support in Linux kernel and upstream it. https://members.pcisig.com/wg/PCI-SIG/document/14076 https://members.pcisig.com/wg/PCI-SIG/document/12888 Patchset (Merged 5.7 mainline): 894020fdd88c PCI/AER: Rationalize error status register clearing ac1c8e35a326 PCI/DPC: Add Error Disconnect Recover (EDR) support aea47413e7ce PCI/DPC: Expose dpc_process_error(), dpc_reset_link() for use by EDR 20e15e673b05 PCI/AER: Add pci_aer_raw_clear_status() to unconditionally clear Error Status 27005618178e PCI/DPC: Cache DPC capabilities in pci_init_capabilities() e8e5ff2aeec1 PCI/ERR: Return status of pcie_do_recovery() b6cf1a42f916 PCI/ERR: Remove service dependency in pcie_do_recovery() be06c1b42eea PCI/DPC: Move DPC data into struct pci_dev 6d2c89441571 PCI/ERR: Update error status after reset_link() b5dfbeacf748 PCI/ERR: Combine pci_channel_io_frozen cases To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1885030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885030] Re: [Intel] Add Error Disconnect Recover support
** Changed in: intel Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885030 Title: [Intel] Add Error Disconnect Recover support Status in intel: Won't Fix Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Incomplete Bug description: As per the following PCIe spec ECNs, implement EDR support in Linux kernel and upstream it. https://members.pcisig.com/wg/PCI-SIG/document/14076 https://members.pcisig.com/wg/PCI-SIG/document/12888 Patchset (Merged 5.7 mainline): 894020fdd88c PCI/AER: Rationalize error status register clearing ac1c8e35a326 PCI/DPC: Add Error Disconnect Recover (EDR) support aea47413e7ce PCI/DPC: Expose dpc_process_error(), dpc_reset_link() for use by EDR 20e15e673b05 PCI/AER: Add pci_aer_raw_clear_status() to unconditionally clear Error Status 27005618178e PCI/DPC: Cache DPC capabilities in pci_init_capabilities() e8e5ff2aeec1 PCI/ERR: Return status of pcie_do_recovery() b6cf1a42f916 PCI/ERR: Remove service dependency in pcie_do_recovery() be06c1b42eea PCI/DPC: Move DPC data into struct pci_dev 6d2c89441571 PCI/ERR: Update error status after reset_link() b5dfbeacf748 PCI/ERR: Combine pci_channel_io_frozen cases To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1885030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856340] Re: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies
** Description changed: [IMPACT] - Here are the kernel and cli updates we discussed in email related to - LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc + In the run up to 20.04 release, Broadcom wants to ensure that customers + running ubuntu 20.04 have the proper support when using Emulex + Fibrechannel cards to use NVMe over FC. + + This updates nvme-fc and nvme with cherry picks from 5.5 upstream that + didn't land in time for the upstream 5.4 release. + + Deferring this request would delay customers using NVMe over FC until + February when the first HWE for Focal is released, roughly 9 months from + now. + + Here are the kernel and cli updates broadcom requested via email related + to LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc 12.6.0.x solution. - Please pull these into Ubuntu 20.04. - - Thank you - Laurie - - Expected that ubuntu is pulling in kernel v5.4 as a base. These would - go on top of that. [FIXES] Additional patches recommended: ( ) f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2 53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes 44fbf3bb1ac3 - Sep 27 2019 - nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu 7db394848ece - Sep 27 2019 - nvme-fc: clarify error messages bcde5f0fc7d3 - Sep 27 2019 - nvme-fc: ensure association_id is cleared regardless of a Disconnect LS 48c9e85b2346 - Oct 14 2019 - nvme: resync include/linux/nvme.h with nvmecli 64fab7290dc3 - Oct 28 2019 - nvme: Fix parsing of ANA log page These are clean cherry-picks from 5.5 into 5.4 and can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1856340-broadcom-nvme-updates These two are already in focal and are only left here for reference as they were part of the original request: 863fbae929c7 - Nov 14 2019 - nvme_fc: add module to ops template to allow module references c869e494ef8b - Nov 21 2019 - nvme-fc: fix double-free scenarios on hw queues - [TESTING] - [REGRESSION RISK] + Low: Patches are already upstream in 5.5 and have been tested there and by Broadcom Emululex. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856340 Title: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [IMPACT] In the run up to 20.04 release, Broadcom wants to ensure that customers running ubuntu 20.04 have the proper support when using Emulex Fibrechannel cards to use NVMe over FC. This updates nvme-fc and nvme with cherry picks from 5.5 upstream that didn't land in time for the upstream 5.4 release. Deferring this request would delay customers using NVMe over FC until February when the first HWE for Focal is released, roughly 9 months from now. Here are the kernel and cli updates broadcom requested via email related to LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc 12.6.0.x solution. [FIXES] Additional patches recommended: ( ) f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2 53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes 44fbf3bb1ac3 - Sep 27 2019 - nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu 7db394848ece - Sep 27 2019 - nvme-fc: clarify error messages bcde5f0fc7d3 - Sep 27 2019 - nvme-fc: ensure association_id is cleared regardless of a Disconnect LS 48c9e85b2346 - Oct 14 2019 - nvme: resync include/linux/nvme.h with nvmecli 64fab7290dc3 - Oct 28 2019 - nvme: Fix parsing of ANA log page These are clean cherry-picks from 5.5 into 5.4 and can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1856340-broadcom-nvme-updates These two are already in focal and are only left here for reference as they were part of the original request: 863fbae929c7 - Nov 14 2019 - nvme_fc: add module to ops template to allow module references c869e494ef8b - Nov 21 2019 - nvme-fc: fix double-free scenarios on hw queues [REGRESSION RISK] Low: Patches are already upstream in 5.5 and have been tested there and by Broadcom Emululex. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
tion warnings d7b761b0694986ea811c0daaa1178bfaaddf036d scsi: lpfc: Make some symbols static a82b3539dc27b3a85f0c46c9bc398734fdd08260 scsi: lpfc: Remove set but not used variables 'qp' a5c990eea5ddd587bcd9af6dc973a1653c8d94af scsi: lpfc: Use *_pool_zalloc rather than *_pool_alloc 852eb63a7179249f95ba2e1faaabf403e39d88b3 scsi: lpfc: Update lpfc version to 12.2.0.3 3ec5ec408ca633e17d3483e8b806c9fa447e19cc scsi: lpfc: Fix incomplete NVME discovery when target d4e9ddd5ae8f26c521692283c7cbedc7e9881529 scsi: lpfc: Fix: Rework setting of fdmi symbolic node name registration a0c94c5ef874b214305cca965acc7edc27bb69a6 scsi: lpfc: Fix missing check for CSF in Write Object Mbox Rsp 3712967ea7f2d3793ae2a39e9eae2df111d770b5 scsi: lpfc: Fix Fabric hostname registration if system hostname changes 25d4132f95c25e6f78a94666a1e067291272888a scsi: lpfc: Fix ras_log via debugfs 265fb8efca11eee1ffe8edd2bc0a9fbf31b6b84e scsi: lpfc: Fix disablement of FC-AL on lpe35000 models b88d705fa037b222ecdd5de867132ae25403fe48 scsi: lpfc: Fix unmap of dpp bars affecting next driver load 78a7872570fbeed44e7362354619b403c6e6de1e scsi: lpfc: Fix MDS Latency Diagnostics Err-drop rates f44ccecf36581a2030313e979127013f9d455d3a scsi: lpfc: Fix improper flag check for IO type e627554eedcfac83bb2ba073adf711a13049273a scsi: lpfc: Update lpfc version to 12.6.0.3 9c75a0dee87b2bad80d381ad9fa8ef90847d3a1d scsi: lpfc: Fix RQ buffer leakage when no IOCBs available 89cc9dba63c91a6c796dc46342c1d57c82c9b0cd scsi: lpfc: Fix lpfc_io_buf resource leak in lpfc_get_scsi_buf_s4 error path 692fc8380ca0f9185e75e01a74357d2cf3083743 scsi: lpfc: Fix broken Credit Recovery after driver load 0f74f70cb674e3b8712e896863ad85db4d193d46 scsi: lpfc: Fix registration of ELS type support in fdmi 01034e708a353fed29963d084c35d58785a317a6 scsi: lpfc: Fix release of hwq to clear the eq relationship 3cd50eac891db354e945bf9898726e163a19560e scsi: lpfc: Fix compiler warning on frame size 3ad04f4f0ad75ad4e7d886133f673d9fe20aa9c4 scsi: lpfc: Fix coverity errors in fmdi attribute handling 8d9fae72109e9921f52be342007b4c78490ea4fe scsi: lpfc: Remove handler for obsolete ELS - Read Port Status (RPS) 20d674a4bf64acf54eadc7215ea32b88a3a7687e scsi: lpfc: Clean up hba max_lun_queue_depth checks 35817310d9e05e666dbd242750008dad33ed8992 scsi: lpfc: Update lpfc version to 12.6.0.4 fd6cc30f341fea14bac45bf1c5c9d10702c18a9d scsi: lpfc: Copyright updates for 12.6.0.4 patches [TESTING] - [REGRESSION RISK] Low, these patches are already accepted upstream in 5.5 and have been tested by Broadcom for regression potential. ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855303 Title: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [IMPACT] This is related to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340 both patch sets are needed to make up This is a massive number of updates by Broadcom to the lpfc driver that didn't make 5.4 in time. As 20.04 is an LTS release with expected hardware support for 5 years, we need to ensure as much hardware support lands as possible to support server vendors over the next couple years. Broadcom has updated the lpfc driver to version 12.6.0.2 in 5.5. The version in focal is 12.2.0.3 and missing several bug fixes and hardware support additions. Please update the driver in focal appropriately. [FIXES] eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by last cpu id set 4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned cpu for allocation 3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version to 12.6.0.2 542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max queues to be hdwq count bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map for not present cpus d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of lpfc_sli4_cleanup_poll_list() 6c6d59e0fe5b86cf273d6d744a6a9768c4ecc756 scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences 6f23f8c5c9f1be4eb17c035129c80e49000c18a7 scsi: lpfc: fix: Coverity: lpfc_get_scsi_buf_s3(): Null pointer dereferences 61951a6d3153b4482404b739be921a7459f8dc12 scsi: lpfc: Fix lpfc_cpumask_of_node_init() eea2d396aa57acb3607f79ef04c08c2c5166f3fa scsi: lpfc: Fix a kernel warning triggered by lpfc_sli4_enable_intr() 765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel warning triggered by lpfc_get_sgl_per_hdwq() aff6ab9e7221c1b5d15418419b9797e5badd4aec
[Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
Hi Vignesh, As I've been working on this and I just noticed that several of these patches do not exist in the upstream kernel: 89cc9dba63c91a6c796dc46342c1d57c82c9b0cd scsi: lpfc: Fix lpfc_io_buf resource leak in lpfc_get_scsi_buf_s4 error path 692fc8380ca0f9185e75e01a74357d2cf3083743 scsi: lpfc: Fix broken Credit Recovery after driver load 0f74f70cb674e3b8712e896863ad85db4d193d46 scsi: lpfc: Fix registration of ELS type support in fdmi 01034e708a353fed29963d084c35d58785a317a6 scsi: lpfc: Fix release of hwq to clear the eq relationship 3cd50eac891db354e945bf9898726e163a19560e scsi: lpfc: Fix compiler warning on frame size 3ad04f4f0ad75ad4e7d886133f673d9fe20aa9c4 scsi: lpfc: Fix coverity errors in fmdi attribute handling 8d9fae72109e9921f52be342007b4c78490ea4fe scsi: lpfc: Remove handler for obsolete ELS - Read Port Status (RPS) 20d674a4bf64acf54eadc7215ea32b88a3a7687e scsi: lpfc: Clean up hba max_lun_queue_depth checks 35817310d9e05e666dbd242750008dad33ed8992 scsi: lpfc: Update lpfc version to 12.6.0.4 fd6cc30f341fea14bac45bf1c5c9d10702c18a9d scsi: lpfc: Copyright updates for 12.6.0.4 patches 73ec6d2748dc35db2b32cf3c182a27c4a0837b9b scsi: fc: Update Descriptor definition and add RDF and Link Integrity FPINs df3fe76658ed47617741819a501e2bd2ae446962 scsi: lpfc: add RDF registration and Link Integrity FPIN logging So I appreciate the patch set you've provided, but due to the number of patches, what I need to do is cherry-pick them from mainline and push a branch with cherry picks rather than 70+ patches that need to be reviewed/applied by the kernel team. And because I can't find these in mainline at all (I've just checked all the proposed commit ids against the most recent updates to mainline) I can't cherry pick these. Do you know when they'll be accepted upstream? I also checked against Linus tree and cant find those commit IDs there either. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855303 Title: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [IMPACT] This is related to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340 both patch sets are needed to make up This is a massive number of updates by Broadcom to the lpfc driver that didn't make 5.4 in time. As 20.04 is an LTS release with expected hardware support for 5 years, we need to ensure as much hardware support lands as possible to support server vendors over the next couple years. Broadcom has updated the lpfc driver to version 12.6.0.2 in 5.5. The version in focal is 12.2.0.3 and missing several bug fixes and hardware support additions. Please update the driver in focal appropriately. [FIXES] eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by last cpu id set 4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned cpu for allocation 3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version to 12.6.0.2 542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max queues to be hdwq count bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map for not present cpus d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of lpfc_sli4_cleanup_poll_list() 6c6d59e0fe5b86cf273d6d744a6a9768c4ecc756 scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences 6f23f8c5c9f1be4eb17c035129c80e49000c18a7 scsi: lpfc: fix: Coverity: lpfc_get_scsi_buf_s3(): Null pointer dereferences 61951a6d3153b4482404b739be921a7459f8dc12 scsi: lpfc: Fix lpfc_cpumask_of_node_init() eea2d396aa57acb3607f79ef04c08c2c5166f3fa scsi: lpfc: Fix a kernel warning triggered by lpfc_sli4_enable_intr() 765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel warning triggered by lpfc_get_sgl_per_hdwq() aff6ab9e7221c1b5d15418419b9797e5badd4a
[Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
Additionally, this one did not cleanly apply:
Additionally, this one does not cleanly apply when cherry-picked:
765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel
warning triggered by lpfc_get_sgl_per_hdwq()
bladernr@galactica:~/development/kernels-ubuntu/focal$ cherrypick
765ab6cdac3b681952da0e22184bf6cf1ae41cf8
error: could not apply 765ab6cdac3b... scsi: lpfc: Fix a kernel warning
triggered by lpfc_get_sgl_per_hdwq()
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add ' or 'git rm '
hint: and commit the result with 'git commit'
bladernr@galactica:~/development/kernels-ubuntu/focal$ git diff
diff --cc drivers/scsi/lpfc/lpfc_sli.c
index e660ee98ad8b,613fbf4a7da9..
--- a/drivers/scsi/lpfc/lpfc_sli.c
+++ b/drivers/scsi/lpfc/lpfc_sli.c
@@@ -20687,7 -20668,7 +20687,11 @@@ lpfc_get_sgl_per_hdwq(struct lpfc_hba *
/* allocate more */
spin_unlock_irqrestore(&hdwq->hdwq_lock, iflags);
tmp = kmalloc_node(sizeof(*tmp), GFP_ATOMIC,
++<<< HEAD
+ cpu_to_node(hdwq->io_wq->chann));
++===
+ cpu_to_node(raw_smp_processor_id()));
++>>> 765ab6cdac3b... scsi: lpfc: Fix a kernel warning triggered by
lpfc_get_sgl_per_hdwq()
if (!tmp) {
lpfc_printf_log(phba, KERN_INFO, LOG_SLI,
"8353 error kmalloc memory for HDWQ "
@@@ -20830,7 -20811,7 +20834,11 @@@ lpfc_get_cmd_rsp_buf_per_hdwq(struct lp
/* allocate more */
spin_unlock_irqrestore(&hdwq->hdwq_lock, iflags);
tmp = kmalloc_node(sizeof(*tmp), GFP_ATOMIC,
++<<< HEAD
+ cpu_to_node(hdwq->io_wq->chann));
++===
+ cpu_to_node(raw_smp_processor_id()));
++>>> 765ab6cdac3b... scsi: lpfc: Fix a kernel warning triggered by
lpfc_get_sgl_per_hdwq()
if (!tmp) {
lpfc_printf_log(phba, KERN_INFO, LOG_SLI,
"8355 error kmalloc memory for HDWQ "
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1855303
Title:
Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Bug description:
[IMPACT]
This is related to bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340
both patch sets are needed to make up
This is a massive number of updates by Broadcom to the lpfc driver that
didn't make 5.4 in time. As 20.04 is an LTS release with expected hardware
support for 5 years, we need to ensure as much hardware support lands as
possible to support server vendors over the next couple years.
Broadcom has updated the lpfc driver to version 12.6.0.2 in 5.5. The
version in focal is 12.2.0.3 and missing several bug fixes and
hardware support additions.
Please update the driver in focal appropriately.
[FIXES]
eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by
last cpu id set
4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned
cpu for allocation
3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version
to 12.6.0.2
542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max
queues to be hdwq count
bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map
for not present cpus
d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of
lpfc_sli4_cleanup_poll_list()
6c6d59e0fe5b86cf273d6d744a6a9768c4ecc756 scsi: lpfc: fix: Coverity:
lpfc_cmpl_els_rsp(): Null pointer dereferences
6f23f8c5c9f1be4eb17c035129c80e49000c18a7 scsi: lpfc: fix: Coverity:
lpfc_get_scsi_buf_s3(): Null pointer dereferences
61951a6d3153b4482404b739be921a7459f8dc12 scsi: lpfc: Fix
lpfc_cpumask_of_node_init()
eea2d396aa57acb3607f79ef04c08c2c5166f3fa scsi: lpfc: Fix a kernel
warning triggered by lpfc_sli4_enable_intr()
765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel
warning triggered by lpfc_get_sgl_per_hdwq()
aff6ab9e7221c1b5d15418419b9797e5badd4aec scsi: lpfc: Update lpfc version
to 12.6.0.1
171f6c41949f6e9d5e09dcac842a10bf8dda8dcc scsi: lpfc: Add enablement of
multiple adapter dumps
dcaa213679387e95a315dca05c57dbb15273703c scsi: lpfc: Change default IRQ
model on AMD architectures
93a4d6f40198dffcca35d9a928c409f9290f1fe0 scsi: lpfc: Add registration
for CPU Offline/Online events
b9da814cd5f5bb93041a6e4dbc9c5149713186ff scsi: lpfc: Clarify FAWNN error
message
69641627c653464db46f3e3d8c438349be055670 scsi: lpfc: Sync with FC-NVMe-2
SLER change to require Conf with SLER
dda5bdf074da3782ff9e785ee50cd2a3f214d498 scsi: lpfc: Fix dynamic fw log
enablement check
2332e
[Kernel-packages] [Bug 1864484] Re: Update SmartPQI driver in Focal to 1.2.10-025
Customer notified to test new kernels and verify the driver updates. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864484 Title: Update SmartPQI driver in Focal to 1.2.10-025 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [IMPACT] Feature request to update the SmartPQI driver in Focal to 1.2.10-025 Microchip produces the Smart Storage controllers that are used by several major OEMs we partner with. There is a new generation of controller coming to market later this summer. While customers will be able to use these new controllers with the driver as it is in Focal today, they will be missing several bug fixes and enhancements that have already landed upstream in 5.5. For this reason, Microchip and HPE have asked us to pull these patches to update the SmartPQI driver in Focal to the current upstream version. [FIXES] These are the recommended patches from Microchip that should be cherry-picked from mainline. 390e28087823 scsi: smartpqi: bump version 694c5d5b4625 scsi: smartpqi: Align driver syntax with oob 0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants 5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device e655d469c32d scsi: smartpqi: correct syntax issue bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung 21432010d528 scsi: smartpqi: add inquiry timeouts b969261134c1 scsi: smartpqi: fix call trace in device discovery 0530736e40a0 scsi: smartpqi: fix controller lockup observed during force reboot 9e322310e16c scsi: smartpqi: clean up an indentation issue 1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info' a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement All are clean cherry picks into the 5.4 branch and can be pulled from my branch here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1864484-smartpqi-to-1.2.10-025 [TESTING] modinfo for smartpqi should show: version:1.2.10-025 description:Driver for Microsemi Smart Family Controller version 1.2.10-025 [REGRESSION RISK] Low - Focal is not yet released, this is not being backported to current releases, patches pick cleanly and have been tested by the upstream maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
27d8bd60b58f422f6df02853c33558b11 scsi: lpfc: use > spin_lock_irqsave in IRQ context > ee9a256cd8d0f7d23d7dd310d7fdc23f28cada0d scsi: lpfc: remove redundant code > 60a8db790255a6bebcdc41d97e8084a440398206 Merge tag 'scsi-fixes' of > git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi > 491beed3b102b6e6c0e7734200661242226e3933 genirq/affinity: Create > affinity mask for single vector > a86c71ba3022331f79662d7f12d1b25188c7e377 scsi: lpfc: Fix crash when cpu > count is 1 and null irq affinity mask > 70a51d8c53176080e82b2aef050f820ccdd4b3f8 scsi: lpfc: Remove unnecessary > null check before kfree > f65420df914a85e33b2c8b1cab310858b2abb7c0 Merge tag 'scsi-fixes' of > git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi > 057959c6e36e4e6e5303a39c4df79c4af9d40923 scsi: lpfc: reduce stack size > with CONFIG_GCC_PLUGIN_STRUCTLEAK_VERBOSE > 1f7563f743d7081710a9d186a8b203997d09f383 Merge tag 'scsi-sg' of > git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi > ba6d10ab8014ac10d25ca513352b6665e73b5785 Merge tag 'scsi-misc' of > git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi > 6b2c8e522c8980fedfd24f3d1e69c3bccdb9414d Merge branch 'nvme-5.3' of > git://git.infradead.org/nvme into for-5.3/block > 41b194b843a255d5a6e9468edd3ab1d71a24abb3 lpfc: add sysfs interface to > post NVME RSCN > 6f2589f478795c46a61696d7d7c2f47a0bc6cfe3 lpfc: add support for > translating an RSCN rcv into a discovery rescan > ab723121a8eade04ecc6bd7116924c359336f4eb lpfc: add nvmet discovery_event > op support > f60cb93bbfecf1ad13713af285c3793e861fc9b2 lpfc: add support to generate > RSCN events for nport > 3dccdf53c2f38399b11085ded4447ce1467f006c scsi: core: avoid preallocating > big SGL for data > 92524fa12312d1f082a473e14c590c48b4ef3fe5 scsi: core: avoid preallocating > big SGL for protection information > 46e8e475a160be5e31e99171b7c0c8a21eb4d6ad scsi: lpfc: use sg helper to > iterate over scatterlist > 336df6eb628298e27e40e23d1eb00a0fb7083269 scsi: lpfc: Avoid unused > function warnings > d7b761b0694986ea811c0daaa1178bfaaddf036d scsi: lpfc: Make some symbols > static > a82b3539dc27b3a85f0c46c9bc398734fdd08260 scsi: lpfc: Remove set but not > used variables 'qp' > a5c990eea5ddd587bcd9af6dc973a1653c8d94af scsi: lpfc: Use *_pool_zalloc > rather than *_pool_alloc > 852eb63a7179249f95ba2e1faaabf403e39d88b3 scsi: lpfc: Update lpfc version > to 12.2.0.3 > 3ec5ec408ca633e17d3483e8b806c9fa447e19cc scsi: lpfc: Fix incomplete NVME > discovery when target > d4e9ddd5ae8f26c521692283c7cbedc7e9881529 scsi: lpfc: Fix: Rework setting of > fdmi symbolic node name registration > a0c94c5ef874b214305cca965acc7edc27bb69a6 scsi: lpfc: Fix missing check for > CSF in Write Object Mbox Rsp > 3712967ea7f2d3793ae2a39e9eae2df111d770b5 scsi: lpfc: Fix Fabric hostname > registration if system hostname changes > 25d4132f95c25e6f78a94666a1e067291272888a scsi: lpfc: Fix ras_log via debugfs > 265fb8efca11eee1ffe8edd2bc0a9fbf31b6b84e scsi: lpfc: Fix disablement of > FC-AL on lpe35000 models > b88d705fa037b222ecdd5de867132ae25403fe48 scsi: lpfc: Fix unmap of dpp bars > affecting next driver load > 78a7872570fbeed44e7362354619b403c6e6de1e scsi: lpfc: Fix MDS Latency > Diagnostics Err-drop rates > f44ccecf36581a2030313e979127013f9d455d3a scsi: lpfc: Fix improper flag > check for IO type > e627554eedcfac83bb2ba073adf711a13049273a scsi: lpfc: Update lpfc version to > 12.6.0.3 > 9c75a0dee87b2bad80d381ad9fa8ef90847d3a1d scsi: lpfc: Fix RQ buffer leakage > when no IOCBs available > 89cc9dba63c91a6c796dc46342c1d57c82c9b0cd scsi: lpfc: Fix lpfc_io_buf > resource leak in lpfc_get_scsi_buf_s4 error path > 692fc8380ca0f9185e75e01a74357d2cf3083743 scsi: lpfc: Fix broken Credit > Recovery after driver load > 0f74f70cb674e3b8712e896863ad85db4d193d46 scsi: lpfc: Fix registration of > ELS type support in fdmi > 01034e708a353fed29963d084c35d58785a317a6 scsi: lpfc: Fix release of hwq to > clear the eq relationship > 3cd50eac891db354e945bf9898726e163a19560e scsi: lpfc: Fix compiler warning > on frame size > 3ad04f4f0ad75ad4e7d886133f673d9fe20aa9c4 scsi: lpfc: Fix coverity errors in > fmdi attribute handling > 8d9fae72109e9921f52be342007b4c78490ea4fe scsi: lpfc: Remove handler for > obsolete ELS - Read Port Status (RPS) > 20d674a4bf64acf54eadc7215ea32b88a3a7687e scsi: lpfc: Clean up hba > max_lun_queue_depth checks > 35817310d9e05e666dbd242750008dad33ed8992 scsi: lpfc: Update lpfc version to > 12.6.0.4 > fd6cc30f341fea14bac45bf1c5c9d10702c18a9d scsi: lpfc: Copyright updates for > 12.6.0.4 patches > > [TESTING] > > [REGRESSION RISK] >
Re: [Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
On Mon, Mar 23, 2020 at 6:41 AM Vignesh Gunasekaran <1855...@bugs.launchpad.net> wrote: > > >So I appreciate the patch set you've provided, but due to the number of > >patches, what I need to do is >cherry-pick them from mainline and push a > >branch with cherry picks rather than 70+ patches that need to be > >>reviewed/applied by the kernel team. > > > >And because I can't find these in mainline at all (I've just checked all the > >proposed commit ids against the >most recent updates to mainline) I can't > >cherry pick these. Do you know when they'll be accepted upstream? > > > >I also checked against Linus tree and cant find those commit IDs there > >either. > > Jeff, > > All of those 72 patches are already accepted by the Kernel community and > most of them are already pulled into linus.git except for the ones you > listed. But, the ones you have listed are present in mkp/scsi.git. So as I mentioned in my reply to Laurie just now, I've built some kernels freshly over the weekend and uploaded them. However, I do have to tell you that I'm pretty sure they won't accept packages from mkp/scsi.git, the general rule of thumb is that they're only accepted into the Ubuntu kernel once they're accepted into the Mainline kernel. However, I'll submit them anyway and see what happens. I still am not sure if they'll accept at all given that several do touch common code rather than being driver specific, but we'll see how everything lands. > > Even when I was creating a patchset I went by searching those commit > IDs, but couldn't find them either in linus.git or mkp/scsi.git. I guess > those commit IDs were from local git. So, I found the equivalent commit > IDs for those patches in mkp/scsi.git and cherry-picked them. > > Ultimately, all 72 patches are already cherry-picked from either > linus.git or mkp/scsi.git. The patchset has the cherry-pick reference in > it. > > > I verified the patchset applies cleanly on the focal tree using: > > #git am //*.patch > > I thought executing this command is all you have to do it from your end. I needed to cherry pick each (or at least I was able to add what I needed via 'git am') and add a signed-off line with my name and add a bug link to the commit message for each patch. The tree I built just now has all that, so it's good now. > Regarding comment 6: > > >Additionally, this one does not cleanly apply when cherry-picked: > >765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel > >warning triggered by lpfc_get_sgl_per_hdwq() > > This commit is already pulled into the focal tree from upstream. Weird, I tried searching out tree for both that commit ID and by text searching the subject and didn't find it... oh well, I've limited the test kernels to just the 72 patches you provided in your tarball. Thanks for that tarball and sorry for any confusion on my end (this isn't something I routinely do, so I'm a bit cobwebby when I have to do these). -- Jeff Lane Engineering Manager IHV/OEM Alliances and Server Certification "Entropy isn't what it used to be." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855303 Title: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [IMPACT] This is related to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340 both patch sets are needed to make up This is a massive number of updates by Broadcom to the lpfc driver that didn't make 5.4 in time. As 20.04 is an LTS release with expected hardware support for 5 years, we need to ensure as much hardware support lands as possible to support server vendors over the next couple years. Broadcom has updated the lpfc driver to version 12.6.0.2 in 5.5. The version in focal is 12.2.0.3 and missing several bug fixes and hardware support additions. Please update the driver in focal appropriately. [FIXES] eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by last cpu id set 4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned cpu for allocation 3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version to 12.6.0.2 542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max queues to be hdwq count bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map for not present cpus d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of lpfc_sli4_cleanup_poll_list() 6c6d59e0fe5b86cf273d
[Kernel-packages] [Bug 1869947] [NEW] revert patch that introduces bug that prevents lpfc driver unloading
Public bug reported: [IMPACT] This upstream commit: 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f nvme_fc: add module to ops template to allow module references was pulled into Focal as part of this bug: https://bugs.launchpad.net/bugs/1860125 and this commit into Focal: a7441301b20dc8a7772972a092968bb353b7a642 This patch was added to prevent the unloading of lpfc driver when doing NVMe BFS booting. Broadcom has identified that this patch introduces a bug that prevents unloading of lpfc driver in the non-BFS case as well. Because of this, they have asked that we revert this patch and remove it from our kernel, and also said that they are working on a patch upstream to revert this as well. As it may not land upstream in time to meet kernel freeze for Focal, I'm providing a patch to revert this commit in Focal. Broadcom has asked that we revert this commit from the Focal tree and are working on a patch to revert this commit upstream. The reason is that this patch has been determined to be the root cause of a bug identified by the upstream provider [FIXES] To resolve, revert the following commit ID in the Focal Tree: a7441301b20dc8a7772972a092968bb353b7a642 nvme_fc: add module to ops template to allow module references BugLink: https://bugs.launchpad.net/bugs/1860125 [ Upstream commit 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f ] In nvme-fc: it's possible to have connected active controllers and as no references are taken on the LLDD, the LLDD can be unloaded. The controller would enter a reconnect state and as long as the LLDD resumed within the reconnect timeout, the controller would resume. But if a namespace on the controller is the root device, allowing the driver to unload can be problematic. To reload the driver, it may require new io to the boot device, and as it's no longer connected we get into a catch-22 that eventually fails, and the system locks up. Fix this issue by taking a module reference for every connected controller (which is what the core layer did to the transport module). Reference is cleared when the controller is removed. Acked-by: Himanshu Madhani Reviewed-by: Christoph Hellwig Signed-off-by: James Smart Signed-off-by: Keith Busch Signed-off-by: Sasha Levin Signed-off-by: Paolo Pisati [REGRESSION RISK] Regression risk is low as this is a new patch introduced upstream and synced into a development release. The patch only exists in our tree from Ubuntu-5.4-5.4.0-13.16 onwards and does not affect older kernels. ** Affects: linux (Ubuntu) Importance: High Assignee: Jeff Lane (bladernr) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869947 Title: revert patch that introduces bug that prevents lpfc driver unloading Status in linux package in Ubuntu: In Progress Bug description: [IMPACT] This upstream commit: 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f nvme_fc: add module to ops template to allow module references was pulled into Focal as part of this bug: https://bugs.launchpad.net/bugs/1860125 and this commit into Focal: a7441301b20dc8a7772972a092968bb353b7a642 This patch was added to prevent the unloading of lpfc driver when doing NVMe BFS booting. Broadcom has identified that this patch introduces a bug that prevents unloading of lpfc driver in the non-BFS case as well. Because of this, they have asked that we revert this patch and remove it from our kernel, and also said that they are working on a patch upstream to revert this as well. As it may not land upstream in time to meet kernel freeze for Focal, I'm providing a patch to revert this commit in Focal. Broadcom has asked that we revert this commit from the Focal tree and are working on a patch to revert this commit upstream. The reason is that this patch has been determined to be the root cause of a bug identified by the upstream provider [FIXES] To resolve, revert the following commit ID in the Focal Tree: a7441301b20dc8a7772972a092968bb353b7a642 nvme_fc: add module to ops template to allow module references BugLink: https://bugs.launchpad.net/bugs/1860125 [ Upstream commit 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f ] In nvme-fc: it's possible to have connected active controllers and as no references are taken on the LLDD, the LLDD can be unloaded. The controller would enter a reconnect state and as long as the LLDD resumed within the reconnect timeout, the controller would resume. But if a namespace on the controller is the root dev
[Kernel-packages] [Bug 1869947] Re: revert patch that introduces bug that prevents lpfc driver unloading
** Description changed: [IMPACT] This upstream commit: 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f nvme_fc: add module to ops template to allow module references was pulled into Focal as part of this bug: https://bugs.launchpad.net/bugs/1860125 and this commit into Focal: a7441301b20dc8a7772972a092968bb353b7a642 This patch was added to prevent the unloading of lpfc driver when doing NVMe BFS booting. Broadcom has identified that this patch introduces a bug that prevents unloading of lpfc driver in the non-BFS case as well. Because of this, they have asked that we revert this patch and remove it from our kernel, and also said that they are working on a patch upstream to revert this as well. As it may not land upstream in time to meet kernel freeze for Focal, I'm providing a patch to revert this commit in Focal. - Broadcom has asked that we revert this commit from the Focal tree and - are working on a patch to revert this commit upstream. The reason is - that this patch has been determined to be the root cause of a bug - identified by the upstream provider - [FIXES] To resolve, revert the following commit ID in the Focal Tree: a7441301b20dc8a7772972a092968bb353b7a642 nvme_fc: add module to ops template to allow module references - BugLink: https://bugs.launchpad.net/bugs/1860125 + BugLink: https://bugs.launchpad.net/bugs/1860125 - [ Upstream commit 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f ] + [ Upstream commit 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f ] - In nvme-fc: it's possible to have connected active controllers - and as no references are taken on the LLDD, the LLDD can be - unloaded. The controller would enter a reconnect state and as - long as the LLDD resumed within the reconnect timeout, the - controller would resume. But if a namespace on the controller - is the root device, allowing the driver to unload can be problematic. - To reload the driver, it may require new io to the boot device, - and as it's no longer connected we get into a catch-22 that - eventually fails, and the system locks up. + In nvme-fc: it's possible to have connected active controllers + and as no references are taken on the LLDD, the LLDD can be + unloaded. The controller would enter a reconnect state and as + long as the LLDD resumed within the reconnect timeout, the + controller would resume. But if a namespace on the controller + is the root device, allowing the driver to unload can be problematic. + To reload the driver, it may require new io to the boot device, + and as it's no longer connected we get into a catch-22 that + eventually fails, and the system locks up. - Fix this issue by taking a module reference for every connected - controller (which is what the core layer did to the transport - module). Reference is cleared when the controller is removed. + Fix this issue by taking a module reference for every connected + controller (which is what the core layer did to the transport + module). Reference is cleared when the controller is removed. - Acked-by: Himanshu Madhani - Reviewed-by: Christoph Hellwig - Signed-off-by: James Smart - Signed-off-by: Keith Busch - Signed-off-by: Sasha Levin - Signed-off-by: Paolo Pisati + Acked-by: Himanshu Madhani + Reviewed-by: Christoph Hellwig + Signed-off-by: James Smart + Signed-off-by: Keith Busch + Signed-off-by: Sasha Levin + Signed-off-by: Paolo Pisati [REGRESSION RISK] Regression risk is low as this is a new patch introduced upstream and synced into a development release. The patch only exists in our tree from Ubuntu-5.4-5.4.0-13.16 onwards and does not affect older kernels. ** Description changed: [IMPACT] This upstream commit: 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f nvme_fc: add module to ops template to allow module references was pulled into Focal as part of this bug: https://bugs.launchpad.net/bugs/1860125 and this commit into Focal: a7441301b20dc8a7772972a092968bb353b7a642 This patch was added to prevent the unloading of lpfc driver when doing NVMe BFS booting. Broadcom has identified that this patch introduces a bug that prevents unloading of lpfc driver in the non-BFS case as well. Because of this, they have asked that we revert this patch and remove it from our kernel, and also said that they are working on a patch upstream to revert this as well. As it may not land upstream in time to meet kernel freeze for Focal, I'm providing a patch to revert this commit in Focal. [FIXES] To resolve, revert the following commit ID in the Focal Tree: a7441301b20dc8a7772972a092968bb353b7a642 nvme_fc: add module to ops template to allow module references BugLink: https://bugs.launchpad.net/bugs/1860125 [ Upstream commit 863fbae929c7a5b64e96b8a3ffb34a29eefb9
[Kernel-packages] [Bug 1869947] Re: nvme_fc patch prevents unloading of lpfc module in both BFS and non-BFS scenarios
** Summary changed: - revert patch that introduces bug that prevents lpfc driver unloading + nvme_fc patch prevents unloading of lpfc module in both BFS and non-BFS scenarios ** Description changed: [IMPACT] This upstream commit: - 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f nvme_fc: add module to ops - template to allow module references + 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f + nvme_fc: add module to ops template to allow module references - was pulled into Focal as part of this bug: - https://bugs.launchpad.net/bugs/1860125 and this commit into Focal: + was pulled into Focal as part of this bug: + https://bugs.launchpad.net/bugs/1860125 + + and this commit into Focal: a7441301b20dc8a7772972a092968bb353b7a642 This patch was added to prevent the unloading of lpfc driver when doing NVMe BFS booting. Broadcom has identified that this patch introduces a bug that prevents unloading of lpfc driver in the non-BFS case as well. Because of this, they have asked that we revert this patch and remove it from our kernel, and also said that they are working on a patch upstream to revert this as well. As it may not land upstream in time to meet kernel freeze for Focal, I'm providing a patch to revert this commit in Focal. [FIXES] To resolve, revert the following commit ID in the Focal Tree: a7441301b20dc8a7772972a092968bb353b7a642 nvme_fc: add module to ops template to allow module references BugLink: https://bugs.launchpad.net/bugs/1860125 [ Upstream commit 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f ] In nvme-fc: it's possible to have connected active controllers and as no references are taken on the LLDD, the LLDD can be unloaded. The controller would enter a reconnect state and as long as the LLDD resumed within the reconnect timeout, the controller would resume. But if a namespace on the controller is the root device, allowing the driver to unload can be problematic. To reload the driver, it may require new io to the boot device, and as it's no longer connected we get into a catch-22 that eventually fails, and the system locks up. Fix this issue by taking a module reference for every connected controller (which is what the core layer did to the transport module). Reference is cleared when the controller is removed. Acked-by: Himanshu Madhani Reviewed-by: Christoph Hellwig Signed-off-by: James Smart Signed-off-by: Keith Busch Signed-off-by: Sasha Levin Signed-off-by: Paolo Pisati An updated tree with the commit reverted can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1869947-revert-lpfc-patch [REGRESSION RISK] Regression risk is low as this is a new patch introduced upstream and synced into a development release. The patch only exists in our tree from Ubuntu-5.4-5.4.0-13.16 onwards and does not affect older kernels. ** Summary changed: - nvme_fc patch prevents unloading of lpfc module in both BFS and non-BFS scenarios + nvme_fc patch prevents unloading lpfs module in both BFS and non-BFS scenarios ** Summary changed: - nvme_fc patch prevents unloading lpfs module in both BFS and non-BFS scenarios + Revert "nvme_fc: add module to ops template to allow module references" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869947 Title: Revert "nvme_fc: add module to ops template to allow module references" Status in linux package in Ubuntu: In Progress Bug description: [IMPACT] This upstream commit: 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f nvme_fc: add module to ops template to allow module references was pulled into Focal as part of this bug: https://bugs.launchpad.net/bugs/1860125 and this commit into Focal: a7441301b20dc8a7772972a092968bb353b7a642 This patch was added to prevent the unloading of lpfc driver when doing NVMe BFS booting. Broadcom has identified that this patch introduces a bug that prevents unloading of lpfc driver in the non-BFS case as well. Because of this, they have asked that we revert this patch and remove it from our kernel. Additionally, Broadcome have also said that they are working on a patch upstream to revert this as well. As it may not land upstream in time to meet kernel freeze for Focal, I'm providing a patch to revert this commit directly. [FIXES] To resolve, revert the following commit ID in the Focal Tree: a7441301b20dc8a7772972a092968bb353b7a642 nvme_fc: add module to ops template to allow module references BugLink: https://bugs.launchpad.net/bugs/1860125 [ Upstream commit 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f ] In nvme-fc: it's possible to have connected active controllers and as no references are taken on the LLDD, the LLDD c
[Kernel-packages] [Bug 1869947] Re: Revert "nvme_fc: add module to ops template to allow module references"
** Description changed: [IMPACT] This upstream commit: - 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f + 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f nvme_fc: add module to ops template to allow module references - was pulled into Focal as part of this bug: - https://bugs.launchpad.net/bugs/1860125 + was pulled into Focal as part of this bug: + https://bugs.launchpad.net/bugs/1860125 - and this commit into Focal: + and this commit into Focal: a7441301b20dc8a7772972a092968bb353b7a642 This patch was added to prevent the unloading of lpfc driver when doing NVMe BFS booting. Broadcom has identified that this patch introduces a bug that prevents unloading of lpfc driver in the non-BFS case as well. - Because of this, they have asked that we revert this patch and remove it - from our kernel, and also said that they are working on a patch upstream - to revert this as well. As it may not land upstream in time to meet - kernel freeze for Focal, I'm providing a patch to revert this commit in - Focal. + + Because of this, they have asked that we revert this patch and remove it from our kernel. Additionally, Broadcome have also said that they are working on a patch upstream to revert this as well. As it may not land upstream in time to meet kernel freeze for Focal, I'm providing a patch + to revert this commit directly. + [FIXES] To resolve, revert the following commit ID in the Focal Tree: a7441301b20dc8a7772972a092968bb353b7a642 nvme_fc: add module to ops template to allow module references BugLink: https://bugs.launchpad.net/bugs/1860125 [ Upstream commit 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f ] In nvme-fc: it's possible to have connected active controllers and as no references are taken on the LLDD, the LLDD can be unloaded. The controller would enter a reconnect state and as long as the LLDD resumed within the reconnect timeout, the controller would resume. But if a namespace on the controller is the root device, allowing the driver to unload can be problematic. To reload the driver, it may require new io to the boot device, and as it's no longer connected we get into a catch-22 that eventually fails, and the system locks up. Fix this issue by taking a module reference for every connected controller (which is what the core layer did to the transport module). Reference is cleared when the controller is removed. Acked-by: Himanshu Madhani Reviewed-by: Christoph Hellwig Signed-off-by: James Smart Signed-off-by: Keith Busch Signed-off-by: Sasha Levin Signed-off-by: Paolo Pisati An updated tree with the commit reverted can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1869947-revert-lpfc-patch [REGRESSION RISK] Regression risk is low as this is a new patch introduced upstream and synced into a development release. The patch only exists in our tree from Ubuntu-5.4-5.4.0-13.16 onwards and does not affect older kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869947 Title: Revert "nvme_fc: add module to ops template to allow module references" Status in linux package in Ubuntu: In Progress Bug description: [IMPACT] This upstream commit: 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f nvme_fc: add module to ops template to allow module references was pulled into Focal as part of this bug: https://bugs.launchpad.net/bugs/1860125 and this commit into Focal: a7441301b20dc8a7772972a092968bb353b7a642 This patch was added to prevent the unloading of lpfc driver when doing NVMe BFS booting. Broadcom has identified that this patch introduces a bug that prevents unloading of lpfc driver in the non-BFS case as well. Because of this, they have asked that we revert this patch and remove it from our kernel. Additionally, Broadcome have also said that they are working on a patch upstream to revert this as well. As it may not land upstream in time to meet kernel freeze for Focal, I'm providing a patch to revert this commit directly. [FIXES] To resolve, revert the following commit ID in the Focal Tree: a7441301b20dc8a7772972a092968bb353b7a642 nvme_fc: add module to ops template to allow module references BugLink: https://bugs.launchpad.net/bugs/1860125 [ Upstream commit 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f ] In nvme-fc: it's possible to have connected active controllers and as no references are taken on the LLDD, the LLDD can be unloaded. The controller would enter a reconnect state and as long as the LLDD resumed within the reconnect timeout, the controller would resume. But if a namespace on the controller is the root device, allowing the driver to unload can be pr
[Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
** Description changed: [IMPACT] This is related to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340 both patch sets are needed to make up This is a massive number of updates by Broadcom to the lpfc driver that didn't make 5.4 in time. As 20.04 is an LTS release with expected hardware support for 5 years, we need to ensure as much hardware support lands as possible to support server vendors over the next couple years. Broadcom has updated the lpfc driver to version 12.6.0.2 in 5.5. The version in focal is 12.2.0.3 and missing several bug fixes and hardware support additions. Please update the driver in focal appropriately. [FIXES] eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by last cpu id set 4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned cpu for allocation 3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version to 12.6.0.2 542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max queues to be hdwq count bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map for not present cpus d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of lpfc_sli4_cleanup_poll_list() 6c6d59e0fe5b86cf273d6d744a6a9768c4ecc756 scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences 6f23f8c5c9f1be4eb17c035129c80e49000c18a7 scsi: lpfc: fix: Coverity: lpfc_get_scsi_buf_s3(): Null pointer dereferences 61951a6d3153b4482404b739be921a7459f8dc12 scsi: lpfc: Fix lpfc_cpumask_of_node_init() eea2d396aa57acb3607f79ef04c08c2c5166f3fa scsi: lpfc: Fix a kernel warning triggered by lpfc_sli4_enable_intr() 765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel warning triggered by lpfc_get_sgl_per_hdwq() aff6ab9e7221c1b5d15418419b9797e5badd4aec scsi: lpfc: Update lpfc version to 12.6.0.1 171f6c41949f6e9d5e09dcac842a10bf8dda8dcc scsi: lpfc: Add enablement of multiple adapter dumps dcaa213679387e95a315dca05c57dbb15273703c scsi: lpfc: Change default IRQ model on AMD architectures 93a4d6f40198dffcca35d9a928c409f9290f1fe0 scsi: lpfc: Add registration for CPU Offline/Online events b9da814cd5f5bb93041a6e4dbc9c5149713186ff scsi: lpfc: Clarify FAWNN error message 69641627c653464db46f3e3d8c438349be055670 scsi: lpfc: Sync with FC-NVMe-2 SLER change to require Conf with SLER dda5bdf074da3782ff9e785ee50cd2a3f214d498 scsi: lpfc: Fix dynamic fw log enablement check 2332e6e475b016e2026763f51333f84e2e6c57a3 scsi: lpfc: Fix unexpected error messages during RSCN handling 6c1e803eac846f886cd35131e6516fc51a8414b9 scsi: lpfc: Fix kernel crash at lpfc_nvme_info_show during remote port bounce 6bfb1620829825c01e1dcdd63b6a7700352babd9 scsi: lpfc: Fix configuration of BB credit recovery in service parameters 7cfd5639d99bec0d27af089d0c8c114330e43a72 scsi: lpfc: Fix duplicate unreg_rpi error in port offline flow 7b10db555257d1248398643a23e10cf36b50d516 scsi: lpfc: Make lpfc_debugfs_ras_log_data static c3e5aac3e2f501ad4fcb03fed0e32a6f009faea2 scsi: lpfc: Fix NULL check before mempool_destroy is not needed 5792a0e81678da41f05bb724ebd20f134604fa15 scsi: lpfc: fix spelling error in MAGIC_NUMER_xxx 9e2edb41c3d4cab6da0eedcc07ae04758af62ab8 scsi: lpfc: fix build error of lpfc_debugfs.c for vfree/vmalloc 5314995e370e46ac12d12378544ad4575b6f6672 scsi: lpfc: lpfc_nvmet: Fix Use plain integer as NULL pointer 2c7fb469024f0da98f4d078fcf570786ec87c384 scsi: lpfc: lpfc_attr: Fix Use plain integer as NULL pointer 74acec655f560ef721c1e191732af2bcb094b537 scsi: lpfc: Update lpfc version to 12.6.0.0 b4b3417cf6c8051f9f210cd694e6342fb008795c scsi: lpfc: Add additional discovery log messages 83c6cb1ae8be6948b5fa43b2450a176dba80688b scsi: lpfc: Add FC-AL support to lpe32000 models e7d8595272553c27846946601b72e4c581f9712a scsi: lpfc: Add FA-WWN Async Event reporting b1dfa5411ea440f7a5bd65176259ffb3bfbdecf0 scsi: lpfc: Add log macros to allow print by serverity or verbosity setting 95bfc6d8ad86a76c89f62bb466f740b0fc05a667 scsi: lpfc: Make FW logging dynamically configurable 8156d378c4cbf8ca19df5d8f0c610ce6923b61e2 scsi: lpfc: Revise interrupt coalescing for missing scenarios ea85a20cd54f3b09880f6c08994b059f0d114a11 scsi: lpfc: Remove lock contention target write path 22770cbabf6bb77a397d9f11d41f97667dd0caa2 scsi: lpfc: Slight fast-path performance optimizations f84f8f93f01feb64fdda8dd6c72d1b7dc24ad11d scsi: lpfc: fix coverity error of dereference after null check 91a52b617cdb8bf6d298892101c061d438b84a19 scsi: lpfc: Fix hardlockup in lpfc_abort_handler 324e1c402069e8d277d2a2b18ce40bde1265b96a scsi: lpfc: Fix bad ndlp ptr in xri aborted handling feff8b3d84d3d9570f893b4d83e5eab6693d6a52 scsi: lpfc: Fix SLI3 hba in loop mode not discovering devices 27f3efd637ce4859a44a7ca730c72392b4111c26 scsi: lpfc: Fix lockdep errors in sli_ringtx_put 0a5ce731977da
[Kernel-packages] [Bug 1856340] Re: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies
** Description changed: [IMPACT] In the run up to 20.04 release, Broadcom wants to ensure that customers running ubuntu 20.04 have the proper support when using Emulex Fibrechannel cards to use NVMe over FC. This updates nvme-fc and nvme with cherry picks from 5.5 upstream that didn't land in time for the upstream 5.4 release. - Deferring this request would delay customers using NVMe over FC until - February when the first HWE for Focal is released, roughly 9 months from - now. + This will enable NVMe over FC on Broadcom Emulex FC controllers on + Focal. - Here are the kernel and cli updates broadcom requested via email related - to LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc + Note this is dependent on and requires this bug as well, which updates + the Broadcom lpfc driver and completes the Broadcom Emulex FC lpfc 12.6.0.x solution. + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855303 [FIXES] Additional patches recommended: ( ) f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2 53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes 44fbf3bb1ac3 - Sep 27 2019 - nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu 7db394848ece - Sep 27 2019 - nvme-fc: clarify error messages bcde5f0fc7d3 - Sep 27 2019 - nvme-fc: ensure association_id is cleared regardless of a Disconnect LS 48c9e85b2346 - Oct 14 2019 - nvme: resync include/linux/nvme.h with nvmecli 64fab7290dc3 - Oct 28 2019 - nvme: Fix parsing of ANA log page These are clean cherry-picks from 5.5 into 5.4 and can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1856340-broadcom-nvme-updates These two are already in focal and are only left here for reference as they were part of the original request: 863fbae929c7 - Nov 14 2019 - nvme_fc: add module to ops template to allow module references c869e494ef8b - Nov 21 2019 - nvme-fc: fix double-free scenarios on hw queues [REGRESSION RISK] Low: Patches are already upstream in 5.5 and have been tested there and by Broadcom Emululex. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856340 Title: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [IMPACT] In the run up to 20.04 release, Broadcom wants to ensure that customers running ubuntu 20.04 have the proper support when using Emulex Fibrechannel cards to use NVMe over FC. This updates nvme-fc and nvme with cherry picks from 5.5 upstream that didn't land in time for the upstream 5.4 release. This will enable NVMe over FC on Broadcom Emulex FC controllers on Focal. Note this is dependent on and requires this bug as well, which updates the Broadcom lpfc driver and completes the Broadcom Emulex FC lpfc 12.6.0.x solution. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855303 [FIXES] Additional patches recommended: ( ) f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2 53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes 44fbf3bb1ac3 - Sep 27 2019 - nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu 7db394848ece - Sep 27 2019 - nvme-fc: clarify error messages bcde5f0fc7d3 - Sep 27 2019 - nvme-fc: ensure association_id is cleared regardless of a Disconnect LS 48c9e85b2346 - Oct 14 2019 - nvme: resync include/linux/nvme.h with nvmecli 64fab7290dc3 - Oct 28 2019 - nvme: Fix parsing of ANA log page These are clean cherry-picks from 5.5 into 5.4 and can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1856340-broadcom-nvme-updates These two are already in focal and are only left here for reference as they were part of the original request: 863fbae929c7 - Nov 14 2019 - nvme_fc: add module to ops template to allow module references c869e494ef8b - Nov 21 2019 - nvme-fc: fix double-free scenarios on hw queues [REGRESSION RISK] Low: Patches are already upstream in 5.5 and have been tested there and by Broadcom Emululex. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
> f44ccecf36581a2030313e979127013f9d455d3a scsi: lpfc: Fix improper flag > check for IO type > e627554eedcfac83bb2ba073adf711a13049273a scsi: lpfc: Update lpfc version to > 12.6.0.3 > 9c75a0dee87b2bad80d381ad9fa8ef90847d3a1d scsi: lpfc: Fix RQ buffer leakage > when no IOCBs available > > This set of paches is included in this request, however they are > accepted upstream in mkp/scsi.git but have not been merged into > mainline yet. > > 89cc9dba63c91a6c796dc46342c1d57c82c9b0cd scsi: lpfc: Fix lpfc_io_buf > resource leak in lpfc_get_scsi_buf_s4 error path > 692fc8380ca0f9185e75e01a74357d2cf3083743 scsi: lpfc: Fix broken Credit > Recovery after driver load > 0f74f70cb674e3b8712e896863ad85db4d193d46 scsi: lpfc: Fix registration of > ELS type support in fdmi > 01034e708a353fed29963d084c35d58785a317a6 scsi: lpfc: Fix release of hwq to > clear the eq relationship > 3cd50eac891db354e945bf9898726e163a19560e scsi: lpfc: Fix compiler warning > on frame size > 3ad04f4f0ad75ad4e7d886133f673d9fe20aa9c4 scsi: lpfc: Fix coverity errors in > fmdi attribute handling > 8d9fae72109e9921f52be342007b4c78490ea4fe scsi: lpfc: Remove handler for > obsolete ELS - Read Port Status (RPS) > 20d674a4bf64acf54eadc7215ea32b88a3a7687e scsi: lpfc: Clean up hba > max_lun_queue_depth checks > 35817310d9e05e666dbd242750008dad33ed8992 scsi: lpfc: Update lpfc version to > 12.6.0.4 > fd6cc30f341fea14bac45bf1c5c9d10702c18a9d scsi: lpfc: Copyright updates for > 12.6.0.4 patches > 73ec6d2748dc35db2b32cf3c182a27c4a0837b9b scsi: fc: Update Descriptor > definition and add RDF and Link Integrity FPINs > df3fe76658ed47617741819a501e2bd2ae446962 scsi: lpfc: add RDF registration > and Link Integrity FPIN logging > > These patches are applied and can be pulled from my branch here: > > https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1855303-lpfc-updates > > [TESTING] > Patches were cleanly cherry picked from mainline and mkp/scsi.git and > tested by Broadcom. > > modinfo lpfc should show version 12.6.0.4 > > [REGRESSION RISK] > Low, these patches are already accepted upstream in 5.5 and mkp/scsi.git > and have been tested by Broadcom for regression potential. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855303/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main; > status=In Progress; importance=Undecided; assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=focal; sourcepackage=linux; > component=main; status=In Progress; importance=Undecided; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: bladernr laurie-barry ubuntu-kernel-bot vignesh-g > Launchpad-Bug-Reporter: laurie barry (laurie-barry) > Launchpad-Bug-Modifier: Vignesh Gunasekaran (vignesh-g) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: bladernr -- Jeff Lane Engineering Manager IHV/OEM Alliances and Server Certification "Entropy isn't what it used to be." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855303 Title: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [IMPACT] This is related to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340 This is a significant number of updates by Broadcom to the lpfc driver that didn't make 5.4 in time. As 20.04 is an LTS release with expected hardware support for 5 years, we need to ensure as much hardware support lands as possible to support server vendors over the next couple years. Broadcom has updated the lpfc driver to version 12.6.0.4 in 5.5. The version in focal is 12.2.0.3 and missing several bug fixes and hardware support additions. Please update the driver in focal appropriately. [FIXES] eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by last cpu id set 4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned cpu for allocation 3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version to 12.6.0.2 542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max queues to be hdwq count bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map for not present cpus d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of lpfc_sli4_clea
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
@MasterCATZ, please check this with the 20.04 5.4 kernel. If it's still an issue could you please file a separate kernel bug for your corruption issue? ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. The exlcusion range limit register needs to contain the base-address of the last page that is part of the range, as bits 0-11 of this register are treated as 0xfff by the hardware for comparisons. So correctly set the exclusion range in the hardware to the last page which is _in_ the range. [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly These can be picked from my branches here: Bionic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic 1823037-amd_iommu-cherrypick b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range in iova-domain ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range correctly Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic 1823037-amd_iommu-cherrypick 0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range in iova-domain fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range correctly Disco: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco 1823037-amd_iommu-cherrypick 6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range correctly Note Disco only required f1cd47fe12 as the first patch was already picked in LP: #1830934 Not necessary for Eoan as these are already upstream in 5.2-rc1 [Regression Risk] Low,this adds memory protection to the driver and has already been applied upstream and tested by Dell for 24 hours with no failures noted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876196] [NEW] apt info does not show the Supported: information for 20.04 LTS kernels
Public bug reported: One of our cert tests has been failing on Focal kernels. Lookning at the -29 kernel today, we noticed that the Supported: item is missing when looking at Apt info. Focal: ubuntu@hogplum:~$ apt-cache show linux-image-`uname -r` Package: linux-image-5.4.0-29-generic Architecture: amd64 Version: 5.4.0-29.33 Built-Using: linux (= 5.4.0-29.33) Priority: optional Section: kernel Source: linux-signed Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 11415 Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-dkms, virtualbox-guest-modules, zfs-dkms, zfs-modules Depends: kmod, linux-base (>= 4.5ubuntu1~16.04.1), linux-modules-5.4.0-29-generic Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, initramfs-tools | linux-initramfs-tool Suggests: fdutils, linux-doc | linux-source-5.4.0, linux-tools, linux-headers-5.4.0-29-generic Conflicts: linux-image-unsigned-5.4.0-29-generic Filename: pool/main/l/linux-signed/linux-image-5.4.0-29-generic_5.4.0-29.33_amd64.deb Size: 8870728 MD5sum: 5af753b944eb16b8f248e236edb6ce54 SHA1: 389bd3f05310f2adc7c1110890afc1ef4a2acc19 SHA256: eb420ae6d31dd3cbf341de32035976271e568b868416e8bd00b644dcb39cde1a Description-en: Signed kernel image generic A kernel image for generic. This version of it is signed with Canonical's UEFI/Opal signing key. Description-md5: 54a18b1adebc179da3c9e59a5db5fe77 For comparison, this is 5.3 from Bionic HWE: Package: linux-image-5.3.0-46-generic Architecture: amd64 Version: 5.3.0-46.38~18.04.1 Built-Using: linux-hwe (= 5.3.0-46.38~18.04.1) Priority: optional Section: kernel Source: linux-signed-hwe Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 8955 Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-dkms, virtualbox-guest-modules, zfs-dkms, zfs-modules Depends: kmod, linux-base (>= 4.5ubuntu1~16.04.1), linux-modules-5.3.0-46-generic Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, initramfs-tools | linux-initramfs-tool Suggests: fdutils, linux-hwe-doc-5.3.0 | linux-hwe-source-5.3.0, linux-hwe-tools, linux-headers-5.3.0-46-generic Conflicts: linux-image-unsigned-5.3.0-46-generic Filename: pool/main/l/linux-signed-hwe/linux-image-5.3.0-46-generic_5.3.0-46.38~18.04.1_amd64.deb Size: 8729628 MD5sum: 6d575e91196fe11ac1437d5e12377d92 SHA1: 88795748a4a757719fa62c950910e510bf6a964a SHA256: 1534e292a6e85d42fc0e34e368fde2a42c044cc239b15f18e5ff8ac467bca2af Description-en: Signed kernel image generic A kernel image for generic. This version of it is signed with Canonical's UEFI/Opal signing key. Description-md5: 54a18b1adebc179da3c9e59a5db5fe77 Supported: 5y And from the last 4.15 I had installed before moving to the HWE stack: Package: linux-image-4.15.0-99-generic Architecture: amd64 Version: 4.15.0-99.100 Built-Using: linux (= 4.15.0-99.100) Priority: optional Section: kernel Source: linux-signed Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 8213 Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-modules, zfs-dkms, zfs-modules Depends: kmod, linux-base (>= 4.5ubuntu1~16.04.1), linux-modules-4.15.0-99-generic Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, initramfs-tools | linux-initramfs-tool Suggests: fdutils, linux-doc-4.15.0 | linux-source-4.15.0, linux-tools, linux-headers-4.15.0-99-generic Conflicts: linux-image-unsigned-4.15.0-99-generic Filename: pool/main/l/linux-signed/linux-image-4.15.0-99-generic_4.15.0-99.100_amd64.deb Size: 8003012 MD5sum: 251da0e19f02f3af93bc3de89bf738c1 SHA1: ad385f85faaad98e80f1886fcb29d16d9626bfa3 SHA256: e17bb925a2266e2b709835e08fcc73aab57a1d29261a3dd0156ed7ced6fc9ccc Description-en: Signed kernel image generic A kernel image for generic. This version of it is signed with Canonical's UEFI/Opal signing key. Description-md5: 54a18b1adebc179da3c9e59a5db5fe77 Supported: 5y ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 30 20:29 seq crw-rw 1 root audio 116, 33 Apr 30 20:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Thu Apr 30 22:24:04 2
[Kernel-packages] [Bug 1877270] Re: Devlink - add RoCE disable kernel support
** Description changed:
[Impact]
RoCE disable feature was added to the kernel v5.5.
This feature was requested by Mellanox customers that use Ubuntu 20.04,
and it's a very high important to deliver this feature to the customers
in one of ubuntu 20.04 SRU.
[SHORT DESCRIPTION]
RoCE enablement state controls driver support for RoCE traffic.
When RoCE is disabled, there is no gid table, only raw ethernet QPs are
supported and traffic on the well known UDP RoCE port is handled as raw
ethernet traffic.
-
[Test Case]
To change RoCE enablement state a user must change the driverinit cmode
value and run devlink reload.
User command examples:
- Disable RoCE::
- $ devlink dev param set pci/:06:00.0 name enable_roce value false
cmode driverinit
- $ devlink dev reload pci/:06:00.0
+ $ devlink dev param set pci/:06:00.0 name enable_roce value false
cmode driverinit
+ $ devlink dev reload pci/:06:00.0
- Read RoCE enablement state::
- $ devlink dev param show pci/:06:00.0 name enable_roce
- pci/:06:00.0:
- name enable_roce type generic
- values:
- cmode driverinit value true
+ $ devlink dev param show pci/:06:00.0 name enable_roce
+ pci/:06:00.0:
+ name enable_roce type generic
+ values:
+ cmode driverinit value true
[Regression Potential]
This feature shouldn't affect the regression because it's only adding support
for
RoCE enable/disable.
Also,
This feature was tested internally by Mellanox QA teams
those tests logs/results are private unfortunately i can't share it here
[Other Info]
Feature patchset:
+ 4383cfcc65e7 net/mlx5: Add devlink reload
+ 32680da71034 net/mlx5: Remove unneeded variable in mlx5_unload_one
94de879c28d8 IB/mlx5: Load profile according to RoCE enablement state
b5a498baf929 IB/mlx5: Rename profile and init methods
cc9defcbb8fa net/mlx5: Handle "enable_roce" devlink param
e90cde0d76f0 net/mlx5: Document flow_steering_mode devlink param
6c7295e13ffd devlink: Add new "enable_roce" generic device param
- patctwork:
- https://patchwork.ozlabs.org/cover/1192314/
+ 070c63f20f6c ("net: devlink: allow to change namespaces during
+ reload")## This one does not apply cleanly
+
+ All are in upstream in 5.5, so no pick into Groovy necessary
userspace:
- No userspace dependency on this. the feature uses the devlink
+ No userspace dependency on this. the feature uses the devlink
param functionality which already exists in UB20.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877270
Title:
Devlink - add RoCE disable kernel support
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Bug description:
[Impact]
RoCE disable feature was added to the kernel v5.5.
This feature was requested by Mellanox customers that use Ubuntu 20.04,
and it's a very high important to deliver this feature to the customers
in one of ubuntu 20.04 SRU.
[SHORT DESCRIPTION]
RoCE enablement state controls driver support for RoCE traffic.
When RoCE is disabled, there is no gid table, only raw ethernet QPs are
supported and traffic on the well known UDP RoCE port is handled as raw
ethernet traffic.
[Test Case]
To change RoCE enablement state a user must change the driverinit
cmode value and run devlink reload.
User command examples:
- Disable RoCE::
$ devlink dev param set pci/:06:00.0 name enable_roce value false
cmode driverinit
$ devlink dev reload pci/:06:00.0
- Read RoCE enablement state::
$ devlink dev param show pci/:06:00.0 name enable_roce
pci/:06:00.0:
name enable_roce type generic
values:
cmode driverinit value true
[Regression Potential]
This feature shouldn't affect the regression because it's only adding support
for
RoCE enable/disable.
Also,
This feature was tested internally by Mellanox QA teams
those tests logs/results are private unfortunately i can't share it here
[Other Info]
Feature patchset:
4383cfcc65e7 net/mlx5: Add devlink reload
32680da71034 net/mlx5: Remove unneeded variable in mlx5_unload_one
94de879c28d8 IB/mlx5: Load profile according to RoCE enablement state
b5a498baf929 IB/mlx5: Rename profile and init methods
cc9defcbb8fa net/mlx5: Handle "enable_roce" devlink param
e90cde0d76f0 net/mlx5: Document flow_steering_mode devlink param
6c7295e13ffd devlink: Add new "enable_roce" generic device param
070c63f20f6c ("net: devlink: allow to change namespaces during
reload")## This one does not apply cleanly
All are in upstream in 5.5, so no pick into Groovy necessary
userspace:
No userspace dependency on this. the
[Kernel-packages] [Bug 1863813] Re: Focal Fossa (20.04) feature request - Cooper Lake
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863813 Title: Focal Fossa (20.04) feature request - Cooper Lake Status in linux package in Ubuntu: Invalid Bug description: This a request to include Cooper Lake into 20.04. I have included the upstream patches. https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=61e5ddca9c2a312f933bf5b12bc08484189fefe6 https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=0959f8256ada0431c1470d89e5a2811ff2305c88 https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=9743cb68f736d986481edba4d00de454d2faa0ec https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=2bcf26528787d92333ed0dfd6abc9835b8e97eab https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=8785968bce1cc7368ea95c3e1e5b9210f56f6667 https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=f5a8f0ecb436a15f50215f27ab70a2e8626a6135 https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=df55029f7ea65d8c653a79dd728918dfe25b1356 https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4fb7d08707565d27ec84a364d011043ade8c38b4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864484] [NEW] Update SmartPQI driver in Focal to 1.2.10-025
Public bug reported: Feature request to update the SmartPQI driver in Focal to 1.2.10-025 Patch List: 4bdc0d676a64 remove ioremap_nocache and devm_ioremap_nocache c593642c8be0 treewide: Use sizeof_field() macro 390e28087823 scsi: smartpqi: bump version 694c5d5b4625 scsi: smartpqi: Align driver syntax with oob 0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants 5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device e655d469c32d scsi: smartpqi: correct syntax issue bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung 21432010d528 scsi: smartpqi: add inquiry timeouts b969261134c1 scsi: smartpqi: fix call trace in device discovery 0530736e40a0 scsi: smartpqi: fix controller lockup observed during force reboot 9e322310e16c scsi: smartpqi: clean up an indentation issue 1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info' a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864484 Title: Update SmartPQI driver in Focal to 1.2.10-025 Status in linux package in Ubuntu: Incomplete Bug description: Feature request to update the SmartPQI driver in Focal to 1.2.10-025 Patch List: 4bdc0d676a64 remove ioremap_nocache and devm_ioremap_nocache c593642c8be0 treewide: Use sizeof_field() macro 390e28087823 scsi: smartpqi: bump version 694c5d5b4625 scsi: smartpqi: Align driver syntax with oob 0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants 5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device e655d469c32d scsi: smartpqi: correct syntax issue bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung 21432010d528 scsi: smartpqi: add inquiry timeouts b969261134c1 scsi: smartpqi: fix call trace in device discovery 0530736e40a0 scsi: smartpqi: fix controller lockup observed during force reboot 9e322310e16c scsi: smartpqi: clean up an indentation issue 1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info' a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864484] Re: Update SmartPQI driver in Focal to 1.2.10-025
Feature request for Focal, no logs necessary ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864484 Title: Update SmartPQI driver in Focal to 1.2.10-025 Status in linux package in Ubuntu: Confirmed Bug description: Feature request to update the SmartPQI driver in Focal to 1.2.10-025 Patch List: 4bdc0d676a64 remove ioremap_nocache and devm_ioremap_nocache c593642c8be0 treewide: Use sizeof_field() macro 390e28087823 scsi: smartpqi: bump version 694c5d5b4625 scsi: smartpqi: Align driver syntax with oob 0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants 5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device e655d469c32d scsi: smartpqi: correct syntax issue bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung 21432010d528 scsi: smartpqi: add inquiry timeouts b969261134c1 scsi: smartpqi: fix call trace in device discovery 0530736e40a0 scsi: smartpqi: fix controller lockup observed during force reboot 9e322310e16c scsi: smartpqi: clean up an indentation issue 1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info' a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864484] Re: Update SmartPQI driver in Focal to 1.2.10-025
** Description changed:
Feature request to update the SmartPQI driver in Focal to 1.2.10-025
Patch List:
- 4bdc0d676a64 remove ioremap_nocache and devm_ioremap_nocache
- c593642c8be0 treewide: Use sizeof_field() macro
+ These are the recommended patches from the IHV:
390e28087823 scsi: smartpqi: bump version
694c5d5b4625 scsi: smartpqi: Align driver syntax with oob
0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants
5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device
e655d469c32d scsi: smartpqi: correct syntax issue
bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds
c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung
21432010d528 scsi: smartpqi: add inquiry timeouts
b969261134c1 scsi: smartpqi: fix call trace in device discovery
0530736e40a0 scsi: smartpqi: fix controller lockup observed during force
reboot
9e322310e16c scsi: smartpqi: clean up an indentation issue
1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info'
a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Also affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Jeff Lane (bladernr)
Status: Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1864484
Title:
Update SmartPQI driver in Focal to 1.2.10-025
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
Feature request to update the SmartPQI driver in Focal to 1.2.10-025
Patch List:
These are the recommended patches from the IHV:
390e28087823 scsi: smartpqi: bump version
694c5d5b4625 scsi: smartpqi: Align driver syntax with oob
0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants
5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device
e655d469c32d scsi: smartpqi: correct syntax issue
bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds
c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung
21432010d528 scsi: smartpqi: add inquiry timeouts
b969261134c1 scsi: smartpqi: fix call trace in device discovery
0530736e40a0 scsi: smartpqi: fix controller lockup observed during force
reboot
9e322310e16c scsi: smartpqi: clean up an indentation issue
1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info'
a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864484/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864484] Re: Update SmartPQI driver in Focal to 1.2.10-025
** Description changed: + [IMPACT] Feature request to update the SmartPQI driver in Focal to 1.2.10-025 + Microchip produces the Smart Storage controllers that are used by several major OEMs we partner with. There is a new generation of controller coming to market later this summer. While customers will be able to use these new controllers with the driver as it is in Focal today, they will be missing several bug fixes and enhancements that have already landed upstream in 5.5. For this reason, Microchip and HPE have asked us to pull these patches to update the SmartPQI driver in Focal to the current upstream version. - Patch List: - These are the recommended patches from the IHV: + [FIXES] + These are the recommended patches from Microchip that should be cherry-picked from mainline. 390e28087823 scsi: smartpqi: bump version 694c5d5b4625 scsi: smartpqi: Align driver syntax with oob 0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants 5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device e655d469c32d scsi: smartpqi: correct syntax issue bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung 21432010d528 scsi: smartpqi: add inquiry timeouts b969261134c1 scsi: smartpqi: fix call trace in device discovery 0530736e40a0 scsi: smartpqi: fix controller lockup observed during force reboot 9e322310e16c scsi: smartpqi: clean up an indentation issue 1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info' a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement + + [TESTING] + modinfo for smartpqi should show: + + version:1.2.10-025 + description:Driver for Microsemi Smart Family Controller version 1.2.10-025 + + + [REGRESSION RISK] + Low - Focal is not yet released, this is not being backported to current releases, patches pick cleanly and have been tested by the upstream maintainers. ** Tags added: hwcert-server -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864484 Title: Update SmartPQI driver in Focal to 1.2.10-025 Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: [IMPACT] Feature request to update the SmartPQI driver in Focal to 1.2.10-025 Microchip produces the Smart Storage controllers that are used by several major OEMs we partner with. There is a new generation of controller coming to market later this summer. While customers will be able to use these new controllers with the driver as it is in Focal today, they will be missing several bug fixes and enhancements that have already landed upstream in 5.5. For this reason, Microchip and HPE have asked us to pull these patches to update the SmartPQI driver in Focal to the current upstream version. [FIXES] These are the recommended patches from Microchip that should be cherry-picked from mainline. 390e28087823 scsi: smartpqi: bump version 694c5d5b4625 scsi: smartpqi: Align driver syntax with oob 0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants 5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device e655d469c32d scsi: smartpqi: correct syntax issue bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung 21432010d528 scsi: smartpqi: add inquiry timeouts b969261134c1 scsi: smartpqi: fix call trace in device discovery 0530736e40a0 scsi: smartpqi: fix controller lockup observed during force reboot 9e322310e16c scsi: smartpqi: clean up an indentation issue 1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info' a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement [TESTING] modinfo for smartpqi should show: version:1.2.10-025 description:Driver for Microsemi Smart Family Controller version 1.2.10-025 [REGRESSION RISK] Low - Focal is not yet released, this is not being backported to current releases, patches pick cleanly and have been tested by the upstream maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864484] Re: Update SmartPQI driver in Focal to 1.2.10-025
** Description changed: [IMPACT] Feature request to update the SmartPQI driver in Focal to 1.2.10-025 Microchip produces the Smart Storage controllers that are used by several major OEMs we partner with. There is a new generation of controller coming to market later this summer. While customers will be able to use these new controllers with the driver as it is in Focal today, they will be missing several bug fixes and enhancements that have already landed upstream in 5.5. For this reason, Microchip and HPE have asked us to pull these patches to update the SmartPQI driver in Focal to the current upstream version. [FIXES] These are the recommended patches from Microchip that should be cherry-picked from mainline. 390e28087823 scsi: smartpqi: bump version 694c5d5b4625 scsi: smartpqi: Align driver syntax with oob 0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants 5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device e655d469c32d scsi: smartpqi: correct syntax issue bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung 21432010d528 scsi: smartpqi: add inquiry timeouts b969261134c1 scsi: smartpqi: fix call trace in device discovery 0530736e40a0 scsi: smartpqi: fix controller lockup observed during force reboot 9e322310e16c scsi: smartpqi: clean up an indentation issue 1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info' a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement + All are clean cherry picks into the 5.4 branch and can be pulled from my branch here: + https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1864484-smartpqi-to-1.2.10-025 + [TESTING] modinfo for smartpqi should show: version:1.2.10-025 description:Driver for Microsemi Smart Family Controller version 1.2.10-025 - [REGRESSION RISK] Low - Focal is not yet released, this is not being backported to current releases, patches pick cleanly and have been tested by the upstream maintainers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864484 Title: Update SmartPQI driver in Focal to 1.2.10-025 Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: [IMPACT] Feature request to update the SmartPQI driver in Focal to 1.2.10-025 Microchip produces the Smart Storage controllers that are used by several major OEMs we partner with. There is a new generation of controller coming to market later this summer. While customers will be able to use these new controllers with the driver as it is in Focal today, they will be missing several bug fixes and enhancements that have already landed upstream in 5.5. For this reason, Microchip and HPE have asked us to pull these patches to update the SmartPQI driver in Focal to the current upstream version. [FIXES] These are the recommended patches from Microchip that should be cherry-picked from mainline. 390e28087823 scsi: smartpqi: bump version 694c5d5b4625 scsi: smartpqi: Align driver syntax with oob 0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants 5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device e655d469c32d scsi: smartpqi: correct syntax issue bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung 21432010d528 scsi: smartpqi: add inquiry timeouts b969261134c1 scsi: smartpqi: fix call trace in device discovery 0530736e40a0 scsi: smartpqi: fix controller lockup observed during force reboot 9e322310e16c scsi: smartpqi: clean up an indentation issue 1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info' a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement All are clean cherry picks into the 5.4 branch and can be pulled from my branch here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1864484-smartpqi-to-1.2.10-025 [TESTING] modinfo for smartpqi should show: version:1.2.10-025 description:Driver for Microsemi Smart Family Controller version 1.2.10-025 [REGRESSION RISK] Low - Focal is not yet released, this is not being backported to current releases, patches pick cleanly and have been tested by the upstream maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864484] Re: Update SmartPQI driver in Focal to 1.2.10-025
** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864484 Title: Update SmartPQI driver in Focal to 1.2.10-025 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [IMPACT] Feature request to update the SmartPQI driver in Focal to 1.2.10-025 Microchip produces the Smart Storage controllers that are used by several major OEMs we partner with. There is a new generation of controller coming to market later this summer. While customers will be able to use these new controllers with the driver as it is in Focal today, they will be missing several bug fixes and enhancements that have already landed upstream in 5.5. For this reason, Microchip and HPE have asked us to pull these patches to update the SmartPQI driver in Focal to the current upstream version. [FIXES] These are the recommended patches from Microchip that should be cherry-picked from mainline. 390e28087823 scsi: smartpqi: bump version 694c5d5b4625 scsi: smartpqi: Align driver syntax with oob 0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants 5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device e655d469c32d scsi: smartpqi: correct syntax issue bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung 21432010d528 scsi: smartpqi: add inquiry timeouts b969261134c1 scsi: smartpqi: fix call trace in device discovery 0530736e40a0 scsi: smartpqi: fix controller lockup observed during force reboot 9e322310e16c scsi: smartpqi: clean up an indentation issue 1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info' a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement All are clean cherry picks into the 5.4 branch and can be pulled from my branch here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1864484-smartpqi-to-1.2.10-025 [TESTING] modinfo for smartpqi should show: version:1.2.10-025 description:Driver for Microsemi Smart Family Controller version 1.2.10-025 [REGRESSION RISK] Low - Focal is not yet released, this is not being backported to current releases, patches pick cleanly and have been tested by the upstream maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856340] Re: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies
In addition to the patches necessary, the following also applies: -- ** This already exists in Focal - nvme cli rev 1.9 or later must be installed in their system as well, so that auto-connect scripts for systemd are installed. see https://github.com/linux-nvme/nvme-cli ** this is optional - nvmetcli rev v0.7 or later should be installed in their system as well see http://git.infradead.org/users/hch/nvmetcli.git ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Description changed: - Jeff, + [IMPACT] Here are the kernel and cli updates we discussed in email related to LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc 12.6.0.x solution. Please pull these into Ubuntu 20.04. Thank you Laurie Expected that ubuntu is pulling in kernel v5.4 as a base. These would go on top of that. + [FIXES] Additional patches recommended: ( ) f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2 53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes 44fbf3bb1ac3 - Sep 27 2019 - nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu 7db394848ece - Sep 27 2019 - nvme-fc: clarify error messages bcde5f0fc7d3 - Sep 27 2019 - nvme-fc: ensure association_id is cleared regardless of a Disconnect LS 48c9e85b2346 - Oct 14 2019 - nvme: resync include/linux/nvme.h with nvmecli 64fab7290dc3 - Oct 28 2019 - nvme: Fix parsing of ANA log page 863fbae929c7 - Nov 14 2019 - nvme_fc: add module to ops template to allow module references c869e494ef8b - Nov 21 2019 - nvme-fc: fix double-free scenarios on hw queues + [TESTING] + + [REGRESSION RISK] + -- - nvme cli rev 1.9 or later must be installed in their system as well, so that auto-connect scripts for systemd are installed. see https://github.com/linux-nvme/nvme-cli - nvmetcli rev v0.7 or later should be installed in their system as well see http://git.infradead.org/users/hch/nvmetcli.git ** Description changed: [IMPACT] Here are the kernel and cli updates we discussed in email related to LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc 12.6.0.x solution. Please pull these into Ubuntu 20.04. Thank you Laurie Expected that ubuntu is pulling in kernel v5.4 as a base. These would go on top of that. [FIXES] Additional patches recommended: ( ) f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2 53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes 44fbf3bb1ac3 - Sep 27 2019 - nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu 7db394848ece - Sep 27 2019 - nvme-fc: clarify error messages bcde5f0fc7d3 - Sep 27 2019 - nvme-fc: ensure association_id is cleared regardless of a Disconnect LS 48c9e85b2346 - Oct 14 2019 - nvme: resync include/linux/nvme.h with nvmecli 64fab7290dc3 - Oct 28 2019 - nvme: Fix parsing of ANA log page + + These are clean cherry-picks from 5.5 into 5.4 and can be found here: + https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1856340-broadcom-nvme-updates + + These two are already in focal and are only left here for reference as they were part of the original request: 863fbae929c7 - Nov 14 2019 - nvme_fc: add module to ops template to allow module references c869e494ef8b - Nov 21 2019 - nvme-fc: fix double-free scenarios on hw queues [TESTING] [REGRESSION RISK] - - -- - - nvme cli rev 1.9 or later must be installed in their system as well, so that auto-connect scripts for systemd are installed. - see https://github.com/linux-nvme/nvme-cli - - - nvmetcli rev v0.7 or later should be installed in their system as well - see http://git.infradead.org/users/hch/nvmetcli.git -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856340 Title: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [IMPACT] Here are the kernel and cli updates we discussed in email related to LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc 12.6.0.x solution. Please pull these into Ubuntu 20.04. Thank you Laurie Expected that ubuntu is pulling in kernel v5.4 as a base. These would go on top of that. [FIXES] Additional patches recommended: ( ) f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2 53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header c
[Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
** Description changed: - This is a massive number of updates by Broadcom to the lpfc driver that - didn't make 5.4 in time. As 20.04 is an LTS release with expected - hardware support for 5 years, we need to ensure as much hardware support - lands as possible to support server vendors over the next couple years. + [IMPACT] + This is a massive number of updates by Broadcom to the lpfc driver that didn't make 5.4 in time. As 20.04 is an LTS release with expected hardware support for 5 years, we need to ensure as much hardware support lands as possible to support server vendors over the next couple years. Broadcom has updated the lpfc driver to version 12.6.0.2 in 5.5. The version in focal is 12.2.0.3 and missing several bug fixes and hardware - support additions. Given the number of patches missing in Focal, and - that they all apply to a single driver, it may be easiest to just pick - the version in 5.5 fully, rather than apply so many patches to the 5.4 - tree, but that's just a suggestion. + support additions. Please update the driver in focal appropriately. + [FIXES] eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by last cpu id set 4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned cpu for allocation 3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version to 12.6.0.2 542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max queues to be hdwq count bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map for not present cpus d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of lpfc_sli4_cleanup_poll_list() 6c6d59e0fe5b86cf273d6d744a6a9768c4ecc756 scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences 6f23f8c5c9f1be4eb17c035129c80e49000c18a7 scsi: lpfc: fix: Coverity: lpfc_get_scsi_buf_s3(): Null pointer dereferences 61951a6d3153b4482404b739be921a7459f8dc12 scsi: lpfc: Fix lpfc_cpumask_of_node_init() eea2d396aa57acb3607f79ef04c08c2c5166f3fa scsi: lpfc: Fix a kernel warning triggered by lpfc_sli4_enable_intr() 765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel warning triggered by lpfc_get_sgl_per_hdwq() aff6ab9e7221c1b5d15418419b9797e5badd4aec scsi: lpfc: Update lpfc version to 12.6.0.1 171f6c41949f6e9d5e09dcac842a10bf8dda8dcc scsi: lpfc: Add enablement of multiple adapter dumps dcaa213679387e95a315dca05c57dbb15273703c scsi: lpfc: Change default IRQ model on AMD architectures 93a4d6f40198dffcca35d9a928c409f9290f1fe0 scsi: lpfc: Add registration for CPU Offline/Online events b9da814cd5f5bb93041a6e4dbc9c5149713186ff scsi: lpfc: Clarify FAWNN error message 69641627c653464db46f3e3d8c438349be055670 scsi: lpfc: Sync with FC-NVMe-2 SLER change to require Conf with SLER dda5bdf074da3782ff9e785ee50cd2a3f214d498 scsi: lpfc: Fix dynamic fw log enablement check 2332e6e475b016e2026763f51333f84e2e6c57a3 scsi: lpfc: Fix unexpected error messages during RSCN handling 6c1e803eac846f886cd35131e6516fc51a8414b9 scsi: lpfc: Fix kernel crash at lpfc_nvme_info_show during remote port bounce 6bfb1620829825c01e1dcdd63b6a7700352babd9 scsi: lpfc: Fix configuration of BB credit recovery in service parameters 7cfd5639d99bec0d27af089d0c8c114330e43a72 scsi: lpfc: Fix duplicate unreg_rpi error in port offline flow 7b10db555257d1248398643a23e10cf36b50d516 scsi: lpfc: Make lpfc_debugfs_ras_log_data static c3e5aac3e2f501ad4fcb03fed0e32a6f009faea2 scsi: lpfc: Fix NULL check before mempool_destroy is not needed 5792a0e81678da41f05bb724ebd20f134604fa15 scsi: lpfc: fix spelling error in MAGIC_NUMER_xxx 9e2edb41c3d4cab6da0eedcc07ae04758af62ab8 scsi: lpfc: fix build error of lpfc_debugfs.c for vfree/vmalloc 5314995e370e46ac12d12378544ad4575b6f6672 scsi: lpfc: lpfc_nvmet: Fix Use plain integer as NULL pointer 2c7fb469024f0da98f4d078fcf570786ec87c384 scsi: lpfc: lpfc_attr: Fix Use plain integer as NULL pointer 74acec655f560ef721c1e191732af2bcb094b537 scsi: lpfc: Update lpfc version to 12.6.0.0 b4b3417cf6c8051f9f210cd694e6342fb008795c scsi: lpfc: Add additional discovery log messages 83c6cb1ae8be6948b5fa43b2450a176dba80688b scsi: lpfc: Add FC-AL support to lpe32000 models e7d8595272553c27846946601b72e4c581f9712a scsi: lpfc: Add FA-WWN Async Event reporting b1dfa5411ea440f7a5bd65176259ffb3bfbdecf0 scsi: lpfc: Add log macros to allow print by serverity or verbosity setting 95bfc6d8ad86a76c89f62bb466f740b0fc05a667 scsi: lpfc: Make FW logging dynamically configurable 8156d378c4cbf8ca19df5d8f0c610ce6923b61e2 scsi: lpfc: Revise interrupt coalescing for missing scenarios ea85a20cd54f3b09880f6c08994b059f0d114a11 scsi: lpfc: Remove lock contention target write path 22770cbabf6bb77a397d9f11d41f97667dd0caa2 scsi: lpfc: Slight fast-path performance optimizations f84f8f93f01feb64fdda8dd6c72d1b7dc24ad11d scsi: lpfc: fix coverity error of dereference after null
[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
** Tags removed: blocks-hwcert-server -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for Power architecture for 16.04 Status in Provider for Plainbox - Checkbox: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Yakkety: Won't Fix Bug description: memory_stress_ng, as part of server certification is failing for IBM Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is defined by the test locking up the server in an unrecoverable state which only a reboot will fix. I will be attaching screen and kern logs for the failures and a successful run on 14.04 on the same server. To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1573062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1564949] Re: Severe latency/skew on AMD Opetron processor
closing, won't be fixing this, its 4 years old now. ** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Tags removed: hwcert-server -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1564949 Title: Severe latency/skew on AMD Opetron processor Status in linux package in Ubuntu: Invalid Bug description: Discovered this while doing pre-release certification testing for 16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core CPU. I have some code that essentially does this: And note, I am NOT a C programmer, I know enough C to read it and do some minor things, and I once knew C++ fairly well, about 10 years ago... gettimeofday(&tval_start, NULL); sleep(sleeptime); gettimeofday(&tval_stop, NULL); where tval_start and tval_stop are timeval structs and sleeptime is 60. Once it gets the start and stop it finds the delta minus the sleep time. In a perfect world, for example, start time would be 123456.123 and end time would be 123516.123 and the delta between them minus the 60 seconds of sleep would be 0. Of course, that isn't how it works in reality so the delta may be a few microseconds here and there depending on what else the kernel is doing at any given moment. The following, however, are on essentially idle Xenial systems (only processes running are whatever Ubuntu Server runs by default, nothing really taxing going on). On my Skylake i7 with Xenial, the time differences are never more than a few 10,000ths of a second: (kernel 4.4.0-15.31) Testing clock direction for 5 minutes... PASSED: Iteration 0 delta: 0.000109 PASSED: Iteration 1 delta: 0.68 PASSED: Iteration 2 delta: 0.000107 PASSED: Iteration 3 delta: 0.000216 PASSED: Iteration 4 delta: 0.89 On a zVM instance (kernel 4.4.0-16.32) it's even better: PASSED: Iteration 0 delta: 0.58 PASSED: Iteration 1 delta: 0.58 PASSED: Iteration 2 delta: 0.74 PASSED: Iteration 3 delta: 0.52 PASSED: Iteration 4 delta: 0.62 But on an AMD cpu with Xenial (the only AMD CPU I have access to), the difference is always in the 10ths of a second, sometimes even several seconds... in other words, I've seen up to a 7.9 second delta with this code. Here's one run that shows 3 seconds in one iteration: (kernel 4.4.0-15.31) FAILED: Iteration 0 delta: 3.057980 FAILED: Iteration 1 delta: 0.225712 FAILED: Iteration 2 delta: 0.241468 FAILED: Iteration 3 delta: 0.229084 FAILED: Iteration 4 delta: 0.223933 I ran a second run on the AMD cpu and the latency was all over the place: FAILED: Iteration 0 delta: 9.302149 FAILED: Iteration 1 delta: 0.624466 FAILED: Iteration 2 delta: 1.644834 FAILED: Iteration 3 delta: 1.011474 FAILED: Iteration 4 delta: 0.923033 After a discussion with cking and apw, deviations of as seen on the Intel and s390 CPUs are about what we should expect to see depending on what the system is doing at the moment gettimeofday() is executed. However, on the AMD CPU, differences of up to 9 seconds or more are NOT expected and highly irregular. Colin said he tested this on an AMD C60 CPU and got numbers inline with the Skylake and s390 chips and could not reproduce the times I am seeing on the Opteron. $ cat /proc/version_signature Ubuntu 4.4.0-15.31-generic 4.4.6 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 31 17:21 seq crw-rw 1 root audio 116, 33 Mar 31 17:21 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL385p Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/06/2014 dmi.bios.vendor: HP dmi.bios.version: A28 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bv
[Kernel-packages] [Bug 1610320] Re: stress-ng memory testing causes Arm64 system to hang
Markng this invalid. SOMETHING resolved it, but we never figured out what. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1610320 Title: stress-ng memory testing causes Arm64 system to hang Status in linux package in Ubuntu: Invalid Bug description: Running the certification memory test using stress-ng on an ARM64 system with 64GB roughly of RAM (MAAS shows 63GB). The test runs several stress-ng memory related tests. It appears that the system locks up when the bigheap test runs, every time so far (two of two runs have failed). I'm doing a third now to confirm that bigheap is where the lockup occurs. I've also run this exact same test on similar and smaller memory amounts on s390x and amd64 without problem. This is also being done to provide data for a similar bug discovered on Power (ppc64le). To test this on an arm64 system: Install Xenial $ add-apt-repository ppa:hardware-certification/public $ apt update $ apt install canonical-certification-server $ /usr/lib/plainbox-provider-checkbox/bin/memory_stress_ng the memory_stress_ng script is a wrapper for stress_ng that only calls certain memory tests. See script for an idea of how it's executing the tests. This could be the same issue that we're seeing on power, or it could be a different issue for ARM that looks similar. Here's the original Power bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: User Name 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 5 09:27 seq crw-rw 1 root audio 116, 33 Aug 5 09:27 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Aug 5 16:15:51 2016 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1610320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel due to mainline commit 24247aeeabe
** Tags removed: hwcert-server
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1733662
Title:
System hang with Linux kernel due to mainline commit 24247aeeabe
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
The following mainline commit introduced a regression in v4.14-rc1:
24247aeeabe9 ("x86/intel_rdt/cqm: Improve limbo list processing")
This commit made it's way into Artful via Launchpad bug 1591609 as Artful
commit
ac2fc5adab0f4b.
This bug was causing regression tests to hang about one in four
times when running cpu_offlining tests.
This patch to fix this regression was just submitted to mainline, so it is
also
needed in Bionic.
== Fix ==
commit d47924417319e3b6a728c0b690f183e75bc2a702
Author: Thomas Gleixner
Date: Tue Jan 16 19:59:59 2018 +0100
x86/intel_rdt/cqm: Prevent use after free
== Regression Potential ==
Low. This patch fixes a current regression that is a use after free.
### Original Bug Description ###
In doing Ubuntu 17.10 regression testing, we've encountered one computer
(boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when
running our cpu_offlining test. This test attempts to take all the CPU cores
offline except one, then brings them back online again. This test ran
successfully on boldore with previous releases, but with 17.10, the system
sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found
no problems; but when I upgraded the 16.04.3 installation to
linux-image-4.13.0-16-generic, the problem appeared again, so I'm confident
this is a problem with the kernel. I'm attaching two files,
dmesg-output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16
kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg
-w" in a second SSH login; the files are cut-and-pasted from that.)
I initiated this bug report from an Ubuntu 16.04.3 installation
running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Nov 21 17:36:06 2017
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851446] [NEW] Backport MPLS patches from 5.3 to 4.15
Public bug reported: Mellanox is requesting a backport of the following commit IDs from 5.3 back to 4.15. Netdevice HW MPLS features are not passed from device driver's netdevice to upper netdevice, specifically VLAN and bonding netdevice which are created by the kernel when needed. This prevents enablement and usage of HW offloads, such as TSO and checksumming for MPLS tagged traffic when running via VLAN or bonding interface. The patches introduce changes to the initialization steps of the VLAN and bonding netdevices to inherit the MPLS features from lower netdevices to allow the HW offloads. Ariel Levkovich (2): net: bonding: Inherit MPLS features from slave devices net: vlan: Inherit MPLS features from parent device drivers/net/bonding/bond_main.c | 11 +++ net/8021q/vlan_dev.c| 1 + 2 files changed, 12 insertions(+) https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html Commit IDs (All landed in 5.3) 600bb0318c18e9616d97ad123caaa7c5f7bf222c 8b6912a5019356d7adb1b8a146c9eef5e679bf98 2e770b507ccde8eedc129946e4b78ceed0a22df2 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851446 Title: Backport MPLS patches from 5.3 to 4.15 Status in linux package in Ubuntu: New Bug description: Mellanox is requesting a backport of the following commit IDs from 5.3 back to 4.15. Netdevice HW MPLS features are not passed from device driver's netdevice to upper netdevice, specifically VLAN and bonding netdevice which are created by the kernel when needed. This prevents enablement and usage of HW offloads, such as TSO and checksumming for MPLS tagged traffic when running via VLAN or bonding interface. The patches introduce changes to the initialization steps of the VLAN and bonding netdevices to inherit the MPLS features from lower netdevices to allow the HW offloads. Ariel Levkovich (2): net: bonding: Inherit MPLS features from slave devices net: vlan: Inherit MPLS features from parent device drivers/net/bonding/bond_main.c | 11 +++ net/8021q/vlan_dev.c| 1 + 2 files changed, 12 insertions(+) https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html Commit IDs (All landed in 5.3) 600bb0318c18e9616d97ad123caaa7c5f7bf222c 8b6912a5019356d7adb1b8a146c9eef5e679bf98 2e770b507ccde8eedc129946e4b78ceed0a22df2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851446] Re: Backport MPLS patches from 5.3 to 4.15
Thanks Sam! I'll pass that along and have them test these to ensure it works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851446 Title: Backport MPLS patches from 5.3 to 4.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Bug description: Mellanox is requesting a backport of the following commit IDs from 5.3 back to 4.15. Netdevice HW MPLS features are not passed from device driver's netdevice to upper netdevice, specifically VLAN and bonding netdevice which are created by the kernel when needed. This prevents enablement and usage of HW offloads, such as TSO and checksumming for MPLS tagged traffic when running via VLAN or bonding interface. The patches introduce changes to the initialization steps of the VLAN and bonding netdevices to inherit the MPLS features from lower netdevices to allow the HW offloads. Ariel Levkovich (2): net: bonding: Inherit MPLS features from slave devices net: vlan: Inherit MPLS features from parent device drivers/net/bonding/bond_main.c | 11 +++ net/8021q/vlan_dev.c| 1 + 2 files changed, 12 insertions(+) https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html Commit IDs (All landed in 5.3) 600bb0318c18e9616d97ad123caaa7c5f7bf222c 8b6912a5019356d7adb1b8a146c9eef5e679bf98 2e770b507ccde8eedc129946e4b78ceed0a22df2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854881] Re: Boot hang after updating and setting up Iscsi with 4.15.0-72 generic kernel
Just out of curiosity, you mention in comment #1 "p.s. I put the Iscsi target back in fstab, rebooted and selected the old kernel - it booted and mounted without any issue at all." Does this mean that at this point you can reboot and the system boots fine with the iscsi target in fstab? Or do you mean that it ONLY boots successfully using the old kernel, but if you boot the new one again, you're back to hanging? Which kernel successfully boots? (boot the system and do a `uname -a`) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854881 Title: Boot hang after updating and setting up Iscsi with 4.15.0-72 generic kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi All, Host Server - Dell PowerEdge R630, Dual Xeon E5-2650 v4, 768GB Memory, ESX 6.5.0 I created a VM with 1vCPU, 2GB Memory, 16GB Hard drive. I installed Ubuntu Server 16.04.2 (latest ISO I had on hand), installed fine. I then ran apt-get update, apt-get upgrade... upgrade failed as repos were out of date. I then ran do-distribution-upgrade, ran through everything and it appears to work. --I don't want to mislead anyone - I can't remember if I rebooted or not at this point. After this, I setup an Iscsi initiator to an external target, added to fstab, formatted and confirmed all working. I then rebooted, and... nothing! No ping, no ssh or anything... Control + Alt + Del did not work, looked like it had frozen. The last line was starting SSH, but the previous line was the Iscsi initiator. At this point, I figured network is down and ISCSI is hanging as it can't connect/maybe I messed up the ISCSI mount. I then went to GRUB and did advanced, I did the recovery console for kernel 4.15.0-72 generic which lead to a kernel panic: https://snipboard.io/YCOZwv.jpg I then went through the options again and selected 4.4.0-62 generic, and it booted fine, and after about 2 seconds at the recovery menu, further ISCSI related text came up: https://snipboard.io/ALZcsF.jpg I went to the shell as root, deleted the line from fstab, and rebooted, but, it hang again at the same point. I then went to advanced, booted normally to 4.4.0-62 generic, and, it went through without any issue what so ever. Messing around with kernels puts me out of my depth... happy to give further info or do more diagnostics if required, however, due to it working in a different kernel and nothing out of the ordinary - I believe this to be a bug. This is on Ubuntu 18.04.3 LTS / Release 18.04 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 3 01:35 seq crw-rw 1 root audio 116, 33 Dec 3 01:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c2e23b2c-adf6-42b4-bdd7-9d825a36d18c InstallationDate: Installed on 2019-12-02 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=dd730eac-9993-408e-aa5c-c79c6cfcb52e ro ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-12-02 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2016 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/05/2016:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopRefe
[Kernel-packages] [Bug 1854881] Re: Boot hang after updating and setting up Iscsi with 4.15.0-72 generic kernel
Note, I only ask because the kernel listed in some of the info is Ubuntu 4.4.0-62.83-generic 4.4.40 but you mention 18.04 and 18.04.3 and 4.4 and 4.15 and a whole mess of confusing info. So I just want to nail down exactly what kernel works, and what kernel fails. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854881 Title: Boot hang after updating and setting up Iscsi with 4.15.0-72 generic kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi All, Host Server - Dell PowerEdge R630, Dual Xeon E5-2650 v4, 768GB Memory, ESX 6.5.0 I created a VM with 1vCPU, 2GB Memory, 16GB Hard drive. I installed Ubuntu Server 16.04.2 (latest ISO I had on hand), installed fine. I then ran apt-get update, apt-get upgrade... upgrade failed as repos were out of date. I then ran do-distribution-upgrade, ran through everything and it appears to work. --I don't want to mislead anyone - I can't remember if I rebooted or not at this point. After this, I setup an Iscsi initiator to an external target, added to fstab, formatted and confirmed all working. I then rebooted, and... nothing! No ping, no ssh or anything... Control + Alt + Del did not work, looked like it had frozen. The last line was starting SSH, but the previous line was the Iscsi initiator. At this point, I figured network is down and ISCSI is hanging as it can't connect/maybe I messed up the ISCSI mount. I then went to GRUB and did advanced, I did the recovery console for kernel 4.15.0-72 generic which lead to a kernel panic: https://snipboard.io/YCOZwv.jpg I then went through the options again and selected 4.4.0-62 generic, and it booted fine, and after about 2 seconds at the recovery menu, further ISCSI related text came up: https://snipboard.io/ALZcsF.jpg I went to the shell as root, deleted the line from fstab, and rebooted, but, it hang again at the same point. I then went to advanced, booted normally to 4.4.0-62 generic, and, it went through without any issue what so ever. Messing around with kernels puts me out of my depth... happy to give further info or do more diagnostics if required, however, due to it working in a different kernel and nothing out of the ordinary - I believe this to be a bug. This is on Ubuntu 18.04.3 LTS / Release 18.04 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 3 01:35 seq crw-rw 1 root audio 116, 33 Dec 3 01:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c2e23b2c-adf6-42b4-bdd7-9d825a36d18c InstallationDate: Installed on 2019-12-02 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=dd730eac-9993-408e-aa5c-c79c6cfcb52e ro ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-12-02 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2016 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/05/2016:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.ne
[Kernel-packages] [Bug 1851446] Re: Backport MPLS patches from 5.3 to 4.15
I can't add a task for Disco but Terry tells me that we need that as well. I validated that the patches were landed in 5.3, I do not believe they are in 5.0, so we'll probably need test kernels built for Disco as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851446 Title: Backport MPLS patches from 5.3 to 4.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Disco: New Bug description: Mellanox is requesting a backport of the following commit IDs from 5.3 back to 4.15. Netdevice HW MPLS features are not passed from device driver's netdevice to upper netdevice, specifically VLAN and bonding netdevice which are created by the kernel when needed. This prevents enablement and usage of HW offloads, such as TSO and checksumming for MPLS tagged traffic when running via VLAN or bonding interface. The patches introduce changes to the initialization steps of the VLAN and bonding netdevices to inherit the MPLS features from lower netdevices to allow the HW offloads. Ariel Levkovich (2): net: bonding: Inherit MPLS features from slave devices net: vlan: Inherit MPLS features from parent device drivers/net/bonding/bond_main.c | 11 +++ net/8021q/vlan_dev.c| 1 + 2 files changed, 12 insertions(+) https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html Commit IDs (All landed in 5.3) 600bb0318c18e9616d97ad123caaa7c5f7bf222c 8b6912a5019356d7adb1b8a146c9eef5e679bf98 2e770b507ccde8eedc129946e4b78ceed0a22df2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in Ubuntu 20.0.4 to 12.6.0.x
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855303 Title: Update Broadcom Emulex lpfc driver in Ubuntu 20.0.4 to 12.6.0.x Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: Jeff, Here's the list of committed patches on top of your current git tree that we require for lpfc. Please let me know what other information you require. I'm working with James Smart to obtain the list of additional patch kernel dependencies needed and will file a separate launchpad bug for that. --- Dick Kennedy Wed, Dec 4, 9:23 AM (1 day ago) to me They can skip all the ones that say Merge, they should know that anyway. I went all the way back to 12.2.0.3 so that they can see where their tree stopped. eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by last cpu id set 4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned cpu for allocation 3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version to 12.6.0.2 542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max queues to be hdwq count bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map for not present cpus d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of lpfc_sli4_cleanup_poll_list() 6c6d59e0fe5b86cf273d6d744a6a9768c4ecc756 scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences 6f23f8c5c9f1be4eb17c035129c80e49000c18a7 scsi: lpfc: fix: Coverity: lpfc_get_scsi_buf_s3(): Null pointer dereferences 61951a6d3153b4482404b739be921a7459f8dc12 scsi: lpfc: Fix lpfc_cpumask_of_node_init() eea2d396aa57acb3607f79ef04c08c2c5166f3fa scsi: lpfc: Fix a kernel warning triggered by lpfc_sli4_enable_intr() 765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel warning triggered by lpfc_get_sgl_per_hdwq() aff6ab9e7221c1b5d15418419b9797e5badd4aec scsi: lpfc: Update lpfc version to 12.6.0.1 171f6c41949f6e9d5e09dcac842a10bf8dda8dcc scsi: lpfc: Add enablement of multiple adapter dumps dcaa213679387e95a315dca05c57dbb15273703c scsi: lpfc: Change default IRQ model on AMD architectures 93a4d6f40198dffcca35d9a928c409f9290f1fe0 scsi: lpfc: Add registration for CPU Offline/Online events b9da814cd5f5bb93041a6e4dbc9c5149713186ff scsi: lpfc: Clarify FAWNN error message 69641627c653464db46f3e3d8c438349be055670 scsi: lpfc: Sync with FC-NVMe-2 SLER change to require Conf with SLER dda5bdf074da3782ff9e785ee50cd2a3f214d498 scsi: lpfc: Fix dynamic fw log enablement check 2332e6e475b016e2026763f51333f84e2e6c57a3 scsi: lpfc: Fix unexpected error messages during RSCN handling 6c1e803eac846f886cd35131e6516fc51a8414b9 scsi: lpfc: Fix kernel crash at lpfc_nvme_info_show during remote port bounce 6bfb1620829825c01e1dcdd63b6a7700352babd9 scsi: lpfc: Fix configuration of BB credit recovery in service parameters 7cfd5639d99bec0d27af089d0c8c114330e43a72 scsi: lpfc: Fix duplicate unreg_rpi error in port offline flow 7b10db555257d1248398643a23e10cf36b50d516 scsi: lpfc: Make lpfc_debugfs_ras_log_data static c3e5aac3e2f501ad4fcb03fed0e32a6f009faea2 scsi: lpfc: Fix NULL check before mempool_destroy is not needed 5792a0e81678da41f05bb724ebd20f134604fa15 scsi: lpfc: fix spelling error in MAGIC_NUMER_xxx 9e2edb41c3d4cab6da0eedcc07ae04758af62ab8 scsi: lpfc: fix build error of lpfc_debugfs.c for vfree/vmalloc 5314995e370e46ac12d12378544ad4575b6f6672 scsi: lpfc: lpfc_nvmet: Fix Use plain integer as NULL pointer 2c7fb469024f0da98f4d078fcf570786ec87c384 scsi: lpfc: lpfc_attr: Fix Use plain integer as NULL pointer 74acec655f560ef721c1e191732af2bcb094b537 scsi: lpfc: Update lpfc version to 12.6.0.0 b4b3417cf6c8051f9f210cd694e6342fb008795c scsi: lpfc: Add additional discovery log messages 83c6cb1ae8be6948b5fa43b2450a176dba80688b scsi: lpfc: Add FC-AL support to lpe32000 models e7d8595272553c27846946601b72e4c581f9712a scsi: lpfc: Add FA-WWN Async Event reporting b1dfa5411ea440f7a5bd65176259ffb3bfbdecf0 scsi: lpfc: Add log macros to allow print by serverity or verbosity setting 95bfc6d8ad86a76c89f62bb466f740b0fc05a667 scsi: lpfc: Make FW logging dynamically configurable 8156d378c4cbf8ca19df5d8f0c610ce6923b61e2 scsi: lpfc: Revise interrupt coalescing for missing scenarios ea85a20cd54f3b09880f6c08994b059f0d114a11 scsi: lpfc: Remove lock contention target write path 22770cbabf6bb77a397d9f11d41f97667dd0caa2 scsi: lpfc: Slight fast-path performance optimizations f84f8f93f01feb64fdda8dd6c72d1b7dc24ad11d scsi: lpfc: fix coverity error of dereference after null check 91a52b617cdb8bf6d298892101c061d438b84a19 scsi: lpfc: Fix hardlockup in lpfc_abort_handler
[Kernel-packages] [Bug 1856340] Re: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies
This is a patch request, logs not needed. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856340 Title: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: Jeff, Here are the kernel and cli updates we discussed in email related to LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc 12.6.0.x solution. Please pull these into Ubuntu 20.04. Thank you Laurie Expected that ubuntu is pulling in kernel v5.4 as a base. These would go on top of that. Additional patches recommended: ( ) f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2 53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes 44fbf3bb1ac3 - Sep 27 2019 - nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu 7db394848ece - Sep 27 2019 - nvme-fc: clarify error messages bcde5f0fc7d3 - Sep 27 2019 - nvme-fc: ensure association_id is cleared regardless of a Disconnect LS 48c9e85b2346 - Oct 14 2019 - nvme: resync include/linux/nvme.h with nvmecli 64fab7290dc3 - Oct 28 2019 - nvme: Fix parsing of ANA log page 863fbae929c7 - Nov 14 2019 - nvme_fc: add module to ops template to allow module references c869e494ef8b - Nov 21 2019 - nvme-fc: fix double-free scenarios on hw queues -- - nvme cli rev 1.9 or later must be installed in their system as well, so that auto-connect scripts for systemd are installed. see https://github.com/linux-nvme/nvme-cli - nvmetcli rev v0.7 or later should be installed in their system as well see http://git.infradead.org/users/hch/nvmetcli.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
** Summary changed: - Update Broadcom Emulex lpfc driver in Ubuntu 20.0.4 to 12.6.0.x + Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5 ** Description changed: - Jeff, + This is a massive number of updates by Broadcom to the lpfc driver that + didn't make 5.4 in time. As 20.04 is an LTS release with expected + hardware support for 5 years, we need to ensure as much hardware support + lands as possible to support server vendors over the next couple years. - Here's the list of committed patches on top of your current git tree - that we require for lpfc. Please let me know what other information you - require. I'm working with James Smart to obtain the list of additional - patch kernel dependencies needed and will file a separate launchpad bug - for that. + Broadcom has updated the lpfc driver to version 12.6.0.2 in 5.5. The + version in focal is 12.2.0.3 and missing several bug fixes and hardware + support additions. Given the number of patches missing in Focal, and + that they all apply to a single driver, it may be easiest to just pick + the version in 5.5 fully, rather than apply so many patches to the 5.4 + tree, but that's just a suggestion. - --- - - Dick Kennedy - Wed, Dec 4, 9:23 AM (1 day ago) - to me - - They can skip all the ones that say Merge, they should know that anyway. - I went all the way back to 12.2.0.3 so that they can see where their tree stopped. + Please update the driver in focal appropriately. eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by last cpu id set 4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned cpu for allocation 3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version to 12.6.0.2 542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max queues to be hdwq count bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map for not present cpus d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of lpfc_sli4_cleanup_poll_list() 6c6d59e0fe5b86cf273d6d744a6a9768c4ecc756 scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences 6f23f8c5c9f1be4eb17c035129c80e49000c18a7 scsi: lpfc: fix: Coverity: lpfc_get_scsi_buf_s3(): Null pointer dereferences 61951a6d3153b4482404b739be921a7459f8dc12 scsi: lpfc: Fix lpfc_cpumask_of_node_init() eea2d396aa57acb3607f79ef04c08c2c5166f3fa scsi: lpfc: Fix a kernel warning triggered by lpfc_sli4_enable_intr() 765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel warning triggered by lpfc_get_sgl_per_hdwq() aff6ab9e7221c1b5d15418419b9797e5badd4aec scsi: lpfc: Update lpfc version to 12.6.0.1 171f6c41949f6e9d5e09dcac842a10bf8dda8dcc scsi: lpfc: Add enablement of multiple adapter dumps dcaa213679387e95a315dca05c57dbb15273703c scsi: lpfc: Change default IRQ model on AMD architectures 93a4d6f40198dffcca35d9a928c409f9290f1fe0 scsi: lpfc: Add registration for CPU Offline/Online events b9da814cd5f5bb93041a6e4dbc9c5149713186ff scsi: lpfc: Clarify FAWNN error message 69641627c653464db46f3e3d8c438349be055670 scsi: lpfc: Sync with FC-NVMe-2 SLER change to require Conf with SLER dda5bdf074da3782ff9e785ee50cd2a3f214d498 scsi: lpfc: Fix dynamic fw log enablement check 2332e6e475b016e2026763f51333f84e2e6c57a3 scsi: lpfc: Fix unexpected error messages during RSCN handling 6c1e803eac846f886cd35131e6516fc51a8414b9 scsi: lpfc: Fix kernel crash at lpfc_nvme_info_show during remote port bounce 6bfb1620829825c01e1dcdd63b6a7700352babd9 scsi: lpfc: Fix configuration of BB credit recovery in service parameters 7cfd5639d99bec0d27af089d0c8c114330e43a72 scsi: lpfc: Fix duplicate unreg_rpi error in port offline flow 7b10db555257d1248398643a23e10cf36b50d516 scsi: lpfc: Make lpfc_debugfs_ras_log_data static c3e5aac3e2f501ad4fcb03fed0e32a6f009faea2 scsi: lpfc: Fix NULL check before mempool_destroy is not needed 5792a0e81678da41f05bb724ebd20f134604fa15 scsi: lpfc: fix spelling error in MAGIC_NUMER_xxx 9e2edb41c3d4cab6da0eedcc07ae04758af62ab8 scsi: lpfc: fix build error of lpfc_debugfs.c for vfree/vmalloc 5314995e370e46ac12d12378544ad4575b6f6672 scsi: lpfc: lpfc_nvmet: Fix Use plain integer as NULL pointer 2c7fb469024f0da98f4d078fcf570786ec87c384 scsi: lpfc: lpfc_attr: Fix Use plain integer as NULL pointer 74acec655f560ef721c1e191732af2bcb094b537 scsi: lpfc: Update lpfc version to 12.6.0.0 b4b3417cf6c8051f9f210cd694e6342fb008795c scsi: lpfc: Add additional discovery log messages 83c6cb1ae8be6948b5fa43b2450a176dba80688b scsi: lpfc: Add FC-AL support to lpe32000 models e7d8595272553c27846946601b72e4c581f9712a scsi: lpfc: Add FA-WWN Async Event reporting b1dfa5411ea440f7a5bd65176259ffb3bfbdecf0 scsi: lpfc: Add log macros to allow print by serverity or verbosity setting 95bfc6d8ad86a76c89f62bb466f740b0fc05a667 scsi: lpfc: Make FW logging dynamically configurable 8156d378c4cbf8ca19
[Kernel-packages] [Bug 1860690] [NEW] Smartpqi updates for 18.04.4
Public bug reported: This request was lost, unfortunately, so I'm resubmitting and at this poing would need to be SRU'd into 5.3 for 18.04.4 to avoid customers needing to wait until August for 18.04.5 to land. The following patches are in 5.4 and Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. Impact: Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Description changed: - This request was lost, unfortunately and so would need to be SRU'd into - 5.3 for 18.04.4 to avoid customers needing to wait until August for - 18.04.5 to land. + This request was lost, unfortunately, so I'm resubmitting and at this + poing would need to be SRU'd into 5.3 for 18.04.4 to avoid customers + needing to wait until August for 18.04.5 to land. The following patches are in 5.4 and Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. + + Impact: + Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update. ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860690 Title: Smartpqi updates for 18.04.4 Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This request was lost, unfortunately, so I'm resubmitting and at this poing would need to be SRU'd into 5.3 for 18.04.4 to avoid customers needing to wait until August for 18.04.5 to land. The following patches are in 5.4 and Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. Impact: Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860690/+subscri
[Kernel-packages] [Bug 1860690] Re: Smartpqi updates for 18.04.4
** Description changed: - This request was lost, unfortunately, so I'm resubmitting and at this - poing would need to be SRU'd into 5.3 for 18.04.4 to avoid customers - needing to wait until August for 18.04.5 to land. + [Impact] + Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update. - The following patches are in 5.4 and Microsemi have asked to have them - pulled into 5.3 to update the SmartPQI driver that we carry. + [Fixes] + The following patches are in 5.4 and Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. - Impact: - Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update. + [Regression Risk] + Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860690 Title: Smartpqi updates for 18.04.4 Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: [Impact] Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update. [Fixes] The following patches are in 5.4 and Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. [Regression Risk] Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860690] Re: Smartpqi updates for 18.04.4
** Description changed: [Impact] Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update. + Microsemi have asked to have them pulled into 5.3 to update the SmartPQI + driver that we carry. + [Fixes] - The following patches are in 5.4 and Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. + The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. [Regression Risk] Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860690 Title: Smartpqi updates for 18.04.4 Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Bug description: [Impact] Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update. Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. [Fixes] The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. [Regression Risk] Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860690] Re: Smartpqi updates for 18.04.4
Patch Pull request, no logs needed. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860690 Title: Smartpqi updates for 18.04.4 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: [Impact] Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update. Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. [Fixes] The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. [Regression Risk] Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860690] Re: Smartpqi updates for 18.04.4
** Description changed: [Impact] - Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update. + Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't land the updates in 18.04.4 customers would be waiting until ~ August 2020 for the 18.04.5 update. Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. [Fixes] The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. + These have been cherry picked into my branch found here: + https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/eoan/+ref/1860690-smartpqi-updates-master-next + + [Testing] + + [Regression Risk] Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860690 Title: Smartpqi updates for 18.04.4 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: [Impact] Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't land the updates in 18.04.4 customers would be waiting until ~ August 2020 for the 18.04.5 update. Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. [Fixes] The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. These have been cherry picked into my branch found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/eoan/+ref/1860690-smartpqi-updates-master-next [Testing] [Regression Risk] Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860690] Re: Smartpqi updates for 18.04.4
** Description changed: [Impact] Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't land the updates in 18.04.4 customers would be waiting until ~ August 2020 for the 18.04.5 update. Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. [Fixes] The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. These have been cherry picked into my branch found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/eoan/+ref/1860690-smartpqi-updates-master-next [Testing] - + Tested by upstream [Regression Risk] Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860690 Title: Smartpqi updates for 18.04.4 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: [Impact] Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't land the updates in 18.04.4 customers would be waiting until ~ August 2020 for the 18.04.5 update. Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. [Fixes] The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. These have been cherry picked into my branch found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/eoan/+ref/1860690-smartpqi-updates-master-next [Testing] Tested by upstream [Regression Risk] Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860690] Re: Smartpqi updates for 18.04.4
** Description changed: [Impact] Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't land the updates in 18.04.4 customers would be waiting until ~ August 2020 for the 18.04.5 update. Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. [Fixes] - The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3. + The following patches are in 5.4 Mainline and Focal. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. These have been cherry picked into my branch found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/eoan/+ref/1860690-smartpqi-updates-master-next [Testing] - Tested by upstream + Verify via lsmod the driver is loaded + Verify via modinfo the driver version is correct (1.2.8-026) [Regression Risk] Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860690 Title: Smartpqi updates for 18.04.4 Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: In Progress Bug description: [Impact] Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't land the updates in 18.04.4 customers would be waiting until ~ August 2020 for the 18.04.5 update. Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry. [Fixes] The following patches are in 5.4 Mainline and Focal. 391a24179423 scsi: smartpqi: bump version 48edb8780100 scsi: smartpqi: update copyright 63a7956ae1e8 scsi: smartpqi: add new pci ids 9946a3987248 scsi: smartpqi: correct REGNEWD return status 71ecc60d9ba4 scsi: smartpqi: add gigabyte controller 530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds 2d2ad4bc724e scsi: smartpqi: add bay identifier 6d90615f1346 scsi: smartpqi: add sysfs entries 522bc026f013 scsi: smartpqi: add module param to hide vsep 8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller 5e6a9760f7da scsi: smartpqi: add module param for exposure order All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. These have been cherry picked into my branch found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/eoan/+ref/1860690-smartpqi-updates-master-next [Testing] Verify via lsmod the driver is loaded Verify via modinfo the driver version is correct (1.2.8-026) [Regression Risk] Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851446] Re: Backport MPLS patches from 5.3 to 4.15
Sam, can you provide a link to your git tree with these commits? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851446 Title: Backport MPLS patches from 5.3 to 4.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Disco: New Bug description: Mellanox is requesting a backport of the following commit IDs from 5.3 back to 4.15. Netdevice HW MPLS features are not passed from device driver's netdevice to upper netdevice, specifically VLAN and bonding netdevice which are created by the kernel when needed. This prevents enablement and usage of HW offloads, such as TSO and checksumming for MPLS tagged traffic when running via VLAN or bonding interface. The patches introduce changes to the initialization steps of the VLAN and bonding netdevices to inherit the MPLS features from lower netdevices to allow the HW offloads. Ariel Levkovich (2): net: bonding: Inherit MPLS features from slave devices net: vlan: Inherit MPLS features from parent device drivers/net/bonding/bond_main.c | 11 +++ net/8021q/vlan_dev.c| 1 + 2 files changed, 12 insertions(+) https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html Commit IDs (All landed in 5.3) 600bb0318c18e9616d97ad123caaa7c5f7bf222c 8b6912a5019356d7adb1b8a146c9eef5e679bf98 2e770b507ccde8eedc129946e4b78ceed0a22df2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851446] Re: Backport MPLS patches from 5.3 to 4.15
Sam, could you please provide a link to your git tree with these commits? The testers ran into issues with MPLS offloads and are asking for a source code link to debug their issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851446 Title: Backport MPLS patches from 5.3 to 4.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Disco: New Bug description: Mellanox is requesting a backport of the following commit IDs from 5.3 back to 4.15. Netdevice HW MPLS features are not passed from device driver's netdevice to upper netdevice, specifically VLAN and bonding netdevice which are created by the kernel when needed. This prevents enablement and usage of HW offloads, such as TSO and checksumming for MPLS tagged traffic when running via VLAN or bonding interface. The patches introduce changes to the initialization steps of the VLAN and bonding netdevices to inherit the MPLS features from lower netdevices to allow the HW offloads. Ariel Levkovich (2): net: bonding: Inherit MPLS features from slave devices net: vlan: Inherit MPLS features from parent device drivers/net/bonding/bond_main.c | 11 +++ net/8021q/vlan_dev.c| 1 + 2 files changed, 12 insertions(+) https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html Commit IDs (All landed in 5.3) 600bb0318c18e9616d97ad123caaa7c5f7bf222c 8b6912a5019356d7adb1b8a146c9eef5e679bf98 2e770b507ccde8eedc129946e4b78ceed0a22df2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858840] Re: Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.3) on Broadcom FC HBAs
** Summary changed: - Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 on Broadcom FC HBAs + Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.3) on Broadcom FC HBAs ** Summary changed: - Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.3) on Broadcom FC HBAs + Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.0) on Broadcom FC HBAs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858840 Title: Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.0) on Broadcom FC HBAs Status in linux package in Ubuntu: Incomplete Bug description: Jeff, We have analyzed this issue and see that there are 3 missing patches required to fix this problem. Otherwise vport creation >3 (depending on the customers configuration) will result in a hang for FC or NVMe/FC adapters. Please pull these changes into the next hardware release. These are the missing commits: 959239d [scsi] scsi: core: avoid pre-allocating big SGL for data 5418f2f [scsi] scsi: core: avoid pre-allocating big SGL for protection information 250f285 [nvme] scsi: lib/sg_pool.c: improve APIs for allocating sg pool Laurie - CONFIGURATION DETAILS Host OS with Support Pack - Ubuntu 18.04.3 - HWE () Guest/VM OS Details- System(s) Under Test - IBM x3650 M4 Adapter(s) Under Test - Prism 1-port IPL Name - Active Profile ID - Network Configuration - SAN Configuration - OneCapture file attached - BUG REPRODUCTION DETAILS Test Case ID or ATID - Reproducibility of Bug - Always Last Known Working Build - Time to Reproduce Bug - 5 mins Steps To Reproduce Bug - Create 126 vports on Prism adapter, observe that server goes out of memory and hung. root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G1.7G 13G1.3M299M 13G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G2.1G 12G1.3M299M 12G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G6.1G8.7G1.5M301M 8.7G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 13G1.4G1.6M303M 1.4G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G523M1.7M303M 528M Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G147M 96K 48M 5.0M Swap: 2.0G 38M2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G145M 96K 49M 3.6M Swap: 2.0G 38M2.0G Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.166689] scsi host112: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.233464] lpfc :11:00.0: 0:(111):1825 Vport Created. Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.234071] scsi host1: vport-1:0-110 created via shost1 channel 0 Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.698396] scsi host113: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable Nov 28 05:37:30 ubuntu18043 kernel: [ 1523.862582] lpfc :11:00.0: 0:(112):1825 Vport Created. Nov 28 05:37:30 ubuntu18043 kernel: [ 1523.863142] scsi host1: vport-1:0-111 created via shost1 channel 0 Nov 28 05:37:31 ubuntu18043 kernel: [ 1525.097335] scsi host114: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable After creating 111 vports, server ran out of memory. As server is in hung state, no Crash dump got collected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/l
[Kernel-packages] [Bug 1858840] Re: Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.0) on Broadcom FC HBAs
Patches are in 5.3 via f7563f743d7081710a9d186a8b203997d09f383 and should be in linux-image-generic-hwe-18.04-edge Asked to have testers verify that edge fixes the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858840 Title: Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.0) on Broadcom FC HBAs Status in linux package in Ubuntu: Incomplete Bug description: Jeff, We have analyzed this issue and see that there are 3 missing patches required to fix this problem. Otherwise vport creation >3 (depending on the customers configuration) will result in a hang for FC or NVMe/FC adapters. Please pull these changes into the next hardware release. These are the missing commits: 959239d [scsi] scsi: core: avoid pre-allocating big SGL for data 5418f2f [scsi] scsi: core: avoid pre-allocating big SGL for protection information 250f285 [nvme] scsi: lib/sg_pool.c: improve APIs for allocating sg pool Laurie - CONFIGURATION DETAILS Host OS with Support Pack - Ubuntu 18.04.3 - HWE () Guest/VM OS Details- System(s) Under Test - IBM x3650 M4 Adapter(s) Under Test - Prism 1-port IPL Name - Active Profile ID - Network Configuration - SAN Configuration - OneCapture file attached - BUG REPRODUCTION DETAILS Test Case ID or ATID - Reproducibility of Bug - Always Last Known Working Build - Time to Reproduce Bug - 5 mins Steps To Reproduce Bug - Create 126 vports on Prism adapter, observe that server goes out of memory and hung. root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G1.7G 13G1.3M299M 13G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G2.1G 12G1.3M299M 12G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G6.1G8.7G1.5M301M 8.7G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 13G1.4G1.6M303M 1.4G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G523M1.7M303M 528M Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G147M 96K 48M 5.0M Swap: 2.0G 38M2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G145M 96K 49M 3.6M Swap: 2.0G 38M2.0G Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.166689] scsi host112: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.233464] lpfc :11:00.0: 0:(111):1825 Vport Created. Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.234071] scsi host1: vport-1:0-110 created via shost1 channel 0 Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.698396] scsi host113: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable Nov 28 05:37:30 ubuntu18043 kernel: [ 1523.862582] lpfc :11:00.0: 0:(112):1825 Vport Created. Nov 28 05:37:30 ubuntu18043 kernel: [ 1523.863142] scsi host1: vport-1:0-111 created via shost1 channel 0 Nov 28 05:37:31 ubuntu18043 kernel: [ 1525.097335] scsi host114: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable After creating 111 vports, server ran out of memory. As server is in hung state, no Crash dump got collected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858840] Re: Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.0) on Broadcom FC HBAs
errr, that should be 1f7563f743d7081710a9d186a8b203997d09f383 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858840 Title: Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.0) on Broadcom FC HBAs Status in linux package in Ubuntu: Incomplete Bug description: Jeff, We have analyzed this issue and see that there are 3 missing patches required to fix this problem. Otherwise vport creation >3 (depending on the customers configuration) will result in a hang for FC or NVMe/FC adapters. Please pull these changes into the next hardware release. These are the missing commits: 959239d [scsi] scsi: core: avoid pre-allocating big SGL for data 5418f2f [scsi] scsi: core: avoid pre-allocating big SGL for protection information 250f285 [nvme] scsi: lib/sg_pool.c: improve APIs for allocating sg pool Laurie - CONFIGURATION DETAILS Host OS with Support Pack - Ubuntu 18.04.3 - HWE () Guest/VM OS Details- System(s) Under Test - IBM x3650 M4 Adapter(s) Under Test - Prism 1-port IPL Name - Active Profile ID - Network Configuration - SAN Configuration - OneCapture file attached - BUG REPRODUCTION DETAILS Test Case ID or ATID - Reproducibility of Bug - Always Last Known Working Build - Time to Reproduce Bug - 5 mins Steps To Reproduce Bug - Create 126 vports on Prism adapter, observe that server goes out of memory and hung. root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G1.7G 13G1.3M299M 13G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G2.1G 12G1.3M299M 12G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G6.1G8.7G1.5M301M 8.7G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 13G1.4G1.6M303M 1.4G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G523M1.7M303M 528M Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G147M 96K 48M 5.0M Swap: 2.0G 38M2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G145M 96K 49M 3.6M Swap: 2.0G 38M2.0G Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.166689] scsi host112: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.233464] lpfc :11:00.0: 0:(111):1825 Vport Created. Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.234071] scsi host1: vport-1:0-110 created via shost1 channel 0 Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.698396] scsi host113: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable Nov 28 05:37:30 ubuntu18043 kernel: [ 1523.862582] lpfc :11:00.0: 0:(112):1825 Vport Created. Nov 28 05:37:30 ubuntu18043 kernel: [ 1523.863142] scsi host1: vport-1:0-111 created via shost1 channel 0 Nov 28 05:37:31 ubuntu18043 kernel: [ 1525.097335] scsi host114: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable After creating 111 vports, server ran out of memory. As server is in hung state, no Crash dump got collected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856340] Re: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies
Initial impressions nvme-cli is currently in Focal at 1.9-1 (Universe) Patches are all in 5.5 and will need to be picked into 5.4. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856340 Title: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: Jeff, Here are the kernel and cli updates we discussed in email related to LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc 12.6.0.x solution. Please pull these into Ubuntu 20.04. Thank you Laurie Expected that ubuntu is pulling in kernel v5.4 as a base. These would go on top of that. Additional patches recommended: ( ) f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2 53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes 44fbf3bb1ac3 - Sep 27 2019 - nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu 7db394848ece - Sep 27 2019 - nvme-fc: clarify error messages bcde5f0fc7d3 - Sep 27 2019 - nvme-fc: ensure association_id is cleared regardless of a Disconnect LS 48c9e85b2346 - Oct 14 2019 - nvme: resync include/linux/nvme.h with nvmecli 64fab7290dc3 - Oct 28 2019 - nvme: Fix parsing of ANA log page 863fbae929c7 - Nov 14 2019 - nvme_fc: add module to ops template to allow module references c869e494ef8b - Nov 21 2019 - nvme-fc: fix double-free scenarios on hw queues -- - nvme cli rev 1.9 or later must be installed in their system as well, so that auto-connect scripts for systemd are installed. see https://github.com/linux-nvme/nvme-cli - nvmetcli rev v0.7 or later should be installed in their system as well see http://git.infradead.org/users/hch/nvmetcli.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856340] Re: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies
** Tags added: fo ** Tags removed: fo ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856340 Title: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: Jeff, Here are the kernel and cli updates we discussed in email related to LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc 12.6.0.x solution. Please pull these into Ubuntu 20.04. Thank you Laurie Expected that ubuntu is pulling in kernel v5.4 as a base. These would go on top of that. Additional patches recommended: ( ) f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2 53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes 44fbf3bb1ac3 - Sep 27 2019 - nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu 7db394848ece - Sep 27 2019 - nvme-fc: clarify error messages bcde5f0fc7d3 - Sep 27 2019 - nvme-fc: ensure association_id is cleared regardless of a Disconnect LS 48c9e85b2346 - Oct 14 2019 - nvme: resync include/linux/nvme.h with nvmecli 64fab7290dc3 - Oct 28 2019 - nvme: Fix parsing of ANA log page 863fbae929c7 - Nov 14 2019 - nvme_fc: add module to ops template to allow module references c869e494ef8b - Nov 21 2019 - nvme-fc: fix double-free scenarios on hw queues -- - nvme cli rev 1.9 or later must be installed in their system as well, so that auto-connect scripts for systemd are installed. see https://github.com/linux-nvme/nvme-cli - nvmetcli rev v0.7 or later should be installed in their system as well see http://git.infradead.org/users/hch/nvmetcli.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858840] Re: Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.0) on Broadcom FC HBAs
Discussed this with OP, and as the patches are already in our 5.3 branch and thus will land in 18.04.4 shortly, there is nothing needed to do here, so marking invalid. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858840 Title: Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.0) on Broadcom FC HBAs Status in linux package in Ubuntu: Invalid Bug description: Jeff, We have analyzed this issue and see that there are 3 missing patches required to fix this problem. Otherwise vport creation >3 (depending on the customers configuration) will result in a hang for FC or NVMe/FC adapters. Please pull these changes into the next hardware release. These are the missing commits: 959239d [scsi] scsi: core: avoid pre-allocating big SGL for data 5418f2f [scsi] scsi: core: avoid pre-allocating big SGL for protection information 250f285 [nvme] scsi: lib/sg_pool.c: improve APIs for allocating sg pool Laurie - CONFIGURATION DETAILS Host OS with Support Pack - Ubuntu 18.04.3 - HWE () Guest/VM OS Details- System(s) Under Test - IBM x3650 M4 Adapter(s) Under Test - Prism 1-port IPL Name - Active Profile ID - Network Configuration - SAN Configuration - OneCapture file attached - BUG REPRODUCTION DETAILS Test Case ID or ATID - Reproducibility of Bug - Always Last Known Working Build - Time to Reproduce Bug - 5 mins Steps To Reproduce Bug - Create 126 vports on Prism adapter, observe that server goes out of memory and hung. root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G1.7G 13G1.3M299M 13G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G2.1G 12G1.3M299M 12G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G6.1G8.7G1.5M301M 8.7G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 13G1.4G1.6M303M 1.4G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G523M1.7M303M 528M Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G147M 96K 48M 5.0M Swap: 2.0G 38M2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G145M 96K 49M 3.6M Swap: 2.0G 38M2.0G Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.166689] scsi host112: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.233464] lpfc :11:00.0: 0:(111):1825 Vport Created. Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.234071] scsi host1: vport-1:0-110 created via shost1 channel 0 Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.698396] scsi host113: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable Nov 28 05:37:30 ubuntu18043 kernel: [ 1523.862582] lpfc :11:00.0: 0:(112):1825 Vport Created. Nov 28 05:37:30 ubuntu18043 kernel: [ 1523.863142] scsi host1: vport-1:0-111 created via shost1 channel 0 Nov 28 05:37:31 ubuntu18043 kernel: [ 1525.097335] scsi host114: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable After creating 111 vports, server ran out of memory. As server is in hung state, no Crash dump got collected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1834990] [NEW] Cascade Lake system with DCPMM devices abends under stress
Private bug reported: I've been trying to run the server certification tools on a server with DPCMM devices that are configured as: 15% MemoryMode, 85% AppDirect mode. I've configured a fsdax, devdax, sector and raw devices on the DCPMMs. fsdax, devdax and sector are all mountable, formatted etc. The test runs CKing's stress-ng disk tests against the DCPMM storage devices, and after so long, the entire server abends and resets. This is the exact same test we run on all servers and it never causes this sort of behaviour. So the likely issues: 1: Some odditiy in testing the AppDirect storage devices on DCPMMs. 2: Some Kernel thing that's not able to deal with high I/O loads on DCPMMs. I'm currently in the middle of recreating this abit easier, so I'll provide directions soon. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 2 04:41 seq crw-rw 1 root audio 116, 33 Jul 2 04:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 2 05:37:17 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. Bus 001 Device 002: ID :0001 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S2600WFD PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=d8f7444e-3965-49ba-bc42-628bc368893a ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2019 dmi.bios.vendor: Intel Corporation dmi.bios.version: SE5C620.86B.0D.01.0395.022720191340 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S2600WFD dmi.board.vendor: Intel Corporation dmi.board.version: J46732-610 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrSE5C620.86B.0D.01.0395.022720191340:bd02/27/2019:svnIntelCorporation:pnS2600WFD:pvr:rvnIntelCorporation:rnS2600WFD:rvrJ46732-610:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S2600WFD dmi.product.version: dmi.sys.vendor: Intel Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images ** Information type changed from Public to Public Security ** Information type changed from Public Security to Private -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834990 Title: Cascade Lake system with DCPMM devices abends under stress Status in linux package in Ubuntu: New Bug description: I've been trying to run the server certification tools on a server with DPCMM devices that are configured as: 15% MemoryMode, 85% AppDirect mode. I've configured a fsdax, devdax, sector and raw devices on the DCPMMs. fsdax, devdax and sector are all mountable, formatted etc. The test runs CKing's stress-ng disk tests against the DCPMM storage devices, and after so long, the entire server abends and resets. This is the exact same test we run on all servers and it never causes this sort of behaviour. So the likely issues: 1: Some odditiy in testing the AppDirect storage devices on DCPMMs. 2: Some Kernel thing that's not able to deal with high I/O loads on DCPMMs. I'm currently in the middle of recreating this abit easier, so I'll provide directions soon. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 2 04:41 seq crw-rw 1 root audio 116, 33 Jul 2 04:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordD
[Kernel-packages] [Bug 1757191] Re: Intel NICs not properly reporting link speed in SysFS in Xenial
It looks like this happened perhaps sometime between 4.10 and 4.13: 4.4.0-112: https://certification.canonical.com/hardware/201802-26096/submission/127640/ Driver: ixgbe (ver: 4.2.1-k) Shows proper speed for both ports 4.10.0-42: https://certification.canonical.com/hardware/201712-26025/submission/125481/ Driver: ixgbe (ver: 4.4.0-k) Shows proper speed for both ports 4.13.0-37: https://certification.canonical.com/hardware/201803-26156/submission/128508/ Driver: ixgbe (ver: 5.1.0-k) Shows -1 for second port 4.16.0-041600rc6 (tester sent via email) Driver version unknown Shows -1 for second port -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757191 Title: Intel NICs not properly reporting link speed in SysFS in Xenial Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Triaged Bug description: This was discovered during certification testing of 16.04.4 (I've now seen this behaviour at least 2 times) A system under test has a 2 port Intel X550 NIC (10Gb) Udev reports the NIC as this: Category: NETWORK Interface: enp94s0f0 Product: Ethernet Controller 10G X550T Vendor: Intel Corporation Driver: ixgbe (ver: 5.1.0-k) Path: /devices/pci:5d/:5d:00.0/:5e:00.0 ID: [8086:1563] Subsystem ID: [152d:8a13] Ethtool shows this info (this is for the second port, which has the issue) Settings for enp94s0f1: Supported ports: [ TP ] Supported link modes: 100baseT/Full 1000baseT/Full 1baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Advertised link modes: 100baseT/Full 1000baseT/Full 1baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Speed: 1Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: umbg Wake-on: g Current message level: 0x0007 (7) drv probe link Link detected: yes Note ethtool shows an active 10Gb link. The test tool determines the NIC speed by introspecting the sysfs data for each NIC port. In this case, by looking at /sys/class/net/DEVICENAME/speed I've now seen this on a couple different NICs using the ixgbe driver. The first port will properly show connected link speed in /sys/class/net/DEVICENAME/speed but the second port shows -1 in that file. Because of this, certification tests are failing because the tool believes that the link speed is incorrect. This current example is using kernel 4.13.0-37.42~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 install screen becomes blur on Huawei server Status in install-package package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server
Hey Mao, Is this visible after install? In other words can you install 16.04 on the failing system, then add the 4.15 kernel and boot into it? Once you do that, does the issue appear? Just to summarize where we are: 16.04, 4.13: No problem 18.04, 4.15: Problem with frame buffer 16.04, 4.15: ??? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 install screen becomes blur on Huawei server Status in install-package package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1331513] Re: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720
Closing this out, it hasn't been commented on in 3 years, is far older than that, and tg3 has been pretty heavily tested across many server makes in the years since. ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete ** Changed in: dell-poweredge Status: Triaged => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1331513 Title: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720 Status in The Dell-poweredge project: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: we have a problem with Dell PowerEdge machines, having the Broadcom 5720 chip. We have this problem on generation 12 systems, across different models (R420, R620), with several combinations of bios firmwares, lifecycle firmwares, etc... We see this on several versions of the linux kernel, ranging from 3.2.x up tot 3.11, with several versions of the tg3 driver, including a manually compiled latest version (3.133d) loaded in a 3.11. The latest machine, where we can reproduce the problem has Ubuntu Precise installed, but we also see this behaviour on Debian machines. We run Xen on it, running HVM hosts on it. Storage is handled over iSCSI (and it is the iSCSI interface we can trigger this bug on in a reproducible way, while we have the impression it also happens on other interfaces, but there we don't have a solid case where we have e reproducible setup). All this info actually points into the direction of the tg3 driver and/or hardware below it not handling certain datastreams or data patterns correctly, and finally crashing the system. It seems unrelated to the version of kernel running, xen-version running, amount of VM's running, firmwares and revisions running, etc... We have been trying to pinpoint this for over a year now, being unable to actually create a scenario where we could reproduce this. As of this week, we finally found a specific setup where we could trigger the error within a reasonable time. The error is triggered by running a certain VM on the Xen stack, and inside that VM, importing a mysqldump in a running mysql on that VM. The VM has it's traffic on an iSCSI volume, so this effectually generates a datastream over the eth1 interface of the machine. Within a short amount of time, the system will crash in 2 steps. We first see a timeout on the tg3 driver on the eth1 interface (dmesg output section attached). This sometimes repeats two or three times, and finally, step 2, the machine freezes and reboots. While debugging, we noticed that the bug goes away when we disable sg offloading with ethtool. If you need any additional info, feel free to ask. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.11.0-19-generic 3.11.0-19.33~precise1 ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Jun 18 16:36 seq crw-rw---T 1 root audio 116, 33 Jun 18 16:36 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Jun 18 16:47:27 2014 HibernationDevice: RESUME=UUID=f3577e02-64e3-4cab-b6e7-f30efa111565 InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) MachineType: Dell Inc. PowerEdge R420 MarkForUpload: True PciMultimedia: ProcFB: ProcKernelCmdLine: placeholder root=UUID=bbc71780-90bf-4647-b579-e48d5d8c2bce ro vga=0x317 RelatedPackageVersions: linux-restricted-modules-3.11.0-19-generic N/A linux-backports-modules-3.11.0-19-generic N/A linux-firmware 1.79.12 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux-lts-saucy UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.2 dmi.board.name: 0JD6X3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.2:bd01/20/2014:svnDellInc.:pnPowerEdgeR420:pvr:rvnDellInc.:rn0JD6X3:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R420 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1331513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubsc
[Kernel-packages] [Bug 1775486] [NEW] Bionic boot kernel oopses on Power
Public bug reported: I'm trying to deploy Bionic to a Power S822LC (8335-GTB). The install fails because the boot kernel throws some oopses and reboots the server in an endless loop. The system powers on. Petitboot loads and populates the boot options. The system PXE boots the ephemeral boot kernel and then OOPSes and reboots, starting the cycle over. The following is the most I could get from a SOL session but it does show where the panics begin and the reboot happens at the end. The dump is from an attempt via MAAS to deploy Xenial with the 4.15 edge kernel. I also tried Bionic using the default kernel and got the same issue. Next I tried Xenial with the 4.13 kernel (hwe-16.04) and that kernel successfully boots. So the issue seems localized to the 4.15 kernel. [2.561982] vgaarb: loaded [2.562036] usbcore: registered new interface driver usbfs [2.562256] usbcore: registered new interface driver hub [2.562652] usbcore: registered new device driver usb [2.562834] pps_core: LinuxPPS API ver. 1 registered [2.563307] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [2.589031] PTP clock support registered [2.589996] EDAC MC: Ver: 3.0.0 [2.590513] NetLabel: Initializing [2.590581] NetLabel: domain hash size = 128 [2.590613] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [2.591086] NetLabel: unlabeled traffic allowed by default [2.592541] clocksource: Switched to clocksource timebase [2.609779] VFS: Disk quotas dquot_6.6.0 [2.610031] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [2.613235] NET: Registered protocol family 2 [2.613651] TCP established hash table entries: 524288 (order: 6, 4194304 bytes) [2.614772] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) [2.619840] TCP: Hash tables configured (established 524288 bind 65536) [2.620414] UDP hash table entries: 65536 (order: 5, 2097152 bytes) [2.621044] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes) [2.622142] NET: Registered protocol family 1 [2.622284] pci 0009:00:00.0: enabling device (0101 -> 0103) [2.622425] pci 0009:01:00.0: enabling device (0141 -> 0143) [2.622915] pci 0009:02:01.0: enabling device (0141 -> 0143) [2.623432] pci 0009:03:00.0: enabling device (0140 -> 0142) [2.624048] Unpacking initramfs... [3.541638] Freeing initrd memory: 53248K [3.546247] Initialise system trusted keyrings [3.546398] Key type blacklist registered [3.546548] workingset: timestamp_bits=38 max_order=23 bucket_order=0 [3.548288] zbud: loaded [3.551021] squashfs: version 4.0 (2009/01/31) Phillip Lougher [3.551827] fuse init (API version 7.26) [3.554352] Key type asymmetric registered [3.554487] Asymmetric key parser 'x509' registered [3.554785] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244) [3.555088] io scheduler noop registered [3.555115] io scheduler deadline registered [3.10] io scheduler cfq registered (default) [3.557442] pci 0009:02:03.0: enabling device (0141 -> 0143) [3.557634] pci 0009:05:00.0: enabling device (0141 -> 0143) [3.557703] pci 0009:06:00.0: enabling device (0141 -> 0143) [3.557753] Using unsupported 1024x768 vga at 3fe28101, depth=32, pitch=4096 [3.691555] Console: switching to colour frame buffer device 128x48 [3.825001] fb0: Open Firmware frame buffer device on /pciex@3fffe4050/pci@0/pci@0/pci@3/pci@0/vga@0 [3.825359] hvc0: raw protocol on /ibm,opal/consoles/serial@0 (boot console) [3.825544] hvc0: No interrupts property, using OPAL event [3.825856] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [3.828204] Linux agpgart interface v0.103 [3.838817] loop: module loaded [3.839111] libphy: Fixed MDIO Bus: probed [3.839213] tun: Universal TUN/TAP device driver, 1.6 [3.839350] PPP generic driver version 2.4.2 [3.839446] VFIO - User Level meta-driver version: 0.3 [3.839587] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [3.839728] ehci-pci: EHCI PCI platform driver [3.839780] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [3.839825] ohci-pci: OHCI PCI platform driver [3.839898] uhci_hcd: USB Universal Host Controller Interface driver [3.840232] xhci_hcd 0009:03:00.0: xHCI Host Controller [3.840298] xhci_hcd 0009:03:00.0: new USB bus registered, assigned bus number 1 [3.840580] xhci_hcd 0009:03:00.0: Using 64-bit DMA iommu bypass [3.840830] xhci_hcd 0009:03:00.0: hcc params 0x0270f06d hci version 0x96 quirks 0x0400 [3.841395] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [3.841516] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [3.841570] usb usb1: Product: xHCI Host Controller [3.841746] usb usb1: Manufacturer: Linux 4.15.0-22-generic xhci-hcd [3.841790] usb usb1: SerialNumber: 0009:03:00.0 [3
[Kernel-packages] [Bug 1775486] Re: Bionic boot kernel oopses on Power
Unable to log collect as this happens in the ephemeral during boot and the system is not usable. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775486 Title: Bionic boot kernel oopses on Power Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to deploy Bionic to a Power S822LC (8335-GTB). The install fails because the boot kernel throws some oopses and reboots the server in an endless loop. The system powers on. Petitboot loads and populates the boot options. The system PXE boots the ephemeral boot kernel and then OOPSes and reboots, starting the cycle over. The following is the most I could get from a SOL session but it does show where the panics begin and the reboot happens at the end. The dump is from an attempt via MAAS to deploy Xenial with the 4.15 edge kernel. I also tried Bionic using the default kernel and got the same issue. Next I tried Xenial with the 4.13 kernel (hwe-16.04) and that kernel successfully boots. So the issue seems localized to the 4.15 kernel. [2.561982] vgaarb: loaded [2.562036] usbcore: registered new interface driver usbfs [2.562256] usbcore: registered new interface driver hub [2.562652] usbcore: registered new device driver usb [2.562834] pps_core: LinuxPPS API ver. 1 registered [2.563307] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [2.589031] PTP clock support registered [2.589996] EDAC MC: Ver: 3.0.0 [2.590513] NetLabel: Initializing [2.590581] NetLabel: domain hash size = 128 [2.590613] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [2.591086] NetLabel: unlabeled traffic allowed by default [2.592541] clocksource: Switched to clocksource timebase [2.609779] VFS: Disk quotas dquot_6.6.0 [2.610031] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [2.613235] NET: Registered protocol family 2 [2.613651] TCP established hash table entries: 524288 (order: 6, 4194304 bytes) [2.614772] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) [2.619840] TCP: Hash tables configured (established 524288 bind 65536) [2.620414] UDP hash table entries: 65536 (order: 5, 2097152 bytes) [2.621044] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes) [2.622142] NET: Registered protocol family 1 [2.622284] pci 0009:00:00.0: enabling device (0101 -> 0103) [2.622425] pci 0009:01:00.0: enabling device (0141 -> 0143) [2.622915] pci 0009:02:01.0: enabling device (0141 -> 0143) [2.623432] pci 0009:03:00.0: enabling device (0140 -> 0142) [2.624048] Unpacking initramfs... [3.541638] Freeing initrd memory: 53248K [3.546247] Initialise system trusted keyrings [3.546398] Key type blacklist registered [3.546548] workingset: timestamp_bits=38 max_order=23 bucket_order=0 [3.548288] zbud: loaded [3.551021] squashfs: version 4.0 (2009/01/31) Phillip Lougher [3.551827] fuse init (API version 7.26) [3.554352] Key type asymmetric registered [3.554487] Asymmetric key parser 'x509' registered [3.554785] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244) [3.555088] io scheduler noop registered [3.555115] io scheduler deadline registered [3.10] io scheduler cfq registered (default) [3.557442] pci 0009:02:03.0: enabling device (0141 -> 0143) [3.557634] pci 0009:05:00.0: enabling device (0141 -> 0143) [3.557703] pci 0009:06:00.0: enabling device (0141 -> 0143) [3.557753] Using unsupported 1024x768 vga at 3fe28101, depth=32, pitch=4096 [3.691555] Console: switching to colour frame buffer device 128x48 [3.825001] fb0: Open Firmware frame buffer device on /pciex@3fffe4050/pci@0/pci@0/pci@3/pci@0/vga@0 [3.825359] hvc0: raw protocol on /ibm,opal/consoles/serial@0 (boot console) [3.825544] hvc0: No interrupts property, using OPAL event [3.825856] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [3.828204] Linux agpgart interface v0.103 [3.838817] loop: module loaded [3.839111] libphy: Fixed MDIO Bus: probed [3.839213] tun: Universal TUN/TAP device driver, 1.6 [3.839350] PPP generic driver version 2.4.2 [3.839446] VFIO - User Level meta-driver version: 0.3 [3.839587] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [3.839728] ehci-pci: EHCI PCI platform driver [3.839780] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [3.839825] ohci-pci: OHCI PCI platform driver [3.839898] uhci_hcd: USB Universal Host Controller Interface driver [3.840232] xhci_hcd 0009:03:00.0: xHCI Host Controller [3.840298] xhci_
[Kernel-packages] [Bug 1775486] Re: Bionic boot kernel oopses on Power
Hi Joseph, I couldn't exactly reproduce this as it happens during deployment. BUT the closest I could get was deploying 16.04.4 (4.13) and then installing 4.17 once I was up and running. So I did that, and I am able to reboot the system into 4.17: ubuntu@fesenkov:~$ uname -a Linux fesenkov 4.17.0-041700-generic #201806041953 SMP Mon Jun 4 20:33:53 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ubuntu@fesenkov:~$ Next I installed linux-image-generic from Cosmic which got me a combination of 16.04.4 with 4.15 (4.15.0-22) and that is not bootable due to the OOPses that lead me to this bug. So this is the matrix of what's been tested: 16.04.4 - 4.13 - Success 16.04.4 - 4.15 - Fail 16.04.4 - 4.17 - Success So 16.04.5 and 18.04(.1) are broken on this system. ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775486 Title: Bionic boot kernel oopses on Power Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I'm trying to deploy Bionic to a Power S822LC (8335-GTB). The install fails because the boot kernel throws some oopses and reboots the server in an endless loop. The system powers on. Petitboot loads and populates the boot options. The system PXE boots the ephemeral boot kernel and then OOPSes and reboots, starting the cycle over. The following is the most I could get from a SOL session but it does show where the panics begin and the reboot happens at the end. The dump is from an attempt via MAAS to deploy Xenial with the 4.15 edge kernel. I also tried Bionic using the default kernel and got the same issue. Next I tried Xenial with the 4.13 kernel (hwe-16.04) and that kernel successfully boots. So the issue seems localized to the 4.15 kernel. [2.561982] vgaarb: loaded [2.562036] usbcore: registered new interface driver usbfs [2.562256] usbcore: registered new interface driver hub [2.562652] usbcore: registered new device driver usb [2.562834] pps_core: LinuxPPS API ver. 1 registered [2.563307] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [2.589031] PTP clock support registered [2.589996] EDAC MC: Ver: 3.0.0 [2.590513] NetLabel: Initializing [2.590581] NetLabel: domain hash size = 128 [2.590613] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [2.591086] NetLabel: unlabeled traffic allowed by default [2.592541] clocksource: Switched to clocksource timebase [2.609779] VFS: Disk quotas dquot_6.6.0 [2.610031] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [2.613235] NET: Registered protocol family 2 [2.613651] TCP established hash table entries: 524288 (order: 6, 4194304 bytes) [2.614772] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) [2.619840] TCP: Hash tables configured (established 524288 bind 65536) [2.620414] UDP hash table entries: 65536 (order: 5, 2097152 bytes) [2.621044] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes) [2.622142] NET: Registered protocol family 1 [2.622284] pci 0009:00:00.0: enabling device (0101 -> 0103) [2.622425] pci 0009:01:00.0: enabling device (0141 -> 0143) [2.622915] pci 0009:02:01.0: enabling device (0141 -> 0143) [2.623432] pci 0009:03:00.0: enabling device (0140 -> 0142) [2.624048] Unpacking initramfs... [3.541638] Freeing initrd memory: 53248K [3.546247] Initialise system trusted keyrings [3.546398] Key type blacklist registered [3.546548] workingset: timestamp_bits=38 max_order=23 bucket_order=0 [3.548288] zbud: loaded [3.551021] squashfs: version 4.0 (2009/01/31) Phillip Lougher [3.551827] fuse init (API version 7.26) [3.554352] Key type asymmetric registered [3.554487] Asymmetric key parser 'x509' registered [3.554785] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244) [3.555088] io scheduler noop registered [3.555115] io scheduler deadline registered [3.10] io scheduler cfq registered (default) [3.557442] pci 0009:02:03.0: enabling device (0141 -> 0143) [3.557634] pci 0009:05:00.0: enabling device (0141 -> 0143) [3.557703] pci 0009:06:00.0: enabling device (0141 -> 0143) [3.557753] Using unsupported 1024x768 vga at 3fe28101, depth=32, pitch=4096 [3.691555] Console: switching to colour frame buffer device 128x48 [3.825001] fb0: Open Firmware frame buffer device on /pciex@3fffe4050/pci@0/pci@0/pci@3/pci@0/vga@0 [3.825359] hvc0: raw protocol on /ibm,opal/consoles/serial@0 (boot console) [3.825544] hvc0: No interrupts property, using OPAL event [3.825856] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [3.828204]
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
** Summary changed: - Ubuntu 18.04 install screen becomes blur on Huawei server + Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767181] [NEW] Upgrade to Bionic and USB audio device no longer works
Public bug reported: I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop for conference calls, hangouts, etc. Yesterday (and ever since I bought the device) I was able to use this device for audio output and input on Xenial. Today, after upgrading to Bionic, I am no longer able to use the device. Plugging it in shows that it's recognized correctly when plugging it into a USB3 port (via dmesg): [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420 [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00 [14133.075895] usb 3-2.1.4: USB disconnect, device number 5 [14145.362837] usb 3-2.4: USB disconnect, device number 7 [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 [14240.079238] usb 3-2.1.3: USB disconnect, device number 8 [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 And it appears on the USB bus: bladernr@galactica:~$ lsusb Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510 Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub And when I open the sound settings (I am using Unity 7) the Jabra device appears as both an available input and output device. However, when I select it, and try a test sound, the output STILL comes out of the desktop's line-out and NOT the USB audio device. Likewise, on the Input tab, if I select the Jabra, no sound is detected when I speak. Thinking this might be because I'm using a USB hub, I disconnected the hub and plugged the device in directly to an onboard USB3 port but the problem persists. The device appears as an available output and input source, but sound does not come out of it (it still comes out the line- out despite the fact I have selected the USB device) and no sound is detected when testing the input side. I also plugged in a USB webcam that has a built in microphone, LIke the Jabra Speak 510, my USB webcam Microphone appears as an available input device and like the Jabra, no sound is detected when I select the webcam microphone. USB audio seems to be completely inoperative on Bionic. Looking at the Sound Settings menu, I notice that the title changes with each device I choose, however it does NOT change when I choose the USB devices. See attached screen shots for more info there. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 26 15:24:56 2018 InstallationDate: Installed on 2016-02-11 (805 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1767181 Title: Upgrade to Bionic and USB audio device no longer works Status in linux-signed package in Ubuntu: New Bug description: I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop for conference calls, hangouts, etc. Yesterday (and ever since I bought the device) I was able to use this device for audio output and in
[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works
In these three screen shots, note that the settings ONLY apply to the line-in device, even when I select the webcam mic and the Jabra Speak, the only settings options are for line-in. Both of these devices worked as input devices under Xenial. ** Attachment added: "sound-Jabra-Speak-input.png" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767181/+attachment/5127840/+files/sound-Jabra-Speak-input.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1767181 Title: Upgrade to Bionic and USB audio device no longer works Status in linux-signed package in Ubuntu: New Bug description: I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop for conference calls, hangouts, etc. Yesterday (and ever since I bought the device) I was able to use this device for audio output and input on Xenial. Today, after upgrading to Bionic, I am no longer able to use the device. Plugging it in shows that it's recognized correctly when plugging it into a USB3 port (via dmesg): [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420 [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00 [14133.075895] usb 3-2.1.4: USB disconnect, device number 5 [14145.362837] usb 3-2.4: USB disconnect, device number 7 [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 [14240.079238] usb 3-2.1.3: USB disconnect, device number 8 [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 And it appears on the USB bus: bladernr@galactica:~$ lsusb Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510 Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub And when I open the sound settings (I am using Unity 7) the Jabra device appears as both an available input and output device. However, when I select it, and try a test sound, the output STILL comes out of the desktop's line-out and NOT the USB audio device. Likewise, on the Input tab, if I select the Jabra, no sound is detected when I speak. Thinking this might be because I'm using a USB hub, I disconnected the hub and plugged the device in directly to an onboard USB3 port but the problem persists. The device appears as an available output and input source, but sound does not come out of it (it still comes out the line-out despite the fact I have selected the USB device) and no sound is detected when testing the input side. I also plugged in a USB webcam that has a built in microphone, LIke the Jabra Speak 510, my USB webcam Microphone appears as an available input device and like the Jabra, no sound is detected when I select the webcam microphone. USB audio seems to be completely inoperative on Bionic. Looking at the Sound Settings menu, I notice that the title changes with each device I choose, however it does NOT change when I choose the USB devices. See attached screen shots for more info there. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 26 15:24:56 2018 InstallationDate:
[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works
** Attachment added: "sound-line-out-output.png" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767181/+attachment/5127836/+files/sound-line-out-output.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1767181 Title: Upgrade to Bionic and USB audio device no longer works Status in linux-signed package in Ubuntu: New Bug description: I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop for conference calls, hangouts, etc. Yesterday (and ever since I bought the device) I was able to use this device for audio output and input on Xenial. Today, after upgrading to Bionic, I am no longer able to use the device. Plugging it in shows that it's recognized correctly when plugging it into a USB3 port (via dmesg): [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420 [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00 [14133.075895] usb 3-2.1.4: USB disconnect, device number 5 [14145.362837] usb 3-2.4: USB disconnect, device number 7 [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 [14240.079238] usb 3-2.1.3: USB disconnect, device number 8 [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 And it appears on the USB bus: bladernr@galactica:~$ lsusb Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510 Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub And when I open the sound settings (I am using Unity 7) the Jabra device appears as both an available input and output device. However, when I select it, and try a test sound, the output STILL comes out of the desktop's line-out and NOT the USB audio device. Likewise, on the Input tab, if I select the Jabra, no sound is detected when I speak. Thinking this might be because I'm using a USB hub, I disconnected the hub and plugged the device in directly to an onboard USB3 port but the problem persists. The device appears as an available output and input source, but sound does not come out of it (it still comes out the line-out despite the fact I have selected the USB device) and no sound is detected when testing the input side. I also plugged in a USB webcam that has a built in microphone, LIke the Jabra Speak 510, my USB webcam Microphone appears as an available input device and like the Jabra, no sound is detected when I select the webcam microphone. USB audio seems to be completely inoperative on Bionic. Looking at the Sound Settings menu, I notice that the title changes with each device I choose, however it does NOT change when I choose the USB devices. See attached screen shots for more info there. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 26 15:24:56 2018 InstallationDate: Installed on 2016-02-11 (805 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bu
[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works
Finally, I plugged a headset into the line-in/out jack on the motherboard and that does work for both input and output. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1767181 Title: Upgrade to Bionic and USB audio device no longer works Status in linux-signed package in Ubuntu: New Bug description: I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop for conference calls, hangouts, etc. Yesterday (and ever since I bought the device) I was able to use this device for audio output and input on Xenial. Today, after upgrading to Bionic, I am no longer able to use the device. Plugging it in shows that it's recognized correctly when plugging it into a USB3 port (via dmesg): [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420 [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00 [14133.075895] usb 3-2.1.4: USB disconnect, device number 5 [14145.362837] usb 3-2.4: USB disconnect, device number 7 [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 [14240.079238] usb 3-2.1.3: USB disconnect, device number 8 [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 And it appears on the USB bus: bladernr@galactica:~$ lsusb Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510 Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub And when I open the sound settings (I am using Unity 7) the Jabra device appears as both an available input and output device. However, when I select it, and try a test sound, the output STILL comes out of the desktop's line-out and NOT the USB audio device. Likewise, on the Input tab, if I select the Jabra, no sound is detected when I speak. Thinking this might be because I'm using a USB hub, I disconnected the hub and plugged the device in directly to an onboard USB3 port but the problem persists. The device appears as an available output and input source, but sound does not come out of it (it still comes out the line-out despite the fact I have selected the USB device) and no sound is detected when testing the input side. I also plugged in a USB webcam that has a built in microphone, LIke the Jabra Speak 510, my USB webcam Microphone appears as an available input device and like the Jabra, no sound is detected when I select the webcam microphone. USB audio seems to be completely inoperative on Bionic. Looking at the Sound Settings menu, I notice that the title changes with each device I choose, however it does NOT change when I choose the USB devices. See attached screen shots for more info there. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 26 15:24:56 2018 InstallationDate: Installed on 2016-02-11 (805 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lin
[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works
In the previous two screen shots, note that the Settings heading changes for each output device I choose, EXCEPT for the USB audio output device (as in this screenshot). ** Attachment added: "sound-Jabra-Speak-output.png" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767181/+attachment/5127837/+files/sound-Jabra-Speak-output.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1767181 Title: Upgrade to Bionic and USB audio device no longer works Status in linux-signed package in Ubuntu: New Bug description: I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop for conference calls, hangouts, etc. Yesterday (and ever since I bought the device) I was able to use this device for audio output and input on Xenial. Today, after upgrading to Bionic, I am no longer able to use the device. Plugging it in shows that it's recognized correctly when plugging it into a USB3 port (via dmesg): [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420 [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00 [14133.075895] usb 3-2.1.4: USB disconnect, device number 5 [14145.362837] usb 3-2.4: USB disconnect, device number 7 [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 [14240.079238] usb 3-2.1.3: USB disconnect, device number 8 [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 And it appears on the USB bus: bladernr@galactica:~$ lsusb Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510 Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub And when I open the sound settings (I am using Unity 7) the Jabra device appears as both an available input and output device. However, when I select it, and try a test sound, the output STILL comes out of the desktop's line-out and NOT the USB audio device. Likewise, on the Input tab, if I select the Jabra, no sound is detected when I speak. Thinking this might be because I'm using a USB hub, I disconnected the hub and plugged the device in directly to an onboard USB3 port but the problem persists. The device appears as an available output and input source, but sound does not come out of it (it still comes out the line-out despite the fact I have selected the USB device) and no sound is detected when testing the input side. I also plugged in a USB webcam that has a built in microphone, LIke the Jabra Speak 510, my USB webcam Microphone appears as an available input device and like the Jabra, no sound is detected when I select the webcam microphone. USB audio seems to be completely inoperative on Bionic. Looking at the Sound Settings menu, I notice that the title changes with each device I choose, however it does NOT change when I choose the USB devices. See attached screen shots for more info there. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 26 15:24:56 2018 InstallationDate: Installed on 2016-02-11 (805 days ago) InstallationMedia: Ubuntu 16.04
[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works
** Attachment added: "sound-line-in-input.png" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767181/+attachment/5127838/+files/sound-line-in-input.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1767181 Title: Upgrade to Bionic and USB audio device no longer works Status in linux-signed package in Ubuntu: New Bug description: I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop for conference calls, hangouts, etc. Yesterday (and ever since I bought the device) I was able to use this device for audio output and input on Xenial. Today, after upgrading to Bionic, I am no longer able to use the device. Plugging it in shows that it's recognized correctly when plugging it into a USB3 port (via dmesg): [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420 [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00 [14133.075895] usb 3-2.1.4: USB disconnect, device number 5 [14145.362837] usb 3-2.4: USB disconnect, device number 7 [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 [14240.079238] usb 3-2.1.3: USB disconnect, device number 8 [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420 [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00 And it appears on the USB bus: bladernr@galactica:~$ lsusb Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510 Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub And when I open the sound settings (I am using Unity 7) the Jabra device appears as both an available input and output device. However, when I select it, and try a test sound, the output STILL comes out of the desktop's line-out and NOT the USB audio device. Likewise, on the Input tab, if I select the Jabra, no sound is detected when I speak. Thinking this might be because I'm using a USB hub, I disconnected the hub and plugged the device in directly to an onboard USB3 port but the problem persists. The device appears as an available output and input source, but sound does not come out of it (it still comes out the line-out despite the fact I have selected the USB device) and no sound is detected when testing the input side. I also plugged in a USB webcam that has a built in microphone, LIke the Jabra Speak 510, my USB webcam Microphone appears as an available input device and like the Jabra, no sound is detected when I select the webcam microphone. USB audio seems to be completely inoperative on Bionic. Looking at the Sound Settings menu, I notice that the title changes with each device I choose, however it does NOT change when I choose the USB devices. See attached screen shots for more info there. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 26 15:24:56 2018 InstallationDate: Installed on 2016-02-11 (805 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go
