[Bug 82423] Re: kacpid constantly using 80-95% CPU on pentium D dual core
This still happens with 8.10. I will post more details when I have them but on resume from suspend my CPU is at 90% + with kacpi_notify and kacpid spinning at 45% each. -- kacpid constantly using 80-95% CPU on pentium D dual core https://bugs.launchpad.net/bugs/82423 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147697] Trying to run "Screens and Graphics" but applicaton crashes without displaying anything
Public bug reported: Binary package hint: gnome-panel Launch "Screens and Graphics" from the System -> Administration menu fails. ProblemType: Bug Architecture: i386 Date: Mon Oct 1 11:10:43 2007 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/gnome-panel NonfreeKernelModules: vmnet vmblock vmmon nvidia Package: gnome-panel 1:2.20.0.1-0ubuntu4 PackageArchitecture: i386 ProcCmdline: gnome-panel --sm-client-id default1 ProcCwd: /home/aim ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel Uname: Linux aim-laptop 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- Trying to run "Screens and Graphics" but applicaton crashes without displaying anything https://bugs.launchpad.net/bugs/147697 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147697] Re: Trying to run "Screens and Graphics" but applicaton crashes without displaying anything
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/9622021/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/9622022/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/9622023/ProcStatus.txt -- Trying to run "Screens and Graphics" but applicaton crashes without displaying anything https://bugs.launchpad.net/bugs/147697 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574437] Re: valgrind crashes on programs linked to openssl
Amy update on when this will land in the archives? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574437 Title: valgrind crashes on programs linked to openssl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1574437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475260] Re: instances cannot resolve their own hostname
@2-xtian - if you're testing on MAAS 2.0 then I suspect you're seeing perfectly working DNS for hosts and their containers. Bootstrap across AWS, GCE, and in particular Azure to see the issues on the public clouds. Note: we are also proposing to land the following as an additional solution for the public clouds _and_ charms: https://github.com/frobware/nss-juju It won't fix the general case of: $ lxc exec juju-68160d-0 -- sh -c 'ping `hostname`' though see my comment about container hostname resolution in comment #6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475260] Re: instances cannot resolve their own hostname
If we use manage_etc_hosts: "true" then we will get: 127.0.1.1 vmhost.home vmhost (for example). I'm concerned about how well charms would hold out if they were always using localhost-esque addresses. For the LXD container case also take a look at: https://bugs.launchpad.net/juju/+bug/1623480 Fixing that bug I believe would fix the container case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475260] Re: instances cannot resolve their own hostname
And for completness: https://github.com/dimitern/juju/commit/60e89f1d6cb02f3f0f9f36dbf8e3156ad4e9f7e8 that tree has, as a PoC, support for returning hostname that will work with nss-juju. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1269921] Re: networking services restart hangs due to missing /etc/network/run/ifenslave.* files
I was trying to do something very similar for Juju - when the machine boots we rewrite /etc/network/interfaces to add bridges for active interfaces to support container networking. Our sequence is: $ ifdown -a $ transform --in-place /etc/network/interfaces $ ifup -a and with bonds configured using 802.3ad this would always hang on the ifup stage. If I add a: $ sleep 0.5 after the transform stage then the sequence of ifdown/up seems to work very reliably. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1269921 Title: networking services restart hangs due to missing /etc/network/run/ifenslave.* files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifenslave/+bug/1269921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590052] Re: juju deploy brings up interfaces in wrong order
If this is only happens with a bond then it's possible you are running into: https://bugs.launchpad.net/juju-core/+bug/1594855 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590052 Title: juju deploy brings up interfaces in wrong order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1590052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1269921] Re: networking services restart hangs due to missing /etc/network/run/ifenslave.* files
To clarify, my "transform" script just bridges active interfaces. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1269921 Title: networking services restart hangs due to missing /etc/network/run/ifenslave.* files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifenslave/+bug/1269921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590052] Re: juju deploy brings up interfaces in wrong order
*** This bug is a duplicate of bug 1594855 *** https://bugs.launchpad.net/bugs/1594855 The fix for: https://bugs.launchpad.net/juju-core/+bug/1594855 will be in juju-2.0-beta10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590052 Title: juju deploy brings up interfaces in wrong order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1590052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590052] Re: juju deploy brings up interfaces in wrong order
*** This bug is a duplicate of bug 1594855 *** https://bugs.launchpad.net/bugs/1594855 Closing this as it is bond related and fixed by: https://bugs.launchpad.net/juju-core/+bug/1594855 ** This bug has been marked a duplicate of bug 1594855 MAAS provider bridge script on trusty does not handle LACP bonds -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590052 Title: juju deploy brings up interfaces in wrong order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1590052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40
I haven't tried recently as I disabled IPv6 on my machine. On 26 January 2017 at 16:31, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Does this bug still happen with the latest Xenial updates? > > ** Changed in: linux (Ubuntu) >Status: In Progress => Incomplete > > ** Changed in: linux (Ubuntu Xenial) >Status: In Progress => Incomplete > > ** Changed in: linux (Ubuntu Yakkety) >Status: In Progress => Incomplete > > ** Changed in: linux (Ubuntu) > Assignee: Joseph Salisbury (jsalisbury) => (unassigned) > > ** Changed in: linux (Ubuntu Xenial) > Assignee: Joseph Salisbury (jsalisbury) => (unassigned) > > ** Changed in: linux (Ubuntu Yakkety) > Assignee: Joseph Salisbury (jsalisbury) => (unassigned) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1614953 > > Title: > hw csum failure when IPv6 interfaces configured in > netdev_rx_csum_fault+0x38/0x40 > > Status in linux package in Ubuntu: > Incomplete > Status in linux source package in Xenial: > Incomplete > Status in linux source package in Yakkety: > Incomplete > > Bug description: > Since I started using IPv6 I noticed the following kernel error: > > Thu Aug 18 15:05:01 2016] : hw csum failure > [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread > Tainted: P OE 4.4.0-34-generic #53-Ubuntu > [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. > To be filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013 > [Thu Aug 18 15:05:01 2016] 0286 c05989f2 > 8807573dfcd0 813f11b3 > [Thu Aug 18 15:05:01 2016] 0008 > 8807573dfce8 8171f6e8 > [Thu Aug 18 15:05:01 2016] 0074 8807573dfd30 > 8171639b fe091360 > [Thu Aug 18 15:05:01 2016] Call Trace: > [Thu Aug 18 15:05:01 2016] [] dump_stack+0x63/0x90 > [Thu Aug 18 15:05:01 2016] [] > netdev_rx_csum_fault+0x38/0x40 > [Thu Aug 18 15:05:01 2016] [] > skb_copy_and_csum_datagram_msg+0xeb/0x100 > [Thu Aug 18 15:05:01 2016] [] > udpv6_recvmsg+0x233/0x670 > [Thu Aug 18 15:05:01 2016] [] inet_recvmsg+0x7e/0xb0 > [Thu Aug 18 15:05:01 2016] [] sock_recvmsg+0x3b/0x50 > [Thu Aug 18 15:05:01 2016] [] SYSC_recvfrom+0xe1/0x160 > [Thu Aug 18 15:05:01 2016] [] ? wake_up_q+0x70/0x70 > [Thu Aug 18 15:05:01 2016] [] SyS_recvfrom+0xe/0x10 > [Thu Aug 18 15:05:01 2016] [] > entry_SYSCALL_64_fastpath+0x16/0x71 > > It repeats periodically: > > $ dmesg -T | grep 'hw csum failure' | wc -l > 201 > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.4.0-34-generic 4.4.0-34.53 > ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 > Uname: Linux 4.4.0-34-generic x86_64 > NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm > nvidia_modeset nvidia > ApportVersion: 2.20.1-0ubuntu2.1 > Architecture: amd64 > CurrentDesktop: Unity > Date: Fri Aug 19 13:47:54 2016 > HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2 > InstallationDate: Installed on 2016-04-24 (116 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. > ProcFB: 0 EFI VGA > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed > root=/dev/mapper/rootpool-rootvol ro intel_iommu=on > RelatedPackageVersions: >linux-restricted-modules-4.4.0-34-generic N/A >linux-backports-modules-4.4.0-34-generic N/A >linux-firmware1.157.3 > RfKill: > > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/14/2013 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: F22 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: Z77-D3H > dmi.board.vendor: Gigabyte Technology Co., Ltd. > dmi.board.version: x.x > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: Gigabyte Technology Co., Ltd. > dmi.chassis.version: To Be Filled By O.E.M. > dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013: > svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.: > rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x: > cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: > dmi.product.name: To be filled by O.E.M. > dmi.product.version: To be filled by O.E.M. > dmi.sys.vendor: Gigabyte
[Bug 1590104] Re: network config from datasource overrides network config from system
I tripped over this again today - will this be released or back-ported to xenial soon? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590104 Title: network config from datasource overrides network config from system To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1590104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565804] Re: ifup of vlan interfaces failing during networking start - RTNETLINK answers: File exists
The Juju bridge script, when creating the bridge device, generally leaves all iface options as it found them. For example: auto eth1.16 iface eth1.16 inet static address 10.245.184.100/24 vlan-raw-device eth1 mtu 1500 vlan_id 16 becomes the following: iface eth1.16 inet manual address 10.245.184.100/24 vlan-raw-device eth1 mtu 1500 vlan_id 16 auto br-eth1.16 iface br-eth1.16 inet static address 10.245.184.100/24 mtu 1500 bridge_ports eth1.16 bridge_stp off bridge_maxwait 0 Note: It doesn't propagate any bond options. For example: auto eth0 iface eth0 inet manual bond-lacp_rate slow bond-xmit_hash_policy layer2 bond-miimon 100 bond-master bond0 mtu 1500 bond-mode active-backup [ skipping eth1 for clarity ] auto bond0 iface bond0 inet dhcp bond-lacp_rate slow bond-xmit_hash_policy layer2 bond-miimon 100 mtu 1500 bond-mode active-backup hwaddress 52:54:00:1c:f1:5b bond-slaves none becomes the following when bridged: auto eth0 iface eth0 inet manual bond-lacp_rate slow bond-xmit_hash_policy layer2 bond-miimon 100 bond-master bond0 mtu 1500 bond-mode active-backup auto bond0 iface bond0 inet manual bond-lacp_rate slow bond-xmit_hash_policy layer2 bond-miimon 100 mtu 1500 bond-mode active-backup hwaddress 52:54:00:1c:f1:5b bond-slaves none dns-nameservers 10.17.20.200 dns-search maas19 auto br-bond0 iface br-bond0 inet dhcp mtu 1500 hwaddress 52:54:00:1c:f1:5b bridge_ports bond0 bridge_stp off bridge_maxwait 0 dns-nameservers 10.17.20.200 dns-search maas19 I generally propagated the existing options when creating the bridge device. Should MTU be an exception now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565804 Title: ifup of vlan interfaces failing during networking start - RTNETLINK answers: File exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1565804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40
I mentioned that it repeats - here's the uptime to get a feeling of the frequency: $ uptime 13:51:59 up 1 day, 4:17, 2 users, load average: 0.40, 0.67, 0.71 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614953 Title: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614953] [NEW] hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40
Public bug reported: Since I started using IPv6 I noticed the following kernel error: Thu Aug 18 15:05:01 2016] : hw csum failure [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P OE 4.4.0-34-generic #53-Ubuntu [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013 [Thu Aug 18 15:05:01 2016] 0286 c05989f2 8807573dfcd0 813f11b3 [Thu Aug 18 15:05:01 2016] 0008 8807573dfce8 8171f6e8 [Thu Aug 18 15:05:01 2016] 0074 8807573dfd30 8171639b fe091360 [Thu Aug 18 15:05:01 2016] Call Trace: [Thu Aug 18 15:05:01 2016] [] dump_stack+0x63/0x90 [Thu Aug 18 15:05:01 2016] [] netdev_rx_csum_fault+0x38/0x40 [Thu Aug 18 15:05:01 2016] [] skb_copy_and_csum_datagram_msg+0xeb/0x100 [Thu Aug 18 15:05:01 2016] [] udpv6_recvmsg+0x233/0x670 [Thu Aug 18 15:05:01 2016] [] inet_recvmsg+0x7e/0xb0 [Thu Aug 18 15:05:01 2016] [] sock_recvmsg+0x3b/0x50 [Thu Aug 18 15:05:01 2016] [] SYSC_recvfrom+0xe1/0x160 [Thu Aug 18 15:05:01 2016] [] ? wake_up_q+0x70/0x70 [Thu Aug 18 15:05:01 2016] [] SyS_recvfrom+0xe/0x10 [Thu Aug 18 15:05:01 2016] [] entry_SYSCALL_64_fastpath+0x16/0x71 It repeats periodically: $ dmesg -T | grep 'hw csum failure' | wc -l 201 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 19 13:47:54 2016 HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2 InstallationDate: Installed on 2016-04-24 (116 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/rootpool-rootvol ro intel_iommu=on RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614953 Title: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40
I only noticed because I had been experimenting with setting up IPv6 support for Juju. I enabled IPv6 on my router, then insisted that "eth0" got an IP address in ENI and only then did I notice the messages. This has only been a recent experiment so no evidence for whether this happened as part of any upgrade. I can try the latest upstream kernel but it won't be for a day or two. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614953 Title: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40
Currently running: $ uname -a Linux spicy 4.8.0-040800rc3-generic #201608212032 SMP Mon Aug 22 00:34:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Will report back tomorrow with a finding either way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614953 Title: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40
Running: $ uname -a Linux spicy 4.8.0-040800rc3-generic #201608212032 SMP Mon Aug 22 00:34:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ uptime 08:18:06 up 1 day, 15:40, 2 users, load average: 0.60, 0.80, 2.73 $ dmesg -T | grep 'hw csum failure' | wc -l 0 Marking this as fixed upstream. ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614953 Title: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590104] Re: network config from datasource overrides network config from system
>From a Juju perspective we need this in trusty too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590104 Title: network config from datasource overrides network config from system To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1590104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973590] [NEW] package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/perf', which is also in package linux-base 3.4
Public bug reported: Trying to install perf. sudo apt-get install linux-base linux-tools-common ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia wl AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0-0ubuntu4 AptOrdering: linux-base: Install linux-tools-common: Install linux-base: Configure linux-tools-common: Configure Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aim1951 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Date: Wed Apr 4 18:23:15 2012 ErrorMessage: trying to overwrite '/usr/bin/perf', which is also in package linux-base 3.4 HibernationDevice: RESUME=UUID=ec43e4ac-945d-49cd-9361-e31042944ede InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64+mac (20120327.1) MachineType: Apple Inc. MacBookPro5,3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic root=UUID=797179ce-c840-4e4f-bcb7-9aa6bbe6a0ee ro nomodeset quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 1.99-21ubuntu1 SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/perf', which is also in package linux-base 3.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP53.88Z.00AC.B03.0906151647 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22587C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22587C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP53.88Z.00AC.B03.0906151647:bd06/15/09:svnAppleInc.:pnMacBookPro5,3:pvr1.0:rvnAppleInc.:rnMac-F22587C8:rvr:cvnAppleInc.:ct10:cvrMac-F22587C8: dmi.product.name: MacBookPro5,3 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package package-conflict precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973590 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/perf', which is also in package linux- base 3.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/973590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973590] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/perf', which is also in package linux-base 3.4
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973590 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/perf', which is also in package linux- base 3.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/973590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] Re: lxc-test-apparmor fails on aarch64
This is no longer happening on stock kernels. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452293] Re: kernel crash when compiling linux-4.1-rc2 with make -j20
This was crashing with 3.19 (i.e., vivid's kernel). I wanted to pick up most of vivid's kernel config and initiated my build on 3.19 with `make olddefconfig' . I briefly tried with utopic and didn't see an issue - but take that with a pinch of salt as I only did one run and wanted to report based on a greater sample size. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452293 Title: kernel crash when compiling linux-4.1-rc2 with make -j20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452293] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1452293/+attachment/4392221/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452293 Title: kernel crash when compiling linux-4.1-rc2 with make -j20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452293] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1452293/+attachment/4392219/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452293 Title: kernel crash when compiling linux-4.1-rc2 with make -j20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452293] [NEW] kernel crash when compiling linux-4.1-rc2 with make -j20
Public bug reported: Kernel crash whilst building new kernel: Steps to reproduce: wget https://www.kernel.org/pub/linux/kernel/v4.x/testing/linux-4.1-rc2.tar.xz tar xf linux-4.1-rc2.tar.xz cd linux-4.1-rc2/ make mrproper make olddefconfig make -j20 I noticed that the output from the build had stopped then noticed the following messages (via dmesg): [ 15.285274] random: nonblocking pool is initialized [ 15.633718] xgene-enet 1702.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 2541.173142] Unable to handle kernel paging request at virtual address 1018 [ 2541.181062] pgd = ffc3ec61d000 [ 2541.184449] [1018] *pgd=, *pud= [ 2541.191476] Internal error: Oops: 9605 [#1] SMP [ 2541.196331] Modules linked in: rtc_xgene xgene_rng uio_pdrv_genirq uio autofs4 realtek ahci_xgene libahci_platform xgene_enet libahci aes_neon_blk ablk_ helper cryptd [ 2541.211214] CPU: 2 PID: 17206 Comm: sh Not tainted 3.19.0-15-generic #15-Ubuntu [ 2541.218488] Hardware name: APM X-Gene Mustang board (DT) [ 2541.223775] task: ffc3ec2d3d40 ti: ffc0fec1c000 task.ti: ffc0fec1c000 [ 2541.231236] PC is at __d_lookup+0x88/0x194 [ 2541.235324] LR is at d_lookup+0x3c/0x64 [ 2541.239148] pc : [] lr : [] pstate: 0145 [ 2541.246509] sp : ffc0fec1fb40 [ 2541.249807] x29: ffc0fec1fb40 x28: 00020241 [ 2541.255114] x27: 1b2865a6 x26: ffc0fec1fe88 [ 2541.260421] x25: x24: ffc0ff01d02d [ 2541.265728] x23: 000b x22: ffc0fec1fda0 [ 2541.271045] x21: ffc3b80ebd80 x20: 0ff8 [ 2541.276353] x19: 1000 x18: [ 2541.281659] x17: 002000118748 x16: ffc00020f430 [ 2541.286967] x15: 0008 x14: 636e692f8134366d [ 2541.292275] x13: 72612f8168637261 x12: 492d812069706175 [ 2541.297594] x11: x10: fefefefefefefeff [ 2541.302904] x9 : x8 : ffc3e9ed2f40 [ 2541.308221] x7 : x6 : 003f [ 2541.313532] x5 : ffc0ff01d000 x4 : 0015 [ 2541.318848] x3 : ffc000b64f60 x2 : 9e370001 [ 2541.324155] x1 : ffc3eec0 x0 : 001e7194 [ 2541.330959] Process sh (pid: 17206, stack limit = 0xffc0fec1c058) [ 2541.337367] Stack: (0xffc0fec1fb40 to 0xffc0fec2) [ 2541.343088] fb40: fec1fba0 ffc0 0022a268 ffc0 dd6e 00b5a000 ffc0 [ 2541.351235] fb60: fec1fda0 ffc0 b80ebd80 ffc3 0301 b80ebd80 ffc3 [ 2541.359378] fb80: 0001 fec1fe88 ffc0 fec1fd90 ffc0 00020241 [ 2541.367516] fba0: fec1fbd0 ffc0 0021b0e0 ffc0 fec1fd40 ffc0 b80ebd80 ffc3 [ 2541.375654] fbc0: fec1fda0 ffc0 fec1fca7 ffc0 fec1fc10 ffc0 0021d790 ffc0 [ 2541.383792] fbe0: fec1fd40 ffc0 b8113458 ffc3 b80ebd80 ffc3 ff01d000 ffc0 [ 2541.391930] fc00: fec1fd3c ffc0 fec1fd90 ffc0 fec1fcb0 ffc0 002204c8 ffc0 [ 2541.400066] fc20: fe52d000 ffc0 fec1fd90 ffc0 fec1fe88 ffc0 ff01d000 ffc0 [ 2541.408204] fc40: 0041 ff9c 011a 0038 [ 2541.416343] fc60: 00b6e000 ffc0 fec1fcb0 ffc0 002204a4 ffc0 [ 2541.424481] fc80: 0001 ff01d000 ffc0 fe52d000 ffc0 0022 (the rest is attached) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 1 1970 seq crw-rw 1 root audio 116, 33 Jan 1 1970 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17.2-0ubuntu1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Wed May 6 14:08:16 2015 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 root=/dev/sda1 rw rootwait RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 1 1970 seq crw-rw 1 root audio
[Bug 1452293] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1452293/+attachment/4392220/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452293 Title: kernel crash when compiling linux-4.1-rc2 with make -j20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452293] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1452293/+attachment/439/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452293 Title: kernel crash when compiling linux-4.1-rc2 with make -j20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452293] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1452293/+attachment/4392223/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452293 Title: kernel crash when compiling linux-4.1-rc2 with make -j20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452293] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1452293/+attachment/4392240/+files/UdevDb.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452293 Title: kernel crash when compiling linux-4.1-rc2 with make -j20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452293] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1452293/+attachment/4392236/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452293 Title: kernel crash when compiling linux-4.1-rc2 with make -j20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452293] Re: kernel crash when compiling linux-4.1-rc2 with make -j20
apport information ** Description changed: Kernel crash whilst building new kernel: Steps to reproduce: wget https://www.kernel.org/pub/linux/kernel/v4.x/testing/linux-4.1-rc2.tar.xz tar xf linux-4.1-rc2.tar.xz cd linux-4.1-rc2/ make mrproper make olddefconfig make -j20 I noticed that the output from the build had stopped then noticed the following messages (via dmesg): [ 15.285274] random: nonblocking pool is initialized [ 15.633718] xgene-enet 1702.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 2541.173142] Unable to handle kernel paging request at virtual address 1018 [ 2541.181062] pgd = ffc3ec61d000 [ 2541.184449] [1018] *pgd=, *pud= [ 2541.191476] Internal error: Oops: 9605 [#1] SMP [ 2541.196331] Modules linked in: rtc_xgene xgene_rng uio_pdrv_genirq uio autofs4 realtek ahci_xgene libahci_platform xgene_enet libahci aes_neon_blk ablk_ helper cryptd [ 2541.211214] CPU: 2 PID: 17206 Comm: sh Not tainted 3.19.0-15-generic #15-Ubuntu [ 2541.218488] Hardware name: APM X-Gene Mustang board (DT) [ 2541.223775] task: ffc3ec2d3d40 ti: ffc0fec1c000 task.ti: ffc0fec1c000 [ 2541.231236] PC is at __d_lookup+0x88/0x194 [ 2541.235324] LR is at d_lookup+0x3c/0x64 [ 2541.239148] pc : [] lr : [] pstate: 0145 [ 2541.246509] sp : ffc0fec1fb40 [ 2541.249807] x29: ffc0fec1fb40 x28: 00020241 [ 2541.255114] x27: 1b2865a6 x26: ffc0fec1fe88 [ 2541.260421] x25: x24: ffc0ff01d02d [ 2541.265728] x23: 000b x22: ffc0fec1fda0 [ 2541.271045] x21: ffc3b80ebd80 x20: 0ff8 [ 2541.276353] x19: 1000 x18: [ 2541.281659] x17: 002000118748 x16: ffc00020f430 [ 2541.286967] x15: 0008 x14: 636e692f8134366d [ 2541.292275] x13: 72612f8168637261 x12: 492d812069706175 [ 2541.297594] x11: x10: fefefefefefefeff [ 2541.302904] x9 : x8 : ffc3e9ed2f40 [ 2541.308221] x7 : x6 : 003f [ 2541.313532] x5 : ffc0ff01d000 x4 : 0015 [ 2541.318848] x3 : ffc000b64f60 x2 : 9e370001 [ 2541.324155] x1 : ffc3eec0 x0 : 001e7194 [ 2541.330959] Process sh (pid: 17206, stack limit = 0xffc0fec1c058) [ 2541.337367] Stack: (0xffc0fec1fb40 to 0xffc0fec2) [ 2541.343088] fb40: fec1fba0 ffc0 0022a268 ffc0 dd6e 00b5a000 ffc0 [ 2541.351235] fb60: fec1fda0 ffc0 b80ebd80 ffc3 0301 b80ebd80 ffc3 [ 2541.359378] fb80: 0001 fec1fe88 ffc0 fec1fd90 ffc0 00020241 [ 2541.367516] fba0: fec1fbd0 ffc0 0021b0e0 ffc0 fec1fd40 ffc0 b80ebd80 ffc3 [ 2541.375654] fbc0: fec1fda0 ffc0 fec1fca7 ffc0 fec1fc10 ffc0 0021d790 ffc0 [ 2541.383792] fbe0: fec1fd40 ffc0 b8113458 ffc3 b80ebd80 ffc3 ff01d000 ffc0 [ 2541.391930] fc00: fec1fd3c ffc0 fec1fd90 ffc0 fec1fcb0 ffc0 002204c8 ffc0 [ 2541.400066] fc20: fe52d000 ffc0 fec1fd90 ffc0 fec1fe88 ffc0 ff01d000 ffc0 [ 2541.408204] fc40: 0041 ff9c 011a 0038 [ 2541.416343] fc60: 00b6e000 ffc0 fec1fcb0 ffc0 002204a4 ffc0 [ 2541.424481] fc80: 0001 ff01d000 ffc0 fe52d000 ffc0 0022 (the rest is attached) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 1 1970 seq crw-rw 1 root audio 116, 33 Jan 1 1970 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17.2-0ubuntu1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Wed May 6 14:08:16 2015 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 root=/dev/sda1 rw rootwait RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: E
[Bug 1452293] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1452293/+attachment/4392238/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452293 Title: kernel crash when compiling linux-4.1-rc2 with make -j20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452293] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1452293/+attachment/4392237/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452293 Title: kernel crash when compiling linux-4.1-rc2 with make -j20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452293] Re: kernel crash when compiling linux-4.1-rc2 with make -j20
I was going straight from 3.19 (ie., vivid) to 4-1-rc2 so don't know if it is applicable to just that version. I would be surprised if it was. Regarding booting into utopic - I can try but it will be a while before I can unload my machine to put utopic back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452293 Title: kernel crash when compiling linux-4.1-rc2 with make -j20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442064] [NEW] /usr/bin/dpkg received a segmentation fault (arm64)
Public bug reported: I did a fresh install of a trusty cloud image to an applied micro X-Gene today and post the installation (and login) I did: apt-get update apt-get dist-upgrade and noticed the following: ubuntu@linaro-test:devstack$ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: acl cpu-checker fontconfig fontconfig-config fonts-dejavu-core hicolor-icon-theme ipxe-qemu libaio1 libasound2 libasound2-data libasyncns0 libatk1.0-0 libatk1.0-data libblas3 libbluetooth3 libbrlapi0.6 libcaca0 libcairo2 libcups2 libdatrie1 libdrm-nouveau2 libdrm-radeon1 libfdt1 libflac8 libfontconfig1 libfreetype6 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgraphite2-3 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libharfbuzz0b libjasper1 libjbig0 libjpeg-turbo8 libjpeg8 libjs-jquery libjs-underscore liblinear-tools liblinear1 liblua5.2-0 libogg0 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpixman-1-0 libpulse0 libsdl1.2debian libsndfile1 libsubunit-perl libthai-data libthai0 libtiff5 libtxc-dxtn-s2tc0 libusbredirparser1 libvorbis0a libvorbisenc2 libx11-xcb1 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxcb-render0 libxcb-shm0 libxcb-sync1 libxcomposite1 libxcursor1 libxdamage1 libxfixes3 libxi6 libxinerama1 libxrandr2 libxrender1 libxshmfence1 libxxf86vm1 python-cairo python-extras python-fixtures python-gobject-2 python-mimeparse python-testtools qemu-system-common Use 'apt-get autoremove' to remove them. The following packages will be upgraded: python-gobject-2 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/145 kB of archives. After this operation, 885 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 54957 files and directories currently installed.) Preparing to unpack .../python-gobject-2_2.28.6-12build1_arm64.deb ... Unpacking python-gobject-2 (2.28.6-12build1) over (2.28.6-12build1) ... E: Sub-process /usr/bin/dpkg received a segmentation fault. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.7 Uname: Linux 3.19.3 aarch64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: arm64 CrashDB: ubuntu Date: Thu Apr 9 10:16:06 2015 PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.update.motd.d.91.release.upgrade: [inaccessible: [Errno 13] Permission denied: '/etc/update-motd.d/91-release-upgrade'] ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 dist-upgrade trusty uec-images ** Description changed: I did a fresh install of a trusty cloud image to an applied micro X-Gene today and post the installation (and login) I did: - apt-get update - apt-get upgrade + apt-get update + apt-get dist-upgrade and noticed the following: - ubuntu@linaro-test:devstack$ sudo apt-get dist-upgrade + ubuntu@linaro-test:devstack$ sudo apt-get dist-upgrade Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: - acl cpu-checker fontconfig fontconfig-config fonts-dejavu-core - hicolor-icon-theme ipxe-qemu libaio1 libasound2 libasound2-data libasyncns0 - libatk1.0-0 libatk1.0-data libblas3 libbluetooth3 libbrlapi0.6 libcaca0 - libcairo2 libcups2 libdatrie1 libdrm-nouveau2 libdrm-radeon1 libfdt1 - libflac8 libfontconfig1 libfreetype6 libgdk-pixbuf2.0-0 - libgdk-pixbuf2.0-common libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa - libgraphite2-3 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libharfbuzz0b - libjasper1 libjbig0 libjpeg-turbo8 libjpeg8 libjs-jquery libjs-underscore - liblinear-tools liblinear1 liblua5.2-0 libogg0 libpango-1.0-0 - libpangocairo-1.0-0 libpangoft2-1.0-0 libpixman-1-0 libpulse0 - libsdl1.2debian libsndfile1 libsubunit-perl libthai-data libthai0 libtiff5 - libtxc-dxtn-s2tc0 libusbredirparser1 libvorbis0a libvorbisenc2 libx11-xcb1 - libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxcb-render0 - libxcb-shm0 libxcb-sync1 libxcomposite1 libxcursor1 libxdamage1 libxfixes3 - libxi6 libxinerama1 libxrandr2 libxrender1 libxshmfence1 libxxf86vm1 - python-cairo python-extras python-fixtures python-gobject-2 python-mimeparse - python-testtools qemu-system-common + acl cpu-checker fontconfig fontconfig-config fonts-dejavu-core + hicolor-icon-theme ipxe-qemu libaio1
[Bug 1433183] [NEW] Kernel oops when running devstack/stack.sh
Public bug reported: I was installing OpenStack using devstack/stack.sh and noticed that at some point a `pip install' had failed. I later untarred linux-3.19.1.tar.xz and get the same (or similar) kernel backtrace. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 1 1970 seq crw-rw 1 root audio 116, 33 Jan 1 1970 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.16.2-0ubuntu3 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Mar 17 16:06:05 2015 Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 root=/dev/sda1 rw rootwait RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 uec-images vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433183 Title: Kernel oops when running devstack/stack.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433183] Re: Kernel oops when running devstack/stack.sh
I will try and reproduce - but this machine is automatically deployed and I have since destroyed it. Please bear with me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433183 Title: Kernel oops when running devstack/stack.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433183] Re: Kernel oops when running devstack/stack.sh
Not noticed on other architectures as I am only testing against AArch64 at the moment. The failure was with the stock kernel that comes with the vivid cloud image (3.19.0-9-generic). I had been building and using 3.19.1 on Trusty (AArch64 again) for about 3 days and hadn't noticed the failure there, so I attempted to untar and build the kernel on vivid. The untar generated the same oops I saw with whatever devstack/stack.sh was doing at the time (which looked like pip install ...). devstack has been working very well for me on AArch64 - I have been running it daily for months, so yes it does work on earlier kernels. Some of the results are captured here: http://openstack.validation.linaro.org/dashboard/image-charts/tempest- measurements. This week has been the first time I have targeted vivid (and therefore 3.19.x). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433183 Title: Kernel oops when running devstack/stack.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433183] Re: Kernel oops when running devstack/stack.sh
I have seen this oops twice; I didn't report the issue first time round as the machine I was using had been powered down and I was unable to collect any logs. I happened to notice the stacktrace in my serial console window so I tried again and saw the issue again (and raised this bug). However, I have tried to reproduce it again this morning but 2 stack/unstack.sh have completed successfully - where success means no kernel oops. Each installation of OpenStack is done from a freshly installed cloud image so perhaps there have been other changes in that image since Monday/Tuesday this week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433183 Title: Kernel oops when running devstack/stack.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433183] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1433183/+attachment/4348909/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433183 Title: Kernel oops when running devstack/stack.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433183] Re: Kernel oops when running devstack/stack.sh
apport information ** Tags added: apport-collected ** Description changed: I was installing OpenStack using devstack/stack.sh and noticed that at some point a `pip install' had failed. I later untarred linux-3.19.1.tar.xz and get the same (or similar) kernel backtrace. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 1 1970 seq crw-rw 1 root audio 116, 33 Jan 1 1970 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.16.2-0ubuntu3 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Mar 17 16:06:05 2015 Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 root=/dev/sda1 rw rootwait RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jan 1 1970 seq + crw-rw 1 root audio 116, 33 Jan 1 1970 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.16.2-0ubuntu3 + Architecture: arm64 + ArecordDevices: Error: [Errno 2] No such file or directory + CRDA: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 15.04 + Lspci: + + Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: console=ttyS0,115200n8 root=/dev/sda1 rw rootwait + ProcVersionSignature: User Name 3.19.0-9.9-generic 3.19.1 + RelatedPackageVersions: + linux-restricted-modules-3.19.0-9-generic N/A + linux-backports-modules-3.19.0-9-generic N/A + linux-firmware1.143 + RfKill: Error: [Errno 2] No such file or directory + Tags: vivid uec-images + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 3.19.0-9-generic aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip floppy libvirtd netdev plugdev sudo video + _MarkForUpload: True ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1433183/+attachment/4348902/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433183 Title: Kernel oops when running devstack/stack.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433183] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1433183/+attachment/4348905/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433183 Title: Kernel oops when running devstack/stack.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433183] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1433183/+attachment/4348907/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433183 Title: Kernel oops when running devstack/stack.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433183] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1433183/+attachment/4348904/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433183 Title: Kernel oops when running devstack/stack.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433183] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1433183/+attachment/4348903/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433183 Title: Kernel oops when running devstack/stack.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433183] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1433183/+attachment/4348906/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433183 Title: Kernel oops when running devstack/stack.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433183] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1433183/+attachment/4348908/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433183 Title: Kernel oops when running devstack/stack.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433183] Re: Kernel oops when running devstack/stack.sh
The appport-collect I just did was from the same machine, but a different cloud image deployment (current/ 18-Mar-2015 06:05) . The recent attachments may/may not be useful to the original bug report. But if you look at the dmesg attachment you can see there is a different (and new) stacktrace. Apologies for the confusion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433183 Title: Kernel oops when running devstack/stack.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496972] Re: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel
Will look at the patch. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1496972 Title: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1496972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496972] Re: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel
I see in comment #33 that the bug became invalid and reassigned. However, it doesn't explain the behaviour I previously saw in comment #15 where pinging a gateway interface appeared to lock up the machine - there was no other changes made to /e/n/i in that case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1496972 Title: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1496972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496972] Re: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel
** Changed in: juju-core Milestone: None => 1.24.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1496972 Title: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1496972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496972] Re: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel
I can see this same issue on amd64. ubuntu@maas-node2:~$ uname -a Linux maas-node2 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ubuntu@maas-node2:~$ lsb_release -cs wily And, having bootstrapped a node, I see the following: ubuntu@maas-node2:~$ ifconfig -a eth0 Link encap:Ethernet HWaddr 52:54:00:c3:72:59 inet addr:10.17.17.103 Bcast:10.17.17.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:28657 errors:0 dropped:2 overruns:0 frame:0 TX packets:20914 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:55451555 (55.4 MB) TX bytes:1666875 (1.6 MB) juju-br0 Link encap:Ethernet HWaddr 52:54:00:c3:72:59 inet addr:10.17.17.103 Bcast:10.17.17.255 Mask:255.255.255.0 inet6 addr: fe80::5054:ff:fec3:7259/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18112 errors:0 dropped:0 overruns:0 frame:0 TX packets:17050 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:40259427 (40.2 MB) TX bytes:1402232 (1.4 MB) 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:9584 errors:0 dropped:0 overruns:0 frame:0 TX packets:9584 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:19054312 (19.0 MB) TX bytes:19054312 (19.0 MB) lxcbr0Link encap:Ethernet HWaddr 3a:f6:90:64:c4:73 inet addr:10.0.3.1 Bcast:0.0.0.0 Mask:255.255.255.0 inet6 addr: fe80::38f6:90ff:fe64:c473/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:570 (570.0 B) networking does appear to continue working on amd64, but not on arm64. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1496972 Title: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1496972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496972] Re: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel
Pending RB: http://reviews.vapour.ws/r/3027/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1496972 Title: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1496972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496972] Re: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel
** Changed in: juju-core/1.25 Assignee: (unassigned) => Andrew McDermott (frobware) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1496972 Title: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1496972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496972] Re: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel
** Changed in: juju-core/1.25 Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1496972 Title: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1496972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496972] Re: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel
** Changed in: juju-core Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1496972 Title: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1496972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] lxc.default.txt
apport information ** Attachment added: "lxc.default.txt" https://bugs.launchpad.net/bugs/1446658/+attachment/4380595/+files/lxc.default.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] [NEW] lxc-test-apparmor fails on aarch64
Public bug reported: Running lxc-test-apparmor fails on aarch64 (arm64) systems. The following files which are listed in files_to_deny[] in src/tests/aa.c: /sys/kernel/uevent_helper /proc/sys/kernel/sysrq are not denied, but should be. Perhaps I should be changing the apparmor profile for lxc before running the tests (but that's just a guess). I'm invoking the tests as: # for i in /usr/bin/lxc-test-* ; do $i || touch /tmp/$(basename $i).failed; done which results in the following failures: lxc-test-apparmor.failed lxc-test-autostart.failed lxc-test-containertests.failed lxc-test-unpriv.failed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.7-0ubuntu0.1 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.19.2 aarch64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: arm64 Date: Tue Apr 21 13:17:28 2015 ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: arm64 DistroRelease: Ubuntu 14.04 KernLog: Package: lxc 1.0.7-0ubuntu0.1 PackageArchitecture: arm64 ProcCmdline: console=ttyS0,115200n8 root=/dev/sda1 rw rootwait ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Tags: trusty uec-images Uname: Linux 3.19.2 aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: kvm libvirtd _MarkForUpload: True defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor apport-bug apport-collected arm64 trusty uec-images ** Tags added: apport-collected ** Description changed: Running lxc-test-apparmor fails on aarch64 (arm64) systems. The following files which are listed in files_to_deny[] in src/tests/aa.c: /sys/kernel/uevent_helper /proc/sys/kernel/sysrq are not denied, but should be. Perhaps I should be changing the apparmor profile for lxc before running the tests (but that's just a guess). I'm invoking the tests as: # for i in /usr/bin/lxc-test-* ; do $i || touch /tmp/$(basename $i).failed; done which results in the following failures: lxc-test-apparmor.failed lxc-test-autostart.failed lxc-test-containertests.failed lxc-test-unpriv.failed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.7-0ubuntu0.1 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.19.2 aarch64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: arm64 Date: Tue Apr 21 13:17:28 2015 ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx + --- + ApportVersion: 2.14.1-0ubuntu3.7 + Architecture: arm64 + DistroRelease: Ubuntu 14.04 + KernLog: + + Package: lxc 1.0.7-0ubuntu0.1 + PackageArchitecture: arm64 + ProcCmdline: console=ttyS0,115200n8 root=/dev/sda1 rw rootwait + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' + Tags: trusty uec-images + Uname: Linux 3.19.2 aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: kvm libvirtd + _MarkForUpload: True + defaults.conf: + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up + lxc.network.hwaddr = 00:16:3e:xx:xx:xx + lxcsyslog: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] RelatedPackageVersions.txt
apport information ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/1446658/+attachment/4380593/+files/RelatedPackageVersions.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1446658/+attachment/4380592/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] lxc-net.default.txt
apport information ** Attachment added: "lxc-net.default.txt" https://bugs.launchpad.net/bugs/1446658/+attachment/4380594/+files/lxc-net.default.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] Re: lxc-test-apparmor fails on aarch64
Yes, the kernel is 3.19.2. I realised I was running a later version than stock just after I submitted the report. I am deploying a fresh cloud image onto a new machine and will double-check that it still happens (but suspecting not). BTW: do you run the tests in a diferent way than my 'for' loop? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] Re: lxc-test-apparmor fails on aarch64
I just installed the following cloud image onto an Applied Micro X-Gene board: http://cloud-images.ubuntu.com/trusty/20150420.1/trusty-server- cloudimg-arm64-disk1.img Running the tests in the same way: # for i in /usr/bin/lxc-test-*; do $i || touch /tmp/$(basename $i).failed; done I see the following failures: root@linaro-test:/tmp# ls -1 /tmp/*.failed /tmp/lxc-test-autostart.failed /tmp/lxc-test-unpriv.failed /tmp/lxc-test-usernic.failed so the previous lxc-test-apparmor is OK. root@linaro-test:~# uname -a Linux linaro-test 3.13.0-46-generic #79-Ubuntu SMP Tue Mar 10 20:08:34 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux root@linaro-test:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.2 LTS Release:14.04 Codename: trusty Apologies for the confusion over the kernel version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] Re: lxc-test-apparmor fails on aarch64
Error output from the three tests that fail: root@linaro-test:/tmp/lxc# id uid=0(root) gid=0(root) groups=0(root) root@linaro-test:/tmp/lxc# lxc-test-unpriv Removing user `lxcunpriv' ... Warning: group `lxcunpriv' has no more members. Done. WARN: could not reopen tty: Permission denied WARN: could not reopen tty: Permission denied WARN: could not reopen tty: Permission denied WARN: could not reopen tty: Permission denied Setting up the GPG keyring Downloading the image index ERROR: Couldn't find a matching image. lxc_container: lxccontainer.c: create_run_template: 1125 container creation template for c1 failed lxc_container: lxc_create.c: main: 271 Error creating container c1 c2 is not running c1 is not running root@linaro-test:/tmp/lxc# echo $? 1 root@linaro-test:/tmp/lxc# lxc-test-autostart Setting up the GPG keyring Downloading the image index ERROR: Couldn't find a matching image. lxc_container: lxccontainer.c: create_run_template: 1125 container creation template for lxc-test-auto failed lxc_container: lxc_create.c: main: 271 Error creating container lxc-test-auto FAIL root@linaro-test:/tmp/lxc# lxc-test-autostart Setting up the GPG keyring Downloading the image index ERROR: Couldn't find a matching image. lxc_container: lxccontainer.c: create_run_template: 1125 container creation template for lxc-test-auto failed lxc_container: lxc_create.c: main: 271 Error creating container lxc-test-auto FAIL root@linaro-test:/tmp/lxc# echo $? 1 root@linaro-test:/tmp/lxc# lxc-test-usernic /usr/sbin/deluser: The user `usernic-user' does not exist. WARN: could not reopen tty: Permission denied WARN: could not reopen tty: Permission denied WARN: could not reopen tty: Permission denied WARN: could not reopen tty: Permission denied Setting up the GPG keyring Downloading the image index ERROR: Couldn't find a matching image. lxc_container: lxccontainer.c: create_run_template: 1125 container creation template for b1 failed lxc_container: lxc_create.c: main: 271 Error creating container b1 FAIL root@linaro-test:/tmp/lxc# echo $? 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] Re: lxc-test-apparmor fails on aarch64
I also ran the tests using the debian/tests/exercise script: SUMMARY: pass=21, fail=4, ignored=0 root@linaro-test:/home/ubuntu/lxc-1.0.7/debian/tests# ./exercise PASS: lxc-tests: /usr/bin/lxc-test-apparmor PASS: lxc-tests: /usr/bin/lxc-test-attach FAIL: lxc-tests: /usr/bin/lxc-test-autostart --- Setting up the GPG keyring Downloading the image index ERROR: Couldn't find a matching image. lxc_container: lxccontainer.c: create_run_template: 1125 container creation template for lxc-test-auto failed lxc_container: lxc_create.c: main: 271 Error creating container lxc-test-auto FAIL --- PASS: lxc-tests: /usr/bin/lxc-test-cgpath PASS: lxc-tests: /usr/bin/lxc-test-clonetest PASS: lxc-tests: /usr/bin/lxc-test-concurrent PASS: lxc-tests: /usr/bin/lxc-test-console PASS: lxc-tests: /usr/bin/lxc-test-containertests PASS: lxc-tests: /usr/bin/lxc-test-createtest PASS: lxc-tests: /usr/bin/lxc-test-destroytest PASS: lxc-tests: /usr/bin/lxc-test-device-add-remove PASS: lxc-tests: /usr/bin/lxc-test-get_item PASS: lxc-tests: /usr/bin/lxc-test-getkeys PASS: lxc-tests: /usr/bin/lxc-test-list PASS: lxc-tests: /usr/bin/lxc-test-locktests PASS: lxc-tests: /usr/bin/lxc-test-lxcpath PASS: lxc-tests: /usr/bin/lxc-test-reboot PASS: lxc-tests: /usr/bin/lxc-test-saveconfig PASS: lxc-tests: /usr/bin/lxc-test-shutdowntest PASS: lxc-tests: /usr/bin/lxc-test-snapshot PASS: lxc-tests: /usr/bin/lxc-test-startone PASS: lxc-tests: /usr/bin/lxc-test-ubuntu FAIL: lxc-tests: /usr/bin/lxc-test-unpriv --- Removing user `lxcunpriv' ... Warning: group `lxcunpriv' has no more members. Done. Setting up the GPG keyring Downloading the image index ERROR: Couldn't find a matching image. lxc_container: lxccontainer.c: create_run_template: 1125 container creation template for c1 failed lxc_container: lxc_create.c: main: 271 Error creating container c1 c2 is not running c1 is not running --- FAIL: lxc-tests: /usr/bin/lxc-test-usernic --- /usr/sbin/deluser: The user `usernic-user' does not exist. Setting up the GPG keyring Downloading the image index ERROR: Couldn't find a matching image. lxc_container: lxccontainer.c: create_run_template: 1125 container creation template for b1 failed lxc_container: lxc_create.c: main: 271 Error creating container b1 FAIL --- FAIL: python3: API --- Setting up the GPG keyring Downloading the image index ERROR: Couldn't find a matching image. lxc_container: lxccontainer.c: create_run_template: 1125 container creation template for 8a397b70-e8cc-11e4-b80c-0001730204af failed Getting instance for '8a397b70-e8cc-11e4-b80c-0001730204af' Creating rootfs using 'download', arch=arm64 Traceback (most recent call last): File "/tmp/tmp.QlGl5dcqZY", line 71, in assert(container.defined) AssertionError --- SUMMARY: pass=21, fail=4, ignored=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] Re: lxc-test-apparmor fails on aarch64
Regarding access to images.linuxcontainers.org - I believe I can "see" this from my test machine: root@linaro-test:/home/ubuntu/lxc-1.0.7/debian/tests# dig +short images.linuxcontainers.org rproxy.stgraber.org. 192.99.34.219 root@linaro-test:/home/ubuntu/lxc-1.0.7/debian/tests# dig +short -x 192.99.34.219 vorash.stgraber.org. root@linaro-test:/home/ubuntu/lxc-1.0.7/debian/tests# ping images.linuxcontainers.org PING rproxy.stgraber.org (192.99.34.219) 56(84) bytes of data. 64 bytes from vorash.stgraber.org (192.99.34.219): icmp_seq=1 ttl=54 time=96.7 ms 64 bytes from vorash.stgraber.org (192.99.34.219): icmp_seq=2 ttl=54 time=88.2 ms 64 bytes from vorash.stgraber.org (192.99.34.219): icmp_seq=3 ttl=54 time=88.2 ms 64 bytes from vorash.stgraber.org (192.99.34.219): icmp_seq=4 ttl=54 time=88.2 ms 64 bytes from vorash.stgraber.org (192.99.34.219): icmp_seq=5 ttl=54 time=88.2 ms 64 bytes from vorash.stgraber.org (192.99.34.219): icmp_seq=6 ttl=54 time=88.2 ms root@linaro-test:/home/ubuntu/lxc-1.0.7/debian/tests# wget images.linuxcontainers.org --2015-04-22 08:56:28-- http://images.linuxcontainers.org/ Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 192.99.34.219, 2001:470:b368:1020:1::2 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|192.99.34.219|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 951 [text/html] Saving to: ‘index.html’ (index.html attached) ** Attachment added: "index.html from wget linux.imagescontainers.org" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1446658/+attachment/4381173/+files/index.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] Re: lxc-test-apparmor fails on aarch64
I believe there is also GPG connectivity: root@linaro-test:/home/ubuntu/lxc-1.0.7/debian/tests# gpg --search-keys andrew.iain.mcderm...@gmail.com gpg: searching for "andrew.iain.mcderm...@gmail.com" from hkp server keys.gnupg.net (1) Andrew McDermott 2048 bit RSA key 1250D2A5, created: 2013-06-02 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] Re: lxc-test-apparmor fails on aarch64
Looking at: http://images.linuxcontainers.org/images/ubuntu/trusty/ I don't see a directory for arm64 (or aarch64) so that explains why lxc- test-usernic fails -- there is no arm64 image to download. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446658] Re: lxc-test-apparmor fails on aarch64
And based on my comment in #14 the tests that I said currently fail: lxc-test-unpriv lxc-test-autostart lxc-test-usernic are also trying to download an arm64 image that, AFAICT at the time of writing, does not exist. So, given that lxc-test-apparmor does work on my trusty install: ubuntu@linaro-test:~$ uname -a Linux linaro-test 3.13.0-49-generic #83-Ubuntu SMP Fri Apr 10 20:16:58 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux and I know now that the three tests which fail are due to a non-existent image it would appear that everything is in fact just hunky-dory. When you run these tests on arm64 are you using a different image repository? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1446658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1518440] Re: tgt fails to install in LXD
I think this fix should be back ported to trusty so that we can eventually install MAAS in a LXD environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1518440 Title: tgt fails to install in LXD To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1518440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282203] Re: gnome-terminal not respecting "Enable menu access keys" setting
Defintely concur with comment #3. I updated this morning, having left my system alone for a few weeks, and immediately noticed this (broken) behaviour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282203 Title: gnome-terminal not respecting "Enable menu access keys" setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1282203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155903] [NEW] lttng-modules-dkms 2.0.2-0ubuntu1: lttng-modules kernel module failed to build
Public bug reported: apt-get install lttng-tools ProblemType: Package DistroRelease: Ubuntu 12.04 Package: lttng-modules-dkms 2.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_eth prl_fs prl_tg ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DKMSKernelVersion: 3.5.0-23-generic Date: Sat Mar 16 09:12:55 2013 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True PackageArchitecture: all PackageVersion: 2.0.2-0ubuntu1 SourcePackage: lttng-modules Title: lttng-modules-dkms 2.0.2-0ubuntu1: lttng-modules kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lttng-modules (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155903 Title: lttng-modules-dkms 2.0.2-0ubuntu1: lttng-modules kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1155903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
