[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
** Changed in: maas Importance: Critical => Undecided -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+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 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Setting this back to incomplete for MAAS because there is not enough information to determine this is a MAAS Bug. That said, given that this work with any VM other than one with 2048 of RAM, the issue may appear to be the kernel or libvirt. -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+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 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
** Changed in: maas Status: Confirmed => 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+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 1805920] Re: iPXE ignores vlan 0 traffic
FWIW, Cisco documentation here states that priority tagging is enabled by default: https://www.cisco.com/c/en/us/td/docs/switches/connectedgrid/cg-switch- sw-master/software/configuration/guide/vlan0/b_vlan_0.html "Default Settings VLAN 0 priority tagging is enabled by default." -- 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/1805920 Title: iPXE ignores vlan 0 traffic Status in MAAS: Invalid Status in ipxe package in Ubuntu: Fix Released Status in ipxe-qemu-256k-compat package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in ipxe source package in Trusty: Won't Fix Status in ipxe source package in Xenial: Won't Fix Status in ipxe source package in Bionic: Incomplete Status in ipxe source package in Cosmic: Incomplete Status in ipxe source package in Disco: Fix Released Bug description: [Impact] * VLAN 0 is special (for QoS actually, not a real VLAN) * Some components in the stack accidentally strip it, so does ipxe in this case. * Fix by porting a fix that is carried by other distributions as upstream didn't follow the suggestion but it is needed for the use case affected by the bug here (Thanks Andres) [Test Case] * TODO [Regression Potential] * The only reference to VLAN tags on iPXE boot that we found was on iBFT boot for SCSI, we tested that in comment #34 and it still worked fine. * We didn't see such cases on review, but there might be use cases that made some unexpected use of the headers which are now stripped. But that seems wrong. [Other Info] * n/a --- I have three MAAS rack/region nodes which are blades in a Cisco UCS chassis. This is an FCE deployment where MAAS has two DHCP servers, infra1 is the primary and infra3 is the secondary. The pod VMs on infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE boot. If I reconfigure the subnet to provide DHCP on infra2 (either as primary or secondary) then the pod VMs on infra2 will PXE boot but the pod VMs on the demoted infra node (that no longer serves DHCP) now fail to PXE boot. While commissioning a pod VM on infra2 I captured network traffic with tcpdump on the vnet interface. Here is the dump when the PXE boot fails (no dhcp server on infra2): https://pastebin.canonical.com/p/THW2gTSv4S/ Here is the dump when PXE boot succeeds (when infra2 is serving dhcp): https://pastebin.canonical.com/p/HH3XvZtTGG/ The only difference I can see is that in the unsuccessful scenario, the reply is an 802.1q packet -- it's got a vlan tag for vlan 0. Normally vlan 0 traffic is passed as if it is not tagged and indeed, I can ping between the blades with no problem. Outgoing packets are untagged but incoming packets are tagged vlan 0 -- but the ping works. It seems vlan 0 is used as a part of 802.1p to set priority of packets. This is separate from vlan, it just happens to use that ethertype to do the priority tagging. Someone confirmed to me that, in the iPXE source, it drops all packets if they are vlan tagged. The customer is unable to figure out why the packets between blades is getting vlan tagged so we either need to figure out how to allow iPXE to accept vlan 0 or the customer will need to use different equipment for the MAAS nodes. I found a conversation on the ipxe-devel mailing list that suggested a commit was submitted and signed off but that was from 2016 so I'm not sure what became of it. Notable messages in the thread: http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html Would it be possible to install a local patch as part of the FCE deployment? I suspect the patch(es) mentioned in the above thread would require some modification to apply properly. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+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 1805920] Re: iPXE ignores vlan 0 traffic
Just to clarify the above statements as it has been source of confusion. MAAS 2.3+ (which is the latest available in Xenial), no longer uses nor supports iSCSI. While the option to fallback to old behavior does exist, it is not enabled by default, its obscured and, given that is not supported, it is to be used at users risk. That said, I'm not sure whether this change should be backported all the way to Xenial. It would seem to be that it should be backported to Bionic only. -- 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/1805920 Title: iPXE ignores vlan 0 traffic Status in MAAS: Invalid Status in ipxe package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have three MAAS rack/region nodes which are blades in a Cisco UCS chassis. This is an FCE deployment where MAAS has two DHCP servers, infra1 is the primary and infra3 is the secondary. The pod VMs on infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE boot. If I reconfigure the subnet to provide DHCP on infra2 (either as primary or secondary) then the pod VMs on infra2 will PXE boot but the pod VMs on the demoted infra node (that no longer serves DHCP) now fail to PXE boot. While commissioning a pod VM on infra2 I captured network traffic with tcpdump on the vnet interface. Here is the dump when the PXE boot fails (no dhcp server on infra2): https://pastebin.canonical.com/p/THW2gTSv4S/ Here is the dump when PXE boot succeeds (when infra2 is serving dhcp): https://pastebin.canonical.com/p/HH3XvZtTGG/ The only difference I can see is that in the unsuccessful scenario, the reply is an 802.1q packet -- it's got a vlan tag for vlan 0. Normally vlan 0 traffic is passed as if it is not tagged and indeed, I can ping between the blades with no problem. Outgoing packets are untagged but incoming packets are tagged vlan 0 -- but the ping works. It seems vlan 0 is used as a part of 802.1p to set priority of packets. This is separate from vlan, it just happens to use that ethertype to do the priority tagging. Someone confirmed to me that, in the iPXE source, it drops all packets if they are vlan tagged. The customer is unable to figure out why the packets between blades is getting vlan tagged so we either need to figure out how to allow iPXE to accept vlan 0 or the customer will need to use different equipment for the MAAS nodes. I found a conversation on the ipxe-devel mailing list that suggested a commit was submitted and signed off but that was from 2016 so I'm not sure what became of it. Notable messages in the thread: http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html Would it be possible to install a local patch as part of the FCE deployment? I suspect the patch(es) mentioned in the above thread would require some modification to apply properly. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+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 1805920] Re: iPXE ignores vlan 0 traffic
FWIW, I patched ipxe with the CentOS patch as a test, which Vern was going to test: https://launchpadlibrarian.net/400355423/ipxe_1.0.0+git-20180124.fbe8c52d-0ubuntu2_1.0.0+git-20180124.fbe8c52d-0ubuntu2.2~18.04.1.diff.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/1805920 Title: iPXE ignores vlan 0 traffic Status in MAAS: Invalid Status in ipxe package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have three MAAS rack/region nodes which are blades in a Cisco UCS chassis. This is an FCE deployment where MAAS has two DHCP servers, infra1 is the primary and infra3 is the secondary. The pod VMs on infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE boot. If I reconfigure the subnet to provide DHCP on infra2 (either as primary or secondary) then the pod VMs on infra2 will PXE boot but the pod VMs on the demoted infra node (that no longer serves DHCP) now fail to PXE boot. While commissioning a pod VM on infra2 I captured network traffic with tcpdump on the vnet interface. Here is the dump when the PXE boot fails (no dhcp server on infra2): https://pastebin.canonical.com/p/THW2gTSv4S/ Here is the dump when PXE boot succeeds (when infra2 is serving dhcp): https://pastebin.canonical.com/p/HH3XvZtTGG/ The only difference I can see is that in the unsuccessful scenario, the reply is an 802.1q packet -- it's got a vlan tag for vlan 0. Normally vlan 0 traffic is passed as if it is not tagged and indeed, I can ping between the blades with no problem. Outgoing packets are untagged but incoming packets are tagged vlan 0 -- but the ping works. It seems vlan 0 is used as a part of 802.1p to set priority of packets. This is separate from vlan, it just happens to use that ethertype to do the priority tagging. Someone confirmed to me that, in the iPXE source, it drops all packets if they are vlan tagged. The customer is unable to figure out why the packets between blades is getting vlan tagged so we either need to figure out how to allow iPXE to accept vlan 0 or the customer will need to use different equipment for the MAAS nodes. I found a conversation on the ipxe-devel mailing list that suggested a commit was submitted and signed off but that was from 2016 so I'm not sure what became of it. Notable messages in the thread: http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html Would it be possible to install a local patch as part of the FCE deployment? I suspect the patch(es) mentioned in the above thread would require some modification to apply properly. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+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 1805920] Re: iPXE ignores vlan 0 traffic
Seems other users in other distros experiencing the same, and a kernel update fixes the issues? https://serverfault.com/questions/497391/ ** Also 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/1805920 Title: iPXE ignores vlan 0 traffic Status in MAAS: Invalid Status in ipxe package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I have three MAAS rack/region nodes which are blades in a Cisco UCS chassis. This is an FCE deployment where MAAS has two DHCP servers, infra1 is the primary and infra3 is the secondary. The pod VMs on infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE boot. If I reconfigure the subnet to provide DHCP on infra2 (either as primary or secondary) then the pod VMs on infra2 will PXE boot but the pod VMs on the demoted infra node (that no longer serves DHCP) now fail to PXE boot. While commissioning a pod VM on infra2 I captured network traffic with tcpdump on the vnet interface. Here is the dump when the PXE boot fails (no dhcp server on infra2): https://pastebin.canonical.com/p/THW2gTSv4S/ Here is the dump when PXE boot succeeds (when infra2 is serving dhcp): https://pastebin.canonical.com/p/HH3XvZtTGG/ The only difference I can see is that in the unsuccessful scenario, the reply is an 802.1q packet -- it's got a vlan tag for vlan 0. Normally vlan 0 traffic is passed as if it is not tagged and indeed, I can ping between the blades with no problem. Outgoing packets are untagged but incoming packets are tagged vlan 0 -- but the ping works. It seems vlan 0 is used as a part of 802.1p to set priority of packets. This is separate from vlan, it just happens to use that ethertype to do the priority tagging. Someone confirmed to me that, in the iPXE source, it drops all packets if they are vlan tagged. The customer is unable to figure out why the packets between blades is getting vlan tagged so we either need to figure out how to allow iPXE to accept vlan 0 or the customer will need to use different equipment for the MAAS nodes. I found a conversation on the ipxe-devel mailing list that suggested a commit was submitted and signed off but that was from 2016 so I'm not sure what became of it. Notable messages in the thread: http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html Would it be possible to install a local patch as part of the FCE deployment? I suspect the patch(es) mentioned in the above thread would require some modification to apply properly. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+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 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
** Changed in: maas Milestone: 2.5.0rc1 => None -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+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 1743595] Re: modprobing mlx5_core doesn't bring the interface up
** Tags added: track -- 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/1743595 Title: modprobing mlx5_core doesn't bring the interface up Status in MAAS: New Status in linux package in Ubuntu: Incomplete Bug description: ubuntu@wrlsrvr321:~$ sudo -i root@wrlsrvr321:~# lsmod Module Size Used by ipmi_devintf 20480 0 iscsi_tcp 20480 0 libiscsi_tcp 24576 1 iscsi_tcp libiscsi 53248 2 libiscsi_tcp,iscsi_tcp scsi_transport_iscsi98304 3 iscsi_tcp,libiscsi overlay49152 1 btrfs 991232 0 raid10 49152 0 raid456 110592 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_pq,raid456,async_xor,async_memcpy,async_raid6_recov xor24576 2 btrfs,async_xor raid6_pq 102400 4 async_pq,raid456,btrfs,async_raid6_recov libcrc32c 16384 1 raid456 raid1 36864 0 raid0 20480 0 multipath 16384 0 linear 16384 0 ipmi_ssif 24576 0 ses20480 0 enclosure 16384 1 ses scsi_transport_sas 45056 1 ses hid_generic16384 0 mxm_wmi16384 0 crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 aesni_intel 167936 0 aes_x86_64 20480 1 aesni_intel lrw16384 1 aesni_intel gf128mul 16384 1 lrw glue_helper16384 1 aesni_intel ablk_helper16384 1 aesni_intel cryptd 20480 3 ghash_clmulni_intel,aesni_intel,ablk_helper i2c_algo_bit 16384 0 ttm98304 0 drm_kms_helper155648 0 ixgbe 290816 0 syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper dca16384 1 ixgbe sysimgblt 16384 1 drm_kms_helper vxlan 49152 1 ixgbe fb_sys_fops16384 1 drm_kms_helper ip6_udp_tunnel 16384 1 vxlan drm 364544 2 ttm,drm_kms_helper udp_tunnel 16384 1 vxlan usbhid 49152 0 ptp20480 1 ixgbe ahci 36864 0 hid 118784 2 hid_generic,usbhid libahci32768 1 ahci pps_core 20480 1 ptp megaraid_sas 135168 0 mdio 16384 1 ixgbe ipmi_si57344 0 fjes 28672 0 ipmi_msghandler49152 3 ipmi_ssif,ipmi_devintf,ipmi_si wmi20480 1 mxm_wmi root@wrlsrvr321:~# root@wrlsrvr321:~# lspci | grep Mell 81:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5] root@wrlsrvr321:~# root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:130767 errors:0 dropped:30 overruns:0 frame:0 TX packets:20809 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:196717409 (196.7 MB) TX bytes:1575915 (1.5 MB) enp3s0f1 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:81 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@wrlsrvr321:~# modprobe mlx5_core root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:131663 errors:0 dropped:59 overruns:0 frame:0 TX packets:21456 errors:0 dropped:0
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Tested the 4.17 kernel, and this is the issue I now see:
[...]
[ 17.340040] raid6: sse2x1 xor() 2828 MB/s
[ 17.408036] raid6: sse2x2 gen() 7445 MB/s
[ 17.472037] raid6: sse2x2 xor() 5425 MB/s
[ 17.540032] raid6: sse2x4 gen() 10259 MB/s
[ 17.604037] raid6: sse2x4 xor() 6286 MB/s
[ 17.668034] raid6: avx2x1 gen() 14089 MB/s
[ 17.732034] raid6: avx2x1 xor() 9346 MB/s
[ 17.796035] raid6: avx2x2 gen() 16758 MB/s
[ 17.860033] raid6: avx2x2 xor() 9779 MB/s
[ 17.924034] raid6: avx2x4 gen() 19079 MB/s
[ 17.988036] raid6: avx2x4 xor() 11383 MB/s
[ 18.007313] raid6: using algorithm avx2x4 gen() 19079 MB/s
[ 18.031519] raid6: xor() 11383 MB/s, rmw enabled
[ 18.054148] raid6: using avx2x2 recovery algorithm
[ 18.076927] xor: automatically using best checksumming function avx
[ 18.109754] async_tx: api initialized (async)
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... [ 18.199553] Btrfs loaded,
crc32c=crc32c-intel
Scanning for Btrfs filesystems
done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ...
mdadm: No devices listed in conf file were found.
done.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: error opening /dev/md?*: No such file or directory
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
mdadm: No devices listed in conf file were found.
done.
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! UUID=bd0dbca3-60b8-474e-ac82-96f1b9ff9cc2 does not exist. Dropping to
a shell!
BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
--
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/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]:
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Maybe I did something wrong, but this kernel (4.18) causes a kernel panic. The process I followed was same as always, to wget the *.deb, dpkg -i *.deb && update-grub at the end to ensure this kernel is used: [6.538003] evm: security.SMACK64 [6.539108] evm: security.SMACK64EXEC [6.540387] evm: security.SMACK64TRANSMUTE [6.541798] evm: security.SMACK64MMAP [6.543023] evm: security.apparmor [6.544209] evm: security.ima [6.545253] evm: security6.668405] usb 2-1: New USB device found, idVendor=8087, idProduct=8002, bcdDevice= 0.05 [6.885734] evm: HMAC attrs: 0x1 [6.886472] Magic number: 14:225:302 [7.048969] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [7.050067] tty tty31: hash matches [7.054948] memory memory160: hash matches [7.056460] rtc_cmos 00:00: setting system clock to 2018-08-14 23:16:59 UTC (1534288619) [7.056552] hub 2-1:1.0: USB hub found [7.060431] hub 2-1:1.0: 8 ports detected [7.063051] md: Waiting for all devices to be available before autodetect [7.093858] md: If you don't use raid, use raid=noautodetect [7.118684] md: Autodetecting RAID arrays. [7.137860] md: autorun ... [7.150409] md: ... autorun DONE. [7.165346] VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6 [7.197757] Please append a correct "root=" boot option; here are the available partitions: [7.235391] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [7.273379] CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.18.0-041800-generic #201808122131 [7.310122] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [7.544633] Call Trace: [7.62] dump_stack+0x63/0x83 [7.570510] panic+0xe7/0x247 [7.583414] mount_block_root+0x231/0x2d8 [7.601354] ? do_early_param+0x95/0x95 [7.618598] mount_root+0x7c/0x7f [7.634231] prepare_namespace+0x139/0x171 [7.653611] kernel_init_freeable+0x236/0x261 [7.673689] ? rest_init+0xb0/0xb0 [7.64] kernel_init+0xe/0x104 [7.704165] ret_from_fork+0x35/0x40 [7.720293] Kernel Offset: 0x29e0 from 0x8100 (relocation range: 0x8000-0xbfff) [7.772913] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- [7.815580] [ cut here ] [7.836276] sched: Unexpected reschedule of offline CPU#0! [7.860432] WARNING: CPU: 6 PID: 1 at arch/x86/kernel/smp.c:128 native_smp_send_reschedule+0x3a/0x40 [7.902510] Modules linked in: [7.916373] CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.18.0-041800-generic #201808122131 [7.953258] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [8.089242] RIP: 0010:native_smp_send_reschedule+0x3a/0x40 [8.113868] Code: cf 62 01 73 17 48 8b 05 94 8c 17 01 be fd 00 00 00 48 8b 40 30 e8 06 a1 ba 00 5d c3 89 fe 48 c7 c7 58 c1 ed ab e8 48 41 03 00 <0f> 0b 5d c3 66 90 0f 1f 44 00 00 55 48 89 e5 53 48 83 ec 20 65 48 [8.198752] RSP: :8cc61f383e08 EFLAGS: 00010086 [8.24] RAX: RBX: 0003 RCX: ac262608 [8.254674] RDX: 0001 RSI: 0096 RDI: 0046 [8.287087] RBP: 8cc61f383e08 R08: 000cc2b4 R09: 0358 [8.319325] R10: 000f R11: ac7837ed R12: [8.351381] R13: 0003 R14: 8cc61b474500 R15: aaf24bc0 [8.383431] FS: () GS:8cc61f38() knlGS: [8.419863] CS: 0010 DS: ES: CR0: 80050033 [8.446342] CR2: CR3: 0001b020a001 CR4: 003606e0 [8.479621] DR0: DR1: DR2: [8.516202] DR3: DR6: fffe0ff0 DR7: 0400 [8.550084] Call Trace: [8.560999] [8.570157] kick_ilb+0x85/0x90 [8.584223] trigger_load_balance+0xa3/0x190 [8.603397] ? tick_sched_do_timer+0x60/0x60 [8.623122] scheduler_tick+0xae/0xd0 [8.639704] update_process_times+0x42/0x60 [8.658527] tick_sched_handle+0x29/0x60 [8.676734] tick_sched_timer+0x3c/0x80 [8.694426] __hrtimer_run_queues+0x107/0x270 [8.714088] hrtimer_interrupt+0x101/0x220 [8.732405] smp_apic_timer_interrupt+0x67/0x130 [8.753195] apic_timer_interrupt+0xf/0x20 [8.771190] [8.780539] RIP: 0010:panic+0x201/0x247 [8.798007] Code: eb a6 83 3d 27 ee 8e 01 00 74 05 e8 10 6b 02 00 48 c7 c6 20 c1 77 ac 48 c7 c7 78 59 ee ab e8 a0 59 06 00 fb 66 0f 1f 44 00 00 <31> db e8 2f a7 0d 00 4c 39 eb 7c 1d 41 83 f4 01 48 8b 05 cf ed 8e [8.882850] RSP: :a274c3167d78 EFLAGS: 0246 ORIG_RAX: ff13 [8.917249] RAX: 005c RBX: 8cc619067000 RCX: ac262608 [8.949417] RDX: RSI:
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Hi Joseph,
Sorry for such a late reply, but with all the recent business travel
I've been unable to continue working on this.
That said, now that things are calmer I can continue, however, I don't
have easy access the hardware in question and it is very time consuming
getting access to this while blocking all the other work that happens
with this hardware.
Is there a way to have all those kernels available so I can test things
in one go?
--
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/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Incomplete
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1777744] Re: Bionic 4.15.0-23-generic on ppc64 kernel panic's during PXE boot
** 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/144 Title: Bionic 4.15.0-23-generic on ppc64 kernel panic's during PXE boot Status in linux package in Ubuntu: Confirmed Bug description: In the MAAS CI we test ppc64, and in the most recent runs (~from the last 1.5 weeks) the CI started failing with the ppc64le machine never enlisting in MAAS. Once we have looked at this, we noticed that there's a kernel panic when loading the ephemeral environment. This is a regression version the previous kernel, provided that this is a recent issue. Current kernel: 4.15.0-23-generic See console log for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/144/+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 1777744] Re: Bionic 4.15.0-23-generic on ppc64 kernel panic's during PXE boot
** Description changed: - The MAAS CI has a PPC64 machine which is failing to boot into the - ephemeral environment. Petite boot loads and kexecs 4.15.0-23-generic - from 4.4.27-openpower1 but 4.15 panics before the initrd is loaded. + In the MAAS CI we test ppc64, and in the most recent runs (~from the + last 1.5 weeks) the CI started failing with the ppc64le machine never + enlisting in MAAS. + + Once we have looked at this, we noticed that there's a kernel panic when + loading the ephemeral environment. This is a regression version the + previous kernel, provided that this is a recent issue. + + Current kernel: 4.15.0-23-generic + + See console log for details. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/144 Title: Bionic 4.15.0-23-generic on ppc64 kernel panic's during PXE boot Status in linux package in Ubuntu: New Bug description: In the MAAS CI we test ppc64, and in the most recent runs (~from the last 1.5 weeks) the CI started failing with the ppc64le machine never enlisting in MAAS. Once we have looked at this, we noticed that there's a kernel panic when loading the ephemeral environment. This is a regression version the previous kernel, provided that this is a recent issue. Current kernel: 4.15.0-23-generic See console log for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/144/+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 1777744] Re: ppc64 4.15.0-23-generic kernel panic during PXE boot
** Summary changed: - 4.15.0-23-generic fails to PXE boot on PPC64 + ppc64 4.15.0-23-generic kernel panic during PXE boot ** Summary changed: - ppc64 4.15.0-23-generic kernel panic during PXE boot + Bionic 4.15.0-23-generic on ppc64 kernel panic's during PXE boot -- 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/144 Title: Bionic 4.15.0-23-generic on ppc64 kernel panic's during PXE boot Status in linux package in Ubuntu: New Bug description: In the MAAS CI we test ppc64, and in the most recent runs (~from the last 1.5 weeks) the CI started failing with the ppc64le machine never enlisting in MAAS. Once we have looked at this, we noticed that there's a kernel panic when loading the ephemeral environment. This is a regression version the previous kernel, provided that this is a recent issue. Current kernel: 4.15.0-23-generic See console log for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/144/+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 1772490] Re: 'Deploying' timed out after 40 minutes / Failedbcache: register_bcache() error
*** This bug is a duplicate of bug 1768893 *** https://bugs.launchpad.net/bugs/1768893 After further looking into this, I can determine that: 1. Curtin installed successfully despite the kernel issues 1. Curtin told MAAS the installation completed successfully. 3. cloud-init told the machine to reboot. At this point, we lose all logs, but from what we can see is that: 1. The machine never attempted to PXE boot post-deployment 2. There's no indication that the machine actually booted into the installed environment. This leads me to believe that due to the kernel error above, the kernel could have crashed right before the machine rebooted, which prevented the machine from rebooting into the installed system. This is not something available in the rsyslog because at the time, networking is down. This would only show on a console log. That said, the logs definitely show that the machine never came up again. -- 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/1772490 Title: 'Deploying' timed out after 40 minutes / Failedbcache: register_bcache() error Status in curtin: Invalid Status in MAAS: Invalid Status in linux package in Ubuntu: Incomplete Bug description: We have a few runs over the weekend failed to deploy with maas 2.3.3. May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from DEPLOYING to FAILED_DEPLOYMENT May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node operation 'Deploying' timed out after 40 minutes. https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e- 4de1-9b30-0ecb28eb3c35 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1772490/+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 1772490] Re: 'Deploying' timed out after 40 minutes / Failedbcache: register_bcache() error
*** This bug is a duplicate of bug 1768893 *** https://bugs.launchpad.net/bugs/1768893 As such, I don't believe this is a MAAS issue. ** Changed in: maas Status: Incomplete => 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/1772490 Title: 'Deploying' timed out after 40 minutes / Failedbcache: register_bcache() error Status in curtin: Invalid Status in MAAS: Invalid Status in linux package in Ubuntu: Incomplete Bug description: We have a few runs over the weekend failed to deploy with maas 2.3.3. May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from DEPLOYING to FAILED_DEPLOYMENT May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node operation 'Deploying' timed out after 40 minutes. https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e- 4de1-9b30-0ecb28eb3c35 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1772490/+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 1772490] Re: bcache: register_bcache() error
@Ryan, Marking this as invalid for curtin again. I looked closely to the log and saw this: May 21 11:00:35 geodude cloud-init[1643]: --2018-05-21 11:00:35-- http://10.244.40.33/MAAS/metadata/latest/by-id/gnbttp/ May 21 11:00:35 geodude cloud-init[1643]: Connecting to 10.244.40.33:80... connected. May 21 11:00:35 geodude cloud-init[1643]: HTTP request sent, awaiting response... 200 OK May 21 11:00:35 geodude cloud-init[1643]: Length: unspecified [text/plain] May 21 11:00:35 geodude cloud-init[1643]: Saving to: ‘/dev/null’ May 21 11:00:35 geodude cloud-init[1643]: 0K 138K=0s May 21 11:00:35 geodude cloud-init[1643]: 2018-05-21 11:00:35 (138 KB/s) - ‘/dev/null’ saved [2] That means curtin run the correct netboot_off command, which should have told MAAS that the machine is to localboot on next reboot. As such, I need the HAProxy logs to continue to be able to debug as it was done against: 10.244.40.33:80 ** Changed in: curtin Status: Incomplete => Invalid ** Summary changed: - bcache: register_bcache() error + 'Deploying' timed out after 40 minutes / Failedbcache: register_bcache() error -- 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/1772490 Title: 'Deploying' timed out after 40 minutes / Failedbcache: register_bcache() error Status in curtin: Invalid Status in MAAS: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: We have a few runs over the weekend failed to deploy with maas 2.3.3. May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from DEPLOYING to FAILED_DEPLOYMENT May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node operation 'Deploying' timed out after 40 minutes. https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e- 4de1-9b30-0ecb28eb3c35 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1772490/+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 1772490] Re: bcache: register_bcache() error
@Ryan, I'm marking this as incomplete for curtin provided that after further debugging, I can see that the late command that's supposed to send the "netboot_off" operation is not being sent. This could be because curtin failed but we are lacking logs to determine this. ** Changed in: curtin Status: Invalid => 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/1772490 Title: bcache: register_bcache() error Status in curtin: Incomplete Status in MAAS: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: We have a few runs over the weekend failed to deploy with maas 2.3.3. May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from DEPLOYING to FAILED_DEPLOYMENT May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node operation 'Deploying' timed out after 40 minutes. https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e- 4de1-9b30-0ecb28eb3c35 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1772490/+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 1772490] Re: bcache: register_bcache() error
@Ashley, Could you please start gathering the logs from HAProxy running for the MAAS servers? -- 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/1772490 Title: bcache: register_bcache() error Status in curtin: Incomplete Status in MAAS: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: We have a few runs over the weekend failed to deploy with maas 2.3.3. May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from DEPLOYING to FAILED_DEPLOYMENT May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node operation 'Deploying' timed out after 40 minutes. https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e- 4de1-9b30-0ecb28eb3c35 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1772490/+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 1772490] Re: deployment timed out after 40 minutes
** Changed in: maas Status: New => Incomplete ** Changed in: maas Status: Incomplete => Invalid ** Also affects: curtin Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - deployment timed out after 40 minutes + bcache: register_bcache() error -- 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/1772490 Title: bcache: register_bcache() error Status in curtin: New Status in MAAS: Incomplete Status in linux package in Ubuntu: New Bug description: We have a few runs over the weekend failed to deploy with maas 2.3.3. May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from DEPLOYING to FAILED_DEPLOYMENT May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node operation 'Deploying' timed out after 40 minutes. https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e- 4de1-9b30-0ecb28eb3c35 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1772490/+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 1772490] Re: bcache: register_bcache() error
** Attachment added: "rsyslog-bcache-failure" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772490/+attachment/5142552/+files/rsyslog-bcache-failure -- 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/1772490 Title: bcache: register_bcache() error Status in curtin: Incomplete Status in MAAS: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: We have a few runs over the weekend failed to deploy with maas 2.3.3. May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from DEPLOYING to FAILED_DEPLOYMENT May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node operation 'Deploying' timed out after 40 minutes. https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e- 4de1-9b30-0ecb28eb3c35 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1772490/+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 1772490] Re: bcache: register_bcache() error
Attached the rsyslog showing the error. It indeed doesn't seem like there were any curtin failures, but I wonder that, while curtin successfully process, the machine actually doesn't actually boot onto the filesystem due to the kernel issue? -- 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/1772490 Title: bcache: register_bcache() error Status in curtin: Incomplete Status in MAAS: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: We have a few runs over the weekend failed to deploy with maas 2.3.3. May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from DEPLOYING to FAILED_DEPLOYMENT May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node operation 'Deploying' timed out after 40 minutes. https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e- 4de1-9b30-0ecb28eb3c35 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1772490/+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 1772490] Re: bcache: register_bcache() error
Hi Ashley, Marking this incomplete for MAAS (although I think it is invalid). Opening a task for curtin and for the kernel team. The error in curtin implies is the same issue as [1]. Judging from [2], it seems that it should already be fixed: May 21 10:57:03 geodude cloud-init[1643]: Processing triggers for libc-bin (2.27-3ubuntu1) ... May 21 10:57:04 geodude cloud-init[1643]: curtin: Installation started. (18.1-623-gae48e86-0ubuntu1~ubuntu16.04.1) May 21 10:57:04 geodude cloud-init[1643]: third party drivers not installed or necessary. May 21 10:57:05 geodude kernel: [ 49.126408] bcache: register_bcache() error /dev/sda3: device already registered (emitting change event) May 21 10:57:05 geodude kernel: [ 49.166935] bcache: register_bcache() error /dev/sda3: device already registered (emitting change event) May 21 10:57:05 geodude kernel: [ 49.209233] bcache: register_bcache() error /dev/sda3: device already registered (emitting change event) May 21 10:57:05 geodude kernel: [ 49.254763] bcache: register_bcache() error /dev/sda3: device already registered (emitting change event) May 21 10:57:05 geodude kernel: [ 49.319986] bcache: register_bcache() error /dev/sda3: device already registered (emitting change event) The ephemeral environment kernel seems to be: May 21 10:56:43 geodude kernel: [0.00] Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 (Ubuntu 4.15.0-20.21-generic 4.15.17) [1]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145 [2]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/comments/54 -- 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/1772490 Title: bcache: register_bcache() error Status in curtin: New Status in MAAS: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: We have a few runs over the weekend failed to deploy with maas 2.3.3. May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from DEPLOYING to FAILED_DEPLOYMENT May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node operation 'Deploying' timed out after 40 minutes. https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e- 4de1-9b30-0ecb28eb3c35 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1772490/+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 1772490] Re: bcache: register_bcache() error
** Changed in: maas Status: Invalid => 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/1772490 Title: bcache: register_bcache() error Status in curtin: New Status in MAAS: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: We have a few runs over the weekend failed to deploy with maas 2.3.3. May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from DEPLOYING to FAILED_DEPLOYMENT May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node operation 'Deploying' timed out after 40 minutes. https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e- 4de1-9b30-0ecb28eb3c35 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1772490/+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 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
@Joseph:
Issue still exists:
ubuntu@superb-whale:~$ uname -a
Linux superb-whale 4.15.0-041500rc6-generic #201805171959 SMP Thu May 17
20:02:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@superb-whale:~$ sudo reboot
===
Stopping LVM2 metadata daemon...
[14/5352]
[ OK ] Stopped LVM2 metadata daemon.
[ 107.570384] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 107.570386] {1}[Hardware Error]: event severity: fatal
[ 107.570388] {1}[Hardware Error]: Error 0, type: fatal
[ 107.570389] {1}[Hardware Error]: section_type: PCIe error
[ 107.570391] {1}[Hardware Error]: port_type: 4, root port
--
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/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
So I've tested all the way from rc2 -> rc7, and confirm that rc7 is the
issue. In two different machines:
machine1: running kernel was rc3
machine2: running kernel was rc4
In both cases, after install of rc7, and reboot, I see the issue. Logs
for the latest:
https://pastebin.ubuntu.com/p/yVTWBRqXSC/
--
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/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date:
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Finally got around to test this. ANd this are my findings:
1. Installed 4.15-rc1 above, rebooted the machine, and did not see the
issue.
ubuntu@just-pika:~$ uname -a
Linux just-pika 4.15.0-041500rc1-generic #201711262030 SMP Mon Nov 27 01:32:09
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@just-pika:~$ sudo reboot
2. I rebooted for a second time to see if the issue was present, but did
not see the issue.
3. On the third attempt. I installed [1]. After I installed, I proceeded
to reboot the machine. ANd this is when I saw the issue, even though the
[1] kernel wasn't the running kernel.
[1]: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/
--
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/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
This issue is not present in Artful. This issue is only present in
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/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Artful:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
collecting logs with mainline kernel.
** Summary changed:
- Rebooting bionic fails with hardware error
+ Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
** Description changed:
From an ephemeral environment in an HPGen9, the machine fails to reboot
when the ephemeral environment is Bionic (it does not fail in Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrP89:bd09/13/2016:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant DL360 Gen9
dmi.sys.vendor: HP
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 6 17:53
[Kernel-packages] [Bug 1761796] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104521/+files/ProcCpuinfoMinimal.txt
** Description changed:
From an ephemeral environment in an HPGen9, the machine fails to reboot
when the ephemeral environment is Bionic (it does not fail in Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrP89:bd09/13/2016:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant DL360 Gen9
dmi.sys.vendor: HP
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 6 17:53 seq
[Kernel-packages] [Bug 1761796] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104523/+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/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
[Kernel-packages] [Bug 1761796] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104427/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
[Kernel-packages] [Bug 1761796] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104424/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error
Test both -proposed & 4.16 kernels, and the issue persists.
** 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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
[Kernel-packages] [Bug 1761796] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104421/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
[Kernel-packages] [Bug 1761796] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104425/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
[Kernel-packages] [Bug 1761796] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104423/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
[Kernel-packages] [Bug 1761796] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104426/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
[Kernel-packages] [Bug 1761796] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104422/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
[Kernel-packages] [Bug 1761796] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104428/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
[Kernel-packages] [Bug 1761796] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104392/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
[Kernel-packages] [Bug 1761796] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104394/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
[Kernel-packages] [Bug 1761796] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104420/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
[Kernel-packages] [Bug 1761796] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104396/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
[Kernel-packages] [Bug 1761796] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104391/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
[Kernel-packages] [Bug 1761796] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104393/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
[Kernel-packages] [Bug 1761796] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104390/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
[Kernel-packages] [Bug 1761796] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104395/+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/1761796
Title:
Rebooting bionic fails with hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error
apport information
** Summary changed:
- Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware
error
+ Rebooting bionic fails with hardware error
** Description changed:
From an ephemeral environment in an HPGen9, the machine fails to reboot
- with the following hardware error.
-
- This doesn't happen on xenial, it only happens in Bionic.
+ when the ephemeral environment is Bionic (it does not fail in Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
-
+ The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
- ---
+ ---
AlsaDevices:
- total 0
- crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
+ total 0
+ crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
-
+
ProcEnviron:
- TERM=screen-256color
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=C.UTF-8
- SHELL=/bin/bash
+ TERM=screen-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=C.UTF-8
+ SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
- linux-restricted-modules-4.15.0-13-generic N/A
- linux-backports-modules-4.15.0-13-generic N/A
- linux-firmware N/A
+ linux-restricted-modules-4.15.0-13-generic N/A
+ linux-backports-modules-4.15.0-13-generic N/A
+ linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
[Kernel-packages] [Bug 1761796] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104389/+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/1761796
Title:
Rebooting bionic running on an ephemeral env (overlayfs) fails with
hardware error
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot with the following hardware error.
This doesn't happen on xenial, it only happens in Bionic.
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware error
apport information
** Tags added: apport-collected uec-images
** Description changed:
From an ephemeral environment in an HPGen9, the machine fails to reboot
with the following hardware error.
This doesn't happen on xenial, it only happens in Bionic.
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
+ ---
+ AlsaDevices:
+ total 0
+ crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.9-0ubuntu2
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
+ CRDA: N/A
+ DistroRelease: Ubuntu 18.04
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
+ MachineType: HP ProLiant DL360 Gen9
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ PciMultimedia:
+
+ ProcEnviron:
+ TERM=screen-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=C.UTF-8
+ SHELL=/bin/bash
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
+ ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
+ RelatedPackageVersions:
+ linux-restricted-modules-4.15.0-13-generic N/A
+ linux-backports-modules-4.15.0-13-generic N/A
+ linux-firmware N/A
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
+ Tags: bionic uec-images
+ Uname: Linux 4.15.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
+ _MarkForUpload: True
+ dmi.bios.date: 09/13/2016
+ dmi.bios.vendor: HP
+ dmi.bios.version: P89
+ dmi.board.name: ProLiant DL360 Gen9
+ dmi.board.vendor: HP
+ dmi.chassis.type: 23
+ dmi.chassis.vendor: HP
+ dmi.modalias:
dmi:bvnHP:bvrP89:bd09/13/2016:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
+ dmi.product.family: ProLiant
+ dmi.product.name: ProLiant DL360 Gen9
+ dmi.sys.vendor: HP
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1761796/+attachment/5104388/+files/CurrentDmesg.txt
--
You received this bug notification because you
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware error
** Description changed:
+ From an ephemeral environment in an HPGen9, the machine fails to reboot
+ with the following hardware error.
+
+ This doesn't happen on xenial, it only happens in Bionic.
+
+ Full log from the moment the 'sudo reboot' was executed:
+ https://pastebin.ubuntu.com/p/hyD6VY7CbW/
+
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
- Starting Reboot...
+ Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
- Stopping LVM2 metadata daemon...
+ Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
** Description changed:
From an ephemeral environment in an HPGen9, the machine fails to reboot
with the following hardware error.
This doesn't happen on xenial, it only happens in Bionic.
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
+
+
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[
[Kernel-packages] [Bug 1761796] [NEW] Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware error
Public bug reported:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
Rebooting bionic running on an ephemeral env (overlayfs) fails with
hardware error
Status in linux package in Ubuntu:
Incomplete
Bug description:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761796/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 1742324] Re: Bionic kernel panics in the MAAS ephemeral environment
** Changed in: maas Status: Won't Fix => Incomplete ** Changed in: maas Status: Incomplete => 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/1742324 Title: Bionic kernel panics in the MAAS ephemeral environment Status in MAAS: Invalid Status in linux package in Ubuntu: Incomplete Bug description: Bionic kernel panics in the MAAS ephemeral environment. This does not always happen during commissioning or testing but does happen every time when trying to enter rescue mode. The test system is a KVM machine using all VirtIO drivers running on a Bionic host system. Both systems are using the 4.13.0-17-generic kernel. [ 13.774332] BUG: unable to handle kernel paging request at f672c3075a20 [ 13.775203] IP: kfree+0x53/0x160 [ 13.775665] PGD 0 [ 13.775666] P4D 0 [ 13.775965] [ 13.776566] Oops: [#1] SMP [ 13.777004] Modules linked in: iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi overlay btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc ttm drm_kms_helper aesni_intel syscopyarea sysfillrect aes_x86_64 crypto_simd glue_helper cryptd sysimgblt fb_sys_fops drm psmouse virtio_blk virtio_net pata_acpi floppy [ 13.782468] CPU: 0 PID: 696 Comm: lxd Not tainted 4.13.0-17-generic #20-Ubuntu [ 13.783169] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 13.784028] task: 9afa30b62e80 task.stack: c07640a5 [ 13.784512] RIP: 0010:kfree+0x53/0x160 [ 13.784884] RSP: 0018:9afa3ca03a18 EFLAGS: 00010286 [ 13.785339] RAX: RBX: f50a81d68280 RCX: 0002 [ 13.785983] RDX: 457c0321e918 RSI: 00010080 RDI: 6505c000 [ 13.786916] RBP: 9afa3ca03a30 R08: 0001f4c0 R09: 94bbb839 [ 13.787877] R10: f672c3075a00 R11: e4e5cd01 R12: 9afa3f794000 [ 13.788854] R13: 947a155e R14: 9afa3f794000 R15: 9afa3f794000 [ 13.789882] FS: 7fc4a7938cc0() GS:9afa3ca0() knlGS: [ 13.791134] CS: 0010 DS: ES: CR0: 80050033 [ 13.792003] CR2: f672c3075a20 CR3: 737f6000 CR4: 001406f0 [ 13.793019] Call Trace: [ 13.793462] [ 13.793886] security_sk_free+0x3e/0x50 [ 13.794680] __sk_destruct+0x108/0x190 [ 13.795465] sk_destruct+0x20/0x30 [ 13.796193] __sk_free+0x82/0xa0 [ 13.796899] sk_free+0x19/0x20 [ 13.797537] sock_put+0x14/0x20 [ 13.797926] tcp_v4_rcv+0x94d/0x9d0 [ 13.798325] ? ep_poll_callback+0x226/0x2b0 [ 13.798704] ip_local_deliver_finish+0x5c/0x1f0 [ 13.799099] ip_local_deliver+0x6f/0xe0 [ 13.799455] ip_rcv_finish+0x120/0x410 [ 13.799868] ip_rcv+0x28c/0x3a0 [ 13.800221] ? csum_partial+0x11/0x20 [ 13.800649] __netif_receive_skb_core+0x39a/0xaa0 [ 13.801295] ? skb_checksum+0x35/0x50 [ 13.801742] ? skb_append_datato_frags+0x200/0x200 [ 13.802164] ? reqsk_fastopen_remove+0x140/0x140 [ 13.802576] __netif_receive_skb+0x18/0x60 [ 13.803163] ? __netif_receive_skb+0x18/0x60 [ 13.803798] netif_receive_skb_internal+0x3f/0x3f0 [ 13.804538] ? dev_gro_receive+0x2dc/0x480 [ 13.805210] napi_gro_receive+0xc2/0xe0 [ 13.805851] receive_buf+0x218/0xf70 [virtio_net] [ 13.806591] ? vring_unmap_one+0x1b/0x80 [ 13.807240] virtnet_poll+0x173/0x268 [virtio_net] [ 13.807998] net_rx_action+0x13b/0x380 [ 13.808621] ? skb_recv_done+0x30/0x40 [virtio_net] [ 13.810159] __do_softirq+0xde/0x2a5 [ 13.810673] irq_exit+0xb6/0xc0 [ 13.811185] do_IRQ+0x80/0xd0 [ 13.811881] common_interrupt+0x89/0x89 [ 13.812668] RIP: 0010:filemap_fault+0xff/0x5e0 [ 13.819490] RSP: 0018:c07640a53cc8 EFLAGS: 0202 ORIG_RAX: ff8e [ 13.820174] RAX: 0012e288 RBX: 9afa3f6e0800 RCX: 0054 [ 13.820760] RDX: RSI: 9afa30b64180 RDI: 9afa3ca1c200 [ 13.821339] RBP: c07640a53d70 R08: 0310 R09: 0001 [ 13.821917] R10: c076406ab738 R11: 00d2 R12: 00ea [ 13.822493] R13: 9afa3262e900 R14: f50a8174eec0 R15: c07640a53db8 [ 13.823075] [ 13.823327] ? filemap_fault+0xb0/0x5e0 [ 13.823703] ? filemap_map_pages+0x179/0x320 [ 13.824101] __do_fault+0x1e/0xb0 [ 13.824434] __handle_mm_fault+0xba7/0x1020 [ 13.824821] handle_mm_fault+0xb1/0x200 [ 13.825189] __do_page_fault+0x24d/0x4d0 [ 13.825560] trace_do_page_fault+0x37/0xd0 [ 13.826051] do_async_page_fault+0x51/0x80 [ 13.826652] async_page_fault+0x28/0x30 [ 13.827246] RIP:
[Kernel-packages] [Bug 1759445] Re: MAAS 2.3.1 fails to deploy Bionic due to kernel panic
Hi Eric, I experience the same issue in non-MAAS deployed machines after upgrading to the latest kernel. AS such, I'm marking this as invalid for MAAS and opening a task for the kernel. ** Changed in: maas Status: New => Invalid ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - MAAS 2.3.1 fails to deploy Bionic due to kernel panic + Bionic due to kernel panic -- 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/1759445 Title: Bionic due to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: New Bug description: cpe_foundation test deployment of Bionic failed. After some investigation, it looks like the nodes deployed and installed bionic, but never came back from a reboot. Accessing the ILO console of a node in question (all nodes failed), it revealed a kernel panic (attached) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1759445/+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 1756337] Re: kernel bug at fscache/operation.c
Hi There, The MAAS images use the kernels that are available in the archive. Since this is a kernel issue, I'm retargetting to the linux package in Ubuntu. If this is already fixed, MAAS will automatically update new images once the packages are available in the archive, otherwise, please feel free to use a different kernel (e.g. hwe-16.04) and see if that fixes your issue. Just make sure your images are latest. ** Changed in: maas Status: New => Invalid ** Also 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/1756337 Title: kernel bug at fscache/operation.c Status in MAAS: Invalid Status in linux package in Ubuntu: Incomplete Bug description: MAAS deployed Ubuntu 16.04 LTS hosts began suffering from either [577275.774627] FS-Cache: [577275.777530] FS-Cache: Assertion failed [577275.781945] FS-Cache: 6 == 5 is false [577275.786304] [ cut here ] [577275.791662] kernel BUG at /build/linux-Fk60NP/linux-4.10.0/fs/fscache/operation.c:494! [577275.800740] invalid opcode: [#1] SMP [577275.805415] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache $ [577275.885578] ib_core configfs 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 multipa$ [577275.925771] CPU: 52 PID: 39395 Comm: kworker/u161:1 Not tainted 4.10.0-19-generic #21-Ubuntu [577275.940896] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.6.0 10/31/2017 or [126530.552030] FS-Cache: [126530.554868] FS-Cache: Assertion failed [126530.559250] FS-Cache: 1 > 0 is false [126530.563472] [ cut here ] [126530.568822] kernel BUG at /build/linux-Fk60NP/linux-4.10.0/fs/fscache/operation.c:68! [126530.577792] invalid opcode: [#1] SMP [126530.582464] Modules linked in: vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache $ [126530.662615] 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 $ [126530.700165] CPU: 6 PID: 13971 Comm: CPU 1/KVM Not tainted 4.10.0-19-generic #21-Ubuntu [126530.709227] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 01/26/2018 Possible solution here: https://patchwork.kernel.org/patch/10234815/ Using MAAS: MAAS version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1756337/+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 1743595] Re: modprobing mlx5_core doesn't bring the interface up
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743595/+attachment/5037964/+files/uname-a.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/1743595 Title: modprobing mlx5_core doesn't bring the interface up Status in MAAS: New Status in linux package in Ubuntu: Incomplete Bug description: ubuntu@wrlsrvr321:~$ sudo -i root@wrlsrvr321:~# lsmod Module Size Used by ipmi_devintf 20480 0 iscsi_tcp 20480 0 libiscsi_tcp 24576 1 iscsi_tcp libiscsi 53248 2 libiscsi_tcp,iscsi_tcp scsi_transport_iscsi98304 3 iscsi_tcp,libiscsi overlay49152 1 btrfs 991232 0 raid10 49152 0 raid456 110592 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_pq,raid456,async_xor,async_memcpy,async_raid6_recov xor24576 2 btrfs,async_xor raid6_pq 102400 4 async_pq,raid456,btrfs,async_raid6_recov libcrc32c 16384 1 raid456 raid1 36864 0 raid0 20480 0 multipath 16384 0 linear 16384 0 ipmi_ssif 24576 0 ses20480 0 enclosure 16384 1 ses scsi_transport_sas 45056 1 ses hid_generic16384 0 mxm_wmi16384 0 crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 aesni_intel 167936 0 aes_x86_64 20480 1 aesni_intel lrw16384 1 aesni_intel gf128mul 16384 1 lrw glue_helper16384 1 aesni_intel ablk_helper16384 1 aesni_intel cryptd 20480 3 ghash_clmulni_intel,aesni_intel,ablk_helper i2c_algo_bit 16384 0 ttm98304 0 drm_kms_helper155648 0 ixgbe 290816 0 syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper dca16384 1 ixgbe sysimgblt 16384 1 drm_kms_helper vxlan 49152 1 ixgbe fb_sys_fops16384 1 drm_kms_helper ip6_udp_tunnel 16384 1 vxlan drm 364544 2 ttm,drm_kms_helper udp_tunnel 16384 1 vxlan usbhid 49152 0 ptp20480 1 ixgbe ahci 36864 0 hid 118784 2 hid_generic,usbhid libahci32768 1 ahci pps_core 20480 1 ptp megaraid_sas 135168 0 mdio 16384 1 ixgbe ipmi_si57344 0 fjes 28672 0 ipmi_msghandler49152 3 ipmi_ssif,ipmi_devintf,ipmi_si wmi20480 1 mxm_wmi root@wrlsrvr321:~# root@wrlsrvr321:~# lspci | grep Mell 81:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5] root@wrlsrvr321:~# root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:130767 errors:0 dropped:30 overruns:0 frame:0 TX packets:20809 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:196717409 (196.7 MB) TX bytes:1575915 (1.5 MB) enp3s0f1 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:81 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@wrlsrvr321:~# modprobe mlx5_core root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[Kernel-packages] [Bug 1743595] Re: modprobing mlx5_core doesn't bring the interface up
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743595/+attachment/5037965/+files/version.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/1743595 Title: modprobing mlx5_core doesn't bring the interface up Status in MAAS: New Status in linux package in Ubuntu: Incomplete Bug description: ubuntu@wrlsrvr321:~$ sudo -i root@wrlsrvr321:~# lsmod Module Size Used by ipmi_devintf 20480 0 iscsi_tcp 20480 0 libiscsi_tcp 24576 1 iscsi_tcp libiscsi 53248 2 libiscsi_tcp,iscsi_tcp scsi_transport_iscsi98304 3 iscsi_tcp,libiscsi overlay49152 1 btrfs 991232 0 raid10 49152 0 raid456 110592 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_pq,raid456,async_xor,async_memcpy,async_raid6_recov xor24576 2 btrfs,async_xor raid6_pq 102400 4 async_pq,raid456,btrfs,async_raid6_recov libcrc32c 16384 1 raid456 raid1 36864 0 raid0 20480 0 multipath 16384 0 linear 16384 0 ipmi_ssif 24576 0 ses20480 0 enclosure 16384 1 ses scsi_transport_sas 45056 1 ses hid_generic16384 0 mxm_wmi16384 0 crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 aesni_intel 167936 0 aes_x86_64 20480 1 aesni_intel lrw16384 1 aesni_intel gf128mul 16384 1 lrw glue_helper16384 1 aesni_intel ablk_helper16384 1 aesni_intel cryptd 20480 3 ghash_clmulni_intel,aesni_intel,ablk_helper i2c_algo_bit 16384 0 ttm98304 0 drm_kms_helper155648 0 ixgbe 290816 0 syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper dca16384 1 ixgbe sysimgblt 16384 1 drm_kms_helper vxlan 49152 1 ixgbe fb_sys_fops16384 1 drm_kms_helper ip6_udp_tunnel 16384 1 vxlan drm 364544 2 ttm,drm_kms_helper udp_tunnel 16384 1 vxlan usbhid 49152 0 ptp20480 1 ixgbe ahci 36864 0 hid 118784 2 hid_generic,usbhid libahci32768 1 ahci pps_core 20480 1 ptp megaraid_sas 135168 0 mdio 16384 1 ixgbe ipmi_si57344 0 fjes 28672 0 ipmi_msghandler49152 3 ipmi_ssif,ipmi_devintf,ipmi_si wmi20480 1 mxm_wmi root@wrlsrvr321:~# root@wrlsrvr321:~# lspci | grep Mell 81:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5] root@wrlsrvr321:~# root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:130767 errors:0 dropped:30 overruns:0 frame:0 TX packets:20809 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:196717409 (196.7 MB) TX bytes:1575915 (1.5 MB) enp3s0f1 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:81 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@wrlsrvr321:~# modprobe mlx5_core root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[Kernel-packages] [Bug 1743595] Re: modprobing mlx5_core doesn't bring the interface up
** Attachment added: "lspci-vvnn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743595/+attachment/5037963/+files/lspci-vvnn.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/1743595 Title: modprobing mlx5_core doesn't bring the interface up Status in MAAS: New Status in linux package in Ubuntu: Incomplete Bug description: ubuntu@wrlsrvr321:~$ sudo -i root@wrlsrvr321:~# lsmod Module Size Used by ipmi_devintf 20480 0 iscsi_tcp 20480 0 libiscsi_tcp 24576 1 iscsi_tcp libiscsi 53248 2 libiscsi_tcp,iscsi_tcp scsi_transport_iscsi98304 3 iscsi_tcp,libiscsi overlay49152 1 btrfs 991232 0 raid10 49152 0 raid456 110592 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_pq,raid456,async_xor,async_memcpy,async_raid6_recov xor24576 2 btrfs,async_xor raid6_pq 102400 4 async_pq,raid456,btrfs,async_raid6_recov libcrc32c 16384 1 raid456 raid1 36864 0 raid0 20480 0 multipath 16384 0 linear 16384 0 ipmi_ssif 24576 0 ses20480 0 enclosure 16384 1 ses scsi_transport_sas 45056 1 ses hid_generic16384 0 mxm_wmi16384 0 crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 aesni_intel 167936 0 aes_x86_64 20480 1 aesni_intel lrw16384 1 aesni_intel gf128mul 16384 1 lrw glue_helper16384 1 aesni_intel ablk_helper16384 1 aesni_intel cryptd 20480 3 ghash_clmulni_intel,aesni_intel,ablk_helper i2c_algo_bit 16384 0 ttm98304 0 drm_kms_helper155648 0 ixgbe 290816 0 syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper dca16384 1 ixgbe sysimgblt 16384 1 drm_kms_helper vxlan 49152 1 ixgbe fb_sys_fops16384 1 drm_kms_helper ip6_udp_tunnel 16384 1 vxlan drm 364544 2 ttm,drm_kms_helper udp_tunnel 16384 1 vxlan usbhid 49152 0 ptp20480 1 ixgbe ahci 36864 0 hid 118784 2 hid_generic,usbhid libahci32768 1 ahci pps_core 20480 1 ptp megaraid_sas 135168 0 mdio 16384 1 ixgbe ipmi_si57344 0 fjes 28672 0 ipmi_msghandler49152 3 ipmi_ssif,ipmi_devintf,ipmi_si wmi20480 1 mxm_wmi root@wrlsrvr321:~# root@wrlsrvr321:~# lspci | grep Mell 81:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5] root@wrlsrvr321:~# root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:130767 errors:0 dropped:30 overruns:0 frame:0 TX packets:20809 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:196717409 (196.7 MB) TX bytes:1575915 (1.5 MB) enp3s0f1 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:81 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@wrlsrvr321:~# modprobe mlx5_core root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[Kernel-packages] [Bug 1743595] Re: modprobing mlx5_core doesn't bring the interface up
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743595/+attachment/5037962/+files/dmesg.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/1743595 Title: modprobing mlx5_core doesn't bring the interface up Status in MAAS: New Status in linux package in Ubuntu: Incomplete Bug description: ubuntu@wrlsrvr321:~$ sudo -i root@wrlsrvr321:~# lsmod Module Size Used by ipmi_devintf 20480 0 iscsi_tcp 20480 0 libiscsi_tcp 24576 1 iscsi_tcp libiscsi 53248 2 libiscsi_tcp,iscsi_tcp scsi_transport_iscsi98304 3 iscsi_tcp,libiscsi overlay49152 1 btrfs 991232 0 raid10 49152 0 raid456 110592 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_pq,raid456,async_xor,async_memcpy,async_raid6_recov xor24576 2 btrfs,async_xor raid6_pq 102400 4 async_pq,raid456,btrfs,async_raid6_recov libcrc32c 16384 1 raid456 raid1 36864 0 raid0 20480 0 multipath 16384 0 linear 16384 0 ipmi_ssif 24576 0 ses20480 0 enclosure 16384 1 ses scsi_transport_sas 45056 1 ses hid_generic16384 0 mxm_wmi16384 0 crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 aesni_intel 167936 0 aes_x86_64 20480 1 aesni_intel lrw16384 1 aesni_intel gf128mul 16384 1 lrw glue_helper16384 1 aesni_intel ablk_helper16384 1 aesni_intel cryptd 20480 3 ghash_clmulni_intel,aesni_intel,ablk_helper i2c_algo_bit 16384 0 ttm98304 0 drm_kms_helper155648 0 ixgbe 290816 0 syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper dca16384 1 ixgbe sysimgblt 16384 1 drm_kms_helper vxlan 49152 1 ixgbe fb_sys_fops16384 1 drm_kms_helper ip6_udp_tunnel 16384 1 vxlan drm 364544 2 ttm,drm_kms_helper udp_tunnel 16384 1 vxlan usbhid 49152 0 ptp20480 1 ixgbe ahci 36864 0 hid 118784 2 hid_generic,usbhid libahci32768 1 ahci pps_core 20480 1 ptp megaraid_sas 135168 0 mdio 16384 1 ixgbe ipmi_si57344 0 fjes 28672 0 ipmi_msghandler49152 3 ipmi_ssif,ipmi_devintf,ipmi_si wmi20480 1 mxm_wmi root@wrlsrvr321:~# root@wrlsrvr321:~# lspci | grep Mell 81:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5] root@wrlsrvr321:~# root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:130767 errors:0 dropped:30 overruns:0 frame:0 TX packets:20809 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:196717409 (196.7 MB) TX bytes:1575915 (1.5 MB) enp3s0f1 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:81 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@wrlsrvr321:~# modprobe mlx5_core root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[Kernel-packages] [Bug 1743595] [NEW] modprobing mlx5_core doesn't bring the interface up
Public bug reported: ubuntu@wrlsrvr321:~$ sudo -i root@wrlsrvr321:~# lsmod Module Size Used by ipmi_devintf 20480 0 iscsi_tcp 20480 0 libiscsi_tcp 24576 1 iscsi_tcp libiscsi 53248 2 libiscsi_tcp,iscsi_tcp scsi_transport_iscsi98304 3 iscsi_tcp,libiscsi overlay49152 1 btrfs 991232 0 raid10 49152 0 raid456 110592 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_pq,raid456,async_xor,async_memcpy,async_raid6_recov xor24576 2 btrfs,async_xor raid6_pq 102400 4 async_pq,raid456,btrfs,async_raid6_recov libcrc32c 16384 1 raid456 raid1 36864 0 raid0 20480 0 multipath 16384 0 linear 16384 0 ipmi_ssif 24576 0 ses20480 0 enclosure 16384 1 ses scsi_transport_sas 45056 1 ses hid_generic16384 0 mxm_wmi16384 0 crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 aesni_intel 167936 0 aes_x86_64 20480 1 aesni_intel lrw16384 1 aesni_intel gf128mul 16384 1 lrw glue_helper16384 1 aesni_intel ablk_helper16384 1 aesni_intel cryptd 20480 3 ghash_clmulni_intel,aesni_intel,ablk_helper i2c_algo_bit 16384 0 ttm98304 0 drm_kms_helper155648 0 ixgbe 290816 0 syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper dca16384 1 ixgbe sysimgblt 16384 1 drm_kms_helper vxlan 49152 1 ixgbe fb_sys_fops16384 1 drm_kms_helper ip6_udp_tunnel 16384 1 vxlan drm 364544 2 ttm,drm_kms_helper udp_tunnel 16384 1 vxlan usbhid 49152 0 ptp20480 1 ixgbe ahci 36864 0 hid 118784 2 hid_generic,usbhid libahci32768 1 ahci pps_core 20480 1 ptp megaraid_sas 135168 0 mdio 16384 1 ixgbe ipmi_si57344 0 fjes 28672 0 ipmi_msghandler49152 3 ipmi_ssif,ipmi_devintf,ipmi_si wmi20480 1 mxm_wmi root@wrlsrvr321:~# root@wrlsrvr321:~# lspci | grep Mell 81:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5] root@wrlsrvr321:~# root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:130767 errors:0 dropped:30 overruns:0 frame:0 TX packets:20809 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:196717409 (196.7 MB) TX bytes:1575915 (1.5 MB) enp3s0f1 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:81 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@wrlsrvr321:~# modprobe mlx5_core root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:131663 errors:0 dropped:59 overruns:0 frame:0 TX packets:21456 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:197368250 (197.3 MB) TX bytes:1659655 (1.6 MB) enp3s0f1 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:81 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0
[Kernel-packages] [Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing
Hi Dimitrii, This request seems like something we have never seen before. This doesn't seem to be quite a complex thing to do. Right now, this is and never has been in our plans to implement. This is also something that has never come up before. I'm going to mark this as a wishlist, and incomplete, until we understand what are the needs and the impact on the project. I would suggest you raise this during the sprint. ** Changed in: maas Status: New => Incomplete ** Changed in: maas Importance: Undecided => Wishlist ** Changed in: maas Milestone: None => next -- 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/1737428 Title: VRF support to solve routing problems associated with multi-homing Status in juju: New Status in MAAS: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Problem description: * a host is multi-homed if it has multiple network interfaces with L3 addresses configured (physical or virtual interfaces, natural to OpenStack regardless of IPv4/IPv6 and IPv6 in general); * if all hosts that need to participate in L3 communication are located on the same L2 network there is no need for a routing device to be present. ARP/NDP and auto-created directly connected routes are enough; * multi-homing with hosts located on different L2 networks requires more intelligent routing: - "directly connected" routes are no longer enough to talk to all relevant hosts in the same network space; - a default gateway in the main routing table may not be the correct routing device that knows where to forward traffic (management network traffic goes to a management switch and router, other traffic goes to L3 ToR switch but may go via different bonds); - even if a default gateway knows where to forward traffic, it may not be the intended physical path (storage replication traffic must go through a specific outgoing interface, not the same interface as storage access traffic although both interfaces are connected to the same ToR); - there is no longer a single "default gateway" as applications need either per-logical-direction routers or to become routers themselves (if destination == X, forward to next-hop Y). Leaf-spine architecture is a good example of how multiple L2 networks force you to use spaces that have VLANs in different switch fabrics => one or more hops between hosts with interfaces associated with the same network space; - while network spaces implicitly require L3 reachability between each host that has a NIC associated with a network space, the current definition does not mention routing infrastructure required for that. For a single L2 this problem is hidden by directly connected routes, for multi-L2, no solution is provided or discussed; * existing solutions to multi-homing require routing table management on a given host: complex static routing rules, dynamic routing (e.g. running an OSPF or BGP daemon on a host); * using static routes is rigid and requires network planning (i.e. working with network engineers which may have varying degrees of experience, doing VLSM planning etc.); * using dynamic routing requires a broader integration into an organization's L3 network infrastructure. Routing can be implemented differently across different organizations and it is a security and operational burden to integrate with a company's routing infrastructure. Summary: a mechanism is needed to associate an interface with a forwarding table (FIB) which has its own default gateway and make an application with a listen(2)ing socket(2) return connected sockets associated with different FIBs. In other words, applications need to implicitly get source/destination-based routing capabilities without the need to use static routing schemes or dynamic routing and with minimum or no modifications to the applications themselves. Goals: * avoid turning individual hosts into routers; * avoid complex static rules; * better support multi-fabric deployments with minimum effort (Juju, charms, MAAS, applications, network infrastructure); * reduce operational complexity (custom L3 infrastructure integration for each deployment); * reduce delivery risks (L3 infrastructure, L3 department responsiveness varies); * avoid any form of L2 stretching at the infrastructure level - this is inefficient for various reasons. NOTE: https://cumulusnetworks.com/blog/vrf-for-linux/ - I recommend to read this post to understand suggestions below. How to solve it? What does it mean for Juju to support VRF devices? * enslave certain devices on provisioning based on network space information (physical NICs, VLAN devices, bonds AND bridges created for containers must be considered) - VRF devices logically enslave devices similar to bridges but work differently (on
[Kernel-packages] [Bug 1701297] Re: NTP reload failure (unable to read library) on overlayfs
@Tyler, The reason why this wasn't seen before is that previously in Xenial, cloud-init did not restart 'ntp' with a new config file. Since cloud- init recently SRU'd a fixed cloud-init that does restart 'ntp' on overlay, the issue started to show up. In other words, after a cloud-init bugfix , these issues started surfacing. -- 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/1701297 Title: NTP reload failure (unable to read library) on overlayfs Status in cloud-init: Incomplete Status in apparmor package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: After update [1] of cloud-init in Ubuntu (which landed in xenial- updates on 2017-06-27), it is causing NTP reload failures. https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f- 0ubuntu1~16.04.1 In MAAS scenarios, this is causing the machine to fail to deploy. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1408106] Re: attach_disconnected not sufficient for overlayfs
@Frode,
Users running 2.2 *already* have the apparmor=0 work around for
*ephemeral* environments only.
For users running previous versions, we recommend you upgrade
immediately, provided that 2.0 and 2.1 are out of support. If you decide
not to upgrade, your options are:
1. Use a HWE kernel (such as hwe-16.04).
https://bugs.launchpad.net/cloud-init/+bug/1701297/comments/21
2. Use apparmor=0 as a global/machine kernel param (this will result in the
deployed machine with apparmor disabled)
Marking this invalid for MAAS provided the bug is overlayfs.
** Changed in: maas
Status: Incomplete => 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/1408106
Title:
attach_disconnected not sufficient for overlayfs
Status in AppArmor:
Invalid
Status in MAAS:
Invalid
Status in apparmor package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Invalid
Bug description:
With the following use of overlayfs, we get a disconnected path:
$ cat ./profile
#include
profile foo {
#include
capability sys_admin,
capability sys_chroot,
mount,
pivot_root,
}
$ cat ./overlay.c
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char* argv[]) {
int i = 0;
int len = 0;
int ret = 0;
char* options;
if (geteuid())
unshare(CLONE_NEWUSER);
unshare(CLONE_NEWNS);
for (i = 1; i < argc; i++) {
if (i == 1) {
len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
options = alloca(len);
ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
}
else {
len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
options = alloca(len);
ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt",
argv[i]);
}
mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
}
chdir("/mnt");
pivot_root(".", ".");
chroot(".");
chdir("/");
execl("/bin/bash", "/bin/bash", NULL);
}
$ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
[255]
...
Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
With the above, the expectation was for the denial to be /mnt/bin/bash. There
are three ways forward:
1. the correct solution is to patch overlayfs to properly track the loopback,
but this will take a while, may ultimately be unachievable. UPDATE: upstream is
currently working on this and Ubuntu will engage with them
2. we could rely on the fact that overlayfs creates a private unshared
submount, and provide a way to not mediate the path when that is present, and
tagged. This would take a bit of time, and might be the preferred method over 1
longer term
3. we could extend attach_disconnected so that we can define the attach root.
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash'
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1408106/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs
When using the following kernel (the default Xenial kernel, aka ga-16.04 in MAAS), we see this issue: 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux When using the HWE kernel (aka hwe-16.04 in MAAS), we do NOT see this issue: 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- 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/1701297 Title: NTP reload failure (unable to read library) on overlayfs Status in cloud-init: Incomplete Status in apparmor package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: After update [1] of cloud-init in Ubuntu (which landed in xenial- updates on 2017-06-27), it is causing NTP reload failures. https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f- 0ubuntu1~16.04.1 In MAAS scenarios, this is causing the machine to fail to deploy. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs
@Tyler, That's is correct, MAAS 2.2.0+ sends the apparmor=0 for the ephemeral environments. That said, however, this affects else who is not using 2.2 (which in fact, affects customers who are still in 2.1). Also, based on my testing, it seems that when using hwe-16.04 kernel this doesn't happen, but it does with the ga-16.04 kernel. ** Summary changed: - NTP reload failure (causing deployment failures with MAAS) + NTP reload failure (unable to read library) on overlayfs -- 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/1701297 Title: NTP reload failure (unable to read library) on overlayfs Status in cloud-init: Incomplete Status in apparmor package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: After update [1] of cloud-init in Ubuntu (which landed in xenial- updates on 2017-06-27), it is causing NTP reload failures. https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f- 0ubuntu1~16.04.1 In MAAS scenarios, this is causing the machine to fail to deploy. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1701297] Re: NTP reload failure (causing deployment failures with MAAS)
It seems that this only happens when using ga-16.04 and doesn't when using hwe-16.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/1701297 Title: NTP reload failure (causing deployment failures with MAAS) Status in cloud-init: Incomplete Status in apparmor package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: After update [1] of cloud-init in Ubuntu (which landed in xenial- updates on 2017-06-27), it is causing NTP reload failures. https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f- 0ubuntu1~16.04.1 In MAAS scenarios, this is causing the machine to fail to deploy. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1701297] Re: NTP reload failure (causing deployment failures with MAAS)
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu) Importance: Undecided => Critical -- 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/1701297 Title: NTP reload failure (causing deployment failures with MAAS) Status in cloud-init: Incomplete Status in apparmor package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: After update [1] of cloud-init in Ubuntu (which landed in xenial- updates on 2017-06-27), it is causing NTP reload failures. https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f- 0ubuntu1~16.04.1 In MAAS scenarios, this is causing the machine to fail to deploy. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1618572] Re: apt-key add fails in overlayfs
Ok, I confirm the issue as per previous comment with Trusty+hwe-x -- 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/1618572 Title: apt-key add fails in overlayfs Status in cloud-init: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: Sending a custom APT config to cloud-init fails to: 1. add keys 2. configure sources 3. configura additional repository. The same config is being sent to curtin, and curtin doesn't seem to fail (curtin install log http://paste.ubuntu.com/23112826/ just in case). config sent by maas = http://pastebin.ubuntu.com/23112834/ cloud-init.log = http://paste.ubuntu.com/23112820/ cloud-init-output.log = http://paste.ubuntu.com/23112822/ sources.list = http://paste.ubuntu.com/23112824/ ubuntu@node03:/var/log$ ls -l /etc/apt/sources.list.d/ total 0 ubuntu@node03:/var/log$ sudo apt-get update Hit:2 http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease Get:3 http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease [92.2 kB] Err:2 http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Ign:3 http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease Get:1 http://us.archive.ubuntu.com/ubuntu yakkety InRelease [247 kB] Err:4 http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Err:1 http://us.archive.ubuntu.com/ubuntu yakkety InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Fetched 339 kB in 0s (388 kB/s) Reading package lists... Error! W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: GPG error: http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: The repository 'http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease' is not signed. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu yakkety InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/yakkety/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/yakkety-updates/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/yakkety-security/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Some index files failed to download. They have been ignored, or old ones used instead. E: Problem renaming the file /var/cache/apt/srcpkgcache.bin.3HKvbX to /var/cache/apt/srcpkgcache.bin - rename (116: Stale file handle) E: Problem renaming the file /var/cache/apt/pkgcache.bin.d0JUHJ to /var/cache/apt/pkgcache.bin - rename (116: Stale file handle) W: You may want to run apt-get update to correct these problems E: The package cache file is corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1618572/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1620525] Re: sbuild with overlayfs fails in yakkety
This may be related to https://bugs.launchpad.net/cloud- init/+bug/1618572 . -- 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/1620525 Title: sbuild with overlayfs fails in yakkety Status in dpkg package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in dpkg source package in Yakkety: Confirmed Status in linux source package in Yakkety: Triaged Status in dpkg package in Debian: New Bug description: overlayfs does not support renaming directories when the directories live in the lower filesystem: * Directory renames only allowed on "pure upper" (already created on * upper filesystem, never copied up). Directories which are on lower or * are merged may not be renamed. For these -EXDEV is returned and * userspace has to deal with it. This means, when copying up a * directory we can rely on it and ancestors being stable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1620525/+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 1618572] Re: apt-key add fails in overlayfs
Hi All, I have come across what seems to be a related issue across the board. This is not exactly the same way to reproduce but a simple 'apt-get update' shows this: In Yakkety: http://pastebin.ubuntu.com/23149838/ on 4.4.0-9136-generic In Xenial: http://pastebin.ubuntu.com/23149864/ Trusty similar issues: https://bugs.launchpad.net/maas/+bug/1621344 -- 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/1618572 Title: apt-key add fails in overlayfs Status in cloud-init: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: Sending a custom APT config to cloud-init fails to: 1. add keys 2. configure sources 3. configura additional repository. The same config is being sent to curtin, and curtin doesn't seem to fail (curtin install log http://paste.ubuntu.com/23112826/ just in case). config sent by maas = http://pastebin.ubuntu.com/23112834/ cloud-init.log = http://paste.ubuntu.com/23112820/ cloud-init-output.log = http://paste.ubuntu.com/23112822/ sources.list = http://paste.ubuntu.com/23112824/ ubuntu@node03:/var/log$ ls -l /etc/apt/sources.list.d/ total 0 ubuntu@node03:/var/log$ sudo apt-get update Hit:2 http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease Get:3 http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease [92.2 kB] Err:2 http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Ign:3 http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease Get:1 http://us.archive.ubuntu.com/ubuntu yakkety InRelease [247 kB] Err:4 http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Err:1 http://us.archive.ubuntu.com/ubuntu yakkety InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Fetched 339 kB in 0s (388 kB/s) Reading package lists... Error! W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: GPG error: http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: The repository 'http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease' is not signed. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu yakkety InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/yakkety/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/yakkety-updates/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/yakkety-security/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Some index files failed to download. They have been ignored, or old ones used instead. E: Problem renaming the file /var/cache/apt/srcpkgcache.bin.3HKvbX to /var/cache/apt/srcpkgcache.bin - rename (116: Stale file handle) E: Problem renaming the file /var/cache/apt/pkgcache.bin.d0JUHJ to
[Kernel-packages] [Bug 1618572] Re: cloud-init failing to configure sources and additional repository
Don't think it matters, but: http://pastebin.ubuntu.com/23119431/ -- 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/1618572 Title: cloud-init failing to configure sources and additional repository Status in cloud-init: New Status in linux package in Ubuntu: Incomplete Bug description: Sending a custom APT config to cloud-init fails to: 1. add keys 2. configure sources 3. configura additional repository. The same config is being sent to curtin, and curtin doesn't seem to fail (curtin install log http://paste.ubuntu.com/23112826/ just in case). config sent by maas = http://pastebin.ubuntu.com/23112834/ cloud-init.log = http://paste.ubuntu.com/23112820/ cloud-init-output.log = http://paste.ubuntu.com/23112822/ sources.list = http://paste.ubuntu.com/23112824/ ubuntu@node03:/var/log$ ls -l /etc/apt/sources.list.d/ total 0 ubuntu@node03:/var/log$ sudo apt-get update Hit:2 http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease Get:3 http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease [92.2 kB] Err:2 http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Ign:3 http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease Get:1 http://us.archive.ubuntu.com/ubuntu yakkety InRelease [247 kB] Err:4 http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Err:1 http://us.archive.ubuntu.com/ubuntu yakkety InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Fetched 339 kB in 0s (388 kB/s) Reading package lists... Error! W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: GPG error: http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: The repository 'http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease' is not signed. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu yakkety InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/yakkety/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/yakkety-updates/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/yakkety-security/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Some index files failed to download. They have been ignored, or old ones used instead. E: Problem renaming the file /var/cache/apt/srcpkgcache.bin.3HKvbX to /var/cache/apt/srcpkgcache.bin - rename (116: Stale file handle) E: Problem renaming the file /var/cache/apt/pkgcache.bin.d0JUHJ to /var/cache/apt/pkgcache.bin - rename (116: Stale file handle) W: You may want to run apt-get update to correct these problems E: The package cache file is corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1618572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1565016] Re: [2.0a4] Xenial deploy boot-initrd timeout and kernel panic
*** This bug is a duplicate of bug 1563779 *** https://bugs.launchpad.net/bugs/1563779 my guess is that a new kernel or a new package has hit xenial, and that is causing the kernel to panic. THe maas images automatically use newest stuff on the archives. ** Also affects: maas-images Importance: Undecided Status: New ** No longer affects: maas ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** This bug has been marked a duplicate of bug 1563779 [2.0a4] maas-rackd missing presumed lost -- 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/1565016 Title: [2.0a4] Xenial deploy boot-initrd timeout and kernel panic Status in maas-images: New Bug description: 1. Installed MAAS 2.0 alpha 4 2. Enlisted and commissioned 2 HP ProLiant DL360 Gen9 servers. 3. Used the UI to select Xenial for deployment. 4. From the server console observed a timeout attempting to TFTP boot-initrd followed by a kernel panic. ii maas 2.0.0~alpha4+bzr4843-0ubuntu1 all "Metal as a Service" is a physical cloud and IPAM ii maas-cli 2.0.0~alpha4+bzr4843-0ubuntu1 all MAAS client and command-line interface ii maas-common2.0.0~alpha4+bzr4843-0ubuntu1 all MAAS server common files ii maas-dhcp 2.0.0~alpha4+bzr4843-0ubuntu1 all MAAS DHCP server ii maas-dns 2.0.0~alpha4+bzr4843-0ubuntu1 all MAAS DNS server ii maas-proxy 2.0.0~alpha4+bzr4843-0ubuntu1 all MAAS Caching Proxy ii maas-rack-controller 2.0.0~alpha4+bzr4843-0ubuntu1 all Rack Controller for MAAS ii maas-region-api2.0.0~alpha4+bzr4843-0ubuntu1 all Region controller API service for MAAS ii maas-region-controller 2.0.0~alpha4+bzr4843-0ubuntu1 all Region Controller for MAAS ii python3-django-maas2.0.0~alpha4+bzr4843-0ubuntu1 all MAAS server Django web framework (Python 3) ii python3-maas-client2.0.0~alpha4+bzr4843-0ubuntu1 all MAAS python API client (Python 3) ii python3-maas-provisioningserver2.0.0~alpha4+bzr4843-0ubuntu1 all MAAS server provisioning libraries (Python 3) To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1565016/+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 1499869] Re: maas wily deployment to HP Proliant m400 arm64 server cartridge fails
** No longer affects: maas -- 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/1499869 Title: maas wily deployment to HP Proliant m400 arm64 server cartridge fails Status in cloud-init: Confirmed Status in curtin: New Status in cloud-init package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: In Progress Status in cloud-init source package in Wily: New Status in linux source package in Wily: Fix Committed Bug description: This is the error seen on the console: [ 64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin [ 124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect timeout=50.0)'))] [ 124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds [ 124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404] This times out eventually and the node is left at the login prompt. I can install wily via netboot without issue and some time back, wily was deployable to this node from MAAS. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1499869/+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 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory
I think the priority of this should be raised as the importance of this being fixed is quite high! -- 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/1464442 Title: installing or upgrading libc6 in Trusty removes all content from /tmp directory Status in linux package in Ubuntu: Invalid Status in upstart package in Ubuntu: Triaged Bug description: We are seeing an issue with installation of dkms package during a curtin installation which ends up with /tmp directory being wiped clean. This is very bad for curtin as it saves critical installation files in /tmp. It turns out that it's the of upgrading libc6, which is triggered as a result of installing dependencies, that removes content of /tmp. For example, installation of gcc results in the same result since it ends up with libc6 being upgraded. The only way that this won't be recreated is if the latest libc6 is already installed. This problem does not exist in precise. It can also be recreated by installing the .deb file for any version in trusty including 2.17. ubuntu@host:~$ ls /tmp tmpHHbRkP ubuntu@sirrush:~$ sudo apt-get install libc6 sudo: unable to resolve host sirrush Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libc-dev-bin libc6-dev Suggested packages: glibc-doc Recommended packages: manpages-dev The following packages will be upgraded: libc-dev-bin libc6 libc6-dev 3 upgraded, 0 newly installed, 0 to remove and 148 not upgraded. Need to get 6,714 kB of archives. After this operation, 6,144 B disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6-dev amd64 2.19-0ubuntu6.6 [1,910 kB] Get:2 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc-dev-bin amd64 2.19-0ubuntu6.6 [68.9 kB] Get:3 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6 amd64 2.19-0ubuntu6.6 [4,735 kB] Fetched 6,714 kB in 0s (18.5 MB/s) Preconfiguring packages ... (Reading database ... 57798 files and directories currently installed.) Preparing to unpack .../libc6-dev_2.19-0ubuntu6.6_amd64.deb ... Unpacking libc6-dev:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ... Preparing to unpack .../libc-dev-bin_2.19-0ubuntu6.6_amd64.deb ... Unpacking libc-dev-bin (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ... Preparing to unpack .../libc6_2.19-0ubuntu6.6_amd64.deb ... Unpacking libc6:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ... Processing triggers for man-db (2.6.7.1-1) ... Setting up libc6:amd64 (2.19-0ubuntu6.6) ... Setting up libc-dev-bin (2.19-0ubuntu6.6) ... Setting up libc6-dev:amd64 (2.19-0ubuntu6.6) ... Processing triggers for libc-bin (2.19-0ubuntu6.3) ... ubuntu@host:~$ ls /tmp ubuntu@host:~$ This is very recreatable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464442/+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 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
Hi David! Yes this is targeted for 14.04. 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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
** Changed in: maas Assignee: Andres Rodriguez (andreserl) = Jason Hobbs (jason-hobbs) -- 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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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
