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
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
** 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 adapt
** 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 firmw
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
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.
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 wh
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 laye
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:
** 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 ra
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 lar
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 yo
** 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
** 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 transf
** 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
** 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
** 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 happ
** 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 happ
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 s
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 i
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
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 de
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
Sta
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 40
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)
** 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
T
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 receiv
** 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 a
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 t
** 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
** 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 6d2
** 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
** 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 w
f1c5c9d10702c18a9d 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) =>
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
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
765ab6cd
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 i
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
@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 Kerne
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
Architectu
** 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 => 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
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1864484
Title:
Update Sm
=> 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
Pa
** 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
** 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 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
S
/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: 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 Plai
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.launchpa
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
** 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
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 prevent
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
Statu
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
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 notifi
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
Packa
** 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 i
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 subs
** 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
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 Kernel
Packages, which is subscribed to linux in U
** 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
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 pac
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
** 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 U
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.
h
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 Ubunt
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
T
** 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 Broa
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
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
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
** 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 Huaw
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: ???
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 F
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 ke
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:/
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
** 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://b
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 abl
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"
** 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 U
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:
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/+att
** 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 Ubunt
1 - 100 of 692 matches
Mail list logo
