[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-hwe-5.15 in 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 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2055238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-hwe-5.15 in 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 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2055238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-hwe-5.15 in 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 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2055238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-hwe-5.15 in 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 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2055238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-hwe-5.15 in 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 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2055238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2054860 Title: AMD-Vi Failed to allocate IRTE Status in linux-hwe-5.15 package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2054860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048988] Re: 1 time ib_umda loading fail during 105 power cycle
** Summary changed: - 1 time ib_umda lloading fail during 105 power cycle + 1 time ib_umda loading fail during 105 power cycle -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2048988 Title: 1 time ib_umda loading fail during 105 power cycle Status in linux-hwe-5.15 package in Ubuntu: New Bug description: found error log like below in 105 power cycles. Dec 23 02:09:27 192-168-111-160 root[5747]: openibd: ERROR: Failed loading kernel module ib_umad. Dec 23 02:09:27 192-168-111-160 root[5750]: openibd: ERROR: Failed loading kernel module ib_ipoib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2048988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048988] [NEW] 1 time ib_umda lloading fail during 105 power cycle
Public bug reported: found error log like below in 105 power cycles. Dec 23 02:09:27 192-168-111-160 root[5747]: openibd: ERROR: Failed loading kernel module ib_umad. Dec 23 02:09:27 192-168-111-160 root[5750]: openibd: ERROR: Failed loading kernel module ib_ipoib. ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2048988 Title: 1 time ib_umda lloading fail during 105 power cycle Status in linux-hwe-5.15 package in Ubuntu: New Bug description: found error log like below in 105 power cycles. Dec 23 02:09:27 192-168-111-160 root[5747]: openibd: ERROR: Failed loading kernel module ib_umad. Dec 23 02:09:27 192-168-111-160 root[5750]: openibd: ERROR: Failed loading kernel module ib_ipoib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2048988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048988] Re: 1 time ib_umda lloading fail during 105 power cycle
For cycle is successful. The related log is Dec 23 23:40:40 192-168-111-160 kernel: [0.00] Linux version 5.15.0-89-generic (buildd@bos03-amd64-016) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #99-Ubuntu SMP Mon Oct 30 20:42:41 UTC 2023 (Ubuntu 5.15.0-89.99-generic 5.15.126) Dec 23 23:40:40 192-168-111-160 systemd[1]: Starting openibd - configure Mellanox devices... Dec 23 23:40:40 192-168-111-160 root[5251]: openibd: running in auto mode Dec 23 23:40:40 192-168-111-160 openibd[5241]: Loading HCA driver and Access Layer:#033[60G[ #033[1;32mOK#033[0;39m ] Dec 23 23:40:40 192-168-111-160 systemd[1]: Finished openibd - configure Mellanox devices. Dec 23 23:40:53 192-168-111-160 root[7723]: openibd: Set node_desc for mlx5_0: 192-168-111-160 HCA-1 Dec 23 23:40:53 192-168-111-160 root[7725]: openibd: Set node_desc for mlx5_1: 192-168-111-160 HCA-2 Dec 23 23:40:53 192-168-111-160 root[7727]: openibd: Set node_desc for mlx5_10: 192-168-111-160 HCA-3 Dec 23 23:40:53 192-168-111-160 root[7729]: openibd: Set node_desc for mlx5_11: 192-168-111-160 HCA-4 Dec 23 23:40:53 192-168-111-160 root[7731]: openibd: Set node_desc for mlx5_12: 192-168-111-160 HCA-5 Dec 23 23:40:53 192-168-111-160 root[7733]: openibd: Set node_desc for mlx5_13: 192-168-111-160 HCA-6 Dec 23 23:40:53 192-168-111-160 root[7735]: openibd: Set node_desc for mlx5_2: 192-168-111-160 HCA-7 Dec 23 23:40:53 192-168-111-160 root[7737]: openibd: Set node_desc for mlx5_3: 192-168-111-160 HCA-8 Dec 23 23:40:53 192-168-111-160 root[7739]: openibd: Set node_desc for mlx5_4: 192-168-111-160 HCA-9 Dec 23 23:40:53 192-168-111-160 root[7741]: openibd: Set node_desc for mlx5_5: 192-168-111-160 HCA-10 Dec 23 23:40:53 192-168-111-160 root[7743]: openibd: Set node_desc for mlx5_6: 192-168-111-160 HCA-11 Dec 23 23:40:53 192-168-111-160 root[7745]: openibd: Set node_desc for mlx5_7: 192-168-111-160 HCA-12 Dec 23 23:40:53 192-168-111-160 root[7747]: openibd: Set node_desc for mlx5_8: 192-168-111-160 HCA-13 Dec 23 23:40:53 192-168-111-160 root[7749]: openibd: Set node_desc for mlx5_9: 192-168-111-160 HCA-14 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2048988 Title: 1 time ib_umda lloading fail during 105 power cycle Status in linux-hwe-5.15 package in Ubuntu: New Bug description: found error log like below in 105 power cycles. Dec 23 02:09:27 192-168-111-160 root[5747]: openibd: ERROR: Failed loading kernel module ib_umad. Dec 23 02:09:27 192-168-111-160 root[5750]: openibd: ERROR: Failed loading kernel module ib_ipoib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2048988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045882] Re: tegra-qspi NVDA1513:00: device reset failed
I was asked whether it relate to no actually device (LCD) connected and could be safely ignored? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045882 Title: tegra-qspi NVDA1513:00: device reset failed Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: The partner report below syslog error related to: Aug 30 09:10:48 localhost kernel: [7.335926] tegra186-gpio NVDA0508:00: invalid resource Aug 30 09:10:48 localhost kernel: [7.341446] tegra186-gpio NVDA0508:00: invalid resource Aug 30 09:10:48 localhost kernel: [ 53.419539] tegra-i2c NVDA0301:00: cannot use DMA: -19 Aug 30 09:10:48 localhost kernel: [ 53.424816] tegra-i2c NVDA0301:00: falling back to PIO Aug 30 09:10:48 localhost kernel: [ 53.508666] tegra-qspi NVDA1513:00: Adding to iommu group 15 Aug 30 09:10:48 localhost kernel: [ 53.510539] tegra-qspi NVDA1513:00: device reset failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2045882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045882] [NEW] tegra-qspi NVDA1513:00: device reset failed
Public bug reported: The partner report below syslog error related to: Aug 30 09:10:48 localhost kernel: [7.335926] tegra186-gpio NVDA0508:00: invalid resource Aug 30 09:10:48 localhost kernel: [7.341446] tegra186-gpio NVDA0508:00: invalid resource Aug 30 09:10:48 localhost kernel: [ 53.419539] tegra-i2c NVDA0301:00: cannot use DMA: -19 Aug 30 09:10:48 localhost kernel: [ 53.424816] tegra-i2c NVDA0301:00: falling back to PIO Aug 30 09:10:48 localhost kernel: [ 53.508666] tegra-qspi NVDA1513:00: Adding to iommu group 15 Aug 30 09:10:48 localhost kernel: [ 53.510539] tegra-qspi NVDA1513:00: device reset failed ** Affects: linux-nvidia-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045882 Title: tegra-qspi NVDA1513:00: device reset failed Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: The partner report below syslog error related to: Aug 30 09:10:48 localhost kernel: [7.335926] tegra186-gpio NVDA0508:00: invalid resource Aug 30 09:10:48 localhost kernel: [7.341446] tegra186-gpio NVDA0508:00: invalid resource Aug 30 09:10:48 localhost kernel: [ 53.419539] tegra-i2c NVDA0301:00: cannot use DMA: -19 Aug 30 09:10:48 localhost kernel: [ 53.424816] tegra-i2c NVDA0301:00: falling back to PIO Aug 30 09:10:48 localhost kernel: [ 53.508666] tegra-qspi NVDA1513:00: Adding to iommu group 15 Aug 30 09:10:48 localhost kernel: [ 53.510539] tegra-qspi NVDA1513:00: device reset failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2045882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041558] Re: failed to load firmware renesas_usb_fw.mem
No issues related to this log warning. One of our vendors raise it to me and let me checking. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2041558 Title: failed to load firmware renesas_usb_fw.mem Status in linux-firmware package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Invalid Bug description: the log show below: xhci_hcd :27:00.0: failed to load firmware renesas_usb_fw.mem, fallback to ROM From this below, it seems just need to add renesas_usb_fw.mem into the initrd. https://bbs.archlinux.org/viewtopic.php?pid=1922549#p1922549 When the firmware is required and is not present, kernel message: Direct firmware load for renesas_usb_fw.mem failed with error When the firmware is required and is an empty file, kernel message: FW has invalid version, followed by the above message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2041558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041558] [NEW] failed to load firmware renesas_usb_fw.mem
Public bug reported: the log show below: xhci_hcd :27:00.0: failed to load firmware renesas_usb_fw.mem, fallback to ROM >From this below, it seems just need to add renesas_usb_fw.mem into the initrd. https://bbs.archlinux.org/viewtopic.php?pid=1922549#p1922549 When the firmware is required and is not present, kernel message: Direct firmware load for renesas_usb_fw.mem failed with error When the firmware is required and is an empty file, kernel message: FW has invalid version, followed by the above message. ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2041558 Title: failed to load firmware renesas_usb_fw.mem Status in linux-hwe-5.15 package in Ubuntu: New Bug description: the log show below: xhci_hcd :27:00.0: failed to load firmware renesas_usb_fw.mem, fallback to ROM From this below, it seems just need to add renesas_usb_fw.mem into the initrd. https://bbs.archlinux.org/viewtopic.php?pid=1922549#p1922549 When the firmware is required and is not present, kernel message: Direct firmware load for renesas_usb_fw.mem failed with error When the firmware is required and is an empty file, kernel message: FW has invalid version, followed by the above message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2041558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012730] Re: lspci can't show physical slot on 22.04
** Description changed: - On 22.04 with ga-5.15-generic kernel the lspci -vvv can get physical + On 22.04 with ga-5.15-generic kernel the lspci -vvv can't get physical slot info, but it works on 5.4.0 kernel of 20.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2012730 Title: lspci can't show physical slot on 22.04 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: On 22.04 with ga-5.15-generic kernel the lspci -vvv can't get physical slot info, but it works on 5.4.0 kernel of 20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2012730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012730] Re: lspci can't show physical slot on 22.04
the 5.4.0 kernel which can show the physical slot info ** Attachment added: "the 5.4.0 kernel which can show the physical slot info" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2012730/+attachment/5657259/+files/image002.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2012730 Title: lspci can't show physical slot on 22.04 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: On 22.04 with ga-5.15-generic kernel the lspci -vvv can get physical slot info, but it works on 5.4.0 kernel of 20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2012730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012730] Re: lspci can't show physical slot on 22.04
the 5.15.0 kernel which can't show physical slot info ** Attachment added: "the 5.15.0 kernel which can't show physical slot info" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2012730/+attachment/5657260/+files/image003.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2012730 Title: lspci can't show physical slot on 22.04 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: On 22.04 with ga-5.15-generic kernel the lspci -vvv can get physical slot info, but it works on 5.4.0 kernel of 20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2012730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012730] [NEW] lspci can't show physical slot on 22.04
Public bug reported: On 22.04 with ga-5.15-generic kernel the lspci -vvv can get physical slot info, but it works on 5.4.0 kernel of 20.4 ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2012730 Title: lspci can't show physical slot on 22.04 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: On 22.04 with ga-5.15-generic kernel the lspci -vvv can get physical slot info, but it works on 5.4.0 kernel of 20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2012730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008050] Re: bmc virtual usb keyboard/mouse can't be detected when resting bmc
We tested on 20.4.5 iso ga-kernel and the lasted kernel of linux- image-5.4.0-144-generic_5.4.0-144.161_amd64.deb and both them works too. So this issues have been fixed both on 20.04 ga-kernel and hwe-kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2008050 Title: bmc virtual usb keyboard/mouse can't be detected when resting bmc Status in linux-hwe-5.4 package in Ubuntu: New Bug description: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of 3.10.0-1160.317.x86_64, the keyboard/mouse of KVM keeps working when resting ibm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2008050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008050] Re: bmc virtual usb keyboard/mouse can't be detected when resting bmc
Summary for more testing results from zte: 1. All works for 20.04.2-20.4.5 hwe-kernel(v5.8.0-41, v5.11.0-27, v5.13.0-30, v5.15.0-46), which we tested boot from iso. 2. It works too if we detach KVM (close browser)before reset BMC. 3. After reset BMC, to unbind "echo '1-7' | sudo tee /sys/bus/usb/drivers/usb/unbind" virtual hub, open KVM can work too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2008050 Title: bmc virtual usb keyboard/mouse can't be detected when resting bmc Status in linux-hwe-5.4 package in Ubuntu: New Bug description: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of 3.10.0-1160.317.x86_64, the keyboard/mouse of KVM keeps working when resting ibm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2008050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008050] Re: bmc virtual usb keyboard/mouse can't be detected when resting bmc
Tried to reload hid and xhci_pic and seems no chance too -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2008050 Title: bmc virtual usb keyboard/mouse can't be detected when resting bmc Status in linux-hwe-5.4 package in Ubuntu: New Bug description: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of 3.10.0-1160.317.x86_64, the keyboard/mouse of KVM keeps working when resting ibm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2008050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008050] Re: bmc virtual usb keyboard/mouse can't be detected when resting bmc
The dmesg for virutal keyboad/mouse when reset os: Feb 19 20:55:17 sysadmin kernel: [4.904530] usb 1-7.1: New USB device found, idVendor=046b, idProduct=ff10, bcdDevice= 1.00 Feb 19 20:55:17 sysadmin kernel: [4.904955] usb 1-7.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 19 20:55:17 sysadmin kernel: [4.905370] usb 1-7.1: Product: Virtual Keyboard and Mouse Feb 19 20:55:17 sysadmin kernel: [4.905779] usb 1-7.1: Manufacturer: American Megatrends Inc. Feb 19 20:55:17 sysadmin kernel: [4.916508] nouveau :17:00.0: fb: 15360 MiB GDDR6 Feb 19 20:55:17 sysadmin kernel: [4.917164] hidraw: raw HID events driver (C) Jiri Kosina Feb 19 20:55:17 sysadmin kernel: [4.922070] usbcore: registered new interface driver usbhid Feb 19 20:55:17 sysadmin kernel: [4.922534] usbhid: USB HID core driver Feb 19 20:55:17 sysadmin kernel: [4.924758] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci:00/:00:14.0/usb1/1-7/1-7.1/1-7.1:1.0/0003:046B:FF10. 0001/input/input1 Feb 19 20:55:17 sysadmin kernel: [4.925350] nouveau :17:00.0: DRM: VRAM: 15360 MiB Feb 19 20:55:17 sysadmin kernel: [4.925677] hid-generic 0003:046B:FF10.0001: input,hidraw0: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-000 0:00:14.0-7.1/input0 Feb 19 20:55:17 sysadmin kernel: [4.926066] nouveau :17:00.0: DRM: GART: 536870912 MiB Feb 19 20:55:17 sysadmin kernel: [4.927045] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci:00/:00:14.0/usb1/1-7/1-7.1/1-7.1:1.1/0003:046B:FF10. 0002/input/input2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2008050 Title: bmc virtual usb keyboard/mouse can't be detected when resting bmc Status in linux-hwe-5.4 package in Ubuntu: New Bug description: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of 3.10.0-1160.317.x86_64, the keyboard/mouse of KVM keeps working when resting ibm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2008050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008050] Re: bmc virtual usb keyboard/mouse can't be detected when resting bmc
We also tested virtual CD, it seems worked fine. Below is udevadm monitor output: KERNEL[310.544164] unbind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) KERNEL[310.544206] remove /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) KERNEL[310.544691] unbind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) KERNEL[310.544737] remove /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) UDEV [310.545677] unbind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) UDEV [310.546176] remove /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) UDEV [310.547452] unbind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) UDEV [310.547917] remove /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) KERNEL[324.302442] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) KERNEL[324.303754] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) KERNEL[324.304074] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14 (scsi) KERNEL[324.304193] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/scsi_host/host14 (scsi_host) KERNEL[324.304238] bind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) KERNEL[324.304384] bind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) UDEV [324.306827] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) UDEV [324.308683] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) UDEV [324.309922] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14 (scsi) UDEV [324.311232] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/scsi_host/host14 (scsi_host) UDEV [324.312534] bind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0 (usb) UDEV [324.314064] bind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3 (usb) KERNEL[325.337392] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0 (scsi) KERNEL[325.337466] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0 (scsi) UDEV [325.338773] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0 (scsi) UDEV [325.340412] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0 (scsi) KERNEL[325.388105] add /devices/virtual/bdi/11:0 (bdi) KERNEL[325.388215] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/block/sr0 (block) UDEV [325.388841] add /devices/virtual/bdi/11:0 (bdi) KERNEL[325.389407] add /kernel/slab/bdev_cache/cgroup/bdev_cache(310:systemd-udevd.service) (cgroup) KERNEL[325.389936] bind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0 (scsi) KERNEL[325.389997] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/scsi_device/14:0:0:0 (scsi_device) KERNEL[325.390106] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/scsi_generic/sg7 (scsi_generic) UDEV [325.390135] add /kernel/slab/bdev_cache/cgroup/bdev_cache(310:systemd-udevd.service) (cgroup) KERNEL[325.390209] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/bsg/14:0:0:0 (bsg) KERNEL[325.432910] change /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/block/sr0 (block) UDEV [326.956962] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/block/sr0 (block) UDEV [326.958339] bind /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0 (scsi) UDEV [326.960110] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/scsi_device/14:0:0:0 (scsi_device) UDEV [326.960752] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/scsi_generic/sg7 (scsi_generic) UDEV [326.962490] add /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/bsg/14:0:0:0 (bsg) UDEV [329.655233] change /devices/pci:00/:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/host14/target14:0:0/14:0:0:0/block/sr0 (block) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2008050 Title: bmc virtual usb keyboard/mouse can't be detected when resting bmc Status in linux-hwe-5.4 package in Ubuntu: New Bug description: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of
[Kernel-packages] [Bug 2008050] Re: bmc virtual usb keyboard/mouse can't be detected when resting bmc
During testing, we can found disconnect log in dmesg and not plugin/connect info: Feb 19 21:14:16 sysadmin kernel: [ 1156.328006] usb 1-7.1: USB disconnect, device number 3 Feb 19 21:17:01 sysadmin CRON[6201]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 19 21:22:15 sysadmin systemd-sysctl[1446]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Feb 19 21:22:15 sysadmin systemd-sysctl[1446]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Feb 19 21:22:15 sysadmin kernel: [0.00] Linux version 5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 (Ubuntu 5.4.0-26.30-generic 5.4.30) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2008050 Title: bmc virtual usb keyboard/mouse can't be detected when resting bmc Status in linux-hwe-5.4 package in Ubuntu: New Bug description: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of 3.10.0-1160.317.x86_64, the keyboard/mouse of KVM keeps working when resting ibm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2008050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008050] [NEW] bmc virtual usb keyboard/mouse can't be detected when resting bmc
Public bug reported: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of 3.10.0-1160.317.x86_64, the keyboard/mouse of KVM keeps working when resting ibm. ** Affects: linux-hwe-5.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2008050 Title: bmc virtual usb keyboard/mouse can't be detected when resting bmc Status in linux-hwe-5.4 package in Ubuntu: New Bug description: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of 3.10.0-1160.317.x86_64, the keyboard/mouse of KVM keeps working when resting ibm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2008050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008037] Re: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350
This was found at 20.04.1 ga-kernel of 5.15.0-60 which is lasted at the time and on a new intel cpu of Intel(R) Xeon(R) Gold 6438Y+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008037 Title: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: Kernel taitned 512 ude to warning of below: #grep taint /var/log/syslog -b2 235407-Feb 20 15:27:14 xfusion kernel: [3.779483] WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 235561-Feb 20 15:27:14 xfusion kernel: [3.779495] Modules linked in: 235627:Feb 20 15:27:14 xfusion kernel: [3.779499] CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-60-generic #66-Ubuntu 235746-Feb 20 15:27:14 xfusion kernel: [3.779505] Hardware name: XFUSION 2288 V7/BC15MBSC, BIOS 2.00.20.Btg 02/08/2023 235862-Feb 20 15:27:14 xfusion kernel: [3.779509] RIP: 0010:uncore_insert_box_info+0x134/0x350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2008037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008037] Re: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350
#grep -i 'call trace' /var/log/dmesg -b19 113581-[3.779479] kernel: [ cut here ] 113641-[3.779483] kernel: WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 113771-[3.779495] kernel: Modules linked in: 113813-[3.779499] kernel: CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-60-generic #66-Ubuntu 113908-[3.779505] kernel: Hardware name: XFUSION 2288 V7/BC15MBSC, BIOS 2.00.20.Btg 02/08/2023 114000-[3.779509] kernel: RIP: 0010:uncore_insert_box_info+0x134/0x350 114068-[3.779515] kernel: Code: c2 01 48 83 c0 04 39 d1 0f 8e c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 42 95 32 00 4c 89 f7 e8 3a 95 32 00 5b 41 5c 41 114291-[3.779521] kernel: RSP: :ff5bc606001fbc98 EFLAGS: 00010246 114358-[3.779527] kernel: RAX: 0008 RBX: RCX: 0003 114447-[3.779531] kernel: RDX: 0002 RSI: 00018000 RDI: 0003 114536-[3.779534] kernel: RBP: ff5bc606001fbcc0 R08: 0010 R09: ff456694ca656f20 114625-[3.779538] kernel: R10: ff456694ca32aec8 R11: e000 R12: ff4566984965a9c0 114714-[3.779541] kernel: R13: ff5bc606001fbcf8 R14: ff456694ca656000 R15: ff456694ca656f20 114803-[3.779545] kernel: FS: () GS:ff4566982f80() knlGS: 114903-[3.779549] kernel: CS: 0010 DS: ES: CR0: 80050033 114976-[3.779553] kernel: CR2: CR3: 0007ba610001 CR4: 00771ee0 115065-[3.779556] kernel: DR0: DR1: DR2: 115154-[3.779559] kernel: DR3: DR6: fffe07f0 DR7: 0400 115243-[3.779563] kernel: PKRU: 5554 115281:[3.779565] kernel: Call Trace: 115316-[3.779569] kernel: 115347-[3.779573] kernel: parse_discovery_table.isra.0+0x162/0x1a0 115412-[3.779580] kernel: intel_uncore_has_discovery_tables+0x19e/0x270 115482-[3.779585] kernel: ? type_pmu_register+0x1c/0x42 115536-[3.779593] kernel: intel_uncore_init+0xe3/0x226 115589-[3.779597] kernel: ? type_pmu_register+0x42/0x42 115643-[3.779601] kernel: do_one_initcall+0x46/0x1e0 115694-[3.779608] kernel: do_initcalls+0x12f/0x159 115743-[3.779615] kernel: kernel_init_freeable+0x162/0x1b5 115800-[3.779622] kernel: ? rest_init+0x100/0x100 115848-[3.779630] kernel: kernel_init+0x1b/0x150 115895-[3.779636] kernel: ? rest_init+0x100/0x100 115943-[3.779641] kernel: ret_from_fork+0x1f/0x30 115991-[3.779647] kernel: 116023-[3.779650] kernel: ---[ end trace 3503eae85cdd4085 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008037 Title: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: Kernel taitned 512 ude to warning of below: #grep taint /var/log/syslog -b2 235407-Feb 20 15:27:14 xfusion kernel: [3.779483] WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 235561-Feb 20 15:27:14 xfusion kernel: [3.779495] Modules linked in: 235627:Feb 20 15:27:14 xfusion kernel: [3.779499] CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-60-generic #66-Ubuntu 235746-Feb 20 15:27:14 xfusion kernel: [3.779505] Hardware name: XFUSION 2288 V7/BC15MBSC, BIOS 2.00.20.Btg 02/08/2023 235862-Feb 20 15:27:14 xfusion kernel: [3.779509] RIP: 0010:uncore_insert_box_info+0x134/0x350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2008037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008037] [NEW] kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350
Public bug reported: Kernel taitned 512 ude to warning of below: #grep taint /var/log/syslog -b2 235407-Feb 20 15:27:14 xfusion kernel: [3.779483] WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 235561-Feb 20 15:27:14 xfusion kernel: [3.779495] Modules linked in: 235627:Feb 20 15:27:14 xfusion kernel: [3.779499] CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-60-generic #66-Ubuntu 235746-Feb 20 15:27:14 xfusion kernel: [3.779505] Hardware name: XFUSION 2288 V7/BC15MBSC, BIOS 2.00.20.Btg 02/08/2023 235862-Feb 20 15:27:14 xfusion kernel: [3.779509] RIP: 0010:uncore_insert_box_info+0x134/0x350 ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008037 Title: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: Kernel taitned 512 ude to warning of below: #grep taint /var/log/syslog -b2 235407-Feb 20 15:27:14 xfusion kernel: [3.779483] WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 235561-Feb 20 15:27:14 xfusion kernel: [3.779495] Modules linked in: 235627:Feb 20 15:27:14 xfusion kernel: [3.779499] CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-60-generic #66-Ubuntu 235746-Feb 20 15:27:14 xfusion kernel: [3.779505] Hardware name: XFUSION 2288 V7/BC15MBSC, BIOS 2.00.20.Btg 02/08/2023 235862-Feb 20 15:27:14 xfusion kernel: [3.779509] RIP: 0010:uncore_insert_box_info+0x134/0x350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2008037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1976511] Re: [SRU]x86, sched: Treat Intel SNC topology as default, COD as exception
Below is full text from syslog ug 31 18:47:45 ubuntu kernel: [8.758773] x86: Booting SMP configuration: Aug 31 18:47:45 ubuntu kernel: [8.762673] node #0, CPUs:#1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15 Aug 31 18:47:45 ubuntu kernel: [8.850673] node #1, CPUs: #16 Aug 31 18:47:45 ubuntu kernel: [2.999509] [ cut here ] Aug 31 18:47:45 ubuntu kernel: [2.999509] sched: CPU #16's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. Aug 31 18:47:45 ubuntu kernel: [2.999509] WARNING: CPU: 16 PID: 0 at arch/x86/kernel/smpboot.c:415 topology_sane.isra.0+0x70/0x80 Aug 31 18:47:45 ubuntu kernel: [2.999509] Modules linked in: Aug 31 18:47:45 ubuntu kernel: [2.999509] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-26-generic #30-Ubuntu Aug 31 18:47:45 ubuntu kernel: [2.999509] Hardware name: Quanta Cloud Technology Inc. QuantaEdge EGX66Y-2U/S6YQ-MB (LBG-T, RTT), BIOS 2A02 05/19/2022 Aug 31 18:47:45 ubuntu kernel: [2.999509] RIP: 0010:topology_sane.isra.0+0x70/0x80 Aug 31 18:47:45 ubuntu kernel: [2.999509] Code: 5d c3 80 3d dc a1 7a 01 00 75 ec 41 89 d9 45 89 e0 44 89 d9 44 89 d6 48 c7 c7 b0 06 75 94 c6 05 c0 a1 7a 01 01 e8 1b dc 03 00 <0f> 0b eb c9 66 66 2e 0f 1f 84 00 00 00 00 00 90 55 be 00 04 00 00 Aug 31 18:47:45 ubuntu kernel: [2.999509] RSP: :a96218c07ea8 EFLAGS: 00010086 Aug 31 18:47:45 ubuntu kernel: [2.999509] RAX: RBX: RCX: 0208 Aug 31 18:47:45 ubuntu kernel: [2.999509] RDX: 0001 RSI: 0086 RDI: 0046 Aug 31 18:47:45 ubuntu kernel: [2.999509] RBP: a96218c07eb8 R08: 0208 R09: 0010 Aug 31 18:47:45 ubuntu kernel: [2.999509] R10: 94f92228 R11: a96218c07d10 R12: 0001 Aug 31 18:47:45 ubuntu kernel: [2.999509] R13: R14: 9d2c3fc10260 R15: Aug 31 18:47:45 ubuntu kernel: [2.999509] FS: () GS:9d6c3f80() knlGS: Aug 31 18:47:45 ubuntu kernel: [2.999509] CS: 0010 DS: ES: CR0: 80050033 Aug 31 18:47:45 ubuntu kernel: [2.999509] CR2: CR3: 0052c160a001 CR4: 00760ee0 Aug 31 18:47:45 ubuntu kernel: [2.999509] DR0: DR1: DR2: Aug 31 18:47:45 ubuntu kernel: [2.999509] DR3: DR6: fffe0ff0 DR7: 0400 Aug 31 18:47:45 ubuntu kernel: [2.999509] PKRU: Aug 31 18:47:45 ubuntu kernel: [2.999509] Call Trace: Aug 31 18:47:45 ubuntu kernel: [2.999509] set_cpu_sibling_map+0x159/0x590 Aug 31 18:47:45 ubuntu kernel: [2.999509] start_secondary+0x6f/0x1c0 Aug 31 18:47:45 ubuntu kernel: [2.999509] secondary_startup_64+0xa4/0xb0 Aug 31 18:47:45 ubuntu kernel: [2.999509] ---[ end trace 4403443dce444e18 ]--- Aug 31 18:47:45 ubuntu kernel: [9.047785] #17 #18 #19 #20 #21 #22 #23 #24 #25 #26 #27 #28 #29 #30 #31 Aug 31 18:47:45 ubuntu kernel: [9.138674] node #2, CPUs: #32 Aug 31 18:47:45 ubuntu kernel: [2.999509] smpboot: CPU 32 Converting physical 0 to logical die 1 Aug 31 18:47:45 ubuntu kernel: [9.238774] #33 #34 #35 #36 #37 #38 #39 #40 #41 #42 #43 #44 #45 #46 #47 Aug 31 18:47:45 ubuntu kernel: [9.326672] node #3, CPUs: #48 #49 #50 #51 #52 #53 #54 #55 #56 #57 #58 #59 #60 #61 #62 #63 Aug 31 18:47:45 ubuntu kernel: [9.420851] smp: Brought up 4 nodes, 64 CPUs Aug 31 18:47:45 ubuntu kernel: [9.426672] smpboot: Max logical packages: 2 Aug 31 18:47:45 ubuntu kernel: [9.430673] smpboot: Total of 64 processors activated (281650.20 BogoMIPS) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976511 Title: [SRU]x86, sched: Treat Intel SNC topology as default, COD as exception Status in linux package in Ubuntu: Confirmed Bug description: 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: [
[Kernel-packages] [Bug 1976511] Re: [SRU]x86, sched: Treat Intel SNC topology as default, COD as exception
Another partner reported below which might be similar. The kernel version is 5.4.0-26-generic which is not lasted, so they was asked to upgrade and verify again. Aug 31 18:47:45 ubuntu kernel: [2.999509] Call Trace: Aug 31 18:47:45 ubuntu kernel: [2.999509] set_cpu_sibling_map+0x159/0x590 Aug 31 18:47:45 ubuntu kernel: [2.999509] start_secondary+0x6f/0x1c0 Aug 31 18:47:45 ubuntu kernel: [2.999509] secondary_startup_64+0xa4/0xb0 Aug 31 18:47:45 ubuntu kernel: [2.999509] ---[ end trace 4403443dce444e18 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976511 Title: [SRU]x86, sched: Treat Intel SNC topology as default, COD as exception Status in linux package in Ubuntu: Confirmed Bug description: 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 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1976511] Re: kernel taint ( warning ) caused by smpboot.c: on 5.4.0
Tested and results for Jeffrey's comment#5: a. Yes, We’ve check other whitley's project (different with G292 series) on 20.04 and 18.04. the miscellanea/kernel_taint_test fail in 5.4 kernel, PASS in 20.04 hwe 5.13 kernel. b. G292-280 also PASS this item on the 20.04 hwe-edge with the 5.15 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: 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 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: 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 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: 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 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: Incomplete Bug description: 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 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: Incomplete Bug description: 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 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: New Bug description: 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:
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1971576
Title:
SATA device hot plug regression on AMD EPYC (Asus) server
Status in linux package in Ubuntu:
Confirmed
Bug description:
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"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server Status in linux package in Ubuntu: Incomplete Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server Status in linux package in Ubuntu: Incomplete Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server Status in linux package in Ubuntu: Incomplete Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server Status in linux package in Ubuntu: Incomplete Bug description: 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory Status in linux package in Ubuntu: Incomplete Bug description: 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". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory Status in linux package in Ubuntu: Incomplete Bug description: 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". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory Status in linux package in Ubuntu: Incomplete Bug description: 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". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory Status in linux package in Ubuntu: Incomplete Bug description: 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". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory Status in linux package in Ubuntu: Incomplete Bug description: 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". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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,
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862720 Title: kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel Status in linux package in Ubuntu: Incomplete Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802832 Title: ethtools report i40e as 10G instead the real 1G Status in linux package in Ubuntu: New Bug description: ethtools report i40e as 10G instead the real 1G on Ubuntu 16.04.5 ga- kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802832 Title: ethtools report i40e as 10G instead the real 1G Status in linux package in Ubuntu: New Bug description: ethtools report i40e as 10G instead the real 1G on Ubuntu 16.04.5 ga- kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796217 Title: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks" Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: We are facing a problem during the certification test. System always stop at below screen while memory stress. In the following re- producing, kernel seems un-normal and it can’t capture above info into the syslog or kernel log, but the console will show same warning as screen shot attachment file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796217 Title: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks" Status in linux package in Ubuntu: New Bug description: We are facing a problem during the certification test. System always stop at below screen while memory stress. In the following re- producing, kernel seems un-normal and it can’t capture above info into the syslog or kernel log, but the console will show same warning as screen shot attachment file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796217 Title: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks" Status in linux package in Ubuntu: New Bug description: We are facing a problem during the certification test. System always stop at below screen while memory stress. In the following re- producing, kernel seems un-normal and it can’t capture above info into the syslog or kernel log, but the console will show same warning as screen shot attachment file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796217] [NEW] Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks"
Public bug reported: We are facing a problem during the certification test. System always stop at below screen while memory stress. In the following re-producing, kernel seems un-normal and it can’t capture above info into the syslog or kernel log, but the console will show same warning as screen shot attachment file. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796217 Title: Qunata server memory stress cause "rcu_sched detected stalls on cpus/tasks" Status in linux package in Ubuntu: New Bug description: We are facing a problem during the certification test. System always stop at below screen while memory stress. In the following re- producing, kernel seems un-normal and it can’t capture above info into the syslog or kernel log, but the console will show same warning as screen shot attachment file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel
hi Guilherme, The partner have tested both for 4.16.0 and 4.15.1 ( I guess it is newer than 4.15.0-34), it was reported that the issues is same. The 4.15.1 testing results are as below: zlmao@zlmao-T460s:~/tmp$ cat test_result.txt uname -r 4.15.1-041501-generic cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.15.1-041501-generic root=UUID=3e875566-3c1b-4bda-a869-6eb59ff1624a ro nvme_core.multipath=0 ls -l /sys/block/* lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop0 -> ../devices/virtual/block/loop0 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop1 -> ../devices/virtual/block/loop1 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop2 -> ../devices/virtual/block/loop2 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop3 -> ../devices/virtual/block/loop3 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop4 -> ../devices/virtual/block/loop4 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop5 -> ../devices/virtual/block/loop5 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop6 -> ../devices/virtual/block/loop6 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/loop7 -> ../devices/virtual/block/loop7 lrwxrwxrwx 1 root root 0 Sep 28 10:13 /sys/block/nvme0n1 -> ../devices/pci:80/:80:03.2/:83:00.0/nvme/nvme2/nvme0n1 lrwxrwxrwx 1 root root 0 Sep 28 10:13 /sys/block/nvme1n1 -> ../devices/pci:80/:80:03.3/:84:00.0/nvme/nvme3/nvme1n1 lrwxrwxrwx 1 root root 0 Sep 28 10:09 /sys/block/nvme1n2 -> ../devices/pci:80/:80:03.3/:84:00.0/nvme/nvme3/nvme1n2 lrwxrwxrwx 1 root root 0 Sep 28 10:13 /sys/block/nvme2n1 -> ../devices/pci:80/:80:03.0/:81:00.0/nvme/nvme0/nvme2n1 lrwxrwxrwx 1 root root 0 Sep 28 10:13 /sys/block/nvme3n1 -> ../devices/pci:80/:80:03.1/:82:00.0/nvme/nvme1/nvme3n1 zlmao@zlmao-T460s:~/tmp$ thanks, Mao -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot with 4.15.0 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: nvme device name such as /dev/nvme?n?p? would be floated that is symbol link to different real ssd device after reboot in 4.15.0 kernel for 16.04.5 HWE and 18.04 GA-kernel. This are not found on 16.04.5 GA- kernel ( 4.4.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel
@Guiherme Firstly, thank you much to provide those inforamtion. I asked customer to check on 4.15.0-34 with kernel parameter of "nvme_core.multipath=0", it was reported the same ( nvme device name would be changed every reboot). ** Attachment added: "nvme name mismatch screen shoot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+attachment/5192975/+files/image003.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot with 4.15.0 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: nvme device name such as /dev/nvme?n?p? would be floated that is symbol link to different real ssd device after reboot in 4.15.0 kernel for 16.04.5 HWE and 18.04 GA-kernel. This are not found on 16.04.5 GA- kernel ( 4.4.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel
The log which collect via apport-cli --save=/tmp/apport-log linux ** Attachment added: "apport-cli log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+attachment/5191267/+files/apport-log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot with 4.15.0 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: nvme device name such as /dev/nvme?n?p? would be floated that is symbol link to different real ssd device after reboot in 4.15.0 kernel for 16.04.5 HWE and 18.04 GA-kernel. This are not found on 16.04.5 GA- kernel ( 4.4.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
@AaronMa Do you have docs for how to compile a new kernel. I can found below doc link https://help.ubuntu.com/community/Kernel/Compile But it seems a bit old. The other difficult is how to get compile config from d-i iso kernel. I found if I use a kernel from running/installed system to replace d-i iso kernel, it would hang (died) after booting in the first language selection screen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
Dann, For the wanland issues, I understood it as comments in #15, that is: Blur screen for GDM login was caused by wayland, it can be fix by force to use Xorg in /etc/gdm3/customer.conf to uncoment WaylandEnable=false Is this right for your wanland issues on D05? In 18.04, we found 2 issues on Huawei X86 server. One is screen blur during d-i install on UEFI model in Language selection screen, but it works for legacy bios model. The other is after start GUI (x-window or Ubuntu desktop). After we sucessfully installed 18.04 in legacy bios model on X86 Huawei server, I tried to start X-windows via apt-get install ubuntu-dekstop and reboot, we would get this blur screen again. This seems caused by this wanyland and can be fixed by this "WaylandEnable=false". As I know, this wayland issues have been happened for D05 but I don't think D05 have above issues during install. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
For #37-#39 This screen blur issues during install are only happened on Huawei X86 server for 18.04 and 18.04.1 d-i iso. As I know, 18.04 and even 18.04.1 ARM64 iso works fine with this new hibmc-drm module for installation on Hisilicon D05 board. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
For #37 screen shot and #39. We found this wayland issues for 18.04 and Huawei x86 server, but it seems no for 18.04.1. In my test, apt-get install ubuntu-desktop and reboot works fine. For #37 "Why would hibmc_drm be arm64-specific?", I guess it might because vendors (sm750 vga) have already provided driver x86. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
Hisilicon team said this driver (hibmc_drm) are only for arm64. For X86 architecture, it need to use default driver for this SM750. It seems we incorrectly include this model in X86. Hisicon team have plans to fix in upstream source code which to limit this modules configure options only to arm64 to prevent someone compile (configure) it for x86. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
Huawei hisilicon team thought it might be caused by hibmc_drm which are upstream and included in v4.10 kernel for their ARM64 server. It is right. After disable this module by: modprobe.blacklist=hibmc_drm In the grub whiling booting iso. The install screen blur was disappeared. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
In case 18.04.1 server and destop iso use same kernel of v4.15.0-29 and the GUI works fine on destop, so the kernel should not be blamed. In 18.04.1 server installation, if I kill bterm process of below: /usr/bin/bterm -f /lib/unifont.bgf -l C.UTF-i /lib/debian-installer/menu Some blur picture would be gone. Please see attach screen shot. ** Attachment added: "blur screen in install and no blur after kill bterm" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5182032/+files/blur-sceen-and-after-bterm-kill-scren%28no%20blur%29.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
Tested on 17.10 server d-i install, it would be screen blur too during installation, the kernel is 4.13.0. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
Tested with 18.04.1 Desktop, it wouldn't screen blur. The kernel log are enclosed. ** Attachment added: "18.04.1 desktop install kernel log (no screen blur)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5181977/+files/kern.log-18.04.1-desktop-noblur.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
ACPI Exception have been reported here and it seems not related to screen blur https://bugzilla.kernel.org/show_bug.cgi?id=198167 ** Bug watch added: Linux Kernel Bug Tracker #198167 https://bugzilla.kernel.org/show_bug.cgi?id=198167 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
In the screen blur kernel syslog, it show below error which 16.04.5 GA kernel don't have this error: ... Aug 21 10:25:50 kernel: [0.589408] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) (repeated 942 lines) ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
I test 16.04.5 ga-kernel would not be screen blur but the hwe- kernel(4.15.0-29) which is same as 18.04.1 would become screen blur. The 16.04.5 hwe (blur) syslog are enclosed. ** Attachment added: "16.04.5 hwe-kernel (4.15.0-29) is blur" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5179078/+files/syslog-16.04.05-hwe-4.15.0-29-blur.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
