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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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 Ubuntu
Bugs, which is
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 Ubuntu
Bugs, which is
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
** Summary changed:
- AMD /proc/iomme 0-0xf2ff is incorrectly reserved
+ AMD cpu (/proc/iomme 0-0xf2ff) is incorrectly reserved
** Summary changed:
- AMD cpu (/proc/iomme 0-0xf2ff) is incorrectly reserved
+ AMD cpu (/proc/iomme 0-0xf2ff) is incorrectly reserved on 22.04
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:
Broken one:
cat proc/iomem
-f2ff : Reserved
-e1ff : Reserved
-d6ff : Reserved
-cbff : Reserved
Good one:
-0fff : Reserved
1000-0009 : System RAM
000a-000b : PCI Bus :60
000a-000b : Reserved
The CPU is below:
processor : 0
vendor_id : AuthenticAMD
cpu family : 25
model : 17
model name : AMD Eng Sample: 100-00894-04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
During kdump verify on Ubuntu 22.04 ga-kernel 5.15.0, kdump would fail
beause 0-0xf2ff(0-3.79G) have been reserved.
It seems have been fixed on Ubuntu 22.04.2 HWE-kernel of
5.19.0-32-generic.
** Affects: ubuntu
Importance: Undecided
Status: New
--
You
It seems very similar to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882478/ which have
been fixed on Bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976511
Title:
kernel taint (
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976511
Title:
kernel taint ( warning ) caused by smpboot.c: on 5.4.0
To manage
You can find above message in kernel.log file.
** Attachment added: "sosreport"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+attachment/5594318/+files/sosreport-G292-280-18.04HWE5.4.0-110-generic-2022-05-25-cvumffx.tar.xz
--
You received this bug notification because you
We didn't find this on Ubuntu 20.04.4 LTS hwe-kernel (
5.13.0-41-generic).
Both Ubuntu 20.04.4 ga-kernel and 18.04.6 hwe-kernel (5.4.0-107-generic)
are found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Apr 6 02:33:31 G292-280 kernel: [0.007531] [ cut here
]
Apr 6 02:33:31 G292-280 kernel: [0.007531] sched: CPU #20's llc-sibling
CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency.
Apr 6 02:33:31 G292-280 kernel: [
@Alberto Thanks for help. Below is log file.
** Attachment added: "mass deploy log file"
https://bugs.launchpad.net/maas/+bug/1975922/+attachment/5593944/+files/messages-0531.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The MAAS version is 3.1.0 (installed by sanp)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975922
Title:
custom image deploy get failed in cmd-curthooks of
DISTROS[DISTROS.index(distname)]
To
To summary
#1 Symptom:
On AMD EPYC, ROME server platform, SATA hot plug not working on Ubuntu 22.04
LTS.
#2 Root cause:
Ubuntu kernel compile with configure CONFIG_SATA_MOBILE_LPM_POLICY=3. During
devices scan ( boot, pci scan, ahci driver load), if didn't detected any valid
@Mario, May I ask you another 2 extending questions.
A. What is results in a AMD client( like laptop)? I thought this hot plug
works out of box in client, what cause this difference from kernel/code?
B. I was told that hot plug works out of box on their Intel's server.
What cause this
@Mario, Thanks for those deep and detail analyse for the root cause.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
SATA device hot plug regression on AMD EPYC (Asus) server
To
Hi Mario,
The test results for 5.18.0-4 are below:
Kernel parameters sata hot plug works or not
default No
hci.mobile_lpm_policy=0 Yes
hci.mobile_lpm_policy=1 Yes
hci.mobile_lpm_policy=2 Yes
By the way, what is
For #40, trace data for hotplug not working
** Attachment added: "trace-no-hotplug.zip"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+attachment/5591529/+files/trace-no-hotplug.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For #39, Marios's，partner said all fails ( hotplug was not working).
I guess we were expected it can work. So I will check him if he set
kernel parameter correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For #40, I asked them to collect trace data on both hotplug working and
not.
** Attachment added: "trace-hotplug.zip"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+attachment/5591527/+files/trace-hotplug.zip
--
You received this bug notification because you are a member of
Hey Haled, Mario,
Both 5.15 and 5.18 are failed, kernel were from (Khaled's) #37 building.
"uname -r "output from screenshots are:
5.15.0-32-generic
5.18.0-4-generic
thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Kahled, For Mario's comments#33, will you or can you build a main
kernel (v5.16) for testing? //thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
SATA device hot plug
Hello Kahled,
First, thanks for your effort to find this root cause in a short time.
For your comment #31, parnter has confirmed it is same for other type of disk.
I also asked them to raise this issue to AMD and AMD technical guy
reply below.
"Yes, 1022:7901h is AMD SATA AHCI
Hello Khaled, the Version 3007 failed. thanks！ //Mao
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
SATA device hot plug regression on AMD EPYC (Asus) server
To manage notifications
Hello Khaled, the 3006 kernel can pass. thanks //Mao
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
SATA device hot plug regression on AMD EPYC (Asus) server
To manage notifications
Hello Khaled, Version 3005 hot plug fail. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
SATA device hot plug regression on AMD EPYC (Asus) server
To manage notifications
Hello Kahled, Version 3004 hot plug can pass. thanks //Mao
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
SATA device hot plug regression on AMD EPYC (Asus) server
To manage
Hello Kahled, Version 3003 hot plug passed. //thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
SATA device hot plug regression on AMD EPYC (Asus) server
To manage notifications
Hello Kahled, thanks for quick response. Your understanding for 3000 bug
and 3002 no bug is correct. I have asked them to verify 3003 now.
//thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Khaled, Version 3002 hot plug can pass. //thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
SATA device hot plug regression on AMD EPYC (Asus) server
To manage
Hello Khaled, thanks for share detail information for your patching and
explains of unable building mulit-kernel.
The partner engineer did use 3000 kernel for sata hotplug test as they
sent me a screenshot of "uname -r" output.
I have asked them to test new 3002 kernel now.
--
You received
Hello Khale, hot plug test is fail for this version kernel. Please build
next kernel. By the way, if it possible to build multi kernel, so that
they can test them all in one shot. You know, the partner engineer is
working on home this week and he have to look for someone else on office
each time.
Hello Khaled, I have asked partner engineer to test your build kernel.
thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
SATA device hot plug regression on AMD EPYC (Asus) server
** Summary changed:
- SATA device hot plug regression on AMD EYPC (Asus) server
+ SATA device hot plug regression on AMD EPYC (Asus) server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Test it as boot int OS with selected 99 kernel, insert SATA and remove
SATA, run sosreport.
** Attachment added: "sosrport for 5.4.0-99 kernel which hotplug does work"
Test it as boot int OS with selected 100 kernle, insert SATA and remove
SATA, run sosreport.
** Attachment added: "sosrport for 5.4.0-100 kernel which hotplug doesn't work"
I was told the test are boot into OS with select kernel, insert sata,
remove, and run sosreport. Below is syslog info related to boot and sdb
or sdc.
--sata hotplug didn't work on 100 kernel --
grep -e 'Linux version' -e 'sdb' -e 'sdc' -e 'SATA link' syslog | tail -n25
May 6 07:24:42 rd1
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
SATA device hot plug regression on AMD EYPC (Asus) server
To
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
SATA device hot plug regression on AMD EYPC (Asus) server
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
SATA device hot plug regression on AMD EYPC (Asus) server
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 Ubuntu
Bugs,
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
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
The call trace seems correlating to ethtools like below:
Jun 18 01:19:08 frank-viper kernel: [69418.453457] BUG: unable to handle page
fault for address: b2660b04
Jun 18 01:19:08 frank-viper kernel: [69418.465204] #PF: supervisor read access
in kernel mode
Jun 18 01:19:08 frank-viper
Public bug reported:
On Asus Server, when it run "sosreport -a" to the network step, the
console would print below call trace and the 100G Nic port became
unreachable.
call trace on ga-kernel ( v5.4): https://paste.ubuntu.com/p/TC5Jn6hYGF/
** Affects: ubuntu
Importance: Undecided
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
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
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
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:
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
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:
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
--
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
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
>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
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.
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,
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
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
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
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
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
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
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
>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)
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
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.
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"
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:
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
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:
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
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
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
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
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
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
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
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
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.
@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
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:
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
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
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
** 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
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
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"
** 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.
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.
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.
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
** 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
** 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
1 - 100 of 215 matches
Mail list logo
