Public bug reported:
A hardware partner has been testing 18.04 subiquity images on their
servers with VROC enabled and configured in a RAID 10 setup.
In their own words:
Steps to reproduce:
1. Boot into VRoC controller in uEFI Setup and create a raid10 disk.
2. Install Ubuntu 18.04.5
The request was also for 5.4 which is why I had added that task. Is
Focal not possible? My apologies for any confusion there.
** Changed in: linux (Ubuntu Focal)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
OK, spoke with Microchip and it's OK to leave it as 5.11 HWE only for
20.04.3.
** Changed in: linux (Ubuntu Focal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933518
Hi Suganath, is there a reason why you re-opened this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863574
Title:
Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04
To manage notification
** Changed in: lvm2 (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887372
Title:
Cannot create lvm upon IMSM raid array
To manage notifications about
** Summary changed:
- [SRU] update ipmctl in Focal
+ [SRU] ipmctl in Focal does not work with Barlow Pass DCPMM hardware
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903204
Title:
[SRU] ipmctl in
** Description changed:
+ [IMPACT]
The ipmctl package in Focal needs to be updated to a newer version to support
Barlow Pass DCPMM
(new hardware enablement).
In Focal, the package supports only Apache Pass (ie, the first
generation of the hardware) -- but by now, Barlow Pass has been r
** Tags added: blocks-hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903204
Title:
[SRU] ipmctl in Focal does not work with Barlow Pass DCPMM hardware
To manage notifications about th
** Description changed:
[IMPACT]
The ipmctl package in Focal needs to be updated to a newer version to support
Barlow Pass DCPMM
(new hardware enablement).
In Focal, the package supports only Apache Pass (ie, the first
generation of the hardware) -- but by now, Barlow Pass has been r
Checking affected versions, this only applies to Focal:
ipmctl | 02.00.00.3709+ds-1 | focal/universe | source, amd64
ipmctl | 02.00.00.3774+ds-1 | groovy/universe | source, amd64
ipmctl | 02.00.00.3825+ds-1 | hirsute/universe | source, amd64
Groovy and Hirsute both have later versions that
** Tags added: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893661
Title:
Support for Intel VROC (Virtual RAID On CPU)
To manage notifications about this bug go to:
https://bugs.lau
** Tags added: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
[Focal] Installation Fails with "Invalid dep_id" when using Intel VROC
To manage notifications about this b
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: Opinion
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
--
You received this bug notification beca
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904848
Title:
Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib
** Tags added: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900668
Title:
MAAS PXE Boot stalls with grub 2.02
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Tag/Log Check - looks like the first patch is already in 5.8
d43b7007dbd1 -- Ubuntu-5.8.0-10.11 -- Wed Mar 18 21:44:32 2020 +0200
410bd754cd73 -- v5.10-rc1 -- Mon Aug 31 15:04:35 2020 +0300
1d5558b1f0de -- v5.10-rc1 -- Tue Jul 21 10:25:52 2020 +0300
50b2412b7e78 -- v5.10-rc1 -- Tue Aug 4 10:40:21
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) =
Public bug reported:
I noticed this in syslog while investigating an unrelated issue today.
I have Focal installed on a Fujitsu RX2530 M5 server with two Xeon Gold
6240 18c/36t CPUs installed. Every reboot results in the following MSR
stack trace:
Dec 3 17:34:31 nabbit kernel: [0.002463] sm
Marking Linux task invalid as this is not necessary for Hirsute or
Groovy.
Will work the Focal task now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905574
Title:
Ubuntu 20.10 four needed fixes
Double Checked and ALL these are in 5.8 already.
These are via this bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902130:
410bd754cd73
1d5558b1f0de
50b2412b7e78
432161ea26d6
and the other one appears directly in the kernel, so I guess that means
it was part of a sync from 5.8/5.9?
c
None of these cleanly pick into Focal. Deferring to Kernel team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905574
Title:
Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905574
Title:
Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Co
After discussion with the kernel team, we will not back port these to
5.4 at this time. There are varying degrees of backporting necessary to
get each patch from 5.8 into 5.4 and unfortunately there's no way to
schedule the work currently.
We can revisit this should there be customer demand, but
Quanxian, Pavel, Can these servers with VROC enabled/configured be
installed using MAAS (https://maas.io)?
For server, while we do have an ISO installer in Subiquity, any time we
do a deployment for customers the preferred method of managing and
deploying DC hardware is MAAS. MAAS deployments do
Has there been any movement on this? We get asked about Secure Boot in
MAAS periodically by various hardware partners.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865515
Title:
Chainbooting from
Public bug reported:
IN order to build ipxdimm_sw (LP: #1752378), there is a build dependency
on invm-frameworks. The source can be found here:
https://github.com/intel/invm-frameworks
>From the ipxdimm_sw page (https://github.com/intel/ixpdimm_sw):
Build
Linux
Kernel 4.12 or newer is suggeste
Hold off on this for now. It's not necessary currently to get the
NVDIMM support in, and there's a good chance this build dependency will
disappear soon anyway.
** Changed in: ubuntu
Importance: Undecided => Wishlist
** Summary changed:
- Please add package for invm-frameworks
+ [Feature] Pl
Testing:
I've tested only installation of the package.
Functional testing performed/validated by an engineer at Intel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760937
Title:
[Feature Freeze Ex
Changelog (Note, there is no CHANGES in the source prior to this release
(0.79 does not have this file)
** Attachment added: "CHANGELOG.md"
https://bugs.launchpad.net/ubuntu/+bug/1760937/+attachment/5100160/+files/CHANGELOG.md
--
You received this bug notification because you are a member of
Install Log:
Reading package lists...
Building dependency tree...
Reading state information...
The following package was automatically installed and is no longer required:
grub-pc-bin
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
libsgutils2-2
Sugg
Public bug reported:
Please update ledmon in Bionic to the latest upstream version 0.90.
Currently, ledmon in Bionic is version 0.79-2. This is pulled from
Debian[1] however the debian package is grossly out of date and the
Debian maintainer has been radio silent since last year. Attempts to
co
buildlog (built in a PPA)
** Attachment added:
"buildlog_ubuntu-bionic-amd64.ledmon_0.90-1_BUILDING.txt.gz"
https://bugs.launchpad.net/ubuntu/+bug/1760937/+attachment/5100159/+files/buildlog_ubuntu-bionic-amd64.ledmon_0.90-1_BUILDING.txt.gz
--
You received this bug notification because you
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/submiss
** Description changed:
Please update ledmon in Bionic to the latest upstream version 0.90.
+ 0.90 is necessary as the updates to ledmon enable monitoring of Intel
+ VROC[1] (Virtual Raid on CPU) and RSTe[2] (Rapid Storage Technologies
+ enterprise) by enabling the use of the drive LEDs to in
Public bug reported:
This was reported by a hardware partner. The system set up is a server
with 512GB RAM and an M.2 NVMe drive as the root filesystem/boot device.
Per the customer, when running the certification Memory Stress test
(utilizing several stress-ng stressors run in sequence) the sys
** Description changed:
This was reported by a hardware partner. The system set up is a server
with 512GB RAM and an M.2 NVMe drive as the root filesystem/boot device.
Per the customer, when running the certification Memory Stress test
(utilizing several stress-ng stressors run in sequ
How about the 4.4 kernel? And are they using a normal HDD/SSD for the
root filesystem, or are they using a NVMe of some sort?
I'm currently following another bug where the memory test fails reliably
when using an NVMe as the root filesystem but passes when a SSD or HDD
is used. In that case, 4.4
I added a nomination for Xenial, but that may not be the right way (I'm
not sure how to add a Xenial task like the Bionic task already added.
But this is a regression in as much as on Xenial this does not occur on
the 4.4 kernel but shows up at least in the 4.15 HWE kernel. For Bionic
it seems to
Assuming I did the git checkout correctly, these are all in 4.18 stable
under the v4.18.16 tag
0001-scsi-smartpqi-add-in-new-supported-controllers.patch
commit b0f9408b14838566b2a9b26434fab667c2afb0ea
No functionality change.
Add in more supported controllers.
0002-scsi-smartpqi-wor
Public bug reported:
When running iperf3 for sufficiently long times or or for sufficiently
large amounts of data transferred, the Transfer Summary shows NULL for
the amount of data transferred.
This seems to be triggered once you hit over 1 terabyte of data
transferred. It was described and fix
I was able to confirm/validate the failure on a set of LXC containers:
bladernr@xenial:~$ iperf3 -c 10.148.80.151 -i 60 -n 999G
Connecting to host 10.148.80.151, port 5201
[ 4] local 10.148.80.13 port 44408 connected to 10.148.80.151 port 5201
[ ID] Interval Transfer Bandwidth
This also affects bionic:
bladernr@xenial:/etc/apt/preferences.d$ iperf3 -c 10.148.80.151 -i 60 -n 1500G
Connecting to host 10.148.80.151, port 5201
[ 4] local 10.148.80.13 port 44836 connected to 10.148.80.151 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00
This is resolved in Cosmic:
bladernr@cosmic:~$ iperf3 -c 10.148.80.151 -n 1500G -i 60
Connecting to host 10.148.80.151, port 5201
[ 5] local 10.148.80.5 port 58834 connected to 10.148.80.151 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-60.00 sec 447 GB
Public bug reported:
I'm seeing a LOT of these messages appear, pretty much every minute or
so
Oct 10 08:11:05 galactica unity-panel-ser[27446]: gtk_icon_info_get_filename:
assertion 'icon_info != NULL' failed
Oct 10 08:11:05 galactica unity-panel-ser[27446]: g_object_unref: assertion
'G_IS_OBJ
moving to kernel itself rather than the hwe package
** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Can any of you recreate this using the mainline kernel?
https://wiki.ubuntu.com/Kernel/MainlineBuilds
that should at least give a point in time where we know either it's not
fixed in 4.18 or it IS fixed in 4.18 and the patches would be easier to
derive.
--
You received this bug notification bec
On Wed, Oct 10, 2018 at 9:20 AM Khurshid Alam
wrote:
>
> I can't reproduce this cosmic. Can you try reproduce this on cosmic?
> Also specify how to reproduce? IS it specific to a particular app ?
I am not currently able to try this with Cosmic. This is my primary
workstation and I don't want to g
Why is Xenial marked invalid? AFAIK this affects 4.15, but not 4.4,
which means Xenial HWE also has this regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798127
Title:
CPU Soft Lockups wh
distribution=ubuntu; distroseries=cosmic; sourcepackage=linux;
> component=main; status=Triaged; importance=High;
> assignee=joseph.salisb...@canonical.com;
> Launchpad-Bug-Tags: blocks-hwcert-server kernel-da-key kernel-fixed-upstream
> Launchpad-Bug-Information-Type: Public
> Launch
If it helps, also, again with the caveat that I'm doing this partially
for my own education, the above also matches what I found in the git
tree from kernel.ubuntu.com:
bladernr@galactica:~/development/git/ubuntu-kernel-git$ git checkout tags/v4.19
Previous HEAD position was 35a7f35ad1b1 Linux 4.1
Can you provide the versions of the checkbox packages by posting the
output of the following:
dpkg -l | grep checkbox
dpkg -l | grep plainbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676842
Tit
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798127
Title:
CPU Soft Lockups when stre
** Description changed:
ethtools report i40e as 10G instead the real 1G on Ubuntu 16.04.5 ga-
kernel
+
+ With the 4.4 driver, this device reports being a 10Gb device when looking at
ethtool:
+ Settings for enp61s0f0:
+ Supported ports: [ TP ]
+ Supported link modes: 1000baseT/
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808437
Title:
Unable to obtain an Emulex LPe35000 series adapter firmware d
Hi Talat. Have you built the current upstream version 0.7.3 and tried it
to verify that has the CX4 support?
I'm working a bit on this to see if I can get this bug rolling again,
but it would help to know for sure that the updated version does show
the info you need it to show.
I'll also try to t
** Changed in: linux-aws (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808437
Title:
Unable to obtain an Emulex LPe35000 series adapter firmware dump in
18.
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 notific
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863813
Title:
Focal Fossa (20.04) feature request - Cooper Lake
To manage notificat
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 sy
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864484
Title:
Update SmartPQI driver
=> 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 Ubuntu
Bugs, whi
** 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 cu
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
omain
[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 (bla
Out of curiosity, Are you using ipmctl and libsafec from Juston Li's
PPAs to do the configuration of the NVDIMMs?
https://launchpad.net/~jhli/+archive/ubuntu/ipmctl
https://launchpad.net/~jhli/+archive/ubuntu/libsafec
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi, so what are the chances that this will be fixed in 20.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843063
Title:
lshw -json output invalid in Eoan
To manage notifications about this bug g
Sam, can you provide a link to your git tree with these commits?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851446
Title:
Backport MPLS patches from 5.3 to 4.15
To manage notifications about th
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
http
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 membe
This isn't a backport request, it is targeted to Focal. AIUI the plan is
for debian to be updated to 0.94, then have that pulled into Focal by
Woodrow when it's ready. So added a Focal task and clarified the
subject a bit.
** Also affects: ledmon (Ubuntu Focal)
Importance: Wishlist
Stat
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
** 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
** 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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** 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
** 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 ~ Augu
** 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 ~ Augu
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 Ubuntu
Bugs,
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855303
Title:
Update Broadcom Emulex lpfc driver in Ubuntu 20.0
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 Ubuntu
Bugs, which is subscrib
** 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
Zesty and Yakkety no longer supported
** Changed in: zesty-backports
Status: New => Invalid
** Changed in: yakkety-backports
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Public bug reported:
[IMPACT]
Intel introduced NVDIMMs (Optane DCPMM devices) last year. Support for these
landed in Bionic prior to release, all except for the ipmctl tool which was not
ready for release at that time. Since then, ipmctl and libipmctl# have been
brought into Eoan and Focal.
Customer notified to test new kernels and verify the driver updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864484
Title:
Update SmartPQI driver in Focal to 1.2.10-025
To manage notificatio
** Description changed:
[IMPACT]
Intel introduced NVDIMMs (Optane DCPMM devices) last year. Support for these
landed in Bionic prior to release, all except for the ipmctl tool which was not
ready for release at that time. Since then, ipmctl and libipmctl# have been
brought into Eoan and F
- ndctl backport from Focal isn't really needed to build it (only a
debhelper version change)
ndctl itself, correct, is not necessary. the current bionic ndctl
package is fine. but package wise, from what I saw, libndctl6 (which I
presume is built from the ndctl source) is a required dependency f
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: U
ae41cf8 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
ow 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)
Stat
** 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:
a7441301
** 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 mo
** 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/1
** 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 w
** 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
d
led 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 ve
** 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 cu
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864484
Title:
Update SmartPQI driver in Focal to 1.2.10-025
To manage noti
/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 Fo
** 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 n
** Tags removed: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1089389
Title:
juju bootstrap fail behind a proxy when a gpg key must be imported
To manage notifications about this bug
401 - 500 of 3393 matches
Mail list logo
