[Bug 2055238] Re: FC680i(qla2xxx) get dma mapping resulted in different sg counts error on 22.04 but not 20.04.5
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. https://bugs.launchpad.net/bugs/2055238 Title: FC680i(qla2xxx) get dma mapping resulted in different sg counts error on 22.04 but not 20.04.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2055238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055238] Re: FC680i(qla2xxx) get dma mapping resulted in different sg counts error on 22.04 but not 20.04.5
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 16/32Gb Fibre Channel to PCIe Adapter [1077:2261] (rev 01) Subsystem: Hangzhou H3C Technologies Co., Ltd. NIC-FC680i-Mb-2x16G [193d:100d] Kernel driver in use: qla2xxx Kernel modules: qla2xxx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055238 Title: FC680i(qla2xxx) get dma mapping resulted in different sg counts error on 22.04 but not 20.04.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2055238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055238] Re: FC680i(qla2xxx) get dma mapping resulted in different sg counts error on 22.04 but not 20.04.5
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055238 Title: FC680i(qla2xxx) get dma mapping resulted in different sg counts error on 22.04 but not 20.04.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2055238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055238] Re: FC680i(qla2xxx) get dma mapping resulted in different sg counts error on 22.04 but not 20.04.5
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055238 Title: FC680i(qla2xxx) get dma mapping resulted in different sg counts error on 22.04 but not 20.04.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2055238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055238] [NEW] FC680i(qla2xxx) get dma mapping resulted in different sg counts error on 22.04 but not 20.04.5
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_cnt: 1 dma_reply_sg_cnt: 1. Reproduce method: qaucli -pr fc -kl 21:00:f4:c7:aa:od:83:e8 DP CRPAT DS 256 TC 1 OE 1 LT 4 ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055238 Title: FC680i(qla2xxx) get dma mapping resulted in different sg counts error on 22.04 but not 20.04.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2055238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054863] Re: AMD cpu (/proc/iomme 0-0xf2ffffff) is incorrectly reserved
** 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 ga-kernel (5.15.0) ** Summary changed: - AMD cpu (/proc/iomme 0-0xf2ff) is incorrectly reserved on 22.04 ga-kernel (5.15.0) + AMD cpu (/proc/iomme 0-0xf2ff) is incorrectly reserved on 22.04 ga-kernel (5.15.0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054863 Title: AMD cpu (/proc/iomme 0-0xf2ff) is incorrectly reserved on 22.04 ga-kernel (5.15.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2054863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054860] [NEW] AMD-Vi Failed to allocate IRTE
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/14/1153 Certain device drivers allocate IO queues on a per-cpu basis. On AMD EPYC platform, which can support up-to 256 cpu threads, this can exceed the current MAX_IRQ_PER_TABLE limit of 256, and result in the error message: AMD-Vi: Failed to allocate IRTE This has been observed with certain NVME devices. AMD IOMMU hardware can actually support upto 512 interrupt remapping table entries. Therefore, update the driver to match the hardware limit. Please note that this also increases the size of interrupt remapping table to 8KB per device when using the 128-bit IRTE format. ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054860 Title: AMD-Vi Failed to allocate IRTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2054860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054863] Re: AMD /proc/iomme 0-0xf2ffffff is incorrectly reserved
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 - : PCI Bus :00 - : PCI Bus :00 - : PCI Bus :00 000c-000c : PCI Bus :00 - : PCI Bus :00 - : PCI Bus :00 ** Description changed: - During kdump verify on Ubuntu 22.04 ga-kernel 5.15.0, kdump would fail - beause 0-0xf2ff(0-3.79G) have been reserved. + a partner reported that During kdump fail on AMD paltfrom which root casue came + + 0xf2ff(0-3.79G) have been reserved in /proc/iomem - It seems have been fixed on Ubuntu 22.04.2 HWE-kernel of - 5.19.0-32-generic. + They verified that kdump worked fine for 22.04.2 HWE-kernel of + 5.19.0-32-generic and iomem resume normal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054863 Title: AMD /proc/iomme 0-0xf2ff is incorrectly reserved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2054863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054863] Re: AMD /proc/iomme 0-0xf2ffffff is incorrectly 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. https://bugs.launchpad.net/bugs/2054863 Title: AMD /proc/iomme 0-0xf2ff is incorrectly reserved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2054863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054863] [NEW] AMD /proc/iomme 0-0xf2ffffff is incorrectly reserved
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054863 Title: AMD /proc/iomme 0-0xf2ff is incorrectly reserved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2054863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976511] Re: kernel taint ( warning ) caused by smpboot.c: on 5.4.0
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 ( warning ) caused by smpboot.c: on 5.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976511] Re: kernel taint ( warning ) caused by smpboot.c: on 5.4.0
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976511] Re: kernel taint ( warning ) caused by smpboot.c: on 5.4.0
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976511] Re: kernel taint ( warning ) caused by smpboot.c: on 5.4.0
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. https://bugs.launchpad.net/bugs/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976511] [NEW] kernel taint ( warning ) caused by smpboot.c: on 5.4.0
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: [0.007531] WARNING: CPU: 20 PID: 0 at /build/linux-hwe-5.4-9Mb2g5/linux-hwe-5.4-5.4.0/arch/x86/kernel/smpboot.c:426 topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Modules linked in: Apr 6 02:33:31 G292-280 kernel: [0.007531] CPU: 20 PID: 0 Comm: swapper/20 Not tainted 5.4.0-107-generic #121~18.04.1-Ubuntu Apr 6 02:33:31 G292-280 kernel: [0.007531] Hardware name: GIGABYTE G292-280-00/MG52-G20-00, BIOS F02 10/28/2021 Apr 6 02:33:31 G292-280 kernel: [0.007531] RIP: 0010:topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Code: 41 5c 5d c3 80 3d 1e 75 ba 01 00 75 ec 89 f1 41 89 d9 89 fe 45 89 e0 48 c7 c7 b8 00 b4 a6 c6 05 04 75 ba 01 01 e8 b4 c7 03 00 <0f> 0b eb cb 0f 1f 44 00 00 55 0f b6 05 a3 8d f0 01 c6 05 9c 8d f0 Apr 6 02:33:31 G292-280 kernel: [0.007531] RSP: :b76b58e17eb8 EFLAGS: 00010086 Apr 6 02:33:31 G292-280 kernel: [0.007531] RAX: RBX: RCX: a7264e88 Apr 6 02:33:31 G292-280 kernel: [0.007531] RDX: a7264e88 RSI: 0096 RDI: 0046 Apr 6 02:33:31 G292-280 kernel: [0.007531] RBP: b76b58e17ec8 R08: R09: 0002f680 Apr 6 02:33:31 G292-280 kernel: [0.007531] R10: 8b69bf80 R11: 02c0 R12: 0001 Apr 6 02:33:31 G292-280 kernel: [0.007531] R13: 0014 R14: 0014 R15: 0002 Apr 6 02:33:31 G292-280 kernel: [0.007531] FS: () GS:8b69bf80() knlGS: Apr 6 02:33:31 G292-280 kernel: [0.007531] CS: 0010 DS: ES: CR0: 80050033 Apr 6 02:33:31 G292-280 kernel: [0.007531] CR2: CR3: 007ee1a0a001 CR4: 00760ee0 Apr 6 02:33:31 G292-280 kernel: [0.007531] DR0: DR1: DR2: Apr 6 02:33:31 G292-280 kernel: [0.007531] DR3: DR6: fffe0ff0 DR7: 0400 Apr 6 02:33:31 G292-280 kernel: [0.007531] PKRU: Apr 6 02:33:31 G292-280 kernel: [0.007531] Call Trace: Apr 6 02:33:31 G292-280 kernel: [0.007531] set_cpu_sibling_map+0x14f/0x600 Apr 6 02:33:31 G292-280 kernel: [0.007531] start_secondary+0x6e/0x1c0 Apr 6 02:33:31 G292-280 kernel: [0.007531] secondary_startup_64+0xa4/0xb0 Apr 6 02:33:31 G292-280 kernel: [0.007531] ---[ end trace 789d1f3abd3d96d4 ]--- ** 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. https://bugs.launchpad.net/bugs/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975922] Re: custom image deploy get failed in cmd-curthooks of DISTROS[DISTROS.index(distname)]
@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. https://bugs.launchpad.net/bugs/1975922 Title: custom image deploy get failed in cmd-curthooks of DISTROS[DISTROS.index(distname)] To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1975922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975922] Re: custom image deploy get failed in cmd-curthooks of DISTROS[DISTROS.index(distname)]
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 manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1975922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 sata port or disk, it will power off the sata controller, so no event can get when plug in sata disk. It seems an expecting logic as AHCI spec shows that once LPM is enabled, then the hotplug needs to be disabled. # To enable hotplug by one of below 2 methods a. Add below kernel parameter can make sata hot plug working ahci.mobile_lpm_policy=1 In our test, set to 0 or 2 also works. Refer to #46 for what 0,1,2,3 represents. b. via proc file To set "max_performance" for "/sys/class/scsi_host/host*/link_power_management_policy" Set min_power or medium_power will enable power save and disable the "Hot Plug" again. # More info about mobile ALPM Aggressive Link Power Management (ALPM) is a mechanism where a SATA AHCI controller can put the SATA link that connects to the disk into a very low power mode during periods of zero I/O activity and into an active power state when work needs to be done. More refer to https://wiki.ubuntu.com/Kernel/PowerManagementALPM. -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
@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 difference? 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
@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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 difference of 0,1,2 for lpm policy. 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 controller. Using the ID should is OK on
AMD EYPC processor."
I just searched the VID:DID= 1022:7901 and find it should belong to AMD FCH
SATA Controller,
as shown below. https://devicehunt.com/view/type/pci/vendor/1022/device/7901
I guess your fix is to remove below line, than hot plug worked, is this right?
{ PCI_VDEVICE(AMD, 0x7901), board_ahci_mobile }, /* AMD Green Sardine */
So your questions is why this new device ID of "AMD SATA AHCI
controller" is conflict with "AMD Green Sardine"? If this understand is
right, I would ask AMD guy.
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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. -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: 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 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EYPC (Asus) server
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" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+attachment/5587308/+files/sosreport-rd1-5.4.0-99-2022-05-06-snasuwj.tar.xz -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EYPC (Asus) server
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" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+attachment/5587307/+files/sosreport-rd1-5.4.0-100-2022-05-06-nhhkods.tar.xz -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EYPC (Asus) server
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 kernel: [0.00] Linux version 5.4.0-100-generic (buildd@lcy02-amd64-002) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #113-Ubuntu SMP Thu Feb 3 18:43:29 UTC 2022 (Ubuntu 5.4.0-100.113-generic 5.4.166) May 6 07:24:42 rd1 lvm[1462]: /dev/sdb: open failed: No medium found May 6 07:24:42 rd1 lvm[1462]: /dev/sdb: open failed: No medium found May 6 07:24:42 rd1 multipath: sdb: can't store path info May 6 07:24:42 rd1 kernel: [5.702421] ata1: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [5.708864] ata2: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [5.718877] ata4: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [5.723683] ata3: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [5.730424] ata11: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [5.734957] ata8: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [5.739442] ata5: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [5.743924] ata7: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [5.748408] ata9: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [5.752913] ata10: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [5.757504] ata12: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [5.920006] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) May 6 07:24:42 rd1 kernel: [6.018166] ata13: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [6.019402] ata14: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [6.020150] ata15: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [6.020852] ata16: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [6.021509] ata18: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [6.022275] ata20: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [6.023117] ata17: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [6.023922] ata19: SATA link down (SStatus 0 SControl 300) May 6 07:24:42 rd1 kernel: [6.356905] sd 1:0:0:0: [sdb] Attached SCSI removable disk zlmao@p14s:~/Downloads/asus/binsec/sosreport-rd1-5.4.0-100-2022-05-06-nhhkods/var/log$ --sata hotplug does work on 99 kernel -- grep -e 'Linux version' -e 'sdb' -e 'sdc' -e 'SATA link' syslog |tail -n41 May 6 07:30:42 rd1 kernel: [0.00] Linux version 5.4.0-99-generic (buildd@lgw01-amd64-007) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #112-Ubuntu SMP Thu Feb 3 13:50:55 UTC 2022 (Ubuntu 5.4.0-99.112-generic 5.4.162) May 6 07:30:42 rd1 lvm[1409]: /dev/sdb: open failed: No medium found May 6 07:30:42 rd1 lvm[1409]: /dev/sdb: open failed: No medium found May 6 07:30:42 rd1 multipath: sdb: can't store path info May 6 07:30:42 rd1 kernel: [5.659454] ata1: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.659533] ata3: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.659584] ata4: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.659613] ata2: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.683576] ata5: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.692154] ata12: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.695185] ata14: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.695548] ata15: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.695574] ata16: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.696090] ata13: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.699290] ata17: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.699579] ata20: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.699607] ata18: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.701774] ata19: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.707358] ata9: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.723384] ata10: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.734049] ata11: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.751312] ata7: SATA link down (SStatus 0 SControl 300) May 6 07:30:42 rd1 kernel: [5.774745] ata8: SATA link down (SStatus 0 SControl 300) May 6
[Bug 1971576] Re: SATA device hot plug regression on AMD EYPC (Asus) server
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EYPC (Asus) server
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: SATA device hot plug regression on AMD EYPC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EYPC (Asus) server
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: 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 5.4.0-42.46-generic 5.4.44) May 4 05:57:33 rd1 kernel: [0.00] Linux version 5.4.0-109-generic (buildd@ubuntu) (gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)) #123-Ubuntu SMP Fri Apr 8 09:10:54 UTC 2022 (Ubuntu 5.4.0-109.123-generic 5.4.178) ** Attachment added: "sosreport-rd1-5.4.0-109-2022-05-04-ppcdgwk.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+attachment/5586680/+files/sosreport-rd1-5.4.0-109-2022-05-04-ppcdgwk.tar.xz ** 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/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EYPC (Asus) server
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EYPC (Asus) server
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:51:57 rd1 kernel: [ 173.391493] ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300) May 4 05:51:57 rd1 kernel: [ 173.406406] ata17.00: ATA-8: WDC WD3200BEKT-22F3T0, 11.01A11, max UDMA/133 May 4 05:51:57 rd1 kernel: [ 173.406409] ata17.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 32), AA May 4 05:51:57 rd1 kernel: [ 173.409409] ata17.00: configured for UDMA/133 May 4 05:51:57 rd1 kernel: [ 173.409606] scsi 16:0:0:0: Direct-Access ATA WDC WD3200BEKT-2 1A11 PQ: 0 ANSI: 5 May 4 05:51:57 rd1 kernel: [ 173.409842] sd 16:0:0:0: Attached scsi generic sg3 type 0 May 4 05:51:57 rd1 kernel: [ 173.409885] sd 16:0:0:0: [sdc] 625142448 512-byte logical blocks: (320 GB/298 GiB) May 4 05:51:57 rd1 kernel: [ 173.409895] sd 16:0:0:0: [sdc] Write Protect is off May 4 05:51:57 rd1 kernel: [ 173.409897] sd 16:0:0:0: [sdc] Mode Sense: 00 3a 00 00 May 4 05:51:57 rd1 kernel: [ 173.409909] sd 16:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA May 4 05:51:57 rd1 kernel: [ 173.437156] sdc: sdc1 sdc2 May 4 05:51:57 rd1 kernel: [ 173.438248] sd 16:0:0:0: [sdc] Attached SCSI removable 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] [NEW] SATA device hot plug regression on AMD EYPC (Asus) server
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934112] Re: Intel 100G nic get call trace for sosreport on focal ga-kenel
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 kernel: [69418.473243] #PF: error_code(0x) - not-present page Jun 18 01:19:08 frank-viper kernel: [69418.473245] PGD 3f72d5a067 P4D 3f72d5a067 PUD 3f72d5b067 PMD 3f515a4067 PTE 0 Jun 18 01:19:08 frank-viper kernel: [69418.473251] Oops: [#1] SMP NOPTI Jun 18 01:19:08 frank-viper kernel: [69418.473255] CPU: 42 PID: 4113544 Comm: ethtool Tainted: P O 5.4.0-74-generic #83-Ubuntu Jun 18 01:19:08 frank-viper kernel: [69418.473256] Hardware name: ASUSTeK COMPUTER INC. AE-SER1UW-A --/AE-SER1UW-A/AF1829.01, BIOS 3.03.00 05/25/2021 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934112 Title: Intel 100G nic get call trace for sosreport on focal ga-kenel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1934112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934112] [NEW] Intel 100G nic get call trace for sosreport on focal ga-kenel
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 Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934112 Title: Intel 100G nic get call trace for sosreport on focal ga-kenel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1934112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911828] [NEW] Ubuntu 18.04.5/20.04 kernel doesn't have latest i40e driver for X710-T2L module
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 Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911828 Title: Ubuntu 18.04.5/20.04 kernel doesn't have latest i40e driver for X710-T2L module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909518] Re: bcache register_bdev() error cannot allocate memory
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909518] Re: bcache register_bdev() error cannot allocate memory
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 Good (in use) LBA Format 1 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best ubuntu@prdhci01a:~$ sudo nvme format /dev/nvme1 -n 1 -l 1 Success formatting namespace:1 ubuntu@prdhci01a:~$ sudo nvme id-ns /dev/nvme1 -n 1 -H |grep "LBA Format" [3:0] : 0x1 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0x2 Good LBA Format 1 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) ubuntu@prdhci01a:~$ ' -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909518] Re: bcache register_bdev() error cannot allocate memory
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: bcache register_bdev() error cannot allocate memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909518] Re: bcache register_bdev() error cannot allocate memory
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 allocate memory [ 727.756456] bcache: register_bcache() error : failed to register device [ 727.756471] bcache: bcache_device_free() bcache device (NULL gendisk) stopped There are fix in 5.9 kernel and it can work after install 5.9 kernel on 20.04. The 5.9 kernel are download it from: https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.9.16/ - The similar bug reports are + The similar bug report can be found at https://bugzilla.redhat.com/show_bug.cgi?id=1783075. - It might related to back device type. We tested on "Lenov SR665 Server" - and "Intel P4510 4.0TB U.2 NVMe SSD", the caching disk are "Intel P4800X - 375GB U.2 NVMe SSD". + It might related to back device type. it was tested on "Lenov SR665 + Server" and "Intel P4510 4.0TB U.2 NVMe SSD", the caching disk are + "Intel P4800X 375GB U.2 NVMe SSD". -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909518] [NEW] bcache register_bdev() error cannot allocate memory
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_bcache() error : failed to register device [ 727.756471] bcache: bcache_device_free() bcache device (NULL gendisk) stopped There are fix in 5.9 kernel and it can work after install 5.9 kernel on 20.04. The 5.9 kernel are download it from: https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.9.16/ The similar bug report can be found at https://bugzilla.redhat.com/show_bug.cgi?id=1783075. It might related to back device type. it was tested on "Lenov SR665 Server" and "Intel P4510 4.0TB U.2 NVMe SSD", the caching disk are "Intel P4800X 375GB U.2 NVMe SSD". ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic focal ga-kernel hwe-kernel ** Tags added: bionic focal ga-kernel hwe-kernel ** 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 ( 102% fail, but - 1024 did not). + 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_bcache() error : failed to register device [ 727.756471] bcache: bcache_device_free() bcache device (NULL gendisk) stopped - - There are fix in 5.9 kernel and it can work after install 5.9 kernel on 20.04. The 5.9 kernel are download it from: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.16/ + There are fix in 5.9 kernel and it can work after install 5.9 kernel on + 20.04. The 5.9 kernel are download it from: https://kernel.ubuntu.com + /~kernel-ppa/mainline/v5.9.16/ The similar bug reports are https://bugzilla.redhat.com/show_bug.cgi?id=1783075. It might related to back device type. We tested on "Lenov SR665 Server" and "Intel P4510 4.0TB U.2 NVMe SSD", the caching disk are "Intel P4800X 375GB U.2 NVMe SSD". -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877083] [NEW] qemu vnc console can only show "no suitable video mode" on taishan2280 server
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877083 Title: qemu vnc console can only show "no suitable video mode" on taishan2280 server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server
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 -name guest=instance-004f,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-20-instance-004f/master-key.aes -machine virt-2.11,accel=kvm,usb=off,dump-guest-core=off,gic-version=3 -cpu host -drive file=/usr/share/AAVMF/AAVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/var/lib/libvirt/qemu/nvram/instance-004f_VARS.fd,if=pflash,format=raw,unit=1 -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid da45ffb1-9501-443a-97e2-f1293fbfd08f -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-20-instance-004f/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-shutdown -boot strict=on -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 -device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 -device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 -device pcie-root-port,port=0xb,chassis=4,id=pci.4,bus=pcie.0,addr=0x1.0x3 -device pcie-root-port,port=0xc,chassis=5,id=pci.5,bus=pcie.0,addr=0x1.0x4 -device pcie-root-port,port=0xd,chassis=6,id=pci.6,bus=pcie.0,addr=0x1.0x5 -device qemu-xhci,id=usb,bus=pci.2,addr=0x0 -object secret,id=virtio-disk0-secret0,data=Z3QA44y9KQVjm1An9Z7JiVegjxUJjdHPo8fjGseVK3E=,keyid=masterKey0,iv=Ysbjc+1zq7/PnAMK2/WjJA==,format=base64 -drive file=rbd:cinder-ceph/volume-ece667dd-5d26-40cd-b27e-64be5803968e:id=cinder-ceph:auth_supported=cephx\;none:mon_host=172.16.25.47\:6789\;172.16.25.54\:6789\;172.16.25.60\:6789,file.password-secret=virtio-disk0-secret0,format=raw,if=none,id=drive-virtio-disk0,serial=ece667dd-5d26-40cd-b27e-64be5803968e,cache=none,discard=unmap -device virtio-blk-pci,scsi=off,bus=pci.3,addr=0x0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,host_mtu=1500,netdev=hostnet0,id=net0,mac=fa:16:3e:85:cc:99,bus=pci.1,addr=0x0 -add-fd set=2,fd=30 -chardev pty,id=charserial0,logfile=/dev/fdset/2,logappend=on -serial chardev:charserial0 -device usb-tablet,id=input0,bus=usb.0,port=1 -device usb-kbd,id=input1,bus=usb.0,port=2 -vnc 0.0.0.0:0 -k en-us -device virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.5,addr=0x0 -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 -msg timestamp=on -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877083 Title: qemu vnc console can only show "no suitable video mode" on taishan2280 server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server
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 for "error: no suitable video mode found". But the openstack dashboard can display nothing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877083 Title: qemu vnc console can only show "no suitable video mode" on taishan2280 server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server
>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 option is to use: -device virtio-gpu-pci and enable the following Linux kernel options: CONFIG_DRM=y CONFIG_DRM_VIRTIO_GPU=y Also, for some reason, the SDL graphic window does not open under certain circumstances as of v2.12, so you might need to use another method such as VNC: -vnc :0 and then connect to it with: vinagre :5900 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877083 Title: qemu vnc console can only show "no suitable video mode" on taishan2280 server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server
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. https://bugs.launchpad.net/bugs/1877083 Title: qemu vnc console can only show "no suitable video mode" on taishan2280 server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877083 Title: qemu vnc console can only show "no suitable video mode" on taishan2280 server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877083 Title: qemu vnc console can only show "no suitable video mode" on taishan2280 server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877083] Re: qemu vnc console can only show "no suitable video mode" on taishan2280 server
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 found" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877083 Title: qemu vnc console can only show "no suitable video mode" on taishan2280 server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
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 number 2 using xhci_hcd usb 1-1: New USB device found, idVendor=05ac, idProduct=1006 usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1: Product: Keyboard Hub usb 1-1: Manufacturer: Apple, Inc. usb 1-1: SerialNumber: kernel: hub 1-1:1.0: USB hub found - full log for a reboot crycle via grep usb messages Feb 17 19:54:41 192-168-129-24 kernel: ACPI: bus type USB registered Feb 17 19:54:41 192-168-129-24 kernel: usbcore: registered new interface driver usbfs Feb 17 19:54:41 192-168-129-24 kernel: usbcore: registered new interface driver hub Feb 17 19:54:41 192-168-129-24 kernel: usbcore: registered new device driver usb Feb 17 19:54:41 192-168-129-24 kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Feb 17 19:54:41 192-168-129-24 kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Feb 17 19:54:41 192-168-129-24 kernel: uhci_hcd: USB Universal Host Controller Interface driver Feb 17 19:54:41 192-168-129-24 kernel: xhci_hcd :00:14.0: new USB bus registered, assigned bus number 1 Feb 17 19:54:41 192-168-129-24 kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 Feb 17 19:54:41 192-168-129-24 kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 17 19:54:41 192-168-129-24 kernel: usb usb1: Product: xHCI Host Controller Feb 17 19:54:41 192-168-129-24 kernel: usb usb1: Manufacturer: Linux 3.10.0-862.el7.x86_64 xhci-hcd Feb 17 19:54:41 192-168-129-24 kernel: usb usb1: SerialNumber: :00:14.0 Feb 17 19:54:41 192-168-129-24 kernel: hub 1-0:1.0: USB hub found Feb 17 19:54:41 192-168-129-24 kernel: xhci_hcd :00:14.0: new USB bus registered, assigned bus number 2 Feb 17 19:54:41 192-168-129-24 kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003 Feb 17 19:54:41 192-168-129-24 kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 17 19:54:41 192-168-129-24 kernel: usb usb2: Product: xHCI Host Controller Feb 17 19:54:41 192-168-129-24 kernel: usb usb2: Manufacturer: Linux 3.10.0-862.el7.x86_64 xhci-hcd Feb 17 19:54:41 192-168-129-24 kernel: usb usb2: SerialNumber: :00:14.0 Feb 17 19:54:41 192-168-129-24 kernel: hub 2-0:1.0: USB hub found Feb 17 19:54:41 192-168-129-24 kernel: usb: port power management may be unreliable Feb 17 19:54:41 192-168-129-24 kernel: usbcore: registered new interface driver usbserial Feb 17 19:54:41 192-168-129-24 kernel: usbcore: registered new interface driver usbserial_generic Feb 17 19:54:41 192-168-129-24 kernel: usbserial: USB Serial support registered for generic Feb 17 19:54:41 192-168-129-24 kernel: usbcore: registered new interface driver usbhid Feb 17 19:54:41 192-168-129-24 kernel: usbhid: USB HID core driver Feb 17 19:54:41 192-168-129-24 kernel: usb 1-1: new high-speed USB device number 2 using xhci_hcd Feb 17 19:54:41 192-168-129-24 kernel: usb 1-1: New USB device found, idVendor=05ac, idProduct=1006 Feb 17 19:54:41 192-168-129-24 kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 17 19:54:41 192-168-129-24 kernel: usb 1-1: Product: Keyboard Hub Feb 17 19:54:41 192-168-129-24 kernel: usb 1-1: Manufacturer: Apple, Inc. Feb 17 19:54:41 192-168-129-24 kernel: usb 1-1: SerialNumber: Feb 17 19:54:41 192-168-129-24 kernel: hub 1-1:1.0: USB hub found Feb 17 19:54:42 192-168-129-24 kernel: usb 1-2: new low-speed USB device number 3 using xhci_hcd Feb 17 19:54:42 192-168-129-24 kernel: usb 1-2: New USB device found, idVendor=046d, idProduct=c31c Feb 17 19:54:42 192-168-129-24 kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 17 19:54:42 192-168-129-24 kernel: usb 1-2: Product: USB Keyboard Feb 17 19:54:42 192-168-129-24 kernel: usb 1-2: Manufacturer: Logitech Feb 17 19:54:42 192-168-129-24 kernel: input: Logitech USB Keyboard as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/input/input1 Feb 17 19:54:42 192-168-129-24 kernel: usb 1-1.2: new low-speed USB device number 4 using xhci_hcd Feb 17 19:54:42 192-168-129-24 kernel: hid-generic 0003:046D:C31C.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-:00:14.0-2/input0 Feb 17 19:54:42 192-168-129-24 kernel: input: Logitech USB Keyboard as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1/input/input2 Feb 17 19:54:42 192-168-129-24 kernel: hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID v1.10 Device [Logitech USB Keyboard] on usb-:00:14.0-2/input1 Feb 17 19:54:42 192-168-129-24 kernel: usb 1-1.2: New USB device found, idVendor=05ac, idProduct=0220 Feb 17 19:54:42 192-168-129-24 kernel: usb
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
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 just 16% reboot were failed to detect keyboard. no-keyboard: Feb 25 20:56:06 13.639502] xhci_hcd :00:14.0: Host supports USB 3.0 SuperSpeed *Feb 25 20:56:06 13.703568] usb usb1-port2: couldn't allocate usb_device *Feb 25 20:56:06 13.769363] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03 Feb 25 20:56:06 13.900828] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 25 20:56:06 13.968612] usb usb2: Product: xHCI Host Controller Feb 25 20:56:06 14.027356] usb usb2: Manufacturer: Linux 5.3.0-28-generic xhci-hcd Feb 25 20:56:06 14.079505] usb usb2: SerialNumber: :00:14.0 with-keyboard: Feb 25 14:58:11 17.021871] xhci_hcd :00:14.0: Host supports USB 3.0 SuperSpeed *Feb 25 14:58:11 17.021903] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03 Feb 25 14:58:11 17.212935] usb 1-2: new low-speed USB device number 2 using xhci_hcd Feb 25 14:58:11 17.220801] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 25 14:58:11 17.220803] usb usb2: Product: xHCI Host Controller Feb 25 14:58:11 17.220803] usb usb2: Manufacturer: Linux 5.3.0-28-generic xhci-hcd Feb 25 14:58:11 17.220804] usb usb2: SerialNumber: :00:14.0 -- 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 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
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 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.796396] xhci_hcd :00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x9810 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.860304] xhci_hcd :00:14.0: cache line size of 64 is not supported Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.924653] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.989809] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.055002] usb usb1: Product: xHCI Host Controller Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.119662] usb usb1: Manufacturer: Linux 5.3.0-28-generic xhci-hcd Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.184980] usb usb1: SerialNumber: :00:14.0 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.249663] hub 1-0:1.0: USB hub found Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.313880] hub 1-0:1.0: 16 ports detected Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.379787] probe of 1-0:1.0 returned 1 after 130128 usecs Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.444761] probe of usb1 returned 1 after 195129 usecs Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.509606] xhci_hcd :00:14.0: xHCI Host Controller Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.574399] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 2 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.609979] usb usb1-port1: couldn't allocate usb_device Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.639502] xhci_hcd :00:14.0: Host supports USB 3.0 SuperSpeed Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.703568] usb usb1-port2: couldn't allocate usb_device Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.769363] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.900828] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 13.968612] usb usb2: Product: xHCI Host Controller Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.027356] usb usb2: Manufacturer: Linux 5.3.0-28-generic xhci-hcd Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.079505] usb usb2: SerialNumber: :00:14.0 Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.133178] hub 2-0:1.0: USB hub found Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.184423] hub 2-0:1.0: 10 ports detected Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.235270] usb: port power management may be unreliable Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.287421] probe of 2-0:1.0 returned 1 after 154246 usecs Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 14.338363] probe of usb2 returned 1 after 205203 usecs -- 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 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
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 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 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
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 kernel: [ 13.372798] probe of usb1 returned 1 after 194395 usecs Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.437456] xhci_hcd :00:14.0: xHCI Host Controller Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.502175] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 2 Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.541288] usb usb1-port1: couldn't allocate usb_device Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.567309] xhci_hcd :00:14.0: Host supports USB 3.0 SuperSpeed Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.567341] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03 Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.757241] usb 1-2: new low-speed USB device number 2 using xhci_hcd Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.764290] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.764291] usb usb2: Product: xHCI Host Controller Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.764292] usb usb2: Manufacturer: Linux 5.3.0-28-generic xhci-hcd Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.764295] usb usb2: SerialNumber: :00:14.0 Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.986189] usb 1-2: New USB device found, idVendor=04ca, idProduct=0027, bcdDevice= 1.18 Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.004749] hub 2-0:1.0: USB hub found Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.056592] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.109726] hub 2-0:1.0: 10 ports detected Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.161986] usb 1-2: Product: USB Multimedia Keyboard Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.161988] usb 1-2: Manufacturer: Lite-On Technology Corp. Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.215697] usb: port power management may be unreliable Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.269095] probe of 1-2 returned 1 after 1173 usecs Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 14.320539] probe of 2-0:1.0 returned 1 after 315796 usecs -- 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 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
>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) support is initialized. Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 21.017745] RAS: Correctable Errors collector initialized. Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 28.579403] calling init_error_injection+0x0/0x6f @ 1 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 28.639458] initcall init_error_injection+0x0/0x6f returned 0 after 160 usecs Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 61.697880] EXT4-fs (nvme0n1p1): re-mounted. Opts: errors=remount-ro $ grep -i keybaord kernel.log|tail -n15 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 14.154902] usb 1-2: Product: USB Multimedia Keyboard Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 36.585889] input: Lite-On Technology Corp. USB Multimedia Keyboard as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04CA:0027.0001/input/input1 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 36.642395] hid-generic 0003:04CA:0027.0001: input,hidraw0: USB HID v1.10 Keyboard [Lite-On Technology Corp. USB Multimedia Keyboard] on usb-:00:14.0-2/input0 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 36.642705] input: Lite-On Technology Corp. USB Multimedia Keyboard System Control as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1/0003:04CA:0027.0002/input/input2 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 36.702392] input: Lite-On Technology Corp. USB Multimedia Keyboard Consumer Control as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1/0003:04CA:0027.0002/input/input3 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 36.702495] input: Lite-On Technology Corp. USB Multimedia Keyboard as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1/0003:04CA:0027.0002/input/input4 Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [ 36.702653] hid-generic 0003:04CA:0027.0002: input,hiddev0,hidraw1: USB HID v1.10 Device [Lite-On Technology Corp. USB Multimedia Keyboard] on usb-:00:14.0-2/input1 Feb 26 10:05:08 user-QuantaGrid-D52PL-4U kernel: [ 88.768902] usb 1-1: Product: Logitech USB Keyboard Feb 26 10:05:08 user-QuantaGrid-D52PL-4U kernel: [ 88.773167] input: Logitech Logitech USB Keyboard as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C315.0003/input/input5 Feb 26 10:05:08 user-QuantaGrid-D52PL-4U kernel: [ 88.830768] hid-generic 0003:046D:C315.0003: input,hidraw0: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-:00:14.0-1/input0 Feb 26 10:06:26 user-QuantaGrid-D52PL-4U kernel: [ 167.205004] usb 1-2: Product: Logitech USB Keyboard Feb 26 10:06:26 user-QuantaGrid-D52PL-4U kernel: [ 167.209006] input: Logitech Logitech USB Keyboard as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:046D:C315.0005/input/input7 Feb 26 10:06:26 user-QuantaGrid-D52PL-4U kernel: [ 167.266672] hid-generic 0003:046D:C315.0005: input,hidraw0: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-:00:14.0-2/input0 Feb 26 10:08:09 user-QuantaGrid-D52PL-4U kernel: [ 270.085139] usb 1-2: Product: Logitech USB Keyboard Feb 26 10:08:09 user-QuantaGrid-D52PL-4U kernel: [ 270.089237] input: Logitech Logitech USB Keyboard as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:046D:C315.0007/input/input9 Feb 26 10:08:09 user-QuantaGrid-D52PL-4U kernel: [ 270.146678] hid-generic 0003:046D:C315.0007: input,hidraw0: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-:00:14.0-2/input0 zlmao@zlmao-T460s:~/tmp/quanta$ -- 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 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
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 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] Re: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
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. https://bugs.launchpad.net/bugs/1869138 Title: The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869138] [NEW] The keyboard does not have responeded when boot system into Ubuntu 18.04.4 with HWE(Legacy Mode) on Quanta server
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" in grub.cfg. ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New -- 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 with HWE(Legacy Mode) on Quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864612] Re: requests ipmi-tool to include lasted patch for supporting quanta server
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: requests ipmi-tool to include lasted patch for supporting quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1864612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864612] Re: requests ipmi-tool to include lasted patch for supporting quanta server
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 0x0 0x00 0x0 0x1 0x0 0x4 0xc 0x87 0x6f 0xa0 0x00 0x00 -- 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: requests ipmi-tool to include lasted patch for supporting quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1864612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864612] [NEW] requests ipmi-tool to include lasted patch for supporting quanta server
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: https://github.com/ipmitool/ipmitool/commit/5c033c06abb45bc183f42cd758c61807ce953726. Hopes to consideration this patch in 20.04 releasing. ** Affects: ipmitool (Ubuntu) Importance: Undecided Status: New -- 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: requests ipmi-tool to include lasted patch for supporting quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1864612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862723] Re: 18.04 can't auto load ub_iverbs (18.04.3 hwe can) for Mellanox PMD nics
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 2019-12-02T15:49:57.262Z|00308|dpdk|INFO|EAL: probe driver: 15b3:1015 net_mlx5 2019-12-02T15:49:57.262Z|00309|dpdk|ERR|net_mlx5: cannot list devices, is ib_uverbs loaded? 2019-12-02T15:49:57.262Z|00310|dpdk|ERR|EAL: Driver cannot attach the device (:3b:00.0) In 18.04.3 hwe-kernel, the ib_uverbs is depened by ib_core which can auto load. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862723 Title: 18.04 can't auto load ub_iverbs (18.04.3 hwe can) for Mellanox PMD nics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1862723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862723] [NEW] 18.04 can't auto load ub_iverbs (18.04.3 hwe can) for Mellanox PMD nics
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862723 Title: 18.04 can't auto load ub_iverbs (18.04.3 hwe can) for Mellanox PMD nics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1862723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862722] Re: call trace during crash kernel boot on Huawei server for 18.04 ga-kernel
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 crashkernel=2G-:536M [0.00] Reserving 536MB of memory at 32MB for crashkernel (System RAM: 261726MB) [0.00] Kernel 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 crashkernel=2G-:536M [ 40.151040] megaraid_sas :1c:00.0: firmware crash dump : no root@node1:~# echo c > /proc/sysrq-trigger OOM as below: [ 62.038374] Kernel panic - not syncing: Out of memory and no killable processes... [ 62.038374] [ 62.166809] CPU: 0 PID: 310 Comm: bcache_writebac Not tainted 4.15.0-72-generic #81-Ubuntu [ 62.275904] Hardware name: Huawei 2288H V5/BC11SPSCB0, BIOS 6.72 04/30/2019 [ 62.369545] Call Trace: [ 62.409415] dump_stack+0x63/0x8e [ 62.459411] panic+0xe4/0x254 [ 62.505216] ? dump_header+0x18e/0x285 [ 62.560348] out_of_memory+0x3b4/0x4e0 [ 62.615663] __alloc_pages_slowpath+0xa53/0xe00 [ 62.680115] __alloc_pages_nodemask+0x29a/0x2c0 [ 62.744505] alloc_pages_current+0x6a/0xe0 [ 62.803676] bio_alloc_pages+0x42/0x90 [ 62.858710] read_dirty+0x211/0x370 [bcache] [ 62.919965] bch_writeback_thread+0x518/0x5a0 [bcache] [ 62.991622] kthread+0x121/0x140 [ 63.040709] ? read_dirty+0x370/0x370 [bcache] [ 63.104073] ? kthread_create_worker_on_cpu+0x70/0x70 [ 63.174627] ret_from_fork+0x35/0x40 [ 63.227373] Kernel Offset: 0x1be0 from 0x8100 (relocation range: 0x8000-0xbfff) [ 63.512588] ---[ end Kernel panic - not syncing: Out of memory and no killable processes... [ 63.512588] -- call trace when memory set 576M or 1024M, below is only one of cpu's call trace. - [ 2407.794096] [ cut here ] [ 2407.855674] sched: Unexpected reschedule of offline CPU#12! [ 2407.928663] WARNING: CPU: 25 PID: 859240 at /build/linux-E6MDAa/linux-4.15.0/arch/x86/kernel/smp.c:128 native_smp_send_reschedule+0x3a/0x40 [ 2408.091827] Modules linked in: vsock_diag vsock sctp_diag sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_addrtype xt_conntrack binfmt_misc veth ip6table_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter br_netfilter openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack 8021q garp mrp bonding bridge stp llc nls_iso8859_1 intel_rapl skx_edac x86_pkg_temp_thermal coretemp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler [ 2408.996649] ioatdma mei_me mei lpc_ich shpchp dca acpi_power_meter mac_hid sch_fq_codel sunrpc ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ib_uverbs ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure ib_core bcache scsi_transport_sas crct10dif_pclmul crc32_pclmul hid_generic ghash_clmulni_intel mlx5_core pcbc usbhid aesni_intel mlxfw i40e aes_x86_64 devlink crypto_simd glue_helper ptp cryptd megaraid_sas pps_core hid [ 2409.673608] CPU: 25 PID: 859240 Comm: bash Tainted: G D W 4.15.0-72-generic #81-Ubuntu [ 2409.790640] Hardware name: Huawei 2288H V5/BC11SPSCB0, BIOS 6.72 04/30/2019 [ 2409.883892] RIP: 0010:native_smp_send_reschedule+0x3a/0x40 [ 2409.959545] RSP: 0018:9e6aff0c33f0 EFLAGS: 00010082 [ 2410.032027] RAX: RBX: 9e3b00be5940 RCX: 0006 [ 2410.127442] RDX: 0007 RSI: 0086 RDI: 9e6aff0d6490 [ 2410.222848] RBP: 9e6aff0c33f0 R08: 10c3 R09: 00cdcdcd [ 2410.318270] R10: 9e6aff0c33d0 R11: R12: 9e3b00be646c [ 2410.413691] R13: 0004 R14: 0046 R15: 00021840 [ 2410.509055] FS: 7f3782413740() GS:9e6aff0c() knlGS: [ 2410.615957] CS: 0010 DS: ES: CR0: 80050033 [ 2410.694883] CR2: CR3: 002386e38002 CR4: 007606e0 [ 2410.790525] DR0: DR1: DR2: [ 2411.064749] [ 2411.099165] try_to_wake_up+0x3ea/0x4a0 [ 2411.346254] __wake_up_locked+0x16/0x20 [
[Bug 1862722] [NEW] call trace during crash kernel boot on Huawei server for 18.04 ga-kernel
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862722 Title: call trace during crash kernel boot on Huawei server for 18.04 ga- kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1862722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862720] [NEW] kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel
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 data :[ 421.979156] print_req_error: I/O error, dev sdb, sector 82830936 flags 0 [ 54.8 %] |[ 422.081318] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 18.04.3 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/1862720 Title: kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862720] Re: kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel
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 8:20 1.1T 0 part ├─infra1--vg-root 253:00 1.1T 0 lvm / └─infra1--vg-swap_1 253:10 976M 0 lvm [SWAP] sdb 8:16 0 557.9G 0 disk sdc 8:32 0 557.9G 0 disk ubuntu@infra1:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 126G 0 126G 0% /dev tmpfs 26G 2.4M 26G 1% /run /dev/mapper/infra1--vg-root 1.1T 313G 729G 31% / tmpfs126G 54M 126G 1% /dev/shm tmpfs5.0M 0 5.0M 0% /run/lock tmpfs126G 0 126G 0% /sys/fs/cgroup /dev/sda1511M 6.1M 505M 2% /boot/efi tmpfs100K 0 100K 0% /var/lib/lxd/shmounts tmpfs100K 0 100K 0% /var/lib/lxd/devlxd /dev/loop094G 6.2G 86G 7% /var/lib/lxd/storage-pools/default tmpfs 26G 0 26G 0% /run/user/1000 ubuntu@infra1:~$ cd /var/crash/ ubuntu@infra1:/var/crash$ ls -lhs total 8.7M 8.7M -rw-r- 1 bind bind 8.7M Dec 24 05:39 _usr_sbin_named.115.crash ubuntu@infra1:/var/crash$ root@node1:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x400 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.0.0-37-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.0.0-37-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/vmlinuz-5.0.0-37-generic root=UUID=d9281738-de5a-4564-852e-f07c29ea4817 ro default_hugepagesz=1GB transparent_hugepage=never solcpus=4-13,32-41,18-27,46-55 console=tty0 console=ttyS0 systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@node1:~# dmesg |grep -i crash [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.0.0-37-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 crashkernel=2G-:512M [0.02] Reserving 512MB of memory at 64MB for crashkernel (System RAM: 261726MB) [1.921643] Kernel command line: BOOT_IMAGE=/vmlinuz-5.0.0-37-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 crashkernel=2G-:512M [ 73.044719] pstore: Using crash dump compression: deflate [ 79.287259] megaraid_sas :1c:00.0: firmware crash dump : no root@node1:~# [ 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 data :[ 421.979156] print_req_error: I/O error, dev sdb, sector 82830936 flags 0 [ 54.8 %] |[ 422.081318] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. C[ 422.203707] Read-error on swap-device (8:0:4709320) opying data [ 422.284891] print_req_error: I/O error, dev sdb, sector 61463240 flags 0 [ 422.386425] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. [ 422.508953] Read-error on swap-device (8:0:2743136) : [ 55.2 %] \ [ 422.589689] print_req_error: I/O error, dev sdb, sector 4070592 flags 80700 eta: 19s[ 422.695501] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. Copying data [ 422.818144] print_req_error: I/O error, dev sdb, sector 4070744 flags 80700 [ 422.924145] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. [ 423.047007] print_req_error: I/O error, dev sda, sector 23649960 flags 80700 : [ 55.6 %] -[ 423.154494] print_req_error: I/O error, dev sda, sector 23650112 flags 80700 eta: 1[ 423.263750] print_req_error: I/O error, dev sdb, sector 65443209 flags 1001 Copying data [ 423.367832] bcache: bch_count_io_errors() sdb1: IO error on writing btree. [ 423.473080] print_req_error: I/O error, dev sdb, sector 4070712 flags 0 [ 423.575254] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. : [ 56.0 %][ 423.698447] print_req_error: I/O error, dev sda,
[Bug 1860403] [NEW] fio call trace on xenial during ceph rbd testing
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 --pool=scbench --rbdname=image01 --iodepth=16 --bs=4k --direct=0 --size=512M --numjobs=8 --runtime=240 --group_reporting --rw=randread ** Affects: fio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860403 Title: fio call trace on xenial during ceph rbd testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fio/+bug/1860403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
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 screen becomes blurry on Huawei server in EFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
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. This hibmc_drm driver can only work for ARM64, as I know, chip vendors don't have any intend/interesting to make this drm/kernel driver to work for x86. For x86, it must use the existing driver which was based Xorg. -- 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 in EFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
@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 in our new source. In last month, I testing with 18.04.2 iso (d-i) and this screen blur is still existing. Does it mean this patch did not solve our cases. -- 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 in EFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
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: assertion 'G_UDEV_IS_DEVICE (device)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1752091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
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). It would prevent this module to load and let you install as usual. **prevent load for installed system Although, we didn't find any issues for X-window during our testing. If you want to prevent loading on a finished installed system. You can add similar setting to /etc/default/grub for line as: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=hibmc_drm" You need to update grub by "sudo grub-update" and reboot to make it be efectly. -- 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 in EFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594317] Re: Cannot start lxd-bridge.service when MAAS is managing DNS
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 notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1594317/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594317] Re: Cannot start lxd-bridge.service when MAAS is managing DNS
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 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:32:18 UTC 2019
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@infra1:/etc/bind$ cat /etc/bind/named.conf.options
..
options { directory "/var/cache/bind";
auth-nxdomain no;
listen-on-v6 { none; };
listen-on { 185.168.3.1; };
//listen-on { !10.54.224.0/24; };
//listen-on { any; };
include "/etc/bind/maas/named.conf.options.inside.maas"; };
ubuntu@infra1:/etc/bind$
--
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 notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1594317/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815847] Re: 16.04 install would get "can't install busybox-initramfs" error with Chinese Language for install
** 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 Ubuntu. https://bugs.launchpad.net/bugs/1815847 Title: 16.04 install would get "can't install busybox-initramfs" error with Chinese Language for install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1815847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815847] [NEW] 16.04 install would get "can't install busybox-initramfs" error with Chinese Language for install
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 first screen (grub menu) 4. Continue as normal install process 5. After partition was finished, it would show "can't install busybox-initramfs" on the screen The error messages from console are: Feb 14 01:02:56 in-target: unexpected error: command not executed: 'sh -c debconf-apt-progress --no-progress --logstderr -- apt-get -q -y --no-remove install busybox-initramfs' ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: - https://bugs.launchpad.net/ubuntu/+filebug + 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 first screen (grub menu) + 4. Continue as normal install process + 5. After partition was finished, it would show "can't install busybox-initramfs" on the screen + + The error messages from console are: + Feb 14 01:02:56 in-target: unexpected error: command not executed: 'sh -c debconf-apt-progress --no-progress --logstderr -- apt-get -q -y --no-remove install busybox-initramfs' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815847 Title: 16.04 install would get "can't install busybox-initramfs" error with Chinese Language for install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1815847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815847] Re: 16.04 install would get "can't install busybox-initramfs" error with Chinese Language for install
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" https://bugs.launchpad.net/ubuntu/+bug/1815847/+attachment/5238502/+files/Lanuage-choose-screen.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815847 Title: 16.04 install would get "can't install busybox-initramfs" error with Chinese Language for install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1815847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815847] Re: 16.04 install would get "can't install busybox-initramfs" error with Chinese Language for install
** 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. https://bugs.launchpad.net/bugs/1815847 Title: 16.04 install would get "can't install busybox-initramfs" error with Chinese Language for install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1815847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802832] Re: ethtools report i40e as 10G instead the real 1G
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. https://bugs.launchpad.net/bugs/1802832 Title: ethtools report i40e as 10G instead the real 1G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802832] [NEW] ethtools report i40e as 10G instead the real 1G
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. https://bugs.launchpad.net/bugs/1802832 Title: ethtools report i40e as 10G instead the real 1G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796217] Re: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks"
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 memory stress cause "rcu_sched detected stalls on cpus/tasks" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796217] Re: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks"
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796217 Title: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796217] Re: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks"
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796217 Title: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
