** Attachment added: "sound-built-in-digital-output.png"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767181/+attachment/5127835/+files/sound-built-in-digital-output.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
** Attachment added: "sound-webcam-mic-input.png"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767181/+attachment/5127839/+files/sound-webcam-mic-input.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in
I also fired up alsamixer and again, the USB audio device is listed and
accessible but not usable for sound in or out.
--
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:
** Summary changed:
- Upgrade to Bionic and USB audio device no longer works
+ Upgrade to Bionic and USB audio devices no longer work
--
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/
Just to be sure, I logged out of Unity and logged into Gnome 3 and the
results are identical. NO USB audio device works.
--
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
OK, so I rebooted into 4.13.0-39 and as soon as I was logged in the USB
audio started working. So I thought maybe that indicated a regression
between 4.13 and 4.15. HOWEVER< I then rebooted again, into 4.15 once
more, and now I have audio in and out on the USB devices.
I'm not sure exactly why,
^^ I also note that the fix is in -24, so I'll re-confirm once that is
available via MAAS.
--
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/1773162
Title:
4.15.0-22-generic fails to boot o
Bionic is still completely uninstallable (via MAAS) because of this.
MAAS is booting (currently) 4.15.0-23 for Bionic deployments and the
oopese still occur sending the machine into a reboot loop.
https://paste.ubuntu.com/p/wwPFmMn4wt/
** Tags added: blocks-hwcert-server
--
You received this bu
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 Kernel
Packa
Tag change to verification-done-bionic per Laurie/Broadcom's update.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Has this been tested with Disco (19.04) or Cosmic (18.10)? IOW does
this issue with ndctl only exist in Bionic, or does it carry forward?
--
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/181
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
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 Kernel
Packages, which is subscribed to linux in Ub
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798127
Title:
CPU So
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
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
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
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => 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/1798127
Title:
CPU Soft Lock
** 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
** Changed in: checkbox
Status: New => 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/1817412
Ti
I don't believe this is a bug in Checkbox, checkbox can only use the
info that the kernel and system tools provide. This could be a driver
issue, or perhaps a cabling issue. Could you
A: verify the cables are plugged into the correct places and check via ethtool
what the connect speeds are for
** Tags added: 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/1810548
Title:
Samsung U.2 NVMe SM961/PM961 randomly will go missing under kernel
4.15
Status in lin
Hi Alec,
1: Please recreate this failure and then run 'apport-collect 1810548' as
requested, it will provide much more in the way of logs for this bug.
2: Is this applicable to ONLY this particular model NVMe or have you
seen this or can you recreate this on other models from this IHV, or
other N
Ahhh, I just now realized you added a note to the certificate that ANY
NVMe drive will cause this failure...
--
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/1810548
Title:
Samsung U.2 NVM
Following that, this sounds like the "Cant use NVMes as the Root File-
system" issue.
So does this only affect this model Samsung NVMe, or all Samsung NVMes
or ALL NVMes (including other makes)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Due to security cert work, we won't be able to get to this until next
week. I've got this on my list to test out on Monday.
--
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/1656112
Title:
ubuntu@fesenkov:~$ dpkg -l |grep qemu | awk '{print $2"\t\t"$3}'
ipxe-qemu 1.0.0+git-20150424.a25a16d-1ubuntu1
qemu-block-extra:ppc64el 1:2.5+dfsg-5ubuntu10.13
qemu-slof 20151103+dfsg-1ubuntu1
qemu-system 1:2.5+dfsg-5ubuntu10.13
qemu-system-arm
Additionally, as noted above, qemu-block-extra modules fail to load:
Failed to initialize module: /usr/lib/powerpc64le-linux-gnu/qemu/block-iscsi.so
Note: only modules from the same build can be loaded.
Failed to initialize module: /usr/lib/powerpc64le-linux-gnu/qemu/block-curl.so
Note: only modul
I've tested the updated qemu in proposed and it fails.
ubuntu@fesenkov:~$ sudo qemu-system-ppc64 -m 1024 -display none -nographic -net
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm
-machine pseries,usb=off -cpu host -drive
file=/home/ubuntu/xenial-server-cloudimg-
So I thought that was a bit weird, so look below:
First, I wanted to see what was installed:
ubuntu@fesenkov:~$ apt-cache policy qemu-system-ppc*
qemu-system-ppcemb:
Installed: (none)
Candidate: (none)
Version table:
qemu-system-ppc: ###this is what I had installed, and I'm not entirely sure
OK, THAT worked. Sorry for the worry. I have no idea why qemu-system-
ppc was skipped over when I upgraded everything, but I did retry and
indeed it does now pass the virt test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
Call it pebkac. It's possible I missed the package when I manually
updated the qemu-* packages.
--
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/1656112
Title:
Power S822LC (8335-GTB) fai
OK, I have a Firestone available, so I'm re-trying this with a cycle of
10 runs to see what happens. Currently using 16.04 w/ HWE-Edge (4.10)
** Changed in: plainbox-provider-checkbox
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: plainbox-provider-checkbox
M
** 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/1905574
Title:
Ubuntu 20.10 four needed fixes to 'Add driver for Mella
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member
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
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
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1905574
Title:
Ubuntu 20.10 four
None of these cleanly pick into Focal. Deferring to Kernel team.
--
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/1905574
Title:
Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox
** Changed in: linux (Ubuntu Focal)
Status: In Progress => 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/1905574
Title:
Ubuntu 20.10 four needed fixes to 'Add driver fo
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
Marked Groovy task as invalid. Patches are all in 5.5, and thus already
present in Groovy.
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Invalid
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because y
,
the version in 5.8 works, so that's the point to start patching.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Jeff Lane (bladernr)
Status: Confirmed
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Jeff Lane (bladernr)
Status:
** Description changed:
The latest Intel NIC based LOMs do not work fully on Focal.
These devices have 4 ports, but only two seem to work and this has been
seen on at least two different systems using LOMs based on this.
We've discovered via testing that while the i40e driver in 5.4
** 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/1893956
Title:
Intel NIC LOMs do not work on Focal
Status in l
branch for this bug:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1893956-update-i40e-intel-lom
** Description changed:
The latest Intel NIC based LOMs do not work fully on Focal.
These devices have 4 ports, but only two seem to work and this has been
seen o
** Tags added: 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/1893956
Title:
Intel NIC LOMs do not work on Focal
Status in linux package in Ubuntu:
Confirmed
Stat
** Description changed:
- The latest Intel NIC based LOMs do not work fully on Focal.
- These devices have 4 ports, but only two seem to work and this has been
- seen on at least two different systems using LOMs based on this.
+ Fix:
+ Testcase:
+
+ [IMPACT]
+ The latest Intel based
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: Confirmed
** 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.
ht
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Groovy)
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.
4, so some backport
+ work is necessary.
** Changed in: linux (Ubuntu Groovy)
Assignee: Jeff Lane (bladernr) => (unassigned)
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Confirmed
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => New
--
Yo
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Groovy)
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
** Description changed:
-
[IMPACT]
The latest Intel based LOMs do not work fully on Focal.
These devices have up to 4 ports, but only two seem to work and this has
been seen on at least two different systems using LOMs based on this.
We've discovered via testing that while the i40
** Summary changed:
- Intel NIC LOMs do not work on Focal
+ Intel x710 LOMs do not work on 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/1893956
Title:
Intel x710 LOMs do not wor
** Description changed:
[IMPACT]
The latest Intel based LOMs do not work fully on Focal.
These devices have up to 4 ports, but only two seem to work and this has
been seen on at least two different systems using LOMs based on this.
We've discovered via testing that while the i40e d
*** This bug is a duplicate of bug 1893956 ***
https://bugs.launchpad.net/bugs/1893956
** This bug is no longer a duplicate of bug 1887703
[Regression] 5.4 is not identifying all ports on Intel x710-TM4 10GbE
controller
** This bug has been marked a duplicate of bug 1893956
Intel x710 L
*** This bug is a duplicate of bug 1893956 ***
https://bugs.launchpad.net/bugs/1893956
** This bug has been marked a duplicate of bug 1893956
Intel x710 LOMs do not work on Focal
** Tags removed: blocks-hwcert-server
--
You received this bug notification because you are a member of Kerne
** Description changed:
[IMPACT]
- The latest Intel based LOMs do not work fully on Focal.
+ The Intel x710-TM4 is one of the latest 10GbE controllers from intel using
the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and
2x RJ-45. This card is enabled in 5.4 via the
** Description changed:
[IMPACT]
The Intel x710-TM4 is one of the latest 10GbE controllers from intel using
the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and
2x RJ-45. This card is enabled in 5.4 via the inbox version of the i40e driver,
and hwinfo does show bo
** Project changed: kernel-sru-workflow => linux (Ubuntu)
** Also affects: linux (Ubuntu Groovy)
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/
The commits are all in 5.9 except for the three that haven't been
accepted yet per Amir's comments.
--
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/1895947
Title:
backport tls-rx to ubunt
Marking this invalid. While I was working on it, it was already
resolved by an upstream sync and handled by this bug:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1893050
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Focal)
Status
** Changed in: linux (Ubuntu Groovy)
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/1895947
Title:
backport tls-rx to ubuntu 5.8
Status in linux p
Public bug reported:
Brodcom network drivers in 5.8 do not have a version string (even though
it is present in the source code) modinfo cannot return a driver
version.
In a vm I installed 20.04.1 and then installed
linux-image-generic-hwe-20.04-edge from the Groovy archive to get the 20.04.2
HW
for comparison, I checked drivers from Intel and they work:
bladernr@vm1:~$ uname -a
Linux vm1 5.8.0-20-generic #21-Ubuntu SMP Wed Sep 23 00:39:43 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
bladernr@vm1:~$ for x in e1000 e1000e e100 fm10k i40e iavf ice igb igbvf igc
ixgb; do echo "$x: `modinfo -F ve
What bugs could this possibly be missing? I filed this using apport in
the first place, and apport collected all the logs the hooks told it to,
didn't it?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kern
Talked to upstream and discovered this is by design on their end:
This is not a bug. The versions of all network drivers in the kernel
tree were removed around March 2020. The arbitrary version of each
driver was considered too arbitrary and not meaningful, so they were all
removed:
https://git.k
nce=Medium; assignee=jeffrey.l...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=focal;
> sourcepackage=linux; component=main; status=Fix Committed;
> importance=Medium; assignee=jeffrey.l...@canonical.com;
> Launchpad-Bug-Tags: blocks-hwcert-server verification-needed-f
** Changed in: linux (Ubuntu Focal)
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/1877270
Title:
Devlink - add RoCE disable ker
** Tags removed: id-5efdfe72b71cb74e0593587c
** 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/1883229
Title:
Ubuntu server installation on S3260M4 server fail
Waiting on Mellanox to report back on test kernels.
** Changed in: linux (Ubuntu Groovy)
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/b
Public bug reported:
The Intel x710-TM4 is one of the latest 10GbE controllers from intel
using the i40e driver. This particular 4 port comes in a 2x2
arrangement: 2x SFP+ and 2x RJ-45. This car is enabled in 5.4 via the
inbox version of the i40e driver, and hwinfo does show both sides of the
ca
*** This bug is a duplicate of bug 1887703 ***
https://bugs.launchpad.net/bugs/1887703
** This bug has been marked a duplicate of bug 1887703
5.4 is not identifying all ports on Intex x710-TM4 10GbE controller
--
You received this bug notification because you are a member of Kernel
Packag
Also, from syslog in the sosreport, looks like something bad happens
when the driver loads and the first two ports are probed:
Jul 15 15:18:05 usable-sloth kernel: [ 26.841704] i40e: Intel(R) Ethernet
Connection XL710 Network Driver - version 2.8.20-k
Jul 15 15:18:05 usable-sloth kernel: [ 26
>From the duplicate bug is a sosreport from the failing system:
** Attachment added: "sosreport-usable-sloth-1-2020-07-15-telgxfb.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887703/+attachment/5392990/+files/sosreport-usable-sloth-1-2020-07-15-telgxfb.tar.xz
--
You receive
All the necessary logs should be in the attached sosreport, if not, I
can ask them to also run apport-collect, but that seemed unnecessary.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Confirmed
** Summary c
Further update,
According to the engineer at SMC, they did try "18.04.3" (not sure if
that means 4.15, or 5.3, hopefully not 5.2) and all four ports did work
for them, so this appears to be a regression in the i40e driver.
I've asked him to provide more info about what kernels they have tried
spe
An additional update, according to the person who reported this to me,
the last known working kernel is 5.3:
$lsb-release -a
No LSB modules are available.
Distributor ID:Ubuntu
Description:Ubuntu 18.04.3 LTS
Release: 18.04
Codename:bionic
ubuntu@Server:~$ uname -
Tester updated i40e driver to version 2.11.29
and says that he can now see all four ports.
So that would mean there's a difference between the version in 5.3,
2.8.20 in focal (The broken version), and 2.11.29 from Intel which works
again.
** Summary changed:
- 5.4 is not identifying all ports o
https://downloadcenter.intel.com/download/24411/Intel-Network-Adapter-
Driver-for-PCIe-40-Gigabit-Ethernet-Network-Connections-Under-Linux-
The current driver from Intel can be found there and is known working.
--
You received this bug notification because you are a member of Kernel
Packages, wh
Asked them to start bisecting the driver versions from Intel to figure
out the earliest update that resolves 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/1887703
Title:
[Reg
.
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jeff La
** Description changed:
+ [IMPACT]
+
The Intel x710-TM4 is one of the latest 10GbE controllers from intel
using the i40e driver. This particular 4 port comes in a 2x2
arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4 via the
inbox version of the i40e driver, and hwinfo does
Test Kernels here:
https://kernel.ubuntu.com/~kmously/kernel-kmously-bc5bba9-bgA6
--
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/1887703
Title:
[Regression] 5.4 is not identifying all p
Per tester, the patched kernel does not resolve the issue.
At least we know the diff.
Also, did some bisecting with the Intel drivers upstream and this is the
earliest version where the card starts working again:
2.10.19.82
So it breaks sometime around 2.8.20 and then starts working again arou
** 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]
Per Amir at Mellanox:
The kernel has been tested and It is good to go
--
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
** 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]
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Jeff Lane (bladernr)
--
You received this bug notification because you are a
** Description changed:
- The bellow upstream commit fixes a bug in Ktls feature.
- It is applied cleanly above the ubuntu-focal tree and passed basic sanity
testing.
- We would like it to be backported ubuntu-focal
- Thanks,
- Amir
+ [IMPACT]
- commit 41b14fb8724d5a4b382a63cb4a1a61880347ccb8
Hi... Verification done. Thanks
** Tags removed: blocks-hwcert-server verification-needed-focal
** Tags added: verification-done-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/18939
** Tags added: 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/1898808
Title:
[maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut
Status in linux pa
Alec, Billy: are these the same MAAS environments you've previously used
to deploy 20.04 for other work, or have you rebuilt the MAAS
environments recently?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
** 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/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
udev
Status in c
101 - 200 of 692 matches
Mail list logo
