[Bug 1013597] Re: No default route for stateful DHCPv6
This is still broken on latest ubuntu server 14.04. No wonder that ipv6 gets no adoption when one needs hours (or dig through bug reports) to get a basic ipv4/ipv6 dual stack setup working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013597 Title: No default route for stateful DHCPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1013597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130007] Re: kvm guests stuck (not in io) and cannot be killed using -9
No logs available. No entries in syslog, kern, dmesg, ... ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1130007 Title: kvm guests stuck (not in io) and cannot be killed using -9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1130007/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1130007] Re: kvm guests stuck (not in io) and cannot be killed using -9
Today another guest got stuck: cat /proc/499/stack [81084d2a] __cond_resched+0x2a/0x40 [81144bf2] isolate_migratepages_range+0xb2/0x5d0 [81145386] compact_zone+0x1b6/0x350 [811458bf] try_to_compact_pages+0x16f/0x1d0 [81677a94] __alloc_pages_direct_compact+0xaa/0x191 [8112bee3] __alloc_pages_nodemask+0x473/0x920 [81164b30] alloc_pages_current+0xb0/0x120 [8116bf5d] new_slab+0x22d/0x2c0 [816790ea] __slab_alloc+0x314/0x46e [811708a1] __kmalloc_node_track_caller+0xa1/0x1b0 [81566e99] __alloc_skb+0x79/0x230 [81560a31] sock_alloc_send_pskb+0x1d1/0x320 [81499ec1] tun_get_user+0x131/0x4a0 [8149a759] tun_chr_aio_write+0x69/0x90 [8118297a] do_sync_readv_writev+0xda/0x120 [81182c64] do_readv_writev+0xd4/0x1e0 [81182da5] vfs_writev+0x35/0x60 [81182f2a] sys_writev+0x4a/0xb0 [8168bb69] system_call_fastpath+0x16/0x1b [] 0x -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1130007 Title: kvm guests stuck (not in io) and cannot be killed using -9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1130007/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1130007] Re: kvm guests stuck (not in io) and cannot be killed using -9
No logs available. No entries in syslog, kern, dmesg, ... ** 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/1130007 Title: kvm guests stuck (not in io) and cannot be killed using -9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1130007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130007] Re: kvm guests stuck (not in io) and cannot be killed using -9
Today another guest got stuck: cat /proc/499/stack [81084d2a] __cond_resched+0x2a/0x40 [81144bf2] isolate_migratepages_range+0xb2/0x5d0 [81145386] compact_zone+0x1b6/0x350 [811458bf] try_to_compact_pages+0x16f/0x1d0 [81677a94] __alloc_pages_direct_compact+0xaa/0x191 [8112bee3] __alloc_pages_nodemask+0x473/0x920 [81164b30] alloc_pages_current+0xb0/0x120 [8116bf5d] new_slab+0x22d/0x2c0 [816790ea] __slab_alloc+0x314/0x46e [811708a1] __kmalloc_node_track_caller+0xa1/0x1b0 [81566e99] __alloc_skb+0x79/0x230 [81560a31] sock_alloc_send_pskb+0x1d1/0x320 [81499ec1] tun_get_user+0x131/0x4a0 [8149a759] tun_chr_aio_write+0x69/0x90 [8118297a] do_sync_readv_writev+0xda/0x120 [81182c64] do_readv_writev+0xd4/0x1e0 [81182da5] vfs_writev+0x35/0x60 [81182f2a] sys_writev+0x4a/0xb0 [8168bb69] system_call_fastpath+0x16/0x1b [] 0x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130007 Title: kvm guests stuck (not in io) and cannot be killed using -9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1130007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130007] [NEW] kvm guests stuck (not in io) and cannot be killed using -9
Public bug reported: I have two stuck kvm guests hanging in state R (for several hours now) on two different hosts. Actually they are not consuming any CPU and cannot be killed with kill -9. They are not responding to anything. Both systems are Ubuntu 12.10 Quantal running on a AMD II X4 965 Processor with 16GB RAM. Stack trace of the first stuck guest: cat /proc/2647/stack [81683e06] retint_careful+0x14/0x32 [] 0x Stack trace of the second stuck guest: cat /proc/11932/stack [81084d2a] __cond_resched+0x2a/0x40 [811544aa] try_to_unmap_file+0x3a/0x6d0 [811553c1] try_to_unmap+0x31/0x70 [811722a8] migrate_pages+0x318/0x500 [811453b4] compact_zone+0x1e4/0x350 [811458bf] try_to_compact_pages+0x16f/0x1d0 [81677a94] __alloc_pages_direct_compact+0xaa/0x191 [8112bee3] __alloc_pages_nodemask+0x473/0x920 [81164b30] alloc_pages_current+0xb0/0x120 [8116bf5d] new_slab+0x22d/0x2c0 [816790ea] __slab_alloc+0x314/0x46e [811708a1] __kmalloc_node_track_caller+0xa1/0x1b0 [81566e99] __alloc_skb+0x79/0x230 [81560a31] sock_alloc_send_pskb+0x1d1/0x320 [81499ec1] tun_get_user+0x131/0x4a0 [8149a759] tun_chr_aio_write+0x69/0x90 [8118297a] do_sync_readv_writev+0xda/0x120 [81182c64] do_readv_writev+0xd4/0x1e0 [81182da5] vfs_writev+0x35/0x60 [81182f2a] sys_writev+0x4a/0xb0 [8168bb69] system_call_fastpath+0x16/0x1b [] 0x Packages: Kernel: 3.5.0-23-generic #35-Ubuntu SMP Thu Jan 24 13:15:40 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux KVM: 1.2.0+noroms-0ubuntu2.12.10.2 Command line: kvm -name vm-16762 -machine pc-1.2 -enable-kvm -cpu kvm64 -smp sockets=1,cores=2 -m 1024 -vga cirrus -drive id=drive1245,if=none,cache=writeback,aio=native,format=raw,media=disk,file=rbd:kvm1/vm-16762-disk-1 -device virtio-blk-pci,id=hdrive1245,addr=0x12,drive=drive1245 -netdev tap,id=netdev1243,ifname=tap1243,script=,downscript= -device virtio-net-pci,id=nic1243,addr=0x03,mac=02:48:6e:2b:4e:55,netdev=netdev1243 -chardev socket,id=qmp,path=/var/run/kvm/vm-16762/qmp,server,nowait -mon chardev=qmp,mode=control -monitor unix:/var/run/kvm/vm-16762/mon,server,nowait -vnc 10.0.0.60:21,password -usbdevice tablet -nodefaults -pidfile /var/run/kvm/vm-16762/pid -boot menu=on -k de -chroot /var/run/kvm/vm-16762 -runas kvm -daemonize Original bug report is here: https://bugzilla.kernel.org/show_bug.cgi?id=54071 ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1130007 Title: kvm guests stuck (not in io) and cannot be killed using -9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1130007/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1130007] [NEW] kvm guests stuck (not in io) and cannot be killed using -9
Public bug reported: I have two stuck kvm guests hanging in state R (for several hours now) on two different hosts. Actually they are not consuming any CPU and cannot be killed with kill -9. They are not responding to anything. Both systems are Ubuntu 12.10 Quantal running on a AMD II X4 965 Processor with 16GB RAM. Stack trace of the first stuck guest: cat /proc/2647/stack [81683e06] retint_careful+0x14/0x32 [] 0x Stack trace of the second stuck guest: cat /proc/11932/stack [81084d2a] __cond_resched+0x2a/0x40 [811544aa] try_to_unmap_file+0x3a/0x6d0 [811553c1] try_to_unmap+0x31/0x70 [811722a8] migrate_pages+0x318/0x500 [811453b4] compact_zone+0x1e4/0x350 [811458bf] try_to_compact_pages+0x16f/0x1d0 [81677a94] __alloc_pages_direct_compact+0xaa/0x191 [8112bee3] __alloc_pages_nodemask+0x473/0x920 [81164b30] alloc_pages_current+0xb0/0x120 [8116bf5d] new_slab+0x22d/0x2c0 [816790ea] __slab_alloc+0x314/0x46e [811708a1] __kmalloc_node_track_caller+0xa1/0x1b0 [81566e99] __alloc_skb+0x79/0x230 [81560a31] sock_alloc_send_pskb+0x1d1/0x320 [81499ec1] tun_get_user+0x131/0x4a0 [8149a759] tun_chr_aio_write+0x69/0x90 [8118297a] do_sync_readv_writev+0xda/0x120 [81182c64] do_readv_writev+0xd4/0x1e0 [81182da5] vfs_writev+0x35/0x60 [81182f2a] sys_writev+0x4a/0xb0 [8168bb69] system_call_fastpath+0x16/0x1b [] 0x Packages: Kernel: 3.5.0-23-generic #35-Ubuntu SMP Thu Jan 24 13:15:40 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux KVM: 1.2.0+noroms-0ubuntu2.12.10.2 Command line: kvm -name vm-16762 -machine pc-1.2 -enable-kvm -cpu kvm64 -smp sockets=1,cores=2 -m 1024 -vga cirrus -drive id=drive1245,if=none,cache=writeback,aio=native,format=raw,media=disk,file=rbd:kvm1/vm-16762-disk-1 -device virtio-blk-pci,id=hdrive1245,addr=0x12,drive=drive1245 -netdev tap,id=netdev1243,ifname=tap1243,script=,downscript= -device virtio-net-pci,id=nic1243,addr=0x03,mac=02:48:6e:2b:4e:55,netdev=netdev1243 -chardev socket,id=qmp,path=/var/run/kvm/vm-16762/qmp,server,nowait -mon chardev=qmp,mode=control -monitor unix:/var/run/kvm/vm-16762/mon,server,nowait -vnc 10.0.0.60:21,password -usbdevice tablet -nodefaults -pidfile /var/run/kvm/vm-16762/pid -boot menu=on -k de -chroot /var/run/kvm/vm-16762 -runas kvm -daemonize Original bug report is here: https://bugzilla.kernel.org/show_bug.cgi?id=54071 ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130007 Title: kvm guests stuck (not in io) and cannot be killed using -9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1130007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
