[Kernel-packages] [Bug 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
I have the same issue on Ubuntu 12.04 LTS using Trusty kernel: Linux version 3.13.0-29-generic (buildd@roseapple) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #53~precise1-Ubuntu SMP Wed Jun 4 22:06:25 UTC 2014 Distributor ID: Ubuntu Description:Ubuntu 12.04.4 LTS Release:12.04 Codename: precise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with "service nfs-kernel-server stop" followed by "service nfs-kernel-server start". With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: #> echo workqueue:workqueue_queue_work > /sys/kernel/debug/tracing/set_event #> cat /sys/kernel/debug/tracing/trace_pipe > /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Thu May 22 22:48:48 2014 HibernationDevice: RESUME=UUID=adcdeef5-9b46-4ea4-b9f4-b6e642ea91e8 InstallationDate: Installed on 2014-05-12 (10 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" -
[Kernel-packages] [Bug 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests
I have this issue running an Ubuntu 12.04.5 guest (running kernel 3.13.0-43-generic) on a KVM Hypervisor with the same configuration (Ubuntu 12.04.5, 3.13.0-43, CPU 4x AMD Opteron(TM) Processor 6274, Dell R915). I'm unable to boot the guest the 80% of the trials. The error is reproducible even with a specific guest CPU configured or with the QEMU generic one. This is the output from a brand new Ubuntu 12.04.5 installation: [5.136174] divide error: [#1] SMP [5.139614] Modules linked in: floppy [5.143686] CPU: 1 PID: 36 Comm: migration/1 Not tainted 3.13.0-43-generic #72~precise1-Ubuntu [5.144868] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007 [5.144868] task: 880409699800 ti: 8804096a task.ti: 8804096a [5.144868] RIP: 0010:[] [] kvm_unlock_kick+0xa4/0x100 [5.144868] RSP: 0018:8804096a1cf8 EFLAGS: 00010046 [5.144868] RAX: 0005 RBX: RCX: 0002 [5.144868] RDX: RSI: 88041fc53480 RDI: 0100 [5.144868] RBP: 8804096a1d18 R08: 81eb54e8 R09: [5.144868] R10: R11: R12: 88041fc53480 [5.144868] R13: 166c R14: 0002 R15: 88041fc53480 [5.144868] FS: 7f8557f1f700() GS:88041fc2() knlGS: [5.144868] CS: 0010 DS: ES: CR0: 8005003b [5.144868] CR2: 7f8556b2f570 CR3: 000404ee2000 CR4: 06e0 [5.144868] Stack: [5.144868] 880404dd 0002 880404dd0654 88041fc33480 [5.144868] 8804096a1d28 8174b8ba 8804096a1d38 817645fa [5.144868] 8804096a1d98 8109d37b 8804096a1d78 0002 [5.144868] Call Trace: [5.144868] [] __ticket_unlock_slowpath+0x2e/0x32 [5.144868] [] _raw_spin_unlock+0x2a/0x30 [5.144868] [] __migrate_task+0xcb/0x180 [5.144868] [] ? __migrate_task+0x180/0x180 [5.144868] [] migration_cpu_stop+0x23/0x30 [5.144868] [] cpu_stopper_thread+0x83/0x150 [5.144868] [] ? __schedule+0x38e/0x700 [5.144868] [] smpboot_thread_fn+0xfd/0x180 [5.144868] [] ? SyS_setgroups+0x170/0x170 [5.144868] [] kthread+0xc9/0xe0 [5.144868] [] ? flush_kthread_worker+0xb0/0xb0 [5.144868] [] ret_from_fork+0x7c/0xb0 [5.144868] [] ? flush_kthread_worker+0xb0/0xb0 [5.144868] Code: 08 66 44 39 ea 75 c0 0f b6 15 e9 35 e6 00 84 d2 75 2e 83 05 fa 35 e6 00 01 48 c7 c0 8a a0 00 00 31 db 0f b7 0c 01 b8 05 00 00 00 <0f> 01 c1 66 0f 1f 84 00 00 00 00 00 5b 41 5c 41 5d 41 5e 5d c3 [5.144868] RIP [] kvm_unlock_kick+0xa4/0x100 [5.144868] RSP [5.144868] ---[ end trace 9f5442e8ee6f35f7 ]--- Attached you can find the full NMI trace (12 vCPU). ** Attachment added: "Full error backtrace" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379340/+attachment/4278654/+files/NMI_backtrace.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379340 Title: qemu-kvm guest panic for AMD smp trusty guests Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: [Impact] When using KVM on an AMD host with a kernel that has CONFIG_DEBUG_RODATA enabled, a guest with: multiple vCPUs, and exposing features to the guest such as tsc_adjust can cause a divide error on kvm_unlock_kick when booting the VM. This impacts kernels 3.12+. [Test Case] 1) Create a VM on an AMD host with appropriate features (Opteron 6xxx for example) 2) Edit virsh xml to have and multiple vCPUs. 3) Boot VM with VGA console using virt-manager (I couldn't reproduce strictly monitoring via virsh console). [Fix] commit c1118b3602c2329671ad5ec8bdf8e374323d6343 upstream -- Just upgraded OpenStack compute hosts in our public cloud (using qemu- kvm via libvirt) from Precise to Trusty (14.04.1), now on kernel 3.13.0-36-generic with qemu-kvm 2.0.0+dfsg-2ubuntu1.5. Following the upgrade, whenever we try to start an smp/multicore Trusty guest (existing or new), we run into this panic [1] inside the guest just towards the end of boot. This happens consistently for smp guests using the Trusty kernel (i.e., it also affects earlier Ubuntus using the HWE kernel from Trusty but not their native versions). I didn't have any other distro images to hand with 3.13.x kernels, but none of the others I tested were affected (in the 3.2 - 3.16 kernel range). There are scarce similar reports out there, but the one we did find pointed to a CPU feature as the trigger. We were running these hosts with libvirt cpu mode set to "host-passthrough" (so qemu starts with "-cpu host"), on AMD 6200 & 6300 Opteron hardware. Switching the
[Kernel-packages] [Bug 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests
I can confirm that the issue looks fixed using 3.13.0-44.73~precise1 from precise-proposed. I made more than ten reboots with the new kernel installed on VMs and all were successful. Then I switched back to the previous 3.13.0-43.72~precise1 and VMs boot failed at the first trial. Again back to propose 3.13.0-44.73~precise1 at VM were booting fine. I'm not using Trusty on these AMD machines so I cannot test it. But the kernel is the same as precise so the issue should be fixed also on Trusty. ** Tags added: verification-done-precise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379340 Title: qemu-kvm guest panic for AMD smp trusty guests Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: [Impact] When using KVM on an AMD host with a kernel that has CONFIG_DEBUG_RODATA enabled, a guest with: multiple vCPUs, and exposing features to the guest such as tsc_adjust can cause a divide error on kvm_unlock_kick when booting the VM. This impacts kernels 3.12+. [Test Case] 1) Create a VM on an AMD host with appropriate features (Opteron 6xxx for example) 2) Edit virsh xml to have and multiple vCPUs. 3) Boot VM with VGA console using virt-manager (I couldn't reproduce strictly monitoring via virsh console). [Fix] commit c1118b3602c2329671ad5ec8bdf8e374323d6343 upstream -- Just upgraded OpenStack compute hosts in our public cloud (using qemu- kvm via libvirt) from Precise to Trusty (14.04.1), now on kernel 3.13.0-36-generic with qemu-kvm 2.0.0+dfsg-2ubuntu1.5. Following the upgrade, whenever we try to start an smp/multicore Trusty guest (existing or new), we run into this panic [1] inside the guest just towards the end of boot. This happens consistently for smp guests using the Trusty kernel (i.e., it also affects earlier Ubuntus using the HWE kernel from Trusty but not their native versions). I didn't have any other distro images to hand with 3.13.x kernels, but none of the others I tested were affected (in the 3.2 - 3.16 kernel range). There are scarce similar reports out there, but the one we did find pointed to a CPU feature as the trigger. We were running these hosts with libvirt cpu mode set to "host-passthrough" (so qemu starts with "-cpu host"), on AMD 6200 & 6300 Opteron hardware. Switching the guest domains to use cpu mode "host-model" instead works around the issue and is perfectly acceptable for most of our users. We have various other Intel compute hosts and they don't seem to be affected. (1) [ 11.256924] divide error: [#1] SMP [ 11.258133] Modules linked in: kvm_amd kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw lp parport psmouse floppy [ 11.260228] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-36-generic #63-Ubuntu [ 11.260228] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011 [ 11.260228] task: 81c15480 ti: 81c0 task.ti: 81c0 [ 11.260228] RIP: 0010:[] [] kvm_unlock_kick+0xa8/0x100 [ 11.260228] RSP: 0018:88023fc03c98 EFLAGS: 00010046 [ 11.260228] RAX: 0005 RBX: RCX: 0001 [ 11.260228] RDX: 81eaf408 RSI: RDI: [ 11.260228] RBP: 88023fc03cb8 R08: 81eaf400 R09: [ 11.260228] R10: 880037612cc0 R11: ea0002eb0a00 R12: 8800374a33c0 [ 11.260228] R13: 0020 R14: 0001 R15: 0286 [ 11.260228] FS: 7f1e8b538740() GS:88023fc0() knlGS: [ 11.260228] CS: 0010 DS: ES: CR0: 8005003b [ 11.260228] CR2: 7f1e8ae09d50 CR3: 01c0e000 CR4: 000406f0 [ 11.260228] Stack: [ 11.260228] 0286 0001 0001 00c3 [ 11.260228] 88023fc03cc8 81717ed6 88023fc03ce0 8172641a [ 11.260228] 8800374a33c0 88023fc03d18 810aaeb0 88023295e000 [ 11.260228] Call Trace: [ 11.260228] [ 11.260228] [] __ticket_unlock_slowpath+0x24/0x34 [ 11.260228] [] _raw_spin_unlock_irqrestore+0x3a/0x40 [ 11.260228] [] __wake_up_sync_key+0x50/0x60 [ 11.260228] [] sock_def_readable+0x3a/0x70 [ 11.260228] [] packet_rcv+0x2fa/0x430 [ 11.260228] [] __netif_receive_skb_core+0x360/0x840 [ 11.260228] [] __netif_receive_skb+0x18/0x60 [ 11.260228] [] netif_receive_skb+0x23/0x90 [ 11.260228] [] virtnet_poll+0x4d4/0x850 [ 11.260228] [] net_rx_action+0x152/0x250 [ 11.260228] [] __do_softirq+0xec/0x2c0 [ 11.260228] [] irq_exit+0x105/0x110 [ 11.260228] [] do_IRQ+0x56/0xc0 [ 11.260228] [] common_interrupt+0x6d/0x6d [ 11.2602
[Kernel-packages] [Bug 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests
During the weekend I was able to reproduce the issue using a Trusty VM with kernel 3.13.0-43.72 kernel 3.13.0-44.73 fixes the issue. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379340 Title: qemu-kvm guest panic for AMD smp trusty guests Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: [Impact] When using KVM on an AMD host with a kernel that has CONFIG_DEBUG_RODATA enabled, a guest with: multiple vCPUs, and exposing features to the guest such as tsc_adjust can cause a divide error on kvm_unlock_kick when booting the VM. This impacts kernels 3.12+. [Test Case] 1) Create a VM on an AMD host with appropriate features (Opteron 6xxx for example) 2) Edit virsh xml to have and multiple vCPUs. 3) Boot VM with VGA console using virt-manager (I couldn't reproduce strictly monitoring via virsh console). [Fix] commit c1118b3602c2329671ad5ec8bdf8e374323d6343 upstream -- Just upgraded OpenStack compute hosts in our public cloud (using qemu- kvm via libvirt) from Precise to Trusty (14.04.1), now on kernel 3.13.0-36-generic with qemu-kvm 2.0.0+dfsg-2ubuntu1.5. Following the upgrade, whenever we try to start an smp/multicore Trusty guest (existing or new), we run into this panic [1] inside the guest just towards the end of boot. This happens consistently for smp guests using the Trusty kernel (i.e., it also affects earlier Ubuntus using the HWE kernel from Trusty but not their native versions). I didn't have any other distro images to hand with 3.13.x kernels, but none of the others I tested were affected (in the 3.2 - 3.16 kernel range). There are scarce similar reports out there, but the one we did find pointed to a CPU feature as the trigger. We were running these hosts with libvirt cpu mode set to "host-passthrough" (so qemu starts with "-cpu host"), on AMD 6200 & 6300 Opteron hardware. Switching the guest domains to use cpu mode "host-model" instead works around the issue and is perfectly acceptable for most of our users. We have various other Intel compute hosts and they don't seem to be affected. (1) [ 11.256924] divide error: [#1] SMP [ 11.258133] Modules linked in: kvm_amd kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw lp parport psmouse floppy [ 11.260228] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-36-generic #63-Ubuntu [ 11.260228] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011 [ 11.260228] task: 81c15480 ti: 81c0 task.ti: 81c0 [ 11.260228] RIP: 0010:[] [] kvm_unlock_kick+0xa8/0x100 [ 11.260228] RSP: 0018:88023fc03c98 EFLAGS: 00010046 [ 11.260228] RAX: 0005 RBX: RCX: 0001 [ 11.260228] RDX: 81eaf408 RSI: RDI: [ 11.260228] RBP: 88023fc03cb8 R08: 81eaf400 R09: [ 11.260228] R10: 880037612cc0 R11: ea0002eb0a00 R12: 8800374a33c0 [ 11.260228] R13: 0020 R14: 0001 R15: 0286 [ 11.260228] FS: 7f1e8b538740() GS:88023fc0() knlGS: [ 11.260228] CS: 0010 DS: ES: CR0: 8005003b [ 11.260228] CR2: 7f1e8ae09d50 CR3: 01c0e000 CR4: 000406f0 [ 11.260228] Stack: [ 11.260228] 0286 0001 0001 00c3 [ 11.260228] 88023fc03cc8 81717ed6 88023fc03ce0 8172641a [ 11.260228] 8800374a33c0 88023fc03d18 810aaeb0 88023295e000 [ 11.260228] Call Trace: [ 11.260228] [ 11.260228] [] __ticket_unlock_slowpath+0x24/0x34 [ 11.260228] [] _raw_spin_unlock_irqrestore+0x3a/0x40 [ 11.260228] [] __wake_up_sync_key+0x50/0x60 [ 11.260228] [] sock_def_readable+0x3a/0x70 [ 11.260228] [] packet_rcv+0x2fa/0x430 [ 11.260228] [] __netif_receive_skb_core+0x360/0x840 [ 11.260228] [] __netif_receive_skb+0x18/0x60 [ 11.260228] [] netif_receive_skb+0x23/0x90 [ 11.260228] [] virtnet_poll+0x4d4/0x850 [ 11.260228] [] net_rx_action+0x152/0x250 [ 11.260228] [] __do_softirq+0xec/0x2c0 [ 11.260228] [] irq_exit+0x105/0x110 [ 11.260228] [] do_IRQ+0x56/0xc0 [ 11.260228] [] common_interrupt+0x6d/0x6d [ 11.260228] [ 11.260228] [] ? native_safe_halt+0x6/0x10 [ 11.260228] [] default_idle+0x1f/0xc0 [ 11.260228] [] arch_cpu_idle+0x26/0x30 [ 11.260228] [] cpu_startup_entry+0xc5/0x290 [ 11.260228] [] rest_init+0x77/0x80 [ 11.260228] [] start_kernel+0x433/0x43e [ 11.260228] [] ? repair_env_string+0x5c/0x5c [ 11.26022
[Kernel-packages] [Bug 1307473] Re: guest hang due to missing clock interrupt
I confirm, like Jeff Wilson, that I had the same issue with 3.13 and got resolved with 3.14.1. I cannot right now test the kernel suggested in #46. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307473 Title: guest hang due to missing clock interrupt Status in “linux” package in Ubuntu: Confirmed Bug description: I noticed on 2 different systems that after upgrade from precise to latest trusty VMs are crashing: - in case of Windows VMs I'm getting BSOD with error message: "A clock interrupt was not received on a secondary processor within the allocated time interval." - On linux VMs I'm noticing "hrtimer: interrupt took 2992229 ns" messages - On some proprietary virtual appliances I'm noticing crashes an due to missing timer interrupts QEMU version is: QEMU emulator version 1.7.91 (Debian 2.0.0~rc1+dfsg-0ubuntu3) Full command line: qemu-system-x86_64 -enable-kvm -name win7eval -S -machine pc- i440fx-1.7,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=4,threads=1 -uuid 05e5089a- 4aa1-6bb2-ef06-ab4d020a -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7eval.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -boot strict=on -device piix3-usb- uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/vm/win7eval.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio- disk0,id=virtio-disk0,bootindex=1 -drive file=/home/damarion/iso/7600.16385.090713-1255_x86fre_enterprise_en- us_EVAL_Eval_Enterprise-GRMCENEVAL_EN_DVD.iso,if=none,id=drive- ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive =drive-ide0-0-0,id=ide0-0-0 -drive file=/home/damarion/iso/virtio- win-0.1-74.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=24,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:38:31:0a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa- serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -device VGA,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
So, it seems we are all on Dell with a Samsung SSD 850 drive. Next week I'll have a chance to try a different SSD from Kingston. I'll see if the bug is still reproducible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
It seems that the code causing the bug will be reverted in 4.9-rc7: https://bugzilla.kernel.org/show_bug.cgi?id=187061#c15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
Could be related to this bug? https://bugzilla.kernel.org/show_bug.cgi?id=187061 https://bugzilla.kernel.org/show_bug.cgi?id=151631 It affects kernels >= 4.8 on (as far as I know) any distro. I'm experiencing problems on both Fedora 24 and Ubuntu 16.10 running kernel 4.8 on a Dell Latitude E5450 with a Samsung 850 SSD. ** Bug watch added: Linux Kernel Bug Tracker #187061 http://bugzilla.kernel.org/show_bug.cgi?id=187061 ** Bug watch added: Linux Kernel Bug Tracker #151631 http://bugzilla.kernel.org/show_bug.cgi?id=151631 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1200533] Re: Please update AMD ucode/microcode in linux-firmware
The AMD microcode coming from linux-firmware - 1.79.6 is freezing 99% of the times my 5 Dell PowerEdge M915 blades (4x64 Cores Opteron 6274, currently with 3.0.4 BIOS). This happens both at boot and also if I blacklist the 'microcode' module and then I run 'modprobe microcode' after the system is up. To have always a successful boot I had to blacklist the microcode module. ### Description:Ubuntu 12.04.3 LTS Release:12.04 Linux marley 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed Sep 11 18:21:16 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ### root@marley:~# dpkg -S /lib/firmware/amd-ucode/microcode_amd* linux-firmware: /lib/firmware/amd-ucode/microcode_amd.bin linux-firmware: /lib/firmware/amd-ucode/microcode_amd.bin.asc linux-firmware: /lib/firmware/amd-ucode/microcode_amd_fam15h.bin linux-firmware: /lib/firmware/amd-ucode/microcode_amd_fam15h.bin.asc ### root@marley:~# apt-cache show linux-firmware Package: linux-firmware Priority: optional Section: misc Installed-Size: 41502 Maintainer: Ubuntu Kernel Team Architecture: all Version: 1.79.6 Replaces: atmel-firmware, linux-restricted-common Provides: atmel-firmware Conflicts: atmel-firmware Filename: pool/main/l/linux-firmware/linux-firmware_1.79.6_all.deb Size: 23217718 MD5sum: b774085d0ad3bb87bdf60b9590df1ba6 SHA1: 89ce403513450402be1190659ddbe1c9ed9db54e SHA256: 5945561ab9bffbf9d91d618bf9fe5862b9d42abdff797429bc75b8d034b7fb28 Description-en: Firmware for Linux kernel drivers This package provides firmware used by Linux kernel drivers. Multi-Arch: foreign Description-md5: 7a047bff9e44dce458a300976c12f9da Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Supported: 5y ### dmidecode attached ** Attachment added: "dmidecode.log" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1200533/+attachment/3879282/+files/dmidecode.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1200533 Title: Please update AMD ucode/microcode in linux-firmware Status in “linux-firmware” package in Ubuntu: Fix Released Status in “linux-firmware” source package in Precise: Fix Released Status in “linux-firmware” source package in Saucy: Fix Released Bug description: Updated AMD-ucode has has just landed on kernel.org Please update amd-ucode in linux-firmware https://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/commit/?id=31f6b3076bab3c4b65f67fdb232f4579ed828b4f Files: amd-ucode/microcode_amd.bin amd-ucode/microcode_amd_fam15h.bin The ucode used to be available here: http://www.amd64.org/support/microcode.html before the site went down last year. This AMD ucode fixes some severe lockup issues on AMD family 15h CPUs when under high load. The fix for erratum #759 being the most severe. Example thread discussing the lockup issues of #759: http://communities.vmware.com/thread/432033?start=30&tstart=0 Dell + others have already updated BIOS updated microcode: http://www.dell.com/support/drivers/au/en/19/DriverDetails?driverId=HPP5C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1200533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1200533] Re: Please update AMD ucode/microcode in linux-firmware
Thanks Grant. The update is already scheduled for next Monday morning. I'll keep you updated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1200533 Title: Please update AMD ucode/microcode in linux-firmware Status in “linux-firmware” package in Ubuntu: Fix Released Status in “linux-firmware” source package in Precise: Fix Released Status in “linux-firmware” source package in Saucy: Fix Released Bug description: Updated AMD-ucode has has just landed on kernel.org Please update amd-ucode in linux-firmware https://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/commit/?id=31f6b3076bab3c4b65f67fdb232f4579ed828b4f Files: amd-ucode/microcode_amd.bin amd-ucode/microcode_amd_fam15h.bin The ucode used to be available here: http://www.amd64.org/support/microcode.html before the site went down last year. This AMD ucode fixes some severe lockup issues on AMD family 15h CPUs when under high load. The fix for erratum #759 being the most severe. Example thread discussing the lockup issues of #759: http://communities.vmware.com/thread/432033?start=30&tstart=0 Dell + others have already updated BIOS updated microcode: http://www.dell.com/support/drivers/au/en/19/DriverDetails?driverId=HPP5C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1200533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
