On Fri, Mar 8, 2019 at 10:05 AM directhex wrote:
>
> @dannf this 4.18.0 HWE build works for me.
>
> builder@xam-taishan-4:~$ uname -a
> Linux xam-taishan-4 4.18.0-16-generic #17 SMP Thu Mar 7 21:31:17 UTC 2019
> aarch64 aarch64 aarch64 GNU/Linux
> builder@xam-taishan-4:~$ ping -c 1 8.8.8.8
>
@directhex: Would you mind also testing a build of the HWE kernel?
http://people.canonical.com/~dannf/lp1818294/hwe/
--
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/1818294
Title:
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubun
On Thu, Mar 7, 2019 at 1:20 PM directhex wrote:
>
> I am online with +xr320.3
>
> So the fix is c77804be53369dd4c15bfc376cf9b45948194cab ?
Apparently.
> The commit message doesn't make it _seem_ relevant, except for the
> reference to 2b3e88ea65287ba738a798622405b15344871085 which makes it
>
On Thu, Mar 7, 2019 at 7:45 AM directhex wrote:
>
> bisect 4.15.0-45.48+xr320.2 good
>
> So the fix is in one of 263c6d75f9a544a3c2f8f6a26de4f4808d8f59cf,
> bb989501abcafa0de5f18b0ec0ec459b5b817908 or
> c77804be53369dd4c15bfc376cf9b45948194cab
Thanks. I'll just hand build the rest to save time.
On Wed, Mar 6, 2019 at 1:10 PM directhex wrote:
>
> dmesg - the only difference from a "good" boot is the absence of "hns-
> nic HISI00C2:02 enahisic2i2: link up"
OK, thanks. Unfortunately, there's no smoking gun there, so I've
started a bisect and uploaded another test kernel to
On Wed, Mar 6, 2019 at 11:25 AM directhex wrote:
>
> I can't actually use `apport-collect` without an internet connection, of
> course, so can't use it when booted to a "bad" kernel
Could you save 'dmesg' output of the bad kernel to a file and upload
that once you reboot to working networking?
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => 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/1818747
Title:
Crash in nvme_irq_check() when using threaded
nassigned) => dann frazier (dannf)
--
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/1818747
Title:
Crash in nvme_irq_check() when using threaded interrupts
Status in linux package in U
the upstream change, which suggests it is not yet know to introduce regressions.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Triaged
** Changed in: linux (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: linux (Ubuntu Cosmic)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I don't think we yet know that one of the changes between 5.0-rc1 &
5.0-rc8 would fix this. It could be an issue with the backport, or a
change in a different subsystem. But, as a test, I went ahead and
backported the hns changes to a PPA:
https://launchpad.net/~dannf/+archive/ubuntu/xr320
If
nifest as a performance hit.
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in
Thanks for subscribing me. I'd like to get to the bottom of your
specific issue and get that addressed vs. dumping a bunch more patches
in and hoping it fixes it. To aide in that, can you provide additional
information about the issue? There should be an auto-update to this bug
soon that provides
Meanwhile, can you confirm whether or not this impacts the 4.18-based
HWE kernel in 18.04? See:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
On Fri, Mar 1, 2019 at 12:15 PM directhex wrote:
>
> Guess what! These changes... regressed my hardware.
Thanks for the report. Please provide a new bug report in which to
track these issues, and note the LP # here.
Also, please confirm that you are using the latest firmware for your device.
of Fixes: commits). Regressions could
manifest as a performance hit.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Confirmed
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Cosmic
: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Cosmic)
Importance: Undecided
[Regression Risk]
Change is restricted to a driver for a specific ARM server SoC, on which we've
directly regression tested.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf
** Changed in: linux (Ubuntu Xenial)
Status: New => 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/1817784
Title:
libsas disks can have non-unique by-path names
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: New
** Affects: linux (Ubuntu Bionic)
Importanc
Public bug reported:
[Impact]
The fix for LP: #1806766 has the issue that the persistent memory reservations
for the GICv3 LPI tables may have been allocated an overwritten by the time we
get to reserving them. This can continue to break kdump in certain conditions.
[Test Case]
sudo apt
These changes were committed after 4.19.0-12.13
** Changed in: linux-signed (Ubuntu Disco)
Status: Fix Released => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Kernel
** Bug watch added: Debian Bug tracker #891256
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891256
** Also affects: kexec-tools (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891256
Importance: Unknown
Status: Unknown
--
You received this bug notification
** 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/1813847
Title:
af-alg stressor triggers modprobe throttling
Verification: Tested both cosmic & bionic kernels using Ubuntu server
cert on D05 & D06 boards
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification because you are a member
Verified successful kdump on d05 (had to blacklist mlx drivers in
crashkernel to avoid OOM, but that is expected).
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is
cosmic verification:
ubuntu@d06-1:~$ cat /proc/version
Linux version 4.18.0-14-generic (buildd@bos02-arm64-012) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #15~18.04.1-Ubuntu SMP Mon Jan 14 11:12:31 UTC
2019
ubuntu@d06-1:~$ ls -l /dev/disk/by-path | cat
total 0
lrwxrwxrwx 1 root root 9
** Description changed:
[Impact]
The Intel IOMMU driver provides an option for strict mode. When disabled,
batching of IOTLB flush operations is permitted, allowing the user to trade-off
isolation for improved performance. Ubuntu's kernel currently lacks a parity
for this feature for ARM.
bionic: regression tested on a d05 system:
ubuntu@d05-3:~$ cat /proc/version
Linux version 4.15.0-44-generic (buildd@bos02-arm64-010) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #47-Ubuntu SMP Mon Jan 14 11:32:55 UTC 2019
ubuntu@d05-3:~$ ls -l /dev/disk/by-path | cat
total 0
lrwxrwxrwx 1
cosmic verification:
ubuntu@ubuntu:~$ cat /proc/version
Linux version 4.18.0-14-generic-lpae (buildd@bos02-arm64-040) (gcc version
8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #15-Ubuntu SMP Mon Jan 14 12:00:36 UTC 2019
bionic verification:
ubuntu@ubuntu:~$ cat /proc/version
Linux version
The most recent d-i for trusty was built w/ 3.13.0-110, so I'll go ahead
and mark fix released. I suspect, however, that this kernel still won't
boot on any modern OpenStack deployment, since the EFI firmware will
require ACPI support that was not available in 3.13.
** Changed in:
.
** Changed in: linux (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1810457
Title:
Update hisilicon SoC-specific drivers
Status in
Public bug reported:
[Impact]
Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active
development, including both hardware enablement and bug fix patches. With the
amount of flux involved, identifying and cherry-picking individual patches
would be more error prone then
** Changed in: linux (Ubuntu Bionic)
Status: New => 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/1806488
Title:
Support non-strict iommu mode on arm64
Status in
change was to allow for ACPI BGRT code, which isn't supported on 32-bit ARM.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu Cosmic)
Status: New => 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/1806488
Title:
Support non-strict iommu mode on arm64
Status in
** Description changed:
[Impact]
- There's a significant performance gain to be had by removing the need to
flush the IOMMU TLB on every unmap. I'm seeing a 25% performance gain w/ fio
reads on a single NVMe device. This mode of operation is available for x86 via
the "intel_iommu=strict"
on
a system w/ SAS connected disks.
[Fix]
437207d3697f5 scsi: libsas: check the ata device status by ata_dev_enabled()
[Regression Risk]
Clean cherry pick from upstream - any regressions will have upstream support.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier
Testing shows performance inline with the 4.18.0-11-generic kernel.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
No regression here (tested ubuntu-server daily on x86 VM)
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages,
le").
+
+ Risk mitigated by testing on both x86 ARM and EFI systems.
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Cosmic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassign
Public bug reported:
[Impact]
kdump support isn't usable on HiSilicon D05 systems. This previously worked in
bionic.
[Test Case]
sudo apt install linux-crashdump
echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT
crashkernel=512M"' | \
sudo tee /etc/default/grub.d/kdump-tools.cfg
[Regression Risk]
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: 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/180648
** Description changed:
[Impact]
Bug 1800664 introduced checksum offload and TSO support for HiNIC adapters.
While that did improve performance in short iperf runs, longer runs were later
found to show a significant regression in performance:
-
/1800664/comments/3
[Test Case]
iperf -c 192.168.99.1 -P5
[Fix]
Revert the offending patch.
[Regression Risk]
This is reverting a patch, returning the driver to 18.10 GA behavior.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status
hanged in: shim (Ubuntu Cosmic)
Status: New => Fix Released
** Changed in: shim (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => d
Public bug reported:
[Impact]
Ubuntu does not currently support SecureBoot for UEFI systems on arm64
platforms.
[Test Case]
See: https://wiki.ubuntu.com/UEFI/SecureBoot/Testing
[Fix]
- Introduce shim-signed for arm64
- Introduce grub-signed for arm64
- Produce signed linux kernels
[Regression
** Tags removed: verification-done-cosmic
** Tags added: verification-failed-cosmic
--
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/1800664
Title:
Add checksum offload and TSO support
Ike has since done some more extensive testing, and found that
performance actually *drops* with longer iperf runs. With a 900s run,
he's seeing it go down to ~200Mbps, while the kernel emits messages like
these:
[ 1070.047048] ITS queue timeout (65440 65504 1120)
[ 1070.051658] ITS cmd
Verified - see attached dmesg.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/bionic/+source/linux-snapdragon/+bug/1797092/+attachment/5214304/+files/dmesg
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug
** Changed in: linux (Ubuntu Cosmic)
Status: New => Fix Released
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Fix Released
** Changed in: linux-raspi2 (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: linux-raspi2 (Ubuntu Cosmic)
Status: New => Fix
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
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/1802023
Title:
hns3: map tx ring to tc
Status in
Smoke tested both bionic-proposed & cosmic-proposed.
** 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.
.
[Fix]
1c77215480bcf net: hns3: Set tx ring' tc info when netdev is up
[Regression Risk]
Restricted to a single driver, which has been tested on the target SoC.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux
** Summary changed:
- xenial guest on arm64 drops to busybux under openstack bionic-rocky
+ xenial guest on arm64 drops to busybox under openstack bionic-rocky
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
[Impact]
- on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail
to launch as they drop to the busybox prompt after booting.
+ on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail
to launch as they drop to the busybox
I'm not aware of any armhf hardware that has PCI and was supported by
the 4.4 kernel. Calxeda gear maybe - but that was never officially
released and I don't have access to it anyway.
I did regression test using the virt model in QEMU. System still boots, lspci
smoke tests OK:
ubuntu@ubuntu:~$
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Cosmic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status
Regression tested on ThunderX/X-Gene, which I believe were the only 2
arm64 servers supported by the 4.4 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/1797092
Title:
xenial
@ppisati: Would you be able to regression test this on armhf?
** Description changed:
- on openstack rocky-bionic (with patch, see 1771662), xenial guests will
- fail to launch as they drop to the busybox prompt after booting.
- However, bionic guests will build and launch successfully.
+
bionic verification:
ubuntu@d06-3:~$ cat /proc/version
Linux version 4.15.0-39-generic (buildd@bos02-arm64-010) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #42-Ubuntu SMP Tue Oct 23 15:43:48 UTC 2018
ubuntu@d06-3:~$ sudo ethtool -s enp125s0f2 speed 100 duplex half autoneg off
cosmic verification:
ubuntu@d06-3:~$ cat /proc/version
Linux version 4.18.0-11-generic (buildd@bos02-arm64-030) (gcc version 8.2.0
(Ubuntu 8.2.0-7ubuntu1)) #12-Ubuntu SMP Tue Oct 23 19:24:51 UTC 2018
ubuntu@d06-3:~$ sudo ethtool -s enp125s0f2 speed 100 duplex half autoneg off
ubuntu@d06-3:~$
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
** Changed in: debian-installer (Ubuntu)
Status: New => Fix Released
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Changed in: debian-installer (Ubuntu Bionic)
I've backported the necessary fixes and verified that the result does solve the
problem:
https://git.launchpad.net/~dannf/ubuntu/+source/linux/+git/linux?h=xenial-arm64-acpi-pci
That being said, the changes are not particularly isolated, so it will
require careful review and testing for
There was no v4.6-yakkety build for arm64, but v4.8 booted fine. I
further bisected this down to:
0cb0786bac159 ARM64: PCI: Support ACPI-based PCI host controller
Presumably nova in newer OpenStack releases has made changes to the
libvirt xml it generates that requires additional kernel support.
tly tested.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Verified - has survived several minutes of:
while :; do
sudo ethtool -s enahisic2i1 speed 1000 duplex full
sudo service systemd-networkd restart
sleep 5
sudo ethtool -s enahisic2i1 speed 10 duplex half
sudo service systemd-networkd restart
sleep 5
done
With ping/iperf still
** Description changed:
[Impact]
MSI-X configuration is hardcoded in the hns3 driver, but the actual
configuration may change across revisions. Query firmware for the MSI-X
offset/numbers instead.
[Test Case]
- Regression testing: Confirm that, on existing hardware, the same MSIs are
Verification (regression test only - we don't yet have the hw that
supports the feature):
ubuntu@d06-3:~$ cat /proc/version
Linux version 4.15.0-37-generic (buildd@bos02-arm64-015) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #40-Ubuntu SMP Tue Oct 2 15:36:22 UTC 2018
$ sudo ethtool -K
With 18.04 UEFI on x86, does passing the kernel parameter
"video=efifb:off" make a difference?
--
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
** Description changed:
[Impact]
Newer revisions of hns3 support toggling the rx-vlan-filter feature, but the
driver does not allow it.
[Test Case]
Currently the command:
- $ sudo strace ethtool -K rx-vlan-filter off
+ $ sudo ethtool -K rx-vlan-filter off
reports:
- Could
(Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
ecause it implements a
previously-unsupported feature. However, there are 2 changesets that refactor
reset code ahead that are required before the above fix, and that refactoring
has a risk of introducing a regression.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier
)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Attachment added: "fio"
https://bugs.launchpad.net/bugs/1794165/+attachme
: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned
Public bug reported:
[Impact]
If something goes wrong during phy initialization, the device may fail to come
up.
[Test Case]
I don't have a way to inject a FIS error, so this will be smoke tested for
regressions only.
Needs to be tested on both D05 and D06 systems, since it touches code on
]
Localized to a single driver, tested on the one SoC that includes this device.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dan
Public bug reported:
[Impact]
MSI-X configuration is hardcoded in the hns3 driver, but the actual
configuration may change across revisions. Query firmware for the MSI-X
offset/numbers instead.
[Test Case]
Regression testing: Confirm that, on existing hardware, the same MSIs are
allocated
Verified - ran this over an ssh connection over the hns3 nic:
ubuntu@d06-3:~$ cat /proc/version
Linux version 4.15.0-35-generic (buildd@bos02-arm64-013) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #38-Ubuntu SMP Wed Sep 12 10:35:16 UTC 2018
** Tags removed: verification-needed-bionic
**
I was able to successfully capture a kernel crash dump file from a
ThunderX-based Gigabyte R120.
** 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
signed) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
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/1792209
Title:
net: hns
Public bug reported:
[Impact]
If an admin uses ethtool to change the link speed or duplex setting while the
hardware is still processing packets, a hardware hang may result.
[Test Case]
While traffic is in-progress, use ethtool to change link speed/duplex.
[Fix]
Fixes have been applied
@Mao: correct, I do not observe screen blur in d-i on D05.
btw, note also bug 1780076
--
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
The smartpqi driver is included in the linux-modules deb. If you are
trying to build/use an out-of-tree smartpqi driver (which your taint
flags suggest), please be clear about that. It could quite likely be a
bug in that out-of-tree driver vs. a bug with Ubuntu.
--
You received this bug
This is definitely reproducible on a D05 (arm64) with 18.04 running
wayland, and the symptoms look identical. I re-tested with the 18.04.1
ISO and confirmed.
** Attachment added: "arm64-hisilicon-d05-18.04-blurry-syslog.txt"
** Attachment removed: "arm64-hisilicon-d05-18.04-blurry-screenshot.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5183108/+files/arm64-hisilicon-d05-18.04-blurry-screenshot.png
--
You received this bug notification because you are a member of Kernel
Packages,
In theory, you should *never* have an "ubuntu" entry in efibootmgr when
MAAS-deployed. I'm guessing this is a dup of the following bug, for which a fix
has not been backported to trusty:
https://bugs.launchpad.net/maas/+bug/1642298
--
You received this bug notification because you are a
As observed on x86, disabling wayland also avoids the problem on ARM.
--
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
This issue also occurs on arm64. Attached is a screenshot from a
HiSilicon D05 running 18.04.
Why would hibmc_drm be arm64-specific? It is the same PCI device
(19e5:1711), so shouldn't it use the same driver regardless of
architecture?
** Attachment added:
** Attachment added: "arm64-hisilicon-d05-18.04-blurry-syslog.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5183109/+files/arm64-hisilicon-d05-18.04-blurry-syslog.png
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Description changed:
[Impact]
On an APM Merlin (X-Gene2) board, the onboard 1G interface fails to
re-establish link when the interface is brought down and back up. Juju + MAAS
provider does this after every install (so to configure a bridge), making this
config unusable.
This was
Verification:
ubuntu@d06-3:~$ cat /proc/version
Linux version 4.15.0-34-generic (buildd@bos02-arm64-002) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #37-Ubuntu SMP Mon Aug 27 15:22:18 UTC 2018
ubuntu@d06-3:~$ lsmod | grep hinic
hinic 94208 0
ubuntu@d06-3:~$ grep eth
** Description changed:
[Impact]
Interfaces associated with Huawei "hinic" PCI adapters will not be assigned
predictable names[*] and instead remain using the kernel names (e.g. eth0).
This can lead to races where the interface names are not the same on every
boot. For example, in a system
701 - 800 of 1621 matches
Mail list logo
