[Bug 1911828] [NEW] Ubuntu 18.04.5/20.04 kernel doesn't have latest i40e driver for X710-T2L module

2021-01-14 Thread Zhanglei Mao
Public bug reported: Ubuntu 18.04.5/20.04 kernel doesn't have latest i40e driver for X710-T2L module,Please add the driver on next kernel version release. More details please refer to https://bugs.launchpad.net/quantatw/+bug/1905673 ** Affects: linux (Ubuntu) Importance: Undecided

[Bug 1909518] Re: bcache register_bdev() error cannot allocate memory

2020-12-29 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory To manage

[Bug 1909518] Re: bcache register_bdev() error cannot allocate memory

2020-12-29 Thread Zhanglei Mao
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

[Bug 1909518] Re: bcache register_bdev() error cannot allocate memory

2020-12-29 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title:

[Bug 1909518] Re: bcache register_bdev() error cannot allocate memory

2020-12-28 Thread Zhanglei Mao
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

[Bug 1909518] [NEW] bcache register_bdev() error cannot allocate memory

2020-12-28 Thread Zhanglei Mao
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:

[Bug 1877083] [NEW] qemu vnc console can only show "no suitable video mode" on taishan2280 server

2020-05-06 Thread Zhanglei Mao
Public bug reported: Qemu vnc console can only show "no suitable video mode" and nothing else both on opensack dashboard (vnc) or virt-manager. This was tested on Taishan2280 server (D05). Please see attached screen shoot. ** Affects: ubuntu Importance: Undecided Status: New --

[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server

2020-05-06 Thread Zhanglei Mao
The commend link for qemu which created by nova compute, the vcn parameter are: -vnc 0.0.0.0:0 -k en-us -device virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.5,addr=0x0 ubuntu@hc3:~$ ps auxww |grep -i qemu libvirt+ 1157628 3.6 0.1 5691124 737996 ? Sl 04:34 1:21 qemu-system-aarch64 -enable-kvm

[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server

2020-05-06 Thread Zhanglei Mao
For 18.04.2 ga-kernel of Linux hc3 4.15.0-47-generic, the CONFIG_DRM=y and CONFIG_DRM_VIRTIO_GPU=y seems already set. Test with drm virtio-gpu modules load, it seems same. I tested by delete instance via dashboard and create it again on the same hc3.maas host. For the virt-manager still display

[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server

2020-05-06 Thread Zhanglei Mao
>From the arm qemu wiki: https://wiki.qemu.org/Documentation/Platforms/ARM vns seems works and require as: virt machine graphics Graphics is also available, but unlike x86 there is no default display device enabled: you should select on from the Display devices section of "-device ?". One good

[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server

2020-05-06 Thread Zhanglei Mao
error screen picture ** Attachment added: "error screen picuture" https://bugs.launchpad.net/ubuntu/+bug/1877083/+attachment/5367295/+files/qemu-vnc-error-in-dashboard.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server

2020-05-06 Thread Zhanglei Mao
qemu error sceen shot via virt-manager ** Attachment added: "qemu error sceen shot via virt-manager" https://bugs.launchpad.net/ubuntu/+bug/1877083/+attachment/5367297/+files/qemu-vn-error-via-virt-manager.png -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server

2020-05-06 Thread Zhanglei Mao
the out put of "virsh dumpxml" ... ... This should be OpenStack configured for VNC and qemu devices. If I manual remove them, and the virt-manager can become normally which show grub menu, boot message and login etc. -- You received this bug

[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server

2020-05-06 Thread Zhanglei Mao
After add this to /etc/default/grub, ubuntu@test-2:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=0ba22f57-08ab-4b84-9592-936a48bd5692 ro console=tty0 quiet splash vt.handoff=1 ubuntu@test-2:~$ The issues is same which still show as "error: no suitalbe video mode

[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server

2020-03-26 Thread Zhanglei Mao
The kernel of Linux version 3.10.0-862.el7.x86_64 which didn't find issues. From the below log of "usb 1-1: Product: Keyboard Hub", it seems ubuntu new hwe kernel can't detected and support this usb hub of the keybaord. The full log about usb 1-1 are below: usb 1-1: new high-speed USB device

[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server

2020-03-26 Thread Zhanglei Mao
Compare the kernel related usb logs between keyboard detected and not, all previous logs are no difference, it began difference only from. I personally thought it might not issues from kernel as it likes external device (keyboad) didn't report devices information back and from testing log it sees

[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server

2020-03-26 Thread Zhanglei Mao
The boot which failed to detected keyboard are below: Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.688666] xhci_hcd :00:14.0: xHCI Host Controller Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.739684] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 1

[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server

2020-03-26 Thread Zhanglei Mao
The Quanta give me hits about error and it seems that in 68 reboot cycles there are 11 times which can't detected out the usb keyboard. $ grep 'Command line' kern.log |wc 68 952 12988 $ grep "usb1-port2: couldn't allocate usb_device" kern.log |wc 11 1321199 -- You

[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server

2020-03-26 Thread Zhanglei Mao
The boot with keyboard detected logs as below: Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.242592] hub 1-0:1.0: 16 ports detected Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.308359] probe of 1-0:1.0 returned 1 after 129930 usecs Feb 25 20:30:37 user-QuantaGrid-D52PL-4U

[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server

2020-03-26 Thread Zhanglei Mao
>From the kernel log, beside below errors, there are no errors for usb or keryboard, it also show correctly dectected keyboard for every reboot. $ grep -i error kern.log | tail -n5 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [4.321273] ERST: Error Record Serialization Table (ERST)

[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server

2020-03-26 Thread Zhanglei Mao
Also, it was said that this issues didn't found on rhel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869138 Title: The keyboard does not have responeded when boot system into Ubuntu 18.04.4

[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server

2020-03-26 Thread Zhanglei Mao
kernel log from testing ** Attachment added: "kernel.log" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+attachment/5341769/+files/log.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1869138] [NEW] The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server

2020-03-26 Thread Zhanglei Mao
Public bug reported: In Quanta server testing for 18.04.3 hwe-kernel 18.04.4 hwe-kernel and 20.04 daily build, it seems usb keyboard would: 1.Same OS would lost keybord and record usb usbx-portx: couldn't allocate usb_device log. 2.It is easy to reproduce the issue if add "open initcall debug"

[Bug 1864612] Re: requests ipmi-tool to include lasted patch for supporting quanta server

2020-02-26 Thread Zhanglei Mao
It was also tested that freeipmi tools of ipmiconsole and ipmipower cmd works fine with Quanta server as it is standard for ipmi. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864612 Title:

[Bug 1864612] Re: requests ipmi-tool to include lasted patch for supporting quanta server

2020-02-26 Thread Zhanglei Mao
Got feedback about what was fixed by the patch as below: New IPMITOOL QCT support OEM DIMM description as below, so customer can know which CPU/DIMM/slot Logged "Correctable ECC / SBE Warning Threshold (DIMM A0) - Asserted": ipmitool -U admin -P admin -H 10.10.12.21 raw 0xa 0x44 0x0 0x0 0x2 0x0

[Bug 1864612] [NEW] requests ipmi-tool to include lasted patch for supporting quanta server

2020-02-24 Thread Zhanglei Mao
Public bug reported: The existing ipmitool can't works for Quanta server as it didn't include lasted patches, even in 20.04. >From Quanta feedback that pmitools in 20.04 can work for quanta server if >apply this patch set:

[Bug 1862723] Re: 18.04 can't auto load ub_iverbs (18.04.3 hwe can) for Mellanox PMD nics

2020-02-10 Thread Zhanglei Mao
in 18.04 ga-kenrel, the mellanox nic PMD would fail. after manually load ib_uverbs, then it works fine. 2019-12-02T15:49:57.243Z|00306|netdev|WARN|dpdk-360bbd6: could not set configuration (Invalid argument) 2019-12-02T15:49:57.262Z|00307|dpdk|INFO|EAL: PCI device :3b:00.0 on NUMA socket 0

[Bug 1862723] [NEW] 18.04 can't auto load ub_iverbs (18.04.3 hwe can) for Mellanox PMD nics

2020-02-10 Thread Zhanglei Mao
Public bug reported: 18.04 ga-kernel to load ib_uverbs model which required by Mellanox PMD ( 18.04.3 hwe can auto load via model depends) ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1862722] Re: call trace during crash kernel boot on Huawei server for 18.04 ga-kernel

2020-02-10 Thread Zhanglei Mao
root@node1:~# dmesg |grep -i crash [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-72-generic root=UUID=d9281738-de5a-4564-852e-f07c29ea4817 ro default_hugepagesz=1GB hugepagesz=1GB hugepages=192 transparent_hugepage=never solcpus=4-13,32-41,18-27,46-55 console=tty0 console=ttyS0

[Bug 1862722] [NEW] call trace during crash kernel boot on Huawei server for 18.04 ga-kernel

2020-02-10 Thread Zhanglei Mao
Public bug reported: To configure kernel crash dump, if memory is less than 576M, it would get oom and to configure crashkernel=2G-:576M, it would get call trace. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member

[Bug 1862720] [NEW] kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel

2020-02-10 Thread Zhanglei Mao
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

[Bug 1862720] Re: kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel

2020-02-10 Thread Zhanglei Mao
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

[Bug 1860403] [NEW] fio call trace on xenial during ceph rbd testing

2020-01-20 Thread Zhanglei Mao
Public bug reported: During fio testing as below on 16.04 (xenial) hwe-kernel ( 4.15.0-55-generic), the below fio woluld get call trace or segment falut: /tmp/juju-exec53975/script.sh: line 1: 1104000 Segmentation fault (core dumped) fio --name=randread --ioengine=rbd --clientname=admin

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2019-05-16 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2019-05-16 Thread Zhanglei Mao
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.

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2019-05-14 Thread Zhanglei Mao
@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(>list, _list); instead of: - list_add(>list, _list); + list_add_tail(>list, _list); Does it mean this patch have been already merged

[Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed

2019-04-25 Thread Zhanglei Mao
One of IHV parnter get this issues too during stressapp + iperf testing. LP#1823615 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752091 Title: gvfsd-metadata[1703]: g_udev_device_has_property:

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2019-04-04 Thread Zhanglei Mao
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

[Bug 1594317] Re: Cannot start lxd-bridge.service when MAAS is managing DNS

2019-03-27 Thread Zhanglei Mao
to add floating ip too as: listen-on { 185.168.3.1; 185.168.3.5; }; -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594317 Title: Cannot start lxd-bridge.service when MAAS is managing DNS To manage

[Bug 1594317] Re: Cannot start lxd-bridge.service when MAAS is managing DNS

2019-03-27 Thread Zhanglei Mao
It seems not works on my side ( 18.04 ARM64). I have to add the listening IP explicitly. ubuntu@infra1:/etc/bind$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS" ubuntu@infra1:/etc/bind$ uname -a Linux infra1

[Bug 1815847] Re: 16.04 install would get "can't install busybox-initramfs" error with Chinese Language for install

2019-02-13 Thread Zhanglei Mao
** Attachment added: "screen shot for console message of the error" https://bugs.launchpad.net/ubuntu/+bug/1815847/+attachment/5238504/+files/16.04.05-Chines-Install-Error-Message.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1815847] [NEW] 16.04 install would get "can't install busybox-initramfs" error with Chinese Language for install

2019-02-13 Thread Zhanglei Mao
Public bug reported: This error was reported by Huawei when they install 16.04 with Chinese Language. I can re-produce it via KVM virtual machine with BIOS (not UEFI) option as: 1. Create new KVM VM with BIOS 2. Boot Ubuntu 16.04.5 server ISO to begin install 3. Select "Chinese Language" in the

[Bug 1815847] Re: 16.04 install would get "can't install busybox-initramfs" error with Chinese Language for install

2019-02-13 Thread Zhanglei Mao
This error would disappear if not Choose Chinese Language in first screen (F2 or grub manual screen). The UEFI boot would not provide this option choosing too. ** Attachment added: "first screen for Language choose"

[Bug 1815847] Re: 16.04 install would get "can't install busybox-initramfs" error with Chinese Language for install

2019-02-13 Thread Zhanglei Mao
** Attachment added: "screen shot for Installer error" https://bugs.launchpad.net/ubuntu/+bug/1815847/+attachment/5238503/+files/16.05.5-Chinese-Language-Insall-Error.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1802832] Re: ethtools report i40e as 10G instead the real 1G

2018-11-11 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1802832] [NEW] ethtools report i40e as 10G instead the real 1G

2018-11-11 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1796217] Re: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks"

2018-10-17 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796217 Title: Qunata server

[Bug 1796217] Re: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks"

2018-10-04 Thread Zhanglei Mao
** 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 Ubuntu Bugs, which is

[Bug 1796217] Re: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks"

2018-10-04 Thread Zhanglei Mao
** 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 Ubuntu Bugs, which is

[Bug 1796217] [NEW] Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks"

2018-10-04 Thread Zhanglei Mao
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

[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel

2018-09-27 Thread Zhanglei Mao
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

[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel

2018-09-25 Thread Zhanglei Mao
@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"

[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel

2018-09-20 Thread Zhanglei Mao
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 Ubuntu Bugs, which is

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-09-18 Thread Zhanglei Mao
@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

[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel

2018-09-15 Thread Zhanglei Mao
** Package changed: ubuntu => kernel-package (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot with 4.15.0 kernel To manage notifications about

[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel

2018-09-15 Thread Zhanglei Mao
** Attachment added: "match name in 4.4.0 kernel for /sys/class/nvme" https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5189362/+files/image004.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel

2018-09-15 Thread Zhanglei Mao
In the 4.15.0 kernel, a mismatch was found under /sys/class/nvme/, for example for the /sys/class/nvme/nvme1/, there is a of nvme3n1 directory which might be wrong. In 4.4 kernel, it is a matched directory of nvme1n1. Please refer to attach screen shot for more details. ** Attachment added:

[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel

2018-09-15 Thread Zhanglei Mao
In the 4.15.0 kernel, a mismatch was found under /sys/class/nvme/, for example for the /sys/class/nvme/nvme1/, there is a of nvme3n1 directory which might be wrong. In 4.4 kernel, it is a matched directory of nvme1n1. Please refer to attach screen shot for more details. ** Attachment added:

[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel

2018-09-15 Thread Zhanglei Mao
** Attachment added: "match name in 4.4.0 kernel for /sys/class/nvme" https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5189361/+files/image004.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel

2018-09-15 Thread Zhanglei Mao
** Summary changed: - nvme name floated after boot in Ubuntu 18.04 + nvme name floated after boot with 4.15.0 kernel ** Description changed: nvme device name such as /dev/nvme?n?p? would be floated that is symbol - link to different real ssd device after reboot in 4.15.0 kernel. + link to

[Bug 1792660] Re: nvme name floated after boot in Ubuntu 18.04

2018-09-14 Thread Zhanglei Mao
** Attachment added: "dmesg before" https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5188979/+files/dmesg_before -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name

[Bug 1792660] Re: nvme name floated after boot in Ubuntu 18.04

2018-09-14 Thread Zhanglei Mao
** Attachment added: "dmegs after" https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5188978/+files/dmesg_after -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name

[Bug 1792660] Re: nvme name floated after boot in Ubuntu 18.04

2018-09-14 Thread Zhanglei Mao
It is also found on 16.04.5 hwe kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot in Ubuntu 18.04 To manage notifications about this bug go to:

[Bug 1792660] Re: nvme name floated after boot in Ubuntu 18.04

2018-09-14 Thread Zhanglei Mao
It was found on v4.15.0 kernel and not for v4.4 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot in Ubuntu 18.04 To manage notifications about this

[Bug 1792660] [NEW] nvme name floated after boot in Ubuntu 18.04

2018-09-14 Thread Zhanglei Mao
Public bug reported: nvme device name such as /dev/nvme?n?p? would be floated that is symbol link to different real ssd device after reboot in 4.15.0 kernel. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-09-05 Thread Zhanglei Mao
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

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-09-04 Thread Zhanglei Mao
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

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-09-04 Thread Zhanglei Mao
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

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-08-31 Thread Zhanglei Mao
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

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-08-30 Thread Zhanglei Mao
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

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-08-29 Thread Zhanglei Mao
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

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-08-28 Thread Zhanglei Mao
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

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-08-28 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-08-23 Thread Zhanglei Mao
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

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-08-23 Thread Zhanglei Mao
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

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-08-22 Thread Zhanglei Mao
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"

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-08-22 Thread Zhanglei Mao
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

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-08-22 Thread Zhanglei Mao
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

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-08-22 Thread Zhanglei Mao
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

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-08-21 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-08-13 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-07-17 Thread Zhanglei Mao
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 Ubuntu Bugs, which

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-07-17 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-06-25 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-05-23 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-05-22 Thread Zhanglei Mao
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

[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-05-17 Thread Zhanglei Mao
** 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

[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-05-17 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title:

[Bug 1770585] Re: 18.04 installer would become failed in UEFI without Internet connection

2018-05-13 Thread Zhanglei Mao
*** This bug is a duplicate of bug 1750819 *** https://bugs.launchpad.net/bugs/1750819 If I change UEIF to BIOS for my local VM (kvm) then it can be installed successfully after I configure an IP without actually internet access. But if I use UEFI, the install would failed and can't boot into

[Bug 1770585] Re: 18.04 installer would become failed in UEFI without Internet connection

2018-05-11 Thread Zhanglei Mao
** 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 Ubuntu Bugs, which is subscribed

[Bug 1770585] [NEW] 18.04 installer would become failed in UEFI without Internet connection

2018-05-11 Thread Zhanglei Mao
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

[Bug 1770585] Re: 18.04 installer would become failed in UEFI without Internet connection

2018-05-11 Thread Zhanglei Mao
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770585 Title: 18.04 installer would become failed in UEFI without Internet connection To manage notifications about this bug go to:

[Bug 1770585] Re: 18.04 installer would become failed in UEFI without Internet connection

2018-05-11 Thread Zhanglei Mao
** 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 Ubuntu Bugs, which is subscribed to

[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-05-10 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762940

[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-05-06 Thread Zhanglei Mao
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.

[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-04-20 Thread Zhanglei Mao
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 Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-04-20 Thread Zhanglei Mao
** 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 Ubuntu Bugs, which is

[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-04-17 Thread Zhanglei Mao
** 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

[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-04-17 Thread Zhanglei Mao
** 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 Ubuntu

[Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-04-17 Thread Zhanglei Mao
** 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 Ubuntu Bugs,

  1   2   >