summary for workaround via kernel parameter to blocker loading:
modprobe.blacklist=hibmc_drm
**prevent load during install
To add "modprobe.blacklist=hibmc_drm" kernel parameter in grub when boot from
d-i iso (press ‘e’ key and then press F10 or ctrl+x ( those key was noticed on
the screen)
@Aaron Ma
I want to test your patch. But seems it would patch with error. I guess, the
new 18.04 source code have been change to:
list_add_tail(&vgadev->list, &vga_list);
instead of:
- list_add(&vgadev->list, &vga_list);
+ list_add_tail(&vgadev->list, &vga_list);
Does it mean
For #44 Aaron's suggested patch, it seems patch have been included after
4.15.0-46. The testing 18.04.2 iso with 4.15.0-48 kernel seems the
system would be hang on language selection after select install server
of grub screen. So it seems this hibmc_drm would caused another this
hang issues too.
T
For #44, in the following testing, if disable hibmc_drm loading, then it
works fine and would not be hang.
--
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
Public bug reported:
coping data get io error
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Started Availability of block devices.
[ 185.379378] kdump-tools[1695]: Starting kdump-tools: * running makedumpfile
-c -d 31 /proc/vmcore /var/crash/201912310519/dump-incomplete
Copying d
ubuntu@infra1:~$ sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:00 93.1G 0 loop
/var/lib/lxd/storage-pools/default
sda 8:00 1.1T 0 disk
├─sda1 8:10 512M 0 part /boot/efi
└─sda2
The screen also get blur after ubuntu 18.04 beta2 was installed by
legacy bios on Huawei server (VGA card is SM750 which was embedded in
Hi1710 iMBC chips). The ubuntu-destktop was installed by "apt-get
install ubuntu-desktop and init 5 to switch to x.
--
You received this bug notification becau
** Attachment added: "sos-report for Ubuntu 18.04 after ubuntu-desktop
installed. it also become screen blur after witch to x-window (init 5)."
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+attachment/5118756/+files/sosreport-2288Hv5-20180417044501.tar.xz
--
You rec
** Attachment added: "bure screen picture for 18.04 beta2 atfter switch to
x-window on Huawei server"
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+attachment/5118758/+files/creen_picture_for_blur.png
--
You received this bug notification because you are a member of
For Xenial ubuntu-deskto on Huawei server testing (UEFI), all kernel 4.4
(default) and 4.13 (hwe) and 4.15 (hwe-edge) works well (no screen
blur).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
** Attachment added: "screen shoot for xenial (16.04.4) with 4.15 kernel on
Huawei server (UEFI)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5119225/+files/xenial-4.15-kernel-gui.png
--
You received this bug notification because you are a member of Kernel
Packag
** Attachment added: "Test matrix for sceen blur on 16.04.4 with 4.4 4.13 4.15
kernel and 18.04"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5120230/+files/test-matrix-on-1604-1804.png
--
You received this bug notification because you are a member of Kernel
Packa
** Attachment added: "sos report for 16.04.04 with 4.15 kernel tesing (no
screen blur after enable x-window)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5120260/+files/sosreport-2288Hv5uefi16.04.44.15-20180417120113.tar.xz
--
You received this bug notification b
** Attachment added: "x-windows test matrix for 16.04.4 with kernel
4.4,4.13,4.15,4.17"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5123905/+files/blur-test0420.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
Today, Huawei side did x-window testing 16.04.04 in legacy BIOS model,
all 4.4,4.13(hwe),4.15(hwe-edge which as as 18.04), 4.17rc1 works fine
(no screen blur).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
The daily build is still use 4.15.0-20 kernel. It was expecting of
update and fix this blur problem. http://cdimage.ubuntu.com/ubuntu-
server/bionic/daily/20180625/bionic-server-amd64.iso
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
I just tested with /boot/vmlinuz-4.15.0-29-generic which from my laptop
( to replace install/vmlinuz with this file), it would be screen blur.
If I use 4.15.0-32-generic, blur would disappear.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
The 16.04.5 ga-kernel wouldn't be screen blur and their syslog are
enclosed.
** Attachment added: "syslog for 16.04.5 ga-kernel which are not screen blur"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5179080/+files/syslog-16045-noblur.txt
--
You received this bug
replace 18.04.1 with 4.15.0-29 kernel from my laptop (16.04) and it
would be screen blur too. The syslog are enclosed here. If I replacing
it with 4.15.0-32-generic from my laptop, it would not be screen bure on
language select screen, but the system seems hanged (died) in case I
can't switch to tt
The 18.04.1 ga-kernel (4.15.0-29) would be screen blur. The syslog are
enclosed too.
** Attachment added: "18.04.1 d-i install iso screen blur syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5179081/+files/syslog-180401-d-i-iso-blur.txt
--
You received this b
I test 16.04.5 ga-kernel would not be screen blur but the hwe-
kernel(4.15.0-29) which is same as 18.04.1 would become screen blur.
The 16.04.5 hwe (blur) syslog are enclosed.
** Attachment added: "16.04.5 hwe-kernel (4.15.0-29) is blur"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/17
In the screen blur kernel syslog, it show below error which 16.04.5 GA kernel
don't have this error:
...
Aug 21 10:25:50 kernel: [0.589408] ACPI Exception: Could not find/resolve
named package element: LNKA (20170831/dspkginit-381)
(repeated 942 lines)
...
--
You received this bug notificat
ACPI Exception have been reported here and it seems not related to
screen blur
https://bugzilla.kernel.org/show_bug.cgi?id=198167
** Bug watch added: Linux Kernel Bug Tracker #198167
https://bugzilla.kernel.org/show_bug.cgi?id=198167
--
You received this bug notification because you are a me
Tested with 18.04.1 Desktop, it wouldn't screen blur. The kernel log are
enclosed.
** Attachment added: "18.04.1 desktop install kernel log (no screen blur)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5181977/+files/kern.log-18.04.1-desktop-noblur.txt
--
You rec
Tested on 17.10 server d-i install, it would be screen blur too during
installation, the kernel is 4.13.0.
--
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
In case 18.04.1 server and destop iso use same kernel of v4.15.0-29 and
the GUI works fine on destop, so the kernel should not be blamed.
In 18.04.1 server installation, if I kill bterm process of below:
/usr/bin/bterm -f /lib/unifont.bgf -l C.UTF-i /lib/debian-installer/menu
Some blur picture wo
Huawei hisilicon team thought it might be caused by hibmc_drm which are
upstream and included in v4.10 kernel for their ARM64 server. It is right.
After disable this module by:
modprobe.blacklist=hibmc_drm
In the grub whiling booting iso. The install screen blur was disappeared.
--
You receiv
Hisilicon team said this driver (hibmc_drm) are only for arm64. For X86
architecture, it need to use default driver for this SM750.
It seems we incorrectly include this model in X86.
Hisicon team have plans to fix in upstream source code which to limit
this modules configure options only to arm64
For ISO of classic Debian installer (d-i), it would become screen blur
after kernel load and in the first screen of "select a langue"
--
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
** Attachment added: "This screen bure on UEFI model for 18.04 classic d-i
installer in the first installer screen of language select"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5141063/+files/uefi-di-screen-blur.png
--
You received this bug notification because
This bug seems related with 4.15.0-20, the test result on UEFI model for
different combination of 16.04, 18.04 and their kernel are below:
18.04(d-i not subiquity) with 4.13 kerel: no screen blur
18.04(d-i not subiquity) with 4.15.22 kerenl: no screen blur
16.04 with 4.15.
In #18, 4.13 should replaced with 4.4.0-116 which used by 16.04.4 ISO.
--
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 Hua
For #37 screen shot and #39. We found this wayland issues for 18.04 and
Huawei x86 server, but it seems no for 18.04.1. In my test, apt-get
install ubuntu-desktop and reboot works fine.
For #37 "Why would hibmc_drm be arm64-specific?", I guess it might
because vendors (sm750 vga) have already prov
For #37-#39
This screen blur issues during install are only happened on Huawei X86
server for 18.04 and 18.04.1 d-i iso. As I know, 18.04 and even 18.04.1
ARM64 iso works fine with this new hibmc-drm module for installation on
Hisilicon D05 board.
--
You received this bug notification because yo
Dann,
For the wanland issues, I understood it as comments in #15, that is:
Blur screen for GDM login was caused by wayland, it can be fix by force
to use Xorg in
/etc/gdm3/customer.conf to uncoment WaylandEnable=false
Is this right for your wanland issues on D05?
In 18.04, we fo
@AaronMa
Do you have docs for how to compile a new kernel. I can found below doc link
https://help.ubuntu.com/community/Kernel/Compile
But it seems a bit old.
The other difficult is how to get compile config from d-i iso kernel. I
found if I use a kernel from running/installed system to replace d
The log which collect via
apport-cli --save=/tmp/apport-log linux
** Attachment added: "apport-cli log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+attachment/5191267/+files/apport-log
--
You received this bug notification because you are a member of Kernel
Packages, which
@Guiherme
Firstly, thank you much to provide those inforamtion. I asked customer
to check on 4.15.0-34 with kernel parameter of "nvme_core.multipath=0",
it was reported the same ( nvme device name would be changed every
reboot).
** Attachment added: "nvme name mismatch screen shoot"
https://
Below image uses the Subiquity and it can be installed successfully. But after
install ubuntu-desktop, the login screen would become screen blur after reboot
or init 5, but it can be start by startx after init 3 in the terminal.
http://releases.ubuntu.com/18.04/ubuntu-18.04-live-server-amd64.iso
Blur screen for GDM login was caused by wayland, it can be fix by force
to use Xorg in /etc/gdm3/customer.conf to uncoment WaylandEnable=false
--
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
Public bug reported:
Below iso use new Subiquity (not d-i) and it would be fail without
correct internet connection in UEFI mode. After reboot it would show
error of "No boot device, please reboot system with manual operaton" in
Huawei server.
This issue can be produce by KVM with UEFI too. It wo
** Attachment added: "debug log for KVM UEFI model without internet access"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770585/+attachment/5137592/+files/subiquity-debug.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
--
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/1770585
Title:
18.04 installer would become failed in UEFI without Internet
connection
Status in linux package in Ubuntu:
New
Bug desc
** Attachment added: "Sos report on KVM UEFI testing"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770585/+attachment/5137665/+files/sosreport-ubuntu-server-20180511073713.tar.xz.md5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
This bug seems related with the kernel or 4.15.0-20 of d-i ISO. Please
refer to #18 for test results on different 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/1762940
Title:
Ub
The daily build is still use 4.15.0-20 kernel.
http://cdimage.ubuntu.com/ubuntu-server/bionic/daily/current/bionic-server-amd64.iso
Anyone can confirm that the 18.04.1 d-i install iso would update the
kernel.
--
You received this bug notification because you are a member of Kernel
Packages, whi
I have tested with 18.04.1 on Huawei FusionServer 2288 again. The screen
blure is same. The kernel of this iso have been update to
4.15.0-29-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
A good feedback from partner is "I just update Ubuntu kernel to v4.19
and Memory Stress can got pass result this time."
--
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/1796217
Title:
Quna
hi Guilherme,
The partner have tested both for 4.16.0 and 4.15.1 ( I guess it is newer than
4.15.0-34), it was reported that the issues is same. The 4.15.1 testing results
are as below:
zlmao@zlmao-T460s:~/tmp$ cat test_result.txt
uname -r
4.15.1-041501-generic
cat /proc/cmdline
BOOT_IMAGE=/bo
Public bug reported:
We are facing a problem during the certification test. System always
stop at below screen while memory stress. In the following re-producing,
kernel seems un-normal and it can’t capture above info into the syslog
or kernel log, but the console will show same warning as screen
** Attachment added: "sos report when issued showed on console"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+attachment/5197396/+files/sosreport-right-goblin-20181003095301.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
** Attachment added: "sos report when issued showed on console"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+attachment/5197397/+files/sosreport-right-goblin-20181003095301.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Public bug reported:
ethtools report i40e as 10G instead the real 1G on Ubuntu 16.04.5 ga-
kernel
** 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
sos-reports
** Attachment added: "sos reports"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802832/+attachment/5211663/+files/sosreport-R4900G3-20180930070440.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
Public bug reported:
On 20.04(focal) ga-kernel and 18.04 (hwe-kernel). To make.bcache would
fail as below if the back devices are large than 1024G ( 1025 would
fail, but not 1024 ).
[ 727.756453] bcache: register_bdev() error nvme12n1: cannot allocate memory
[ 727.756456] bcache: register_bcach
Also, 18.04 ga-kernel worked fine too.
** Description changed:
On 20.04(focal) ga-kernel and 18.04 (hwe-kernel). To make.bcache would
fail as below if the back devices are large than 1024G ( 1025 would
fail, but not 1024 ).
[ 727.756453] bcache: register_bdev() error nvme12n1: cannot
This max 1024G size applies to the 512byte sector, most NVME ssd can
change ( LBA format ) to 4K and the max limits will be 16T than.
--
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/1909518
The command example to change 512 sector to 4K for “Intel P4510 4.0TB
U.2 NVMe SSD”
ubuntu@prdhci01a:~$ sudo nvme id-ns /dev/nvme1 -n 1 -H |grep "LBA Format"
[3:0] : 0 Current LBA Format Selected
LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative
Performance: 0x2 Goo
For the 4K sectors, the max limits should be 8T then. (1024G*4096/512)
--
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/1909518
Title:
bcache register_bdev() error cannot allocate memory
Call traces for this bug on D05 for kernel 4.15.0-10-generic which
tested on 1 March 2018 on 18.04 daily build
** Attachment added: "Call traces for this bug on D05 for kernel
4.15.0-10-generic which tested on 1 March 2018 on 18.04 daily build"
https://bugs.launchpad.net/ubuntu/+source/linux/
Hawei team just tested and verified this bug on 4.15.0-10-generic kernel
on D05 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/1738334
Title:
hisilicon hibmc regression due to ea
For the newest upstream kernel of http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.14-rc2/linux-
image-4.14.0-041400rc2-generic_4.14.0-041400rc2.201709242031_amd64.deb.
The S4 test is same error.
tags:kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
Tested works well kernel are:
kernel 3.13.0-24-generic of 14.04
Kernel 3.13.0-031300-generic on 14.04 from
（http://kernel.ubuntu.com/~kernel-ppa/mainline/)
Tested was failed kernel are:
linux-image-4.4.0-93-generic of lasted 16.04.1
4.4.9-21-generic, 4.12.0-041200-generic,4.14.0-999-gene
The attach file of ap.bug is apport-cli report on 16.04.3 with kernel of
4.10.0-28-generic. This kernel have same issue for s4.
** Attachment added: "The attach file of ap.bug is apport-cli report on 16.04.3
with kernel of 4.10.0-28-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bu
ebruary, the HWE kernel will work
> with Xorg.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1738334/+subscriptions
>
--
Zhanglei Mao
Solutions Architect, Sales and Business Development
Canonical Group Ltd.
zhanglei@cano
4.1.demsg is from kernel 4.1 which works fine for s4 suspend.
** Attachment added: "4.1.dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718871/+attachment/4978138/+files/4.1.dmesg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
For different kernel on http://kernel.ubuntu.com/~kernel-ppa/mainline/
and test on Ubuntu 14.04.1. All version below 4.2 works fine for S4, the
kernel of 4.2, 4.3, 4.3 can't works for S4.
The 4.1 and 4.2 dmesg was attach.
** Attachment added: "4.2.dmesg"
https://bugs.launchpad.net/ubuntu/+sou
This patch need to merged and fixed for the release 16.04.04. The final
SRU4 windows is 8 Dec. to 6 Jan 2018.
--
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/1738334
Title:
hisilicon hibm
Notes and some more detail for this bug/patch:
The bug is from/caused by 4.12 DRM architecture, the main line commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.15-rc3&id=ea642c3216cb2a60d1c0e760ae47ee85c9c16447
It will cause x-window start hanged, the detail
This patch have been accepted to be merged in in kernel V4.16. Please
refer to: https://lkml.org/lkml/2017/12/25/24
--
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/1738334
Title:
hisilic
** Description changed:
The user upgrade Ubuntu server to linux-
image-4.10.0-26-generic_4.10.0-26.30_amd64.deb and it use a SSD of
ES3000 V2 SSD which the correspond module driver of hio.ko is include in
this kernel. The data write to disk seems was incorrect.
To format this sdd disk
It is Ubuntu server without Desktop environment and I can't provide my
launchpad access to customer too.
I will ask them to collect bug reports by:
apport-bug linux-image-4.10.0-26-generic_4.10.0-26.30_amd64.deb
I am not family for apport. Can apport-bug provide what you want?
--
You received
We found same problem on Ubuntu17.04 the kernel version is
linux-image-4.10.0-19-generic上. The apport report is in the attachment file.
We compared and testing on kernel 4.9 an 4.10， this HIO driver works fine on
4.9 but does not work
on kernel 4.10-rc5 and aboe.
** Attachment added: "Th
Huawei have fix this bug and provide patch to our team that will be
merged in 4.12.
--
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/1702253
Title:
hio.ko driver from linux-
image-4.10.
It was reported by Huawei by mail this was tested and verified. So I
change the tag to to 'verification-done-zesty'.
** Tags removed: kernel-da-key verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages,
Comments 25
> (https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/25
> )
> and 31 onwards detail this issue.
>
> [1] https://patchwork.ozlabs.org/patch/778054/
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+b
** Summary changed:
- 1 time ib_umda lloading fail during 105 power cycle
+ 1 time ib_umda loading fail during 105 power cycle
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2048
We tested on 20.4.5 iso ga-kernel and the lasted kernel of linux-
image-5.4.0-144-generic_5.4.0-144.161_amd64.deb and both them works too.
So this issues have been fixed both on 20.04 ga-kernel and hwe-kernel.
--
You received this bug notification because you are a member of Kernel
Packages, whi
Public bug reported:
On 22.04 with ga-5.15-generic kernel the lspci -vvv can get physical
slot info, but it works on 5.4.0 kernel of 20.4
** Affects: linux-hwe-5.15 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
the 5.15.0 kernel which can't show physical slot info
** Attachment added: "the 5.15.0 kernel which can't show physical slot info"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2012730/+attachment/5657260/+files/image003.png
--
You received this bug notification because you a
the 5.4.0 kernel which can show the physical slot info
** Attachment added: "the 5.4.0 kernel which can show the physical slot info"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2012730/+attachment/5657259/+files/image002.png
--
You received this bug notification because you
** Description changed:
- On 22.04 with ga-5.15-generic kernel the lspci -vvv can get physical
+ On 22.04 with ga-5.15-generic kernel the lspci -vvv can't get physical
slot info, but it works on 5.4.0 kernel of 20.4
--
You received this bug notification because you are a member of Kernel
Packa
Public bug reported:
A partner report below error which seems a fixed issue from upstream and
it affect NVME performance, hope to backport it.
Oct 27 06:05:17 quanta kernel: [ 1238.707245] AMD-Vi: Failed to allocate
IRTE
The related patch and discussion is below:
https://lkml.org/lkml/2020/10/1
Public bug reported:
On of our partner reported that FC680i internalLoopBack test would fail on
22.04 but worked fine on 20.04.5. The dmesg error log is
[ 941.140500] qla2xxx [:63:00.1]-701c:7: dma mapping resulted in different
sg counts, request_sg_cnt: 2 dma_request_sg_cnt: 1 reply_sg_cn
screen pictures for test commands and error output
** Attachment added: "image001.png"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2055238/+attachment/5749968/+files/image001.png
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
screen pictures for test commands and error output
** Attachment added: "image003.png"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2055238/+attachment/5749969/+files/image003.png
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
>From lspci
63:00.0 Fibre Channel [0c04]: QLogic Corp. ISP2722-based 16/32Gb Fibre Channel
to PCIe Adapter [1077:2261] (rev 01)
Subsystem: Hangzhou H3C Technologies Co., Ltd. NIC-FC680i-Mb-2x16G
[193d:100d]
Physical Slot: 9
63:00.1 Fibre Channel [0c04]: QLogic Corp. ISP2722-based
It seems specific to 5.15.0-25 version and have been fixed since
5.15.0-46-generic from 20.04.5 hwe-kernel and 5.15.0-97-generic (both
are tested and verified -- worked well)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 i
Public bug reported:
The partner report below syslog error related to:
Aug 30 09:10:48 localhost kernel: [7.335926] tegra186-gpio NVDA0508:00:
invalid resource
Aug 30 09:10:48 localhost kernel: [7.341446] tegra186-gpio NVDA0508:00:
invalid resource
Aug 30 09:10:48 localhost kernel: [
I was asked whether it relate to no actually device (LCD) connected and
could be safely ignored?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2045882
Title:
tegra-qspi NVDA1
For cycle is successful. The related log is
Dec 23 23:40:40 192-168-111-160 kernel: [0.00] Linux version
5.15.0-89-generic (buildd@bos03-amd64-016) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04)
11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #99-Ubuntu SMP Mon Oct 30
20:42:41 UTC 2023 (Ubuntu 5.15
Public bug reported:
found error log like below in 105 power cycles.
Dec 23 02:09:27 192-168-111-160 root[5747]: openibd: ERROR: Failed
loading kernel module ib_umad.
Dec 23 02:09:27 192-168-111-160 root[5750]: openibd: ERROR: Failed
loading kernel module ib_ipoib.
** Affects: linux-hwe-5.15 (U
Public bug reported:
SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux
version 5.4.0-109-generic", but it works on earlier version of " Linux
version 5.4.0-42-generic"
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug noti
For 5.4.0-109 kernel, if "rescan-scsi-bus" after plug in, it can find
disk.
--
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/1971576
Title:
SATA device hot plug regression on AMD EYPC (Asu
5. un-plugin sata disk; restart system
6. restart and boot into 5.4.0-109 kernel
7. login and monitor kernel log like sudo tail -f /var/log/syslog
8. plug in sata disk, there no similar log and no disk was found.
--
You received this bug notification because you are a member of Kernel
Packages,
reproduce method
1. On Ubuntu 20.04, install both 5.4.0-42 and 5.4.0-109 kernel
2. restart and boot into 5.4.0-42 kernel via grub menu
3. login and monitor kernel log like sudo tail -f /var/log/syslog
4. plug in sata disk, the log showed disk was dected like below:
---
May 4 05:5
Below is full sosreports of our test. Test and log please refer to last
2 boot (42 and 109 kernel)
May 4 05:49:11 rd1 kernel: [0.00] Linux version
5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu
9.3.0-10ubuntu2)) #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 (Ubuntu
5.4
more test as below:
5.11.0-27 hotplug works
5.13.0-40 hotplug doesn't work
--
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/1971576
Title:
SATA device hot plug regression on AMD EYPC (Asu
For Rome, it is the same as Melian which the 20.04.4 kernel
5.4.0-42-generic can work with hotplug, while kernel 5.4.0-109-generic
does't.
--
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/197
Partner have verified that 5.4.0-99 hotplug works, while 5.4.0-100
doesn't
--
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/1971576
Title:
SATA device hot plug regression on AMD EYPC (Asus
1 - 100 of 150 matches
Mail list logo
