[Kernel-packages] [Bug 1824372] Re: mlx5 : not able to set a high MTU on the representor port for a VF
Sorry for various reasons I won't be able to test 20.04 -- 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/1824372 Title: mlx5 : not able to set a high MTU on the representor port for a VF Status in linux package in Ubuntu: Incomplete Bug description: Hi, Using Ubuntu 18.04, kernel 4.15.0-47, with a Mellanox MCX556M-ECAT-S25 [1]. With the distro driver, it's impossible to increase the MTU of a representor port : $ sudo ip li set enp50s0f0_0 mtu 1501 RTNETLINK answers: Invalid argument Whereas with the OFED driver [2], I can set it up to 9978 : $ sudo ip li set mtu 9978 enp50s0f0_0 $ This is blocking to use OVS offloading with jumbo frames. Could we please get the feature in the distro driver ? Thanks ! Steps to create the representor : echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs echo :32:00.3 | sudo tee /sys/bus/pci/drivers/mlx5_core/unbind sudo devlink dev eswitch set pci/:32:00.0 mode switchdev echo :32:00.2 | sudo tee /sys/bus/pci/drivers/mlx5_core/bind [1] http://www.mellanox.com/related-docs/prod_adapter_cards /PB_ConnectX-5_VPI_Card_SocketDirect.pdf [2] http://www.mellanox.com/page/mlnx_ofed_eula?mtag=linux_sw_drivers=downloads=ofed=MLNX_OFED-4.5-1.0.1.0=MLNX_OFED_LINUX-4.5-1.0.1.0-ubuntu18.04-x86_64.tgz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 11 14:18 seq crw-rw 1 root audio 116, 33 Apr 11 14:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 11 14:42:57 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=UUID=89c8c952-93fa-499c-bebe-fd9f4c4fbedb ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.2:bd02/21/2019:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824372/+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 1826376] Re: cxgb4 : no VXLAN offloading with distro driver, only with OFED drivers
Sorry I won't be able to test 20.04 as I don't have a Chelsio NIC anymore -- 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/1826376 Title: cxgb4 : no VXLAN offloading with distro driver, only with OFED drivers Status in linux package in Ubuntu: Incomplete Bug description: Hi, Using ubuntu 18.04 with kernel 4.15.0-47-generic, my Chelsio NIC can't offload VXLAN with the distro drivers (features "tx-udp_tnl- segmentation" and "tx-udp_tnl-csum-segmentation"), but with the OFED driver ("ChelsioUwire-3.10.0.0"), it can. Can we please get this in the distro driver ? Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 19 14:48 seq crw-rw 1 root audio 116, 33 Apr 19 14:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 25 08:53:20 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro Super Server PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=UUID=7b06790c-9447-446a-b1cf-b25104638b26 ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.2:bd02/21/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826376/+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 1824372] Re: mlx5 : not able to set a high MTU on the representor port for a VF
Actually the cma_alloc error is present much before VF creation. dmesg is attached. -- 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/1824372 Title: mlx5 : not able to set a high MTU on the representor port for a VF Status in linux package in Ubuntu: Confirmed Bug description: Hi, Using Ubuntu 18.04, kernel 4.15.0-47, with a Mellanox MCX556M-ECAT-S25 [1]. With the distro driver, it's impossible to increase the MTU of a representor port : $ sudo ip li set enp50s0f0_0 mtu 1501 RTNETLINK answers: Invalid argument Whereas with the OFED driver [2], I can set it up to 9978 : $ sudo ip li set mtu 9978 enp50s0f0_0 $ This is blocking to use OVS offloading with jumbo frames. Could we please get the feature in the distro driver ? Thanks ! Steps to create the representor : echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs echo :32:00.3 | sudo tee /sys/bus/pci/drivers/mlx5_core/unbind sudo devlink dev eswitch set pci/:32:00.0 mode switchdev echo :32:00.2 | sudo tee /sys/bus/pci/drivers/mlx5_core/bind [1] http://www.mellanox.com/related-docs/prod_adapter_cards /PB_ConnectX-5_VPI_Card_SocketDirect.pdf [2] http://www.mellanox.com/page/mlnx_ofed_eula?mtag=linux_sw_drivers=downloads=ofed=MLNX_OFED-4.5-1.0.1.0=MLNX_OFED_LINUX-4.5-1.0.1.0-ubuntu18.04-x86_64.tgz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 11 14:18 seq crw-rw 1 root audio 116, 33 Apr 11 14:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 11 14:42:57 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=UUID=89c8c952-93fa-499c-bebe-fd9f4c4fbedb ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.2:bd02/21/2019:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824372/+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 1824372] Re: mlx5 : not able to set a high MTU on the representor port for a VF
I am unable to test with latest mainline (5.1.0-050100rc6-generic) as the creation of a single VF starts spamming dmesg with "cma: cma_alloc: alloc failed, req-size: 1 pages, ret: -12" ** Tags added: kernel-bug-exists-upstream -- 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/1824372 Title: mlx5 : not able to set a high MTU on the representor port for a VF Status in linux package in Ubuntu: Confirmed Bug description: Hi, Using Ubuntu 18.04, kernel 4.15.0-47, with a Mellanox MCX556M-ECAT-S25 [1]. With the distro driver, it's impossible to increase the MTU of a representor port : $ sudo ip li set enp50s0f0_0 mtu 1501 RTNETLINK answers: Invalid argument Whereas with the OFED driver [2], I can set it up to 9978 : $ sudo ip li set mtu 9978 enp50s0f0_0 $ This is blocking to use OVS offloading with jumbo frames. Could we please get the feature in the distro driver ? Thanks ! Steps to create the representor : echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs echo :32:00.3 | sudo tee /sys/bus/pci/drivers/mlx5_core/unbind sudo devlink dev eswitch set pci/:32:00.0 mode switchdev echo :32:00.2 | sudo tee /sys/bus/pci/drivers/mlx5_core/bind [1] http://www.mellanox.com/related-docs/prod_adapter_cards /PB_ConnectX-5_VPI_Card_SocketDirect.pdf [2] http://www.mellanox.com/page/mlnx_ofed_eula?mtag=linux_sw_drivers=downloads=ofed=MLNX_OFED-4.5-1.0.1.0=MLNX_OFED_LINUX-4.5-1.0.1.0-ubuntu18.04-x86_64.tgz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 11 14:18 seq crw-rw 1 root audio 116, 33 Apr 11 14:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 11 14:42:57 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=UUID=89c8c952-93fa-499c-bebe-fd9f4c4fbedb ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.2:bd02/21/2019:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824372/+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 1824372] Re: mlx5 : not able to set a high MTU on the representor port for a VF
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824372/+attachment/5259994/+files/kern.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/1824372 Title: mlx5 : not able to set a high MTU on the representor port for a VF Status in linux package in Ubuntu: Confirmed Bug description: Hi, Using Ubuntu 18.04, kernel 4.15.0-47, with a Mellanox MCX556M-ECAT-S25 [1]. With the distro driver, it's impossible to increase the MTU of a representor port : $ sudo ip li set enp50s0f0_0 mtu 1501 RTNETLINK answers: Invalid argument Whereas with the OFED driver [2], I can set it up to 9978 : $ sudo ip li set mtu 9978 enp50s0f0_0 $ This is blocking to use OVS offloading with jumbo frames. Could we please get the feature in the distro driver ? Thanks ! Steps to create the representor : echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs echo :32:00.3 | sudo tee /sys/bus/pci/drivers/mlx5_core/unbind sudo devlink dev eswitch set pci/:32:00.0 mode switchdev echo :32:00.2 | sudo tee /sys/bus/pci/drivers/mlx5_core/bind [1] http://www.mellanox.com/related-docs/prod_adapter_cards /PB_ConnectX-5_VPI_Card_SocketDirect.pdf [2] http://www.mellanox.com/page/mlnx_ofed_eula?mtag=linux_sw_drivers=downloads=ofed=MLNX_OFED-4.5-1.0.1.0=MLNX_OFED_LINUX-4.5-1.0.1.0-ubuntu18.04-x86_64.tgz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 11 14:18 seq crw-rw 1 root audio 116, 33 Apr 11 14:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 11 14:42:57 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=UUID=89c8c952-93fa-499c-bebe-fd9f4c4fbedb ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.2:bd02/21/2019:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824372/+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 1821305] Re: csiostor and cxgb4 fight for the NIC
working kern.log ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821305/+attachment/5259992/+files/kern.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/1821305 Title: csiostor and cxgb4 fight for the NIC Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have a server with 2 * Chelsio T62100-LP-CR. Whenever the server is booted, the csiostor and cxgb4 modules will fight for the card. If csiostor wins, the following is logged : [9.331803] csiostor :21:00.6: PF: 6, Coming up as MASTER, HW state: Initializing ... [ 15.048308] cxgb4 :21:00.4: Coming up as SLAVE: Adapter already initialized and then the interface comes up a 40 Gbps. If cxgb4 wins, however, the following is logged : [8.960020] cxgb4 :21:00.4: Coming up as MASTER: Initializing adapter ... [ 12.141538] csiostor :21:00.6: PF: 6, Coming up as SLAVE, Master PF: 4, HW state: Initialized and the interface comes up at 100 Gbps as expected. Since I'm not using FCoE, I blacklisted the csiostor module, but these 2 modules should play nice with each other. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 15:42 seq crw-rw 1 root audio 116, 33 Mar 21 15:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 22 09:05:38 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=7a2aa06e-2ea8-451c-9b77-e0c5cdc445ce ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821305/+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 1821305] Re: csiostor and cxgb4 fight for the NIC
Hi, This is indeed fixed in 5.1.0-rc6. ** Tags added: kernel-fixed-upstream -- 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/1821305 Title: csiostor and cxgb4 fight for the NIC Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have a server with 2 * Chelsio T62100-LP-CR. Whenever the server is booted, the csiostor and cxgb4 modules will fight for the card. If csiostor wins, the following is logged : [9.331803] csiostor :21:00.6: PF: 6, Coming up as MASTER, HW state: Initializing ... [ 15.048308] cxgb4 :21:00.4: Coming up as SLAVE: Adapter already initialized and then the interface comes up a 40 Gbps. If cxgb4 wins, however, the following is logged : [8.960020] cxgb4 :21:00.4: Coming up as MASTER: Initializing adapter ... [ 12.141538] csiostor :21:00.6: PF: 6, Coming up as SLAVE, Master PF: 4, HW state: Initialized and the interface comes up at 100 Gbps as expected. Since I'm not using FCoE, I blacklisted the csiostor module, but these 2 modules should play nice with each other. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 15:42 seq crw-rw 1 root audio 116, 33 Mar 21 15:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 22 09:05:38 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=7a2aa06e-2ea8-451c-9b77-e0c5cdc445ce ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821305/+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 1826376] [NEW] cxgb4 : no VXLAN offloading with distro driver, only with OFED drivers
Public bug reported: Hi, Using ubuntu 18.04 with kernel 4.15.0-47-generic, my Chelsio NIC can't offload VXLAN with the distro drivers (features "tx-udp_tnl- segmentation" and "tx-udp_tnl-csum-segmentation"), but with the OFED driver ("ChelsioUwire-3.10.0.0"), it can. Can we please get this in the distro driver ? Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 19 14:48 seq crw-rw 1 root audio 116, 33 Apr 19 14:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 25 08:53:20 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro Super Server PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=UUID=7b06790c-9447-446a-b1cf-b25104638b26 ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.2:bd02/21/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic uec-images -- 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/1826376 Title: cxgb4 : no VXLAN offloading with distro driver, only with OFED drivers Status in linux package in Ubuntu: Confirmed Bug description: Hi, Using ubuntu 18.04 with kernel 4.15.0-47-generic, my Chelsio NIC can't offload VXLAN with the distro drivers (features "tx-udp_tnl- segmentation" and "tx-udp_tnl-csum-segmentation"), but with the OFED driver ("ChelsioUwire-3.10.0.0"), it can. Can we please get this in the distro driver ? Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 19 14:48 seq crw-rw 1 root audio 116, 33 Apr 19 14:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 25 08:53:20 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro Super Server PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=UUID=7b06790c-9447-446a-b1cf-b25104638b26 ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro
[Kernel-packages] [Bug 1824367] Re: mlx5 : not able to set a high MTU on the representor port for a VF
*** This bug is a duplicate of bug 1824372 *** https://bugs.launchpad.net/bugs/1824372 ** This bug has been marked a duplicate of bug 1824372 mlx5 : not able to set a high MTU on the representor port for a VF -- 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/1824367 Title: mlx5 : not able to set a high MTU on the representor port for a VF Status in linux package in Ubuntu: Incomplete Bug description: Hi, Using Ubuntu 18.04, kernel 4.15.0-47, with a Mellanox MCX556M-ECAT-S25 [1]. With the distro driver, it's impossible to increase the MTU of a representor port : $ sudo ip li set enp50s0f0_0 mtu 1501 RTNETLINK answers: Invalid argument Whereas with the OFED driver [2], I can set it up to 9978 : $ sudo ip li set mtu 9978 enp50s0f0_0 $ This is blocking to use OVS offloading with jumbo frames. Could we please get the feature in the distro driver ? Thanks ! Steps to create the representor : echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs echo :32:00.3 | sudo tee /sys/bus/pci/drivers/mlx5_core/unbind sudo devlink dev eswitch set pci/:32:00.0 mode switchdev echo :32:00.2 | sudo tee /sys/bus/pci/drivers/mlx5_core/bind [1] http://www.mellanox.com/related-docs/prod_adapter_cards /PB_ConnectX-5_VPI_Card_SocketDirect.pdf [2] http://www.mellanox.com/page/mlnx_ofed_eula?mtag=linux_sw_drivers=downloads=ofed=MLNX_OFED-4.5-1.0.1.0=MLNX_OFED_LINUX-4.5-1.0.1.0-ubuntu18.04-x86_64.tgz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824367/+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 1824372] [NEW] mlx5 : not able to set a high MTU on the representor port for a VF
Public bug reported: Hi, Using Ubuntu 18.04, kernel 4.15.0-47, with a Mellanox MCX556M-ECAT-S25 [1]. With the distro driver, it's impossible to increase the MTU of a representor port : $ sudo ip li set enp50s0f0_0 mtu 1501 RTNETLINK answers: Invalid argument Whereas with the OFED driver [2], I can set it up to 9978 : $ sudo ip li set mtu 9978 enp50s0f0_0 $ This is blocking to use OVS offloading with jumbo frames. Could we please get the feature in the distro driver ? Thanks ! Steps to create the representor : echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs echo :32:00.3 | sudo tee /sys/bus/pci/drivers/mlx5_core/unbind sudo devlink dev eswitch set pci/:32:00.0 mode switchdev echo :32:00.2 | sudo tee /sys/bus/pci/drivers/mlx5_core/bind [1] http://www.mellanox.com/related-docs/prod_adapter_cards/PB_ConnectX- 5_VPI_Card_SocketDirect.pdf [2] http://www.mellanox.com/page/mlnx_ofed_eula?mtag=linux_sw_drivers=downloads=ofed=MLNX_OFED-4.5-1.0.1.0=MLNX_OFED_LINUX-4.5-1.0.1.0-ubuntu18.04-x86_64.tgz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 11 14:18 seq crw-rw 1 root audio 116, 33 Apr 11 14:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 11 14:42:57 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=UUID=89c8c952-93fa-499c-bebe-fd9f4c4fbedb ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.2:bd02/21/2019:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic uec-images -- 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/1824372 Title: mlx5 : not able to set a high MTU on the representor port for a VF Status in linux package in Ubuntu: Confirmed Bug description: Hi, Using Ubuntu 18.04, kernel 4.15.0-47, with a Mellanox MCX556M-ECAT-S25 [1]. With the distro driver, it's impossible to increase the MTU of a representor port : $ sudo ip li set enp50s0f0_0 mtu 1501 RTNETLINK answers: Invalid argument Whereas with the OFED driver [2], I can set it up to 9978 : $ sudo ip li set mtu 9978 enp50s0f0_0 $ This is blocking to use OVS offloading with jumbo frames. Could we please get the feature in the distro driver ? Thanks ! Steps to create the representor : echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs echo :32:00.3 | sudo tee /sys/bus/pci/drivers/mlx5_core/unbind sudo devlink dev eswitch set pci/:32:00.0 mode switchdev echo :32:00.2 | sudo tee /sys/bus/pci/drivers/mlx5_core/bind [1] http://www.mellanox.com/related-docs/prod_adapter_cards /PB_ConnectX-5_VPI_Card_SocketDirect.pdf [2] http://www.mellanox.com/page/mlnx_ofed_eula?mtag=linux_sw_drivers=downloads=ofed=MLNX_OFED-4.5-1.0.1.0=MLNX_OFED_LINUX-4.5-1.0.1.0-ubuntu18.04-x86_64.tgz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 11 14:18 seq crw-rw 1 root audio 116, 33 Apr 11 14:18 timer AplayDevices: Error: [Errno
[Kernel-packages] [Bug 1824367] [NEW] mlx5 : not able to set a high MTU on the representor port for a VF
Public bug reported: Hi, Using Ubuntu 18.04, kernel 4.15.0-47, with a Mellanox MCX556M-ECAT-S25 [1]. With the distro driver, it's impossible to increase the MTU of a representor port : $ sudo ip li set enp50s0f0_0 mtu 1501 RTNETLINK answers: Invalid argument Whereas with the OFED driver [2], I can set it up to 9978 : $ sudo ip li set mtu 9978 enp50s0f0_0 $ This is blocking to use OVS offloading with jumbo frames. Could we please get the feature in the distro driver ? Thanks ! Steps to create the representor : echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs echo :32:00.3 | sudo tee /sys/bus/pci/drivers/mlx5_core/unbind sudo devlink dev eswitch set pci/:32:00.0 mode switchdev echo :32:00.2 | sudo tee /sys/bus/pci/drivers/mlx5_core/bind [1] http://www.mellanox.com/related-docs/prod_adapter_cards/PB_ConnectX- 5_VPI_Card_SocketDirect.pdf [2] http://www.mellanox.com/page/mlnx_ofed_eula?mtag=linux_sw_drivers=downloads=ofed=MLNX_OFED-4.5-1.0.1.0=MLNX_OFED_LINUX-4.5-1.0.1.0-ubuntu18.04-x86_64.tgz ** 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/1824367 Title: mlx5 : not able to set a high MTU on the representor port for a VF Status in linux package in Ubuntu: Incomplete Bug description: Hi, Using Ubuntu 18.04, kernel 4.15.0-47, with a Mellanox MCX556M-ECAT-S25 [1]. With the distro driver, it's impossible to increase the MTU of a representor port : $ sudo ip li set enp50s0f0_0 mtu 1501 RTNETLINK answers: Invalid argument Whereas with the OFED driver [2], I can set it up to 9978 : $ sudo ip li set mtu 9978 enp50s0f0_0 $ This is blocking to use OVS offloading with jumbo frames. Could we please get the feature in the distro driver ? Thanks ! Steps to create the representor : echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs echo :32:00.3 | sudo tee /sys/bus/pci/drivers/mlx5_core/unbind sudo devlink dev eswitch set pci/:32:00.0 mode switchdev echo :32:00.2 | sudo tee /sys/bus/pci/drivers/mlx5_core/bind [1] http://www.mellanox.com/related-docs/prod_adapter_cards /PB_ConnectX-5_VPI_Card_SocketDirect.pdf [2] http://www.mellanox.com/page/mlnx_ofed_eula?mtag=linux_sw_drivers=downloads=ofed=MLNX_OFED-4.5-1.0.1.0=MLNX_OFED_LINUX-4.5-1.0.1.0-ubuntu18.04-x86_64.tgz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824367/+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 1821345] Re: Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number of VFs is >= 64 : alloc irq vectors failed
Here is the reply from Mellanox support : == • There is a limitations on the firmware/driver for ConnectX-5 Socket direct adapter • There is a limitation on the number of total PFs+VFs that wecan allocate on the adapter which is 256. • The max number of VF's of each port/PF is 63 VF's => 63*4=252 . Currently on your setup NUM_PF_MSIX==63. for all PFs it is 252. In order to bring up the max supported number of VF'S=63 , please reduce the NUM_PF_MSIX to 32 - mlxconfig -d /dev/mst/mt4119_pciconf0 set NUM_PF_MSIX=32 - mlxconfig -d /dev/mst/mt4119_pciconf0.1 set NUM_PF_MSIX=32 - mlxconfig -d /dev/mst/mt4119_pciconf1 set NUM_PF_MSIX=32 - mlxconfig -d /dev/mst/mt4119_pciconf1.1 set NUM_PF_MSIX=32 == And indeed, setting NUM_PF_MSIX to 32 allowed me to create 4*63 VFs. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1821345 Title: Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number of VFs is >= 64 : alloc irq vectors failed Status in linux package in Ubuntu: Invalid Bug description: Hi, For the Mellanox NIC MT27800 (MCX556M-ECAT-S25 to be precise), the maximum number of VF per PF can be configured in the firmware, by running e.g. : $ sudo mstconfig -d 32:00.1 set NUM_OF_VFS=127 If I set this NUM_OF_VFS to 64 or more, the creation of even a single VF fails mid-way : $ echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs 1 dmesg shows : [101418.090970] (:32:00.0): E-Switch: E-Switch enable SRIOV: nvfs(1) mode (1) [101418.182736] (:32:00.0): E-Switch: SRIOV enabled: active vports(2) [101418.289642] pci :32:00.2: [15b3:1018] type 00 class 0x02 [101418.290235] pci :32:00.2: Max Payload Size set to 512 (was 128, max 512) [101418.290261] pci :32:00.2: enabling Extended Tags [101418.292432] iommu: Adding device :32:00.2 to group 139 [101418.292580] iommu: Using direct mapping for device :32:00.2 [101418.292979] mlx5_core :32:00.2: enabling device ( -> 0002) [101418.293719] mlx5_core :32:00.2: firmware version: 16.24.1000 [101418.550589] mlx5_core :32:00.2: alloc irq vectors failed [101418.974082] mlx5_core :32:00.2: mlx5_load_one failed with error code -28 [101418.981656] mlx5_core: probe of :32:00.2 failed with error -28 This is a problem with both the Ubuntu kernel driver and the OFED driver. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 08:33 seq crw-rw 1 root audio 116, 33 Mar 21 08:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 22 12:43:26 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=52d72a05-517b-4c16-8dcb-486bdebcc695 ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821345/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1821345] Re: Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number of VFs is >= 64 : alloc irq vectors failed
Note : if NUM_OF_VFS is set to 32, VF creation works fine. If it's set to 64 or above, VF creation fails. I haven't tested in between. -- 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/1821345 Title: Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number of VFs is >= 64 : alloc irq vectors failed Status in linux package in Ubuntu: Confirmed Bug description: Hi, For the Mellanox NIC MT27800 (MCX556M-ECAT-S25 to be precise), the maximum number of VF per PF can be configured in the firmware, by running e.g. : $ sudo mstconfig -d 32:00.1 set NUM_OF_VFS=127 If I set this NUM_OF_VFS to 64 or more, the creation of even a single VF fails mid-way : $ echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs 1 dmesg shows : [101418.090970] (:32:00.0): E-Switch: E-Switch enable SRIOV: nvfs(1) mode (1) [101418.182736] (:32:00.0): E-Switch: SRIOV enabled: active vports(2) [101418.289642] pci :32:00.2: [15b3:1018] type 00 class 0x02 [101418.290235] pci :32:00.2: Max Payload Size set to 512 (was 128, max 512) [101418.290261] pci :32:00.2: enabling Extended Tags [101418.292432] iommu: Adding device :32:00.2 to group 139 [101418.292580] iommu: Using direct mapping for device :32:00.2 [101418.292979] mlx5_core :32:00.2: enabling device ( -> 0002) [101418.293719] mlx5_core :32:00.2: firmware version: 16.24.1000 [101418.550589] mlx5_core :32:00.2: alloc irq vectors failed [101418.974082] mlx5_core :32:00.2: mlx5_load_one failed with error code -28 [101418.981656] mlx5_core: probe of :32:00.2 failed with error -28 This is a problem with both the Ubuntu kernel driver and the OFED driver. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 08:33 seq crw-rw 1 root audio 116, 33 Mar 21 08:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 22 12:43:26 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=52d72a05-517b-4c16-8dcb-486bdebcc695 ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821345/+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 1821345] [NEW] Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number of VFs is >= 64 : alloc irq vectors failed
Public bug reported: Hi, For the Mellanox NIC MT27800 (MCX556M-ECAT-S25 to be precise), the maximum number of VF per PF can be configured in the firmware, by running e.g. : $ sudo mstconfig -d 32:00.1 set NUM_OF_VFS=127 If I set this NUM_OF_VFS to 64 or more, the creation of even a single VF fails mid-way : $ echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs 1 dmesg shows : [101418.090970] (:32:00.0): E-Switch: E-Switch enable SRIOV: nvfs(1) mode (1) [101418.182736] (:32:00.0): E-Switch: SRIOV enabled: active vports(2) [101418.289642] pci :32:00.2: [15b3:1018] type 00 class 0x02 [101418.290235] pci :32:00.2: Max Payload Size set to 512 (was 128, max 512) [101418.290261] pci :32:00.2: enabling Extended Tags [101418.292432] iommu: Adding device :32:00.2 to group 139 [101418.292580] iommu: Using direct mapping for device :32:00.2 [101418.292979] mlx5_core :32:00.2: enabling device ( -> 0002) [101418.293719] mlx5_core :32:00.2: firmware version: 16.24.1000 [101418.550589] mlx5_core :32:00.2: alloc irq vectors failed [101418.974082] mlx5_core :32:00.2: mlx5_load_one failed with error code -28 [101418.981656] mlx5_core: probe of :32:00.2 failed with error -28 This is a problem with both the Ubuntu kernel driver and the OFED driver. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 08:33 seq crw-rw 1 root audio 116, 33 Mar 21 08:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 22 12:43:26 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=52d72a05-517b-4c16-8dcb-486bdebcc695 ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic uec-images -- 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/1821345 Title: Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number of VFs is >= 64 : alloc irq vectors failed Status in linux package in Ubuntu: Confirmed Bug description: Hi, For the Mellanox NIC MT27800 (MCX556M-ECAT-S25 to be precise), the maximum number of VF per PF can be configured in the firmware, by running e.g. : $ sudo mstconfig -d 32:00.1 set NUM_OF_VFS=127 If I set this NUM_OF_VFS to 64 or more, the creation of even a single VF fails mid-way : $ echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs 1 dmesg shows : [101418.090970] (:32:00.0): E-Switch: E-Switch enable SRIOV: nvfs(1) mode (1) [101418.182736] (:32:00.0): E-Switch: SRIOV enabled: active vports(2) [101418.289642] pci :32:00.2: [15b3:1018] type 00 class 0x02 [101418.290235] pci :32:00.2: Max Payload Size set to 512 (was 128, max 512) [101418.290261] pci :32:00.2: enabling Extended Tags [101418.292432] iommu: Adding device :32:00.2 to group 139 [101418.292580] iommu: Using direct mapping for device :32:00.2 [101418.292979] mlx5_core :32:00.2: enabling device ( -> 0002) [101418.293719] mlx5_core :32:00.2: firmware version: 16.24.1000
[Kernel-packages] [Bug 1821305] [NEW] csiostor and cxgb4 fight for the NIC
Public bug reported: Hi, I have a server with 2 * Chelsio T62100-LP-CR. Whenever the server is booted, the csiostor and cxgb4 modules will fight for the card. If csiostor wins, the following is logged : [9.331803] csiostor :21:00.6: PF: 6, Coming up as MASTER, HW state: Initializing ... [ 15.048308] cxgb4 :21:00.4: Coming up as SLAVE: Adapter already initialized and then the interface comes up a 40 Gbps. If cxgb4 wins, however, the following is logged : [8.960020] cxgb4 :21:00.4: Coming up as MASTER: Initializing adapter ... [ 12.141538] csiostor :21:00.6: PF: 6, Coming up as SLAVE, Master PF: 4, HW state: Initialized and the interface comes up at 100 Gbps as expected. Since I'm not using FCoE, I blacklisted the csiostor module, but these 2 modules should play nice with each other. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 15:42 seq crw-rw 1 root audio 116, 33 Mar 21 15:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 22 09:05:38 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=7a2aa06e-2ea8-451c-9b77-e0c5cdc445ce ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1821305 Title: csiostor and cxgb4 fight for the NIC Status in linux package in Ubuntu: New Bug description: Hi, I have a server with 2 * Chelsio T62100-LP-CR. Whenever the server is booted, the csiostor and cxgb4 modules will fight for the card. If csiostor wins, the following is logged : [9.331803] csiostor :21:00.6: PF: 6, Coming up as MASTER, HW state: Initializing ... [ 15.048308] cxgb4 :21:00.4: Coming up as SLAVE: Adapter already initialized and then the interface comes up a 40 Gbps. If cxgb4 wins, however, the following is logged : [8.960020] cxgb4 :21:00.4: Coming up as MASTER: Initializing adapter ... [ 12.141538] csiostor :21:00.6: PF: 6, Coming up as SLAVE, Master PF: 4, HW state: Initialized and the interface comes up at 100 Gbps as expected. Since I'm not using FCoE, I blacklisted the csiostor module, but these 2 modules should play nice with each other. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 15:42 seq crw-rw 1 root audio 116, 33 Mar 21 15:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 22 09:05:38 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType:
[Kernel-packages] [Bug 1821205] [NEW] "couldn't find IFLA_VF_INFO for VF 1 in netlink response" when trying to start libvirt VM with Chelsio VF
Public bug reported: Hi, I have a Chelsio T62100-LP-CR and I'm trying to create a libvirt VM that gets a VF from the NIC. The following XML is used : When starting the VM, libvirt fails with the following : ubuntu@lubbock:~$ sudo virsh start vmaxino error: Failed to start domain vmaxino error: internal error: couldn't find IFLA_VF_INFO for VF 1 in netlink response This is similar to bug 1496942. I can create the VM with the VF if I pass it as a like this : More info : ubuntu@lubbock:~$ sudo virsh nodedev-dumpxml pci__21_01_4 pci__21_01_4 /sys/devices/pci:20/:20:03.1/:21:01.4 pci__20_03_1 vfio-pci 0 33 1 4 T62100-LP-CR Unified Wire Ethernet Controller [VF] Chelsio Communications Inc pcap of netlink exchange is attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 15:42 seq crw-rw 1 root audio 116, 33 Mar 21 15:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Mar 21 16:16:41 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=7a2aa06e-2ea8-451c-9b77-e0c5cdc445ce ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "pcap of netlink exchange" https://bugs.launchpad.net/bugs/1821205/+attachment/5248235/+files/pcap.bz2 -- 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/1821205 Title: "couldn't find IFLA_VF_INFO for VF 1 in netlink response" when trying to start libvirt VM with Chelsio VF Status in linux package in Ubuntu: New Bug description: Hi, I have a Chelsio T62100-LP-CR and I'm trying to create a libvirt VM that gets a VF from the NIC. The following XML is used : When starting the VM, libvirt fails with the following : ubuntu@lubbock:~$ sudo virsh start vmaxino error: Failed to start domain vmaxino error: internal error: couldn't find IFLA_VF_INFO for VF 1 in netlink response This is similar to bug 1496942. I can create the VM with the VF if I pass it as a like this : More info : ubuntu@lubbock:~$ sudo virsh nodedev-dumpxml pci__21_01_4 pci__21_01_4 /sys/devices/pci:20/:20:03.1/:21:01.4 pci__20_03_1 vfio-pci 0 33 1 4 T62100-LP-CR Unified Wire Ethernet Controller [VF] Chelsio Communications Inc pcap of netlink exchange is attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 15:42
[Kernel-packages] [Bug 1771467] Re: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
What's the status of the SRU for this bug ? 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/1771467 Title: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0 Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == Mainline commit introduced a regression in v4.15-rc1. The regression causes a kernel panic during system shutdown. This commit fixes that regression. This commit was also cc'd to upstream stable, but it has not landed in Bionic as of yet. == Fix == 0d98ba8d70b0 ("scsi: hpsa: disable device during shutdown") == Regression Potential == Low. This patch fixes a current regression. It has been cc'd to upstream stable, so it has had additon upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. Verified on multiple DL360 Gen9 servers with up to date firmware. Just before reboot or shutdown, there is the following panic: [ 289.093083] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 289.093085] {1}[Hardware Error]: event severity: fatal [ 289.093087] {1}[Hardware Error]: Error 0, type: fatal [ 289.093088] {1}[Hardware Error]: section_type: PCIe error [ 289.093090] {1}[Hardware Error]: port_type: 4, root port [ 289.093091] {1}[Hardware Error]: version: 1.16 [ 289.093093] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 289.093094] {1}[Hardware Error]: device_id: :00:01.0 [ 289.093095] {1}[Hardware Error]: slot: 0 [ 289.093096] {1}[Hardware Error]: secondary_bus: 0x03 [ 289.093097] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02 [ 289.093098] {1}[Hardware Error]: class_code: 040600 [ 289.093378] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 289.093380] {1}[Hardware Error]: Error 1, type: fatal [ 289.093381] {1}[Hardware Error]: section_type: PCIe error [ 289.093382] {1}[Hardware Error]: port_type: 4, root port [ 289.093383] {1}[Hardware Error]: version: 1.16 [ 289.093384] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 289.093386] {1}[Hardware Error]: device_id: :00:01.0 [ 289.093386] {1}[Hardware Error]: slot: 0 [ 289.093387] {1}[Hardware Error]: secondary_bus: 0x03 [ 289.093388] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02 [ 289.093674] {1}[Hardware Error]: class_code: 040600 [ 289.093676] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 289.093678] Kernel panic - not syncing: Fatal hardware error! [ 289.093745] Kernel Offset: 0x1cc0 from 0x8100 (relocation range: 0x8000-0xbfff) [ 289.105835] ERST: [Firmware Warn]: Firmware does not respond in time. It does eventually restart after this. Then during the subsequent POST, the following warning appears: Embedded RAID 1 : Smart Array P440ar Controller - (2048 MB, V6.30) 7 Logical Drive(s) - Operation Failed - 1719-Slot 0 Drive Array - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13) Action: Install the latest controller firmware. If the problem persists, replace the controller. The latter's symptoms are described in https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565 but the running storage controller firmware is much newer than the doc's resolution. Neither of these problems occur during shutdown/reboot on the xenial kernel. FWIW, when running on old P89 (1.50 (07/20/2015) vs 2.56 (01/22/2018)), the shutdown failure mode was a loop like so: [529151.035267] NMI: IOCK error (debug interrupt?) for reason 75 on CPU 0. [529153.222883] Uhhuh. NMI received for unknown reason 25 on CPU 0. [529153.222884] Do you have a strange power saving mode enabled? [529153.222884] Dazed and confused, but trying to continue [529153.554447] Uhhuh. NMI received for unknown reason 25 on CPU 0. [529153.554448] Do you have a strange power saving mode enabled? [529153.554449] Dazed and confused, but trying to continue [529153.554450] Uhhuh. NMI received for unknown reason 25 on CPU 0. [529153.554451] Do you have a strange power saving mode enabled? [529153.554452] Dazed and confused, but trying to continue [529153.554452] Uhhuh. NMI received for unknown reason 25 on CPU 0. [529153.554453] Do you have a strange power saving mode enabled? [529153.554454] Dazed and confused, but trying to continue [529153.554454] Uhhuh. NMI received for unknown reason 35 on CPU 0. [529153.554455] Do you have a strange power saving mode enabled?
[Kernel-packages] [Bug 1775732] Re: arm64 soft lock crashes on nova-compute charm running
4.19 appears to fix this problem -- 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/1775732 Title: arm64 soft lock crashes on nova-compute charm running Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Discovered on bionic, arm64 (Moonshot, verified on multiple swirlix cartridges), 4.15.0-22-generic. After deploying the nova-compute Juju charm, on subsequent reboots, within a few seconds after complete boot, everything will freeze and eventually display on the serial console (just these, no traces): [ 188.010510] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] [ 216.010292] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] (From here on, "lock up" refers to that sequence: boot a kernel, it completes boot to login prompt, then everything freezes a few seconds later, then BUGs.) It's usually but not always juju-log, sometimes a relation-ids or similar. I was able to briefly notice that it was in its startup config-changed hook. I've separated out and tested nearly everything it does during its startup config-changed (sets up bridging, writes some config files, restarts libvirtd/nova-compute/etc) without being able to trigger the bug, but I suspect proximity to boot is a factor. If I disable jujud- unit-nova-compute startup, boot, log in, re-enable and start (by which time over a minute or so has elapsed from boot finish), it will not lock up. Similarly, if I wrap the jujud startup in a `strace -Ff -o /var/log/strace.log` (which slows it down massively), it will not lock up. Watched pot syndrome. I've tried kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/ . I noticed most of the recent arm64 mainline kernels had failed builds, notified the kernel team channel and apw fixed the issue and started some rebuilds. What I've discovered (after many dead ends and a futile bisection) is that mainline builds before the rebuilds lock up, but fixed mainline builds initiated by apw DO NOT lock up. e.g. 4.16.3-041603.201804190730 locks up, but 4.16.6-041606.201806042022 does not lock up. (4.16.4 and 4.16.5 appear to have never been rebuilt and don't have arm64 debs, and that period is what I tried to bisect after figuring a fix must be in there.) But when I try to compile any of these recent kernels myself, they lock up when booted. Same kernel configs, tried on both bionic and in a cosmic chroot, tried both native arm64 compile and cross-compile from amd64. e.g. 4.16.6-041606.201806042022 from k.u.c does not lock up, but when I build it myself, it does. TBC, I've verified lock ups on the following kernels (all assume kernel configs from their respective Ubuntu or k.u.c mainline builds): - 4.15.0-22-generic from bionic (both Ubuntu-provided and my own recompile) - v4.16 (and all point releases) - v4.17 As I write this, my compiled v4.10 DOES NOT appear to lock up. I will attempt to bisect at a macro level from 4.10..4.15 and dig deeper. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 2 04:22 seq crw-rw 1 root audio 116, 33 Jun 2 04:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Jun 8 00:13:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775732/+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 1766543] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168128/+files/UdevDb.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current diagnostics
[Kernel-packages] [Bug 1766543] nvram.gz
apport information ** Attachment added: "nvram.gz" https://bugs.launchpad.net/bugs/1766543/+attachment/5168130/+files/nvram.gz ** 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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg:
[Kernel-packages] [Bug 1766543] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168126/+files/ProcModules.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] ProcMisc.txt
apport information ** Attachment added: "ProcMisc.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168125/+files/ProcMisc.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] ProcPpc64.tar.gz
apport information ** Attachment added: "ProcPpc64.tar.gz" https://bugs.launchpad.net/bugs/1766543/+attachment/5168127/+files/ProcPpc64.tar.gz -- 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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] HookError_powerpc.txt
apport information ** Attachment added: "HookError_powerpc.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168119/+files/HookError_powerpc.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve
[Kernel-packages] [Bug 1766543] DeviceTree.tar.gz
apport information ** Attachment added: "DeviceTree.tar.gz" https://bugs.launchpad.net/bugs/1766543/+attachment/5168117/+files/DeviceTree.tar.gz -- 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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168122/+files/ProcCpuinfoMinimal.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not
[Kernel-packages] [Bug 1766543] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168116/+files/CurrentDmesg.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] HookError_generic.txt
apport information ** Attachment added: "HookError_generic.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168118/+files/HookError_generic.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve
[Kernel-packages] [Bug 1766543] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168123/+files/ProcInterrupts.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve
[Kernel-packages] [Bug 1766543] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168129/+files/WifiSyslog.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168120/+files/Lspci.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current diagnostics
[Kernel-packages] [Bug 1766543] OpalElog.tar.gz
apport information ** Attachment added: "OpalElog.tar.gz" https://bugs.launchpad.net/bugs/1766543/+attachment/5168121/+files/OpalElog.tar.gz -- 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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] ProcLocks.txt
apport information ** Attachment added: "ProcLocks.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168124/+files/ProcLocks.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168115/+files/CRDA.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current diagnostics mode,
[Kernel-packages] [Bug 1766543] Re: instance deletion takes a while and blocks nova-compute
apport information ** Tags added: apport-collected uec-images xenial ** Description changed: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jun 23 14:23 seq + crw-rw 1 root audio 116, 33 Jun 23 14:23 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: ppc64el + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Package: nova (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect + ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 + ProcSwaps: + Filename TypeSizeUsedPriority + /swap.img file 8388544 0 -1 + ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 + ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-128-generic N/A + linux-backports-modules-4.4.0-128-generic N/A + linux-firmware 1.157.20 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial uec-images xenial uec-images xenial uec-images + Uname: Linux 4.4.0-128-generic ppc64le + UnreportableReason: The report belongs to a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: False + cpu_cores: Number of cores present = 20 + cpu_coreson: Number of cores online = 20 + cpu_dscr: DSCR is 0 + cpu_freq: + min: 1.201 GHz (cpu 48) + max: 3.710 GHz (cpu 112) + avg: 2.615 GHz + cpu_runmode: + Could not retrieve current diagnostics mode, + No kernel interface to firmware + cpu_smt: SMT is off ** Attachment added: ".sys.firmware.opal.msglog.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168114/+files/.sys.firmware.opal.msglog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1766543] Re: instance deletion takes a while and blocks nova-compute
By the way the task blocks on the following : ==> /proc/54255/task/54255/stack <== [] wakeup_preempt_entity.isra.6+0x7c/0x90 [] __switch_to+0x1f8/0x350 [] get_request+0x29c/0x910 [] blk_queue_bio+0x164/0x500 [] generic_make_request+0x154/0x310 [] submit_bio+0xd4/0x1f0 [] ext4_io_submit+0x7c/0xb0 [] ext4_writepages+0x4a8/0xdd0 [] do_writepages+0x60/0xc0 [] __filemap_fdatawrite_range+0xf8/0x170 [] jbd2_journal_begin_ordered_truncate+0xe8/0x130 [] ext4_evict_inode+0x530/0x5e0 [] evict+0xf8/0x2a0 [] do_unlinkat+0x1a8/0x3a0 [] system_call+0x38/0xe4 -- 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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Incomplete Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766543/+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 1715609] Re: kernel warning: skb_warn_bad_offload
Hi, I got this on 4.4.0-116-generic : [266447.178906] [ cut here ] [266447.178919] WARNING: CPU: 0 PID: 3343 at /build/linux-fQ94TU/linux-4.4.0/net/core/dev.c:2448 skb_warn_bad_offload+0xd1/0x120() [266447.178924] qr-8a4bd2f3-04: caps=(0x0184075b59e9, 0x0184075b59e9) len=2058 data_len=582 gso_size=1406 gso_type=1 ip_summed=3 [266447.178926] Modules linked in: kpatch_livepatch_Ubuntu_4_4_0_116_140_generic_36(OE) xt_REDIRECT nf_nat_redirect ip6table_mangle xt_nat xt_mark xt_connmark ip6table_raw iptable_raw ip_gre ip_tunnel gre xt_recent ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_addrtype xt_conntrack dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag veth netlink_diag nbd ip6table_filter ip6_tables xt_CHECKSUM iptable_mangle xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat iptable_filter ip_tables x_tables openvswitch nf_defrag_ipv6 nf_conntrack binfmt_misc ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel bridge stp kvm llc [266447.178988] irqbypass sb_edac edac_core ipmi_si hpilo ipmi_msghandler serio_raw 8250_fintek lpc_ich shpchp acpi_power_meter ioatdma mac_hid dca ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse tg3 ptp pps_core hpsa scsi_transport_sas wmi fjes [266447.179045] CPU: 0 PID: 3343 Comm: haproxy Tainted: GW OE K 4.4.0-116-generic #140-Ubuntu [266447.179048] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [266447.179050] 0286 6f5737dc927d16dd 880a3646b818 813ffc13 [266447.179055] 880a3646b860 81d715e8 880a3646b850 810830f2 [266447.179059] 880064507ce8 880b4ff12000 0001 8808723268fc [266447.179064] Call Trace: [266447.179072] [] dump_stack+0x63/0x90 [266447.179079] [] warn_slowpath_common+0x82/0xc0 [266447.179084] [] warn_slowpath_fmt+0x5c/0x80 [266447.179090] [] ? ___ratelimit+0xa2/0xe0 [266447.179094] [] skb_warn_bad_offload+0xd1/0x120 [266447.179100] [] skb_checksum_help+0x185/0x1a0 [266447.179106] [] checksum_tg+0x22/0x29 [xt_CHECKSUM] [266447.179112] [] ipt_do_table+0x301/0x720 [ip_tables] [266447.179117] [] ? ipt_do_table+0x349/0x720 [ip_tables] [266447.179122] [] ? enqueue_entity+0x3a7/0xd20 [266447.179129] [] iptable_mangle_hook+0x39/0x107 [iptable_mangle] [266447.179134] [] nf_iterate+0x68/0x80 [266447.179137] [] nf_hook_slow+0x73/0xd0 [266447.179143] [] ip_output+0xcf/0xe0 [266447.179148] [] ? __ip_flush_pending_frames.isra.42+0x90/0x90 [266447.179153] [] ip_local_out+0x3b/0x50 [266447.179158] [] ip_queue_xmit+0x154/0x380 [266447.179164] [] tcp_transmit_skb+0x51b/0x980 [266447.179169] [] tcp_write_xmit+0x1d6/0xf40 [266447.179174] [] __tcp_push_pending_frames+0x31/0xd0 [266447.179178] [] tcp_push+0xec/0x110 [266447.179181] [] tcp_sendmsg+0x739/0xb80 [266447.179186] [] inet_sendmsg+0x6b/0xa0 [266447.179192] [] sock_sendmsg+0x3e/0x50 [266447.179196] [] SYSC_sendto+0x101/0x190 [266447.179203] [] ? syscall_trace_enter_phase1+0xc8/0x140 [266447.179208] [] SyS_sendto+0xe/0x10 [266447.179215] [] entry_SYSCALL_64_fastpath+0x1c/0xbb [266447.179218] ---[ end trace 4c054fa8d617289c ]--- Joseph, can we maybe get a new kernel to test ? The one in your last comment is gone. Note that this isn't appearing a lot (~10 occurrences on a server with 3 days of uptime) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Xenial) 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/1715609 Title: kernel warning: skb_warn_bad_offload Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Since upgrading to kernel version 4.10.0-33.37, we're seeing a lot of call traces triggered by skb_warn_bad_offload in the syslog. Regression introduced when fixing this bug? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705447 kernel: [570943.49] [ cut here ] kernel: [570943.494448] WARNING: CPU: 3 PID: 21982 at /build/linux-hwe-YA6IuF/linux-hwe-4.10.0/net/core/dev.c:2576 skb_warn_bad_offload+0xd1/0x120 kernel: [570943.494450] e1000e: caps=(0x0030002149a9, 0x) len=1701 data_len=1659 gso_size=1480 gso_type=2 ip_summed=0 kernel: [570943.494451] Modules linked in:
[Kernel-packages] [Bug 1751028] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1751028/+attachment/5060309/+files/BootDmesg.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/1751028 Title: impossible to start a xen domain on precise with the spectre/meltdown kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic - precise ESM), it's not possible to boot my xen domUs anymore (dom0 is fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lts-trusty with Spectre/Meltdown mitigations). This is with xen 4.1.6.1-0ubuntu0.12.04.13 xend.log below : [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'], ['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux', ['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'], ['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'], ['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac', '02:00:5B:BD:5E:E2') [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain [2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free; need 16384; done. [2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 2 256 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x18000, memory_static_min=0x0. [2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2 vcpus=1 [2018-02-22 10:56:03 1566] DEBUG (image:721) domid = 2 [2018-02-22 10:56:03 1566] DEBUG (image:722) memsize= 6144 [2018-02-22 10:56:03 1566] DEBUG (image:723) image = /vmlinuz [2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn = 1 [2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2 [2018-02-22 10:56:03 1566] DEBUG (image:726) cmdline= root=/dev/xvda1 ro nogbpages console=hvc0 earlyprintk=xen nosplash
[Kernel-packages] [Bug 1751028] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1751028/+attachment/5060317/+files/UdevDb.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/1751028 Title: impossible to start a xen domain on precise with the spectre/meltdown kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic - precise ESM), it's not possible to boot my xen domUs anymore (dom0 is fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lts-trusty with Spectre/Meltdown mitigations). This is with xen 4.1.6.1-0ubuntu0.12.04.13 xend.log below : [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'], ['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux', ['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'], ['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'], ['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac', '02:00:5B:BD:5E:E2') [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain [2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free; need 16384; done. [2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 2 256 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x18000, memory_static_min=0x0. [2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2 vcpus=1 [2018-02-22 10:56:03 1566] DEBUG (image:721) domid = 2 [2018-02-22 10:56:03 1566] DEBUG (image:722) memsize= 6144 [2018-02-22 10:56:03 1566] DEBUG (image:723) image = /vmlinuz [2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn = 1 [2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2 [2018-02-22 10:56:03 1566] DEBUG (image:726) cmdline= root=/dev/xvda1 ro nogbpages console=hvc0 earlyprintk=xen nosplash
[Kernel-packages] [Bug 1751028] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1751028/+attachment/5060316/+files/ProcModules.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/1751028 Title: impossible to start a xen domain on precise with the spectre/meltdown kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic - precise ESM), it's not possible to boot my xen domUs anymore (dom0 is fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lts-trusty with Spectre/Meltdown mitigations). This is with xen 4.1.6.1-0ubuntu0.12.04.13 xend.log below : [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'], ['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux', ['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'], ['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'], ['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac', '02:00:5B:BD:5E:E2') [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain [2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free; need 16384; done. [2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 2 256 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x18000, memory_static_min=0x0. [2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2 vcpus=1 [2018-02-22 10:56:03 1566] DEBUG (image:721) domid = 2 [2018-02-22 10:56:03 1566] DEBUG (image:722) memsize= 6144 [2018-02-22 10:56:03 1566] DEBUG (image:723) image = /vmlinuz [2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn = 1 [2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2 [2018-02-22 10:56:03 1566] DEBUG (image:726) cmdline= root=/dev/xvda1 ro nogbpages console=hvc0 earlyprintk=xen nosplash
[Kernel-packages] [Bug 1751028] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1751028/+attachment/5060318/+files/WifiSyslog.txt ** 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/1751028 Title: impossible to start a xen domain on precise with the spectre/meltdown kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic - precise ESM), it's not possible to boot my xen domUs anymore (dom0 is fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lts-trusty with Spectre/Meltdown mitigations). This is with xen 4.1.6.1-0ubuntu0.12.04.13 xend.log below : [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'], ['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux', ['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'], ['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'], ['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac', '02:00:5B:BD:5E:E2') [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain [2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free; need 16384; done. [2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 2 256 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x18000, memory_static_min=0x0. [2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2 vcpus=1 [2018-02-22 10:56:03 1566] DEBUG (image:721) domid = 2 [2018-02-22 10:56:03 1566] DEBUG (image:722) memsize= 6144 [2018-02-22 10:56:03 1566] DEBUG (image:723) image = /vmlinuz [2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn = 1 [2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2 [2018-02-22 10:56:03 1566] DEBUG (image:726) cmdline= root=/dev/xvda1 ro nogbpages console=hvc0 earlyprintk=xen nosplash
[Kernel-packages] [Bug 1751028] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1751028/+attachment/5060314/+files/ProcCpuinfo.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/1751028 Title: impossible to start a xen domain on precise with the spectre/meltdown kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic - precise ESM), it's not possible to boot my xen domUs anymore (dom0 is fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lts-trusty with Spectre/Meltdown mitigations). This is with xen 4.1.6.1-0ubuntu0.12.04.13 xend.log below : [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'], ['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux', ['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'], ['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'], ['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac', '02:00:5B:BD:5E:E2') [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain [2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free; need 16384; done. [2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 2 256 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x18000, memory_static_min=0x0. [2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2 vcpus=1 [2018-02-22 10:56:03 1566] DEBUG (image:721) domid = 2 [2018-02-22 10:56:03 1566] DEBUG (image:722) memsize= 6144 [2018-02-22 10:56:03 1566] DEBUG (image:723) image = /vmlinuz [2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn = 1 [2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2 [2018-02-22 10:56:03 1566] DEBUG (image:726) cmdline= root=/dev/xvda1 ro nogbpages console=hvc0 earlyprintk=xen nosplash
[Kernel-packages] [Bug 1751028] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1751028/+attachment/5060311/+files/IwConfig.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/1751028 Title: impossible to start a xen domain on precise with the spectre/meltdown kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic - precise ESM), it's not possible to boot my xen domUs anymore (dom0 is fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lts-trusty with Spectre/Meltdown mitigations). This is with xen 4.1.6.1-0ubuntu0.12.04.13 xend.log below : [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'], ['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux', ['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'], ['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'], ['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac', '02:00:5B:BD:5E:E2') [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain [2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free; need 16384; done. [2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 2 256 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x18000, memory_static_min=0x0. [2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2 vcpus=1 [2018-02-22 10:56:03 1566] DEBUG (image:721) domid = 2 [2018-02-22 10:56:03 1566] DEBUG (image:722) memsize= 6144 [2018-02-22 10:56:03 1566] DEBUG (image:723) image = /vmlinuz [2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn = 1 [2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2 [2018-02-22 10:56:03 1566] DEBUG (image:726) cmdline= root=/dev/xvda1 ro nogbpages console=hvc0 earlyprintk=xen nosplash
[Kernel-packages] [Bug 1751028] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1751028/+attachment/5060315/+files/ProcInterrupts.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/1751028 Title: impossible to start a xen domain on precise with the spectre/meltdown kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic - precise ESM), it's not possible to boot my xen domUs anymore (dom0 is fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lts-trusty with Spectre/Meltdown mitigations). This is with xen 4.1.6.1-0ubuntu0.12.04.13 xend.log below : [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'], ['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux', ['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'], ['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'], ['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac', '02:00:5B:BD:5E:E2') [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain [2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free; need 16384; done. [2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 2 256 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x18000, memory_static_min=0x0. [2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2 vcpus=1 [2018-02-22 10:56:03 1566] DEBUG (image:721) domid = 2 [2018-02-22 10:56:03 1566] DEBUG (image:722) memsize= 6144 [2018-02-22 10:56:03 1566] DEBUG (image:723) image = /vmlinuz [2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn = 1 [2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2 [2018-02-22 10:56:03 1566] DEBUG (image:726) cmdline= root=/dev/xvda1 ro nogbpages console=hvc0 earlyprintk=xen nosplash
[Kernel-packages] [Bug 1751028] Re: impossible to start a xen domain on precise with the spectre/meltdown kernel
apport information ** Tags added: apport-collected ** Description changed: Hi, Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic - precise ESM), it's not possible to boot my xen domUs anymore (dom0 is fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lts- trusty with Spectre/Meltdown mitigations). This is with xen 4.1.6.1-0ubuntu0.12.04.13 xend.log below : [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'], ['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux', ['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'], ['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'], ['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac', '02:00:5B:BD:5E:E2') [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain [2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free; need 16384; done. [2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 2 256 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x18000, memory_static_min=0x0. [2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2 vcpus=1 [2018-02-22 10:56:03 1566] DEBUG (image:721) domid = 2 [2018-02-22 10:56:03 1566] DEBUG (image:722) memsize= 6144 [2018-02-22 10:56:03 1566] DEBUG (image:723) image = /vmlinuz [2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn = 1 [2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2 [2018-02-22 10:56:03 1566] DEBUG (image:726) cmdline= root=/dev/xvda1 ro nogbpages console=hvc0 earlyprintk=xen nosplash [2018-02-22 10:56:03 1566] DEBUG (image:727) ramdisk= /initrd.img [2018-02-22 10:56:03 1566] DEBUG (image:728)
[Kernel-packages] [Bug 1751028] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1751028/+attachment/5060310/+files/CurrentDmesg.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/1751028 Title: impossible to start a xen domain on precise with the spectre/meltdown kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic - precise ESM), it's not possible to boot my xen domUs anymore (dom0 is fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lts-trusty with Spectre/Meltdown mitigations). This is with xen 4.1.6.1-0ubuntu0.12.04.13 xend.log below : [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'], ['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux', ['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'], ['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'], ['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac', '02:00:5B:BD:5E:E2') [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain [2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free; need 16384; done. [2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 2 256 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x18000, memory_static_min=0x0. [2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2 vcpus=1 [2018-02-22 10:56:03 1566] DEBUG (image:721) domid = 2 [2018-02-22 10:56:03 1566] DEBUG (image:722) memsize= 6144 [2018-02-22 10:56:03 1566] DEBUG (image:723) image = /vmlinuz [2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn = 1 [2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2 [2018-02-22 10:56:03 1566] DEBUG (image:726) cmdline= root=/dev/xvda1 ro nogbpages console=hvc0 earlyprintk=xen nosplash
[Kernel-packages] [Bug 1751028] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1751028/+attachment/5060313/+files/Lsusb.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/1751028 Title: impossible to start a xen domain on precise with the spectre/meltdown kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic - precise ESM), it's not possible to boot my xen domUs anymore (dom0 is fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lts-trusty with Spectre/Meltdown mitigations). This is with xen 4.1.6.1-0ubuntu0.12.04.13 xend.log below : [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'], ['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux', ['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'], ['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'], ['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac', '02:00:5B:BD:5E:E2') [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain [2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free; need 16384; done. [2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 2 256 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x18000, memory_static_min=0x0. [2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2 vcpus=1 [2018-02-22 10:56:03 1566] DEBUG (image:721) domid = 2 [2018-02-22 10:56:03 1566] DEBUG (image:722) memsize= 6144 [2018-02-22 10:56:03 1566] DEBUG (image:723) image = /vmlinuz [2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn = 1 [2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2 [2018-02-22 10:56:03 1566] DEBUG (image:726) cmdline= root=/dev/xvda1 ro nogbpages console=hvc0 earlyprintk=xen nosplash
[Kernel-packages] [Bug 1751028] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1751028/+attachment/5060312/+files/Lspci.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/1751028 Title: impossible to start a xen domain on precise with the spectre/meltdown kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic - precise ESM), it's not possible to boot my xen domUs anymore (dom0 is fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lts-trusty with Spectre/Meltdown mitigations). This is with xen 4.1.6.1-0ubuntu0.12.04.13 xend.log below : [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'], ['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux', ['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'], ['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'], ['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac', '02:00:5B:BD:5E:E2') [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain [2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free; need 16384; done. [2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 2 256 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x18000, memory_static_min=0x0. [2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2 vcpus=1 [2018-02-22 10:56:03 1566] DEBUG (image:721) domid = 2 [2018-02-22 10:56:03 1566] DEBUG (image:722) memsize= 6144 [2018-02-22 10:56:03 1566] DEBUG (image:723) image = /vmlinuz [2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn = 1 [2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2 [2018-02-22 10:56:03 1566] DEBUG (image:726) cmdline= root=/dev/xvda1 ro nogbpages console=hvc0 earlyprintk=xen nosplash
[Kernel-packages] [Bug 1751028] Re: impossible to start a xen domain on precise with the spectre/meltdown kernel
$ cat /proc/version_signature Ubuntu 3.13.0-141.190~precise1-generic 3.13.11-ckt39 $ sudo lspci -vnvn 00:03.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 [1002:515e] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:31fb] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [90] PCI-X bridge device Secondary Status: 64bit+ 133MHz+ SCD- USC- SCO- SRD- Freq=133MHz Status: Dev=00:05.0 64bit- 133MHz- SCD- USC- SCO- SRD- Upstream: Capacity=0 CommitmentLimit=0 Downstream: Capacity=0 CommitmentLimit=0 Capabilities: [a0] HyperTransport: MSI Mapping Enable+ Fixed- Mapping Address Base: fee0 Capabilities: [b0] HyperTransport: Slave or Primary Interface Command: BaseUnitID=5 UnitCnt=3 MastHost- DefDir- Link Control 0: CFlE+ CST- CFE- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [a0] HyperTransport: MSI Mapping Enable+ Fixed- Mapping Address Base: fee0 Capabilities: [b0] Express (v1) Root Port (Slot-), MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us ExtTag- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 512 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <4us, L1 <16us ClockPM- Surprise+ LLActRep+ BwNot- LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- RootCtl: ErrCorrectable- ErrNon-Fatal+ ErrFatal+ PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Capabilities: [98] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] MSI: Enable- Count=1/2 Maskable- 64bit+ Address: Data: Capabilities: [78] Subsystem: Hewlett-Packard Company Device [103c:3113] Capabilities: [50] HyperTransport: Slave or Primary Interface Command: BaseUnitID=15 UnitCnt=5 MastHost- DefDir- DUL- Link Control 0: CFlE+ CST- CFE- Kernel driver in use: pcieport Kernel modules: shpchp 00:10.0 PCI bridge [0604]: Broadcom HT2100 PCI-Express Bridge [1166:0142] (rev a2) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [a0] HyperTransport: MSI Mapping Enable+ Fixed- Mapping Address Base: fee0 Capabilities: [b0] Express (v1) Root Port (Slot-), MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us ExtTag- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 512 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x8, ASPM L0s L1, Latency L0 <4us, L1 <16us ClockPM- Surprise+ LLActRep+ BwNot- LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x8, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- RootCtl: ErrCorrectable- ErrNon-Fatal+ ErrFatal+ PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID ,
[Kernel-packages] [Bug 1751028] [NEW] impossible to start a xen domain on precise with the spectre/meltdown kernel
Public bug reported: Hi, Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic - precise ESM), it's not possible to boot my xen domUs anymore (dom0 is fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lts- trusty with Spectre/Meltdown mitigations). This is with xen 4.1.6.1-0ubuntu0.12.04.13 xend.log below : [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'], ['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux', ['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'], ['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'], ['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac', '02:00:5B:BD:5E:E2') [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain [2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free; need 16384; done. [2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 2 256 [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x18000, memory_static_min=0x0. [2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2 vcpus=1 [2018-02-22 10:56:03 1566] DEBUG (image:721) domid = 2 [2018-02-22 10:56:03 1566] DEBUG (image:722) memsize= 6144 [2018-02-22 10:56:03 1566] DEBUG (image:723) image = /vmlinuz [2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn = 1 [2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2 [2018-02-22 10:56:03 1566] DEBUG (image:726) cmdline= root=/dev/xvda1 ro nogbpages console=hvc0 earlyprintk=xen nosplash [2018-02-22 10:56:03 1566] DEBUG (image:727) ramdisk= /initrd.img [2018-02-22 10:56:03 1566] DEBUG (image:728) vcpus = 1
[Kernel-packages] [Bug 1701316] Re: Data corruption with hio driver
So we tested both Huawei driver 2.1.0.40+patch on 4.10.0-26-generic (from the repo), and 4.10.0-25.29+lp1701316v201707070815 (which includes 2.1.0.28), and both work (at least mkfs.xfs, and loop jillrouleau mentioned above). -- 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/1701316 Title: Data corruption with hio driver Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Invalid Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: Fix Committed Bug description: Impact: Data corruption is seen when using the hio driver with 4.10 and later kernels. Fix: Patch to fix incorrect use of enumerated values as bitmasks. Test case: See below. Regression potential: Very low. Changes are simple and Obviously Correct (TM), and they only affect the hio driver. --- We are seeing data corruption issues using the hio driver with kernel 4.10.0 # uname -a Linux arbok 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Making xfs fails: root@arbok:~# mkfs.xfs /dev/hioa meta-data=/dev/hioa isize=512agcount=4, agsize=48835584 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0 data = bsize=4096 blocks=195342336, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=95382, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 bad magic number bad magic number Metadata corruption detected at xfs_sb block 0x0/0x200 libxfs_writebufr: write verifer failed on xfs_sb bno 0x0/0x200 The drive appears to be healthy. Firmware has been upgraded to ver 656: root@arbok:~# hio_info -d /dev/hioa hioaSerial number: 022XWV10G2000325 Size(GB): 800 Max size(GB): 800 Hardware version: 1.0 Firmware version: 656 Driver version: 2.1.0.28 Work mode: MLC Run time (sec.):8910490 Total read(MB):8499 Total write(MB):0 Lifetime remaining: 99.844% Max bad block rate: 0.167% Health: OK Comment:NA No relevant entries about read/write errors in dmesg Also just copying 8G random data and reading those back gives a hash mismatch: root@arbok:~# dd if=/dev/urandom of=test.dat bs=1G count=8 iflag=fullblock 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 85.6076 s, 100 MB/s root@arbok:~# dd if=test.dat of=/dev/hioa bs=1G count=8 iflag=fullblock 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 10.6034 s, 810 MB/s root@arbok:~# dd if=/dev/hioa of=read-back.dat bs=1G count=8 iflag=fullblock sha256sum test.dat read- 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 66.1872 s, 130 MB/s root@arbok:~# sha256sum test.dat read-back.dat 6376d245a07c42c990589a3c17c44e63d826d1cb583fc5a065deff9dae69fd3a test.dat ebfb4ef19ae410f190327b5ebd312711263bc7579970e87d9c1e2d84e06b3c25 read-back.dat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701316/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
OK cool. I think we can wait. Do you have an ETA for the fix to come down ? And will trusty also get the fix ? -- 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
Compute node is still up. I think we can consider upstream 4.4.23 to be good. -- 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
FAOD $ cat /proc/version Linux version 4.4.23-040423-generic (kernel@tangerine) (gcc version 5.3.1 20160413 (Ubuntu/Linaro 5.3.1-14ubuntu2) ) #201609300709 SMP Fri Sep 30 11:52:40 UTC 2016 -- 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
upstream 4.4.23 has been installed on a compute node, we'll let you know how it goes -- 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
Yes, this is with the kernel from #26 -- 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
It's booting \o/ We're trying to replicate the instability, we'll let you know. -- 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1608854] Re: [arm64] nova instances can't boot with 3.13.0-92
It boots fine ! $ cat /proc/version Linux version 3.13.0-97-generic (rtg@gloin) (gcc version 4.8.2 20140110 (prerelease) [ibm/gcc-4_8-branch merged from gcc-4_8-branch, revision 205847] (Ubuntu/Linaro 4.8.2-13ubuntu1) ) #144 SMP Mon Sep 12 16:38:12 UTC 2016 -- 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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in debian-installer source package in Trusty: New Status in linux source package in Trusty: In Progress Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1608854/+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 1608854] Re: [arm64] nova instances can't boot with 3.13.0-92
Hi Tim, I can't see any arm64 kernel in http://people.canonical.com/~rtg/arm64 -efi-lp1608854/, only amd64. -- 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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in debian-installer source package in Trusty: New Status in linux source package in Trusty: In Progress Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1608854/+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 1608854] Re: [arm64] nova instances can't boot with 3.13.0-92
Looks good to me : $ cat /proc/version Linux version 3.13.0-94-generic (rtg@gloin) (gcc version 4.8.2 20140110 (prerelease) [ibm/gcc-4_8-branch merged from gcc-4_8-branch, revision 205847] (Ubuntu/Linaro 4.8.2-13ubuntu1) ) #141 SMP Tue Aug 9 14:58:41 UTC 2016 -- 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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in debian-installer source package in Trusty: New Status in linux source package in Trusty: In Progress Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1608854/+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 1608854] Re: [arm64] nova instances can't boot with 3.13.0-92
So, just to be clear, you want us to test http://people.canonical.com/~rtg/arm64-efi-lp1608854/ ? This is the kernel built from git://kernel.ubuntu.com/rtg/ubuntu-trusty.git arm64 -efi-lp1608854 ? -- 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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in debian-installer source package in Trusty: New Status in linux source package in Trusty: In Progress Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1608854/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
Well, this 4.8-rc1 doesn't have CONFIG_VIRTUALIZATION so it's not very useful for a compute node kernel ... I reverted to 4.2. Can you please build a kernel with CONFIG_VIRTUALIZATION and CONFIG_KVM ? 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
4.8-rc1 had the same behaviour (landed into initramfs), so I figure I'd dig a bit. Long story short, this was entirely due to the following error : /scripts/init-top/udev: line 14: can't create /sys/kernel/uevent_helper: Permission denied CONFIG_UEVENT_HELPER was y in 4.2, but got switched to "not set" in at least 4.7 and 4.8. I modified /usr/share/initramfs-tools/scripts/init-top/udev to not error out on the "echo" to /sys/kernel/uevent_helper, and then the node booted properly \o/ I'll let you know if it's more stable or not. -- 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1608854] Re: [arm64] nova instances can't boot with 3.13.0-92
OK. For now I'm using 3.13.0-91 or inferior, which works fine. -- 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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in debian-installer source package in Trusty: New Status in linux source package in Trusty: In Progress Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1608854/+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 1608854] Re: [arm64] nova instances can't boot with 3.13.0-92
I think all the files are here ? ** 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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: Confirmed Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712258/+files/UdevLog.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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712256/+files/ProcModules.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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712255/+files/ProcInterrupts.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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712259/+files/WifiSyslog.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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712257/+files/UdevDb.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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] Re: [arm64] nova instances can't boot with 3.13.0-92
apport information ** Tags added: apport-collected ec2-images trusty ** Description changed: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. + --- + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.21 + Architecture: arm64 + ArecordDevices: Error: [Errno 2] No such file or directory + CRDA: Error: [Errno 2] No such file or directory + CurrentDmesg: + [ 27.314355] random: nonblocking pool is initialized + [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 + DistroRelease: Ubuntu 14.04 + Ec2AMI: ami-08ce + Ec2AMIManifest: FIXME + Ec2AvailabilityZone: nova + Ec2InstanceType: m1.medium + Ec2Kernel: None + Ec2Ramdisk: None + IwConfig: + lono wireless extensions. + + eth0 no wireless extensions. + Lspci: + + Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk + ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-85-generic N/A + linux-backports-modules-3.13.0-85-generic N/A + linux-firmware 1.127.22 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty ec2-images + Uname: Linux 3.13.0-85-generic aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712252/+files/AudioDevicesInUse.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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+subscriptions -- Mailing
[Kernel-packages] [Bug 1608854] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712253/+files/BootDmesg.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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712254/+files/ProcCpuinfo.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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] [NEW] [arm64] nova instances can't boot with 3.13.0-92
Public bug reported: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. ** 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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
Hi Joseph, I tried the 4.7, but it made the compute node unbootable : https://paste.ubuntu.com/21865889/ >From the initramfs shell, I had to manually load a few modules (ahci_xgene, >sd_mod and ext4) so I could mount the root filesystem and get back to the >previous working version (4.2). Was that expected ? Will the same thing happen with the 4.6 based yakkety kernel you pasted above ? 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
I can't find an arm64 build in http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.7-rc7/ -- 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
Yes we can do that. If you have documentation for this process, please let us know. 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1602577/+attachment/4699963/+files/WifiSyslog.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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1531768] Re: [arm64] lockups some time after booting
Filed LP#1602577 for the host instability issue on 4.4 -- 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/1531768 Title: [arm64] lockups some time after booting Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I want to use for armhf autopkgtesting in LXD). I started with wily as that has lxd available (it's not yet available in trusty nor the PPA for arm64). However, pretty much any LXD task that I do (I haven't tried much else) on this machine takes unbearably long. A simple "lxc profile set default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes. I see tons of [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0 [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds. in dmesg (the attached apport info has the complete dmesg). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 09:18 seq crw-rw 1 root audio 116, 33 Jan 7 09:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Jan 7 09:24:01 2016 IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. Lspci: 00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008] Subsystem: Red Hat, Inc Device [1af4:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+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 1602577] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1602577/+attachment/4699955/+files/CurrentDmesg.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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1602577/+attachment/4699959/+files/ProcInterrupts.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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1602577/+attachment/4699956/+files/IwConfig.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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1602577/+attachment/4699954/+files/BootDmesg.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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1602577/+attachment/4699961/+files/UdevDb.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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1602577/+attachment/4699957/+files/Lspci.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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1602577/+attachment/4699962/+files/UdevLog.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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1602577/+attachment/4699958/+files/ProcCpuinfo.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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1602577/+attachment/4699960/+files/ProcModules.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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
perf data is at : https://private- fileshare.canonical.com/~axino/swirlix01.perf.data.LP1602577.xz I'll run apport from this host, note that it's now running 4.2. Version string of the unstable kernel was : swirlix01 kernel: [0.00] Linux version 4.4.0-30-generic (buildd@bos01-arm64-006) (gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.3) ) #49~14.04.1-Ubuntu SMP Thu Jun 30 22:20:09 UTC 2016 (Ubuntu 4.4.0-30.49~14.04.1-generic 4.4.13) ** Tags added: apport-collected trusty uec-images ** Description changed: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jul 12 12:54 seq + crw-rw 1 root audio 116, 33 Jul 12 12:54 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.21 + Architecture: arm64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 14.04 + Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l + ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 + RelatedPackageVersions: + linux-restricted-modules-4.2.0-41-generic N/A + linux-backports-modules-4.2.0-41-generic N/A + linux-firmware1.127.22 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty uec-images + Uname: Linux 4.2.0-41-generic aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True -- 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags:
[Kernel-packages] [Bug 1602577] [NEW] [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
Public bug reported: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected trusty uec-images -- 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1531768] Re: [arm64] lockups some time after booting
Hi, I'm sorry but 4.4 is too unstable on the hosts. We have to reboot and/or power cycle them multiple times a day. We're back on 4.2 everywhere. Haw gathered some perf data on a failing 4.4 host, perhaps we can start digging the issue from here ? Perhaps it should be a separate bug as well. 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/1531768 Title: [arm64] lockups some time after booting Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I want to use for armhf autopkgtesting in LXD). I started with wily as that has lxd available (it's not yet available in trusty nor the PPA for arm64). However, pretty much any LXD task that I do (I haven't tried much else) on this machine takes unbearably long. A simple "lxc profile set default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes. I see tons of [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0 [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds. in dmesg (the attached apport info has the complete dmesg). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 09:18 seq crw-rw 1 root audio 116, 33 Jan 7 09:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Jan 7 09:24:01 2016 IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. Lspci: 00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008] Subsystem: Red Hat, Inc Device [1af4:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+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 1531768] Re: [arm64] lockups when idle if tickless (nohz=on) is used
Hi ! kvm cmdline : https://paste.ubuntu.com/17430254/ cpuinfo : https://paste.ubuntu.com/17430265/ dmesg: https://paste.ubuntu.com/17430277/ -- 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/1531768 Title: [arm64] lockups when idle if tickless (nohz=on) is used Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I want to use for armhf autopkgtesting in LXD). I started with wily as that has lxd available (it's not yet available in trusty nor the PPA for arm64). However, pretty much any LXD task that I do (I haven't tried much else) on this machine takes unbearably long. A simple "lxc profile set default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes. I see tons of [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0 [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds. in dmesg (the attached apport info has the complete dmesg). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 09:18 seq crw-rw 1 root audio 116, 33 Jan 7 09:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Jan 7 09:24:01 2016 IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. Lspci: 00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008] Subsystem: Red Hat, Inc Device [1af4:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 12:23 seq crw-rw 1 root audio 116, 33 Nov 24 12:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL385 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-36-generic root=UUID=13289ac9-8dc9-4feb-b6bd-ca7db66b21d6 ro console=tty0 console=ttyS1,38400 nosplash crashkernel=384M-:512M nox2apic intremap=off ProcVersionSignature: Ubuntu 3.19.0-36.41~14.04.1hf00090138v20151122b1-generic 3.19.8-ckt9 RelatedPackageVersions: linux-restricted-modules-3.19.0-36-generic N/A linux-backports-modules-3.19.0-36-generic N/A linux-firmware 1.127.18 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.19.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/02/2014 dmi.bios.vendor: HP dmi.bios.version: A18 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrA18:bd02/02/2014:svnHP:pnProLiantDL385G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL385 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
I resumed the tests on Monday, and so far we're looking good. Your change prevented ~10 locks so far, it would seem. -- 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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 12:23 seq crw-rw 1 root audio 116, 33 Nov 24 12:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL385 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-36-generic root=UUID=13289ac9-8dc9-4feb-b6bd-ca7db66b21d6 ro console=tty0 console=ttyS1,38400 nosplash crashkernel=384M-:512M nox2apic intremap=off ProcVersionSignature: Ubuntu 3.19.0-36.41~14.04.1hf00090138v20151122b1-generic 3.19.8-ckt9 RelatedPackageVersions: linux-restricted-modules-3.19.0-36-generic N/A linux-backports-modules-3.19.0-36-generic N/A linux-firmware 1.127.18 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.19.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/02/2014 dmi.bios.vendor: HP dmi.bios.version: A18 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrA18:bd02/02/2014:svnHP:pnProLiantDL385G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL385 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
I applied the patch, and it saved a reboot twice already, I think. dmesg from one server : http://pastebin.ubuntu.com/14438525/ I have to stop the tests for the weekend though, I'll resume on Monday. -- 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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 12:23 seq crw-rw 1 root audio 116, 33 Nov 24 12:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL385 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-36-generic root=UUID=13289ac9-8dc9-4feb-b6bd-ca7db66b21d6 ro console=tty0 console=ttyS1,38400 nosplash crashkernel=384M-:512M nox2apic intremap=off ProcVersionSignature: Ubuntu 3.19.0-36.41~14.04.1hf00090138v20151122b1-generic 3.19.8-ckt9 RelatedPackageVersions: linux-restricted-modules-3.19.0-36-generic N/A linux-backports-modules-3.19.0-36-generic N/A linux-firmware 1.127.18 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.19.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/02/2014 dmi.bios.vendor: HP dmi.bios.version: A18 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrA18:bd02/02/2014:svnHP:pnProLiantDL385G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL385 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
Re-reading comment #318 Dan, I realize that we may be investigating a symptom and not the root cause. Whenever the soft-lockup happens, the serial console does get flooded "block nbdX: Attempted send on closed socket". If the serial console getting flooded causes soft lockups, then it is indeed a concerning issue, but shouldn't we focus, in this bug, on making nbd not flood the console in the first place ? -- 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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 12:23 seq crw-rw 1 root audio 116, 33 Nov 24 12:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL385 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-36-generic root=UUID=13289ac9-8dc9-4feb-b6bd-ca7db66b21d6 ro console=tty0 console=ttyS1,38400 nosplash crashkernel=384M-:512M nox2apic intremap=off ProcVersionSignature: Ubuntu 3.19.0-36.41~14.04.1hf00090138v20151122b1-generic 3.19.8-ckt9 RelatedPackageVersions: linux-restricted-modules-3.19.0-36-generic N/A linux-backports-modules-3.19.0-36-generic N/A linux-firmware 1.127.18 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.19.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/02/2014 dmi.bios.vendor: HP dmi.bios.version: A18 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrA18:bd02/02/2014:svnHP:pnProLiantDL385G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL385 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
Hi Dan, Thanks for your investigation. Sorry for the delay, but finally I managed to reboot the compute nodes with the "notsc" kernel parameter. I also disabled the qemu-nbd workaround. Once that was done, it didn't take long for a node to crash, which would indicate that notsc didn't fix the problem. However, the host got stuck and didn't dump anything. OK then. It happened a second time a few minutes after on a different host, so I thought I'd investigate this more. It turns out, the kernel booted through kexec fails booting probably because of the notsc option : https://pastebin.canonical.com/146714/ I'm a bit worried about the following line : [0.00] tsc: Kernel compiled with CONFIG_X86_TSC, cannot disable TSC completely which is also displayed during "regular" boots (eg not through kexec). I guess I can remove "notsc" from the kexec command line, but this will take additional time. I thought I'd let you know the current status in the meantime. Cheers -- 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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 12:23 seq crw-rw 1 root audio 116, 33 Nov 24 12:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL385 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-36-generic root=UUID=13289ac9-8dc9-4feb-b6bd-ca7db66b21d6 ro console=tty0 console=ttyS1,38400 nosplash crashkernel=384M-:512M nox2apic intremap=off ProcVersionSignature: Ubuntu 3.19.0-36.41~14.04.1hf00090138v20151122b1-generic 3.19.8-ckt9 RelatedPackageVersions: linux-restricted-modules-3.19.0-36-generic N/A linux-backports-modules-3.19.0-36-generic N/A linux-firmware 1.127.18 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.19.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/02/2014 dmi.bios.vendor: HP dmi.bios.version: A18 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrA18:bd02/02/2014:svnHP:pnProLiantDL385G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL385 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1505564] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1505564/+attachment/4524659/+files/WifiSyslog.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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 12:23 seq crw-rw 1 root audio 116, 33 Nov 24 12:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL385 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-36-generic root=UUID=13289ac9-8dc9-4feb-b6bd-ca7db66b21d6 ro console=tty0 console=ttyS1,38400 nosplash crashkernel=384M-:512M nox2apic intremap=off ProcVersionSignature: Ubuntu 3.19.0-36.41~14.04.1hf00090138v20151122b1-generic 3.19.8-ckt9 RelatedPackageVersions: linux-restricted-modules-3.19.0-36-generic N/A linux-backports-modules-3.19.0-36-generic N/A linux-firmware 1.127.18 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.19.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/02/2014 dmi.bios.vendor: HP dmi.bios.version: A18 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrA18:bd02/02/2014:svnHP:pnProLiantDL385G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL385 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1505564] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1505564/+attachment/4524650/+files/CRDA.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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 12:23 seq crw-rw 1 root audio 116, 33 Nov 24 12:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL385 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-36-generic root=UUID=13289ac9-8dc9-4feb-b6bd-ca7db66b21d6 ro console=tty0 console=ttyS1,38400 nosplash crashkernel=384M-:512M nox2apic intremap=off ProcVersionSignature: Ubuntu 3.19.0-36.41~14.04.1hf00090138v20151122b1-generic 3.19.8-ckt9 RelatedPackageVersions: linux-restricted-modules-3.19.0-36-generic N/A linux-backports-modules-3.19.0-36-generic N/A linux-firmware 1.127.18 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.19.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/02/2014 dmi.bios.vendor: HP dmi.bios.version: A18 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrA18:bd02/02/2014:svnHP:pnProLiantDL385G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL385 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
apport information ** Description changed: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Nov 24 12:23 seq + crw-rw 1 root audio 116, 33 Nov 24 12:23 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.19 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 14.04 + IwConfig: Error: [Errno 2] No such file or directory + MachineType: HP ProLiant DL385 G7 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-36-generic root=UUID=13289ac9-8dc9-4feb-b6bd-ca7db66b21d6 ro console=tty0 console=ttyS1,38400 nosplash crashkernel=384M-:512M nox2apic intremap=off + ProcVersionSignature: Ubuntu 3.19.0-36.41~14.04.1hf00090138v20151122b1-generic 3.19.8-ckt9 + RelatedPackageVersions: + linux-restricted-modules-3.19.0-36-generic N/A + linux-backports-modules-3.19.0-36-generic N/A + linux-firmware 1.127.18 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty uec-images + Uname: Linux 3.19.0-36-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 02/02/2014 + dmi.bios.vendor: HP + dmi.bios.version: A18 + dmi.chassis.type: 23 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrA18:bd02/02/2014:svnHP:pnProLiantDL385G7:pvr:cvnHP:ct23:cvr: + dmi.product.name: ProLiant DL385 G7 + dmi.sys.vendor: HP ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1505564/+attachment/4524649/+files/BootDmesg.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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 12:23 seq crw-rw 1 root audio 116, 33 Nov 24 12:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL385 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-36-generic root=UUID=13289ac9-8dc9-4feb-b6bd-ca7db66b21d6 ro console=tty0 console=ttyS1,38400 nosplash crashkernel=384M-:512M nox2apic intremap=off ProcVersionSignature: Ubuntu 3.19.0-36.41~14.04.1hf00090138v20151122b1-generic 3.19.8-ckt9 RelatedPackageVersions: linux-restricted-modules-3.19.0-36-generic N/A linux-backports-modules-3.19.0-36-generic N/A linux-firmware 1.127.18 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.19.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/02/2014 dmi.bios.vendor: HP dmi.bios.version: A18 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrA18:bd02/02/2014:svnHP:pnProLiantDL385G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL385 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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