[Kernel-packages] [Bug 1682402] Re: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine
I did some more testing with upstream kernel. The upstream kernel similarly has the occasional freeze where the entire desktop stops responding or updating (while the hardware mouse cursor is usually still movable but clicking doesn't do anything), however unlike the Ubuntu 17.04 kernel it always recovers immediately after 1-3 seconds and responds again. Ubuntu's kernel just gets stuck for me forever - one time I waited over a minute to see if something would wake up again, but the image just remained frozen forever and that's it. -- 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/1682402 Title: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine Status in linux package in Ubuntu: Confirmed Bug description: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine. I am filing this as a kernel bug because the following steps will still hang the system: 1. Open up gnome-terminal 2. Start copying a really large file between two different EXT4 partitions on my local SSD with a "cp" command 3. Switch to a TTY 4. Login to TTY and observe htop or iotop Expected result: I can see the operation happen and after a while it completes Actual result: Keyboard drops out some time during operation (TTY stops responding, caps lock light no longer responds to pressing caps lock, computer appears effectively dead with last screen image frozen) When I run the "cp" operation on the TTY to start with, no matter if the X session is running in parallel or not, it works as expected with no trouble. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-generic 4.10.0.19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jonas 2297 F...m pulseaudio /dev/snd/controlC0: jonas 2297 F pulseaudio CurrentDesktop: GNOME Date: Thu Apr 13 13:04:03 2017 InstallationDate: Installed on 2017-04-08 (4 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 003: ID 13d3:5248 IMC Networks Bus 001 Device 005: ID 056a:5047 Wacom Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FDCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/fedora-root ro rootdelay=5 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-12 (1 days ago) dmi.bios.date: 11/16/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N1GET35W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1GET35W(1.12):bd11/16/2015:svnLENOVO:pn20FDCTO1WW:pvrThinkPadYoga260:rvnLENOVO:rn20FDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FDCTO1WW dmi.product.version: ThinkPad Yoga 260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682402/+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 1682402] Re: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682402 Title: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine Status in linux package in Ubuntu: Confirmed Bug description: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine. I am filing this as a kernel bug because the following steps will still hang the system: 1. Open up gnome-terminal 2. Start copying a really large file between two different EXT4 partitions on my local SSD with a "cp" command 3. Switch to a TTY 4. Login to TTY and observe htop or iotop Expected result: I can see the operation happen and after a while it completes Actual result: Keyboard drops out some time during operation (TTY stops responding, caps lock light no longer responds to pressing caps lock, computer appears effectively dead with last screen image frozen) When I run the "cp" operation on the TTY to start with, no matter if the X session is running in parallel or not, it works as expected with no trouble. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-generic 4.10.0.19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jonas 2297 F...m pulseaudio /dev/snd/controlC0: jonas 2297 F pulseaudio CurrentDesktop: GNOME Date: Thu Apr 13 13:04:03 2017 InstallationDate: Installed on 2017-04-08 (4 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 003: ID 13d3:5248 IMC Networks Bus 001 Device 005: ID 056a:5047 Wacom Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FDCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/fedora-root ro rootdelay=5 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-12 (1 days ago) dmi.bios.date: 11/16/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N1GET35W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1GET35W(1.12):bd11/16/2015:svnLENOVO:pn20FDCTO1WW:pvrThinkPadYoga260:rvnLENOVO:rn20FDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FDCTO1WW dmi.product.version: ThinkPad Yoga 260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682402/+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 1682402] Re: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine
I just tested the latest upstream 4.11-rc7 which works fine. I didn't test a previous version of Ubuntu, since I just switched to 17.04 from Fedora 25. ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682402 Title: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine Status in linux package in Ubuntu: Incomplete Bug description: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine. I am filing this as a kernel bug because the following steps will still hang the system: 1. Open up gnome-terminal 2. Start copying a really large file between two different EXT4 partitions on my local SSD with a "cp" command 3. Switch to a TTY 4. Login to TTY and observe htop or iotop Expected result: I can see the operation happen and after a while it completes Actual result: Keyboard drops out some time during operation (TTY stops responding, caps lock light no longer responds to pressing caps lock, computer appears effectively dead with last screen image frozen) When I run the "cp" operation on the TTY to start with, no matter if the X session is running in parallel or not, it works as expected with no trouble. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-generic 4.10.0.19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jonas 2297 F...m pulseaudio /dev/snd/controlC0: jonas 2297 F pulseaudio CurrentDesktop: GNOME Date: Thu Apr 13 13:04:03 2017 InstallationDate: Installed on 2017-04-08 (4 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 003: ID 13d3:5248 IMC Networks Bus 001 Device 005: ID 056a:5047 Wacom Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FDCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/fedora-root ro rootdelay=5 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-12 (1 days ago) dmi.bios.date: 11/16/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N1GET35W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1GET35W(1.12):bd11/16/2015:svnLENOVO:pn20FDCTO1WW:pvrThinkPadYoga260:rvnLENOVO:rn20FDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FDCTO1WW dmi.product.version: ThinkPad Yoga 260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682402/+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 1682402] Re: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine
Some additional info: - a short self-test of the SSD has already completed without errors - there was barely any memory usage while the bug occured, so it shouldn't be an out of memory issue - iotop shows always ~5 seconds of 99% I/O usage of the "cp" command at the top with nothing notable else going on, then ~8 seconds of ~50% usage of the "dmcrypt_write" command at the top with nothing else notable going on. This might be normal, I just mentioned it because the weird switching back and forth between those two looked a bit odd -- 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/1682402 Title: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine Status in linux package in Ubuntu: Confirmed Bug description: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine. I am filing this as a kernel bug because the following steps will still hang the system: 1. Open up gnome-terminal 2. Start copying a really large file between two different EXT4 partitions on my local SSD with a "cp" command 3. Switch to a TTY 4. Login to TTY and observe htop or iotop Expected result: I can see the operation happen and after a while it completes Actual result: Keyboard drops out some time during operation (TTY stops responding, caps lock light no longer responds to pressing caps lock, computer appears effectively dead with last screen image frozen) When I run the "cp" operation on the TTY to start with, no matter if the X session is running in parallel or not, it works as expected with no trouble. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-generic 4.10.0.19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jonas 2297 F...m pulseaudio /dev/snd/controlC0: jonas 2297 F pulseaudio CurrentDesktop: GNOME Date: Thu Apr 13 13:04:03 2017 InstallationDate: Installed on 2017-04-08 (4 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 003: ID 13d3:5248 IMC Networks Bus 001 Device 005: ID 056a:5047 Wacom Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FDCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/fedora-root ro rootdelay=5 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-12 (1 days ago) dmi.bios.date: 11/16/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N1GET35W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1GET35W(1.12):bd11/16/2015:svnLENOVO:pn20FDCTO1WW:pvrThinkPadYoga260:rvnLENOVO:rn20FDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FDCTO1WW dmi.product.version: ThinkPad Yoga 260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682402/+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 1682402] Re: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine
Just to rule out hardware issues: smartctl --all on the SSD shows no sector reallocations, barely any media wearout, no uncorrectable error count and barely any CRC errors (9). I am just running a long self-test and will report back whether it shows any errors. -- 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/1682402 Title: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine Status in linux package in Ubuntu: New Bug description: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine. I am filing this as a kernel bug because the following steps will still hang the system: 1. Open up gnome-terminal 2. Start copying a really large file between two different EXT4 partitions on my local SSD with a "cp" command 3. Switch to a TTY 4. Login to TTY and observe htop or iotop Expected result: I can see the operation happen and after a while it completes Actual result: Keyboard drops out some time during operation (TTY stops responding, caps lock light no longer responds to pressing caps lock, computer appears effectively dead with last screen image frozen) When I run the "cp" operation on the TTY to start with, no matter if the X session is running in parallel or not, it works as expected with no trouble. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-generic 4.10.0.19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jonas 2297 F...m pulseaudio /dev/snd/controlC0: jonas 2297 F pulseaudio CurrentDesktop: GNOME Date: Thu Apr 13 13:04:03 2017 InstallationDate: Installed on 2017-04-08 (4 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 003: ID 13d3:5248 IMC Networks Bus 001 Device 005: ID 056a:5047 Wacom Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FDCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/fedora-root ro rootdelay=5 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-12 (1 days ago) dmi.bios.date: 11/16/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N1GET35W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1GET35W(1.12):bd11/16/2015:svnLENOVO:pn20FDCTO1WW:pvrThinkPadYoga260:rvnLENOVO:rn20FDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FDCTO1WW dmi.product.version: ThinkPad Yoga 260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682402/+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 1682402] [NEW] Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine
Public bug reported: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine. I am filing this as a kernel bug because the following steps will still hang the system: 1. Open up gnome-terminal 2. Start copying a really large file between two different EXT4 partitions on my local SSD with a "cp" command 3. Switch to a TTY 4. Login to TTY and observe htop or iotop Expected result: I can see the operation happen and after a while it completes Actual result: Keyboard drops out some time during operation (TTY stops responding, caps lock light no longer responds to pressing caps lock, computer appears effectively dead with last screen image frozen) When I run the "cp" operation on the TTY to start with, no matter if the X session is running in parallel or not, it works as expected with no trouble. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-generic 4.10.0.19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jonas 2297 F...m pulseaudio /dev/snd/controlC0: jonas 2297 F pulseaudio CurrentDesktop: GNOME Date: Thu Apr 13 13:04:03 2017 InstallationDate: Installed on 2017-04-08 (4 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 003: ID 13d3:5248 IMC Networks Bus 001 Device 005: ID 056a:5047 Wacom Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FDCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/fedora-root ro rootdelay=5 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-12 (1 days ago) dmi.bios.date: 11/16/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N1GET35W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1GET35W(1.12):bd11/16/2015:svnLENOVO:pn20FDCTO1WW:pvrThinkPadYoga260:rvnLENOVO:rn20FDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FDCTO1WW dmi.product.version: ThinkPad Yoga 260 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1682402 Title: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine Status in linux package in Ubuntu: New Bug description: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine. I am filing this as a kernel bug because the following steps will still hang the system: 1. Open up gnome-terminal 2. Start copying a really large file between two different EXT4 partitions on my local SSD with a "cp" command 3. Switch to a TTY 4. Login to TTY and observe htop or iotop Expected result: I can see the operation happen and after a while it completes Actual result: Keyboard drops out some time during operation (TTY stops responding, caps lock light no longer responds to pressing caps lock, computer appears effectively dead with last screen image frozen) When I run the "cp" operation on the TTY to start with, no matter if the X session is running in parallel or not, it works as expected with no trouble. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-generic 4.10.0.19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jonas 2297 F...m pulseaudio /dev/snd/controlC0: jonas 2297 F pulseaudio CurrentDesktop: GNOME Date: Thu Apr 13 13:04:03 2017 InstallationDate: Installed on 2017-04-08 (4 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 003: ID 13d3:5248 IMC Networks Bus 001 Device 005: ID 056a:5047 Wacom Co., Ltd Bus
[Kernel-packages] [Bug 1643533] Re: Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely)
I got the impression from my virtual server hoster (which runs the hypervisor) that other customers don't have this issue. I was also inquiried about my use of BTRFS as a filesystem, and I also use Docker very heavily which makes heavy use of special BTRFS, DeviceMapper and Cgroup features, which might be something not every other customer does. I am just adding this information in case it is helpful for tracking down the cause of this crash. -- 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/1643533 Title: Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: With Ubuntu 16.04, I get frequent kernel panic crashes in my Linux KVM guest. After notifying the hosting company the machine was migrated to a different physical host which didn't fix the problem. A complete reinstall of Ubuntu 16.04 also didn't fix anything. Therefore, I suspect some sort of bug in the kernel and not a hardware fault or a corrupted install. /proc/version_signature: Ubuntu 4.4.0-47.68-generic 4.4.24 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 21 12:51 seq crw-rw 1 root audio 116, 33 Nov 21 12:51 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' Date: Mon Nov 21 12:57:11 2016 HibernationDevice: RESUME=UUID=704a373a-9754-4c59-bff2-001601f1c0bf IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hetzner vServer PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=UUID=fc92f1ac-ee98-4991-8a92-93451bd36d56 ro nomodeset elevator=noop net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.8.2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.6 dmi.modalias: dmi:bvnSeaBIOS:bvr1.8.2:bd04/01/2014:svnHetzner:pnvServer:pvr2:cvnQEMU:ct1:cvrpc-i440fx-2.6: dmi.product.name: vServer dmi.product.version: 2 dmi.sys.vendor: Hetzner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643533/+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 1643533] Re: Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely)
I am now very confident that this bug is NOT present in 4.9-rc7, therefore marking kernel-fixed-upstream. ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1643533 Title: Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: With Ubuntu 16.04, I get frequent kernel panic crashes in my Linux KVM guest. After notifying the hosting company the machine was migrated to a different physical host which didn't fix the problem. A complete reinstall of Ubuntu 16.04 also didn't fix anything. Therefore, I suspect some sort of bug in the kernel and not a hardware fault or a corrupted install. /proc/version_signature: Ubuntu 4.4.0-47.68-generic 4.4.24 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 21 12:51 seq crw-rw 1 root audio 116, 33 Nov 21 12:51 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' Date: Mon Nov 21 12:57:11 2016 HibernationDevice: RESUME=UUID=704a373a-9754-4c59-bff2-001601f1c0bf IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hetzner vServer PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=UUID=fc92f1ac-ee98-4991-8a92-93451bd36d56 ro nomodeset elevator=noop net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.8.2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.6 dmi.modalias: dmi:bvnSeaBIOS:bvr1.8.2:bd04/01/2014:svnHetzner:pnvServer:pvr2:cvnQEMU:ct1:cvrpc-i440fx-2.6: dmi.product.name: vServer dmi.product.version: 2 dmi.sys.vendor: Hetzner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643533/+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 1643533] Re: Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely)
It appears as if the issue is NOT present in mainline 4.9-rc7. I will wait a few more days to be sure before marking this 'kernel-fixed- upstream', since the bug always appeared in a varying interval of 2-5 days, just to get a higher level of confidence. -- 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/1643533 Title: Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely) Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: With Ubuntu 16.04, I get frequent kernel panic crashes in my Linux KVM guest. After notifying the hosting company the machine was migrated to a different physical host which didn't fix the problem. A complete reinstall of Ubuntu 16.04 also didn't fix anything. Therefore, I suspect some sort of bug in the kernel and not a hardware fault or a corrupted install. /proc/version_signature: Ubuntu 4.4.0-47.68-generic 4.4.24 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 21 12:51 seq crw-rw 1 root audio 116, 33 Nov 21 12:51 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' Date: Mon Nov 21 12:57:11 2016 HibernationDevice: RESUME=UUID=704a373a-9754-4c59-bff2-001601f1c0bf IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hetzner vServer PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=UUID=fc92f1ac-ee98-4991-8a92-93451bd36d56 ro nomodeset elevator=noop net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.8.2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.6 dmi.modalias: dmi:bvnSeaBIOS:bvr1.8.2:bd04/01/2014:svnHetzner:pnvServer:pvr2:cvnQEMU:ct1:cvrpc-i440fx-2.6: dmi.product.name: vServer dmi.product.version: 2 dmi.sys.vendor: Hetzner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643533/+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 1643533] Re: Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely)
For what it's worth, I am now running 4.9.0-040900rc7-generic since a few minutes ago. The bug always hit me after 2-5 days but always under a week, so I can tell you in at the earliest a week that the bug is or is not in upstream with high certainty. (so around 9th of December) -- 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/1643533 Title: Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely) Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: With Ubuntu 16.04, I get frequent kernel panic crashes in my Linux KVM guest. After notifying the hosting company the machine was migrated to a different physical host which didn't fix the problem. A complete reinstall of Ubuntu 16.04 also didn't fix anything. Therefore, I suspect some sort of bug in the kernel and not a hardware fault or a corrupted install. /proc/version_signature: Ubuntu 4.4.0-47.68-generic 4.4.24 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 21 12:51 seq crw-rw 1 root audio 116, 33 Nov 21 12:51 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' Date: Mon Nov 21 12:57:11 2016 HibernationDevice: RESUME=UUID=704a373a-9754-4c59-bff2-001601f1c0bf IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hetzner vServer PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=UUID=fc92f1ac-ee98-4991-8a92-93451bd36d56 ro nomodeset elevator=noop net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.8.2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.6 dmi.modalias: dmi:bvnSeaBIOS:bvr1.8.2:bd04/01/2014:svnHetzner:pnvServer:pvr2:cvnQEMU:ct1:cvrpc-i440fx-2.6: dmi.product.name: vServer dmi.product.version: 2 dmi.sys.vendor: Hetzner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643533/+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 1643533] Re: Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely)
The kernel panic itself locks up the system instantly and therefore no logging to disk happens of that error. Therefore, see the attached screenshot of the qemu screen after the crash. ** Attachment added: "Screenshot of VM in Qemu after crashing" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643533/+attachment/4780974/+files/qemu-crash.png -- 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/1643533 Title: Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely) Status in linux package in Ubuntu: New Bug description: With Ubuntu 16.04, I get frequent kernel panic crashes in my Linux KVM guest. After notifying the hosting company the machine was migrated to a different physical host which didn't fix the problem. A complete reinstall of Ubuntu 16.04 also didn't fix anything. Therefore, I suspect some sort of bug in the kernel and not a hardware fault or a corrupted install. /proc/version_signature: Ubuntu 4.4.0-47.68-generic 4.4.24 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 21 12:51 seq crw-rw 1 root audio 116, 33 Nov 21 12:51 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' Date: Mon Nov 21 12:57:11 2016 HibernationDevice: RESUME=UUID=704a373a-9754-4c59-bff2-001601f1c0bf IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hetzner vServer PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=UUID=fc92f1ac-ee98-4991-8a92-93451bd36d56 ro nomodeset elevator=noop net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.8.2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.6 dmi.modalias: dmi:bvnSeaBIOS:bvr1.8.2:bd04/01/2014:svnHetzner:pnvServer:pvr2:cvnQEMU:ct1:cvrpc-i440fx-2.6: dmi.product.name: vServer dmi.product.version: 2 dmi.sys.vendor: Hetzner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643533/+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 1643533] [NEW] Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely)
Public bug reported: With Ubuntu 16.04, I get frequent kernel panic crashes in my Linux KVM guest. After notifying the hosting company the machine was migrated to a different physical host which didn't fix the problem. A complete reinstall of Ubuntu 16.04 also didn't fix anything. Therefore, I suspect some sort of bug in the kernel and not a hardware fault or a corrupted install. /proc/version_signature: Ubuntu 4.4.0-47.68-generic 4.4.24 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 21 12:51 seq crw-rw 1 root audio 116, 33 Nov 21 12:51 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' Date: Mon Nov 21 12:57:11 2016 HibernationDevice: RESUME=UUID=704a373a-9754-4c59-bff2-001601f1c0bf IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hetzner vServer PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=UUID=fc92f1ac-ee98-4991-8a92-93451bd36d56 ro nomodeset elevator=noop net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.8.2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.6 dmi.modalias: dmi:bvnSeaBIOS:bvr1.8.2:bd04/01/2014:svnHetzner:pnvServer:pvr2:cvnQEMU:ct1:cvrpc-i440fx-2.6: dmi.product.name: vServer dmi.product.version: 2 dmi.sys.vendor: Hetzner ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1643533/+attachment/4780963/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1643533 Title: Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely) Status in linux package in Ubuntu: New Bug description: With Ubuntu 16.04, I get frequent kernel panic crashes in my Linux KVM guest. After notifying the hosting company the machine was migrated to a different physical host which didn't fix the problem. A complete reinstall of Ubuntu 16.04 also didn't fix anything. Therefore, I suspect some sort of bug in the kernel and not a hardware fault or a corrupted install. /proc/version_signature: Ubuntu 4.4.0-47.68-generic 4.4.24 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 21 12:51 seq crw-rw 1 root audio 116, 33 Nov 21 12:51 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' Date: Mon Nov 21 12:57:11 2016 HibernationDevice: RESUME=UUID=704a373a-9754-4c59-bff2-001601f1c0bf IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hetzner vServer PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=UUID=fc92f1ac-ee98-4991-8a92-93451bd36d56 ro nomodeset elevator=noop net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.8.2 dmi.chassis.type: 1
[Kernel-packages] [Bug 1469145] Re: Bluetooth device sometimes instantly turns off again after turning it on
It doesn't happen *every* time when waking up from suspend, just sometimes. I can try switching to the mainline kernel and run it for a while, and hope it happens again. However, I had exactly the same problem on Fedora 21 through multiple kernel upgrades. -- 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/1469145 Title: Bluetooth device sometimes instantly turns off again after turning it on Status in linux package in Ubuntu: Incomplete Bug description: Sometimes when turning on bluetooth in the gnome bluetooth panel, it is shown as On for like a second and reverts back to Off. This is what I see in dmesg: [1199362.625284] usb 1-1.4: Product: Broadcom Bluetooth Device [1199362.625286] usb 1-1.4: Manufacturer: Broadcom Corp [1199362.625287] usb 1-1.4: SerialNumber: EC55F9EFBB65 [1199362.839031] usb 1-1.4: USB disconnect, device number 10 [1199371.232776] usb 1-1.4: new full-speed USB device number 11 using ehci-pci [1199371.330552] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=217f [1199371.330556] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1199371.330559] usb 1-1.4: Product: Broadcom Bluetooth Device [1199371.330560] usb 1-1.4: Manufacturer: Broadcom Corp [1199371.330562] usb 1-1.4: SerialNumber: EC55F9EFBB65 [1199371.544424] usb 1-1.4: USB disconnect, device number 11 This situation is usually triggered after waking up from suspend, and then permanent up to the next reboot. I would assume the USB disconnect is the problem. I don't have bluetooth disabled in the BIOS settings. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-generic 3.19.0.21.20 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jonas 1889 F...m pulseaudio /dev/snd/controlC0: jonas 1889 F pulseaudio CurrentDesktop: GNOME Date: Fri Jun 26 14:18:56 2015 MachineType: LENOVO 429137G ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=UUID=ee26293f-6471-4bb2-abe2-a8faf67adf96 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 429137G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn429137G:pvrThinkPadX220:rvnLENOVO:rn429137G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429137G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469145/+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 1469145] Re: Bluetooth device sometimes instantly turns off again after turning it on
(I don't have the bluetooth headphones long enough to know if this ever not happened) -- 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/1469145 Title: Bluetooth device sometimes instantly turns off again after turning it on Status in linux package in Ubuntu: Incomplete Bug description: Sometimes when turning on bluetooth in the gnome bluetooth panel, it is shown as On for like a second and reverts back to Off. This is what I see in dmesg: [1199362.625284] usb 1-1.4: Product: Broadcom Bluetooth Device [1199362.625286] usb 1-1.4: Manufacturer: Broadcom Corp [1199362.625287] usb 1-1.4: SerialNumber: EC55F9EFBB65 [1199362.839031] usb 1-1.4: USB disconnect, device number 10 [1199371.232776] usb 1-1.4: new full-speed USB device number 11 using ehci-pci [1199371.330552] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=217f [1199371.330556] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1199371.330559] usb 1-1.4: Product: Broadcom Bluetooth Device [1199371.330560] usb 1-1.4: Manufacturer: Broadcom Corp [1199371.330562] usb 1-1.4: SerialNumber: EC55F9EFBB65 [1199371.544424] usb 1-1.4: USB disconnect, device number 11 This situation is usually triggered after waking up from suspend, and then permanent up to the next reboot. I would assume the USB disconnect is the problem. I don't have bluetooth disabled in the BIOS settings. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-generic 3.19.0.21.20 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jonas 1889 F...m pulseaudio /dev/snd/controlC0: jonas 1889 F pulseaudio CurrentDesktop: GNOME Date: Fri Jun 26 14:18:56 2015 MachineType: LENOVO 429137G ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=UUID=ee26293f-6471-4bb2-abe2-a8faf67adf96 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 429137G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn429137G:pvrThinkPadX220:rvnLENOVO:rn429137G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429137G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469145/+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 1469145] Re: Bluetooth device sometimes instantly turns off again after turning it on
** Summary changed: - Bluetooth device sometimes instantly disconnects after turning it on + Bluetooth device sometimes instantly turns off again after turning it on -- 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/1469145 Title: Bluetooth device sometimes instantly turns off again after turning it on Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when turning on bluetooth in the gnome bluetooth panel, it is shown as On for like a second and reverts back to Off. This is what I see in dmesg: [1199362.625284] usb 1-1.4: Product: Broadcom Bluetooth Device [1199362.625286] usb 1-1.4: Manufacturer: Broadcom Corp [1199362.625287] usb 1-1.4: SerialNumber: EC55F9EFBB65 [1199362.839031] usb 1-1.4: USB disconnect, device number 10 [1199371.232776] usb 1-1.4: new full-speed USB device number 11 using ehci-pci [1199371.330552] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=217f [1199371.330556] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1199371.330559] usb 1-1.4: Product: Broadcom Bluetooth Device [1199371.330560] usb 1-1.4: Manufacturer: Broadcom Corp [1199371.330562] usb 1-1.4: SerialNumber: EC55F9EFBB65 [1199371.544424] usb 1-1.4: USB disconnect, device number 11 This situation is usually triggered after waking up from suspend, and then permanent up to the next reboot. I would assume the USB disconnect is the problem. I don't have bluetooth disabled in the BIOS settings. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-generic 3.19.0.21.20 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jonas 1889 F...m pulseaudio /dev/snd/controlC0: jonas 1889 F pulseaudio CurrentDesktop: GNOME Date: Fri Jun 26 14:18:56 2015 MachineType: LENOVO 429137G ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=UUID=ee26293f-6471-4bb2-abe2-a8faf67adf96 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 429137G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn429137G:pvrThinkPadX220:rvnLENOVO:rn429137G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429137G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469145/+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 1469145] [NEW] Bluetooth device sometimes instantly turns off again after turning it on
Public bug reported: Sometimes when turning on bluetooth in the gnome bluetooth panel, it is shown as On for like a second and reverts back to Off. This is what I see in dmesg: [1199362.625284] usb 1-1.4: Product: Broadcom Bluetooth Device [1199362.625286] usb 1-1.4: Manufacturer: Broadcom Corp [1199362.625287] usb 1-1.4: SerialNumber: EC55F9EFBB65 [1199362.839031] usb 1-1.4: USB disconnect, device number 10 [1199371.232776] usb 1-1.4: new full-speed USB device number 11 using ehci-pci [1199371.330552] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=217f [1199371.330556] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1199371.330559] usb 1-1.4: Product: Broadcom Bluetooth Device [1199371.330560] usb 1-1.4: Manufacturer: Broadcom Corp [1199371.330562] usb 1-1.4: SerialNumber: EC55F9EFBB65 [1199371.544424] usb 1-1.4: USB disconnect, device number 11 This situation is usually triggered after waking up from suspend, and then permanent up to the next reboot. I would assume the USB disconnect is the problem. I don't have bluetooth disabled in the BIOS settings. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-generic 3.19.0.21.20 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jonas 1889 F...m pulseaudio /dev/snd/controlC0: jonas 1889 F pulseaudio CurrentDesktop: GNOME Date: Fri Jun 26 14:18:56 2015 MachineType: LENOVO 429137G ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=UUID=ee26293f-6471-4bb2-abe2-a8faf67adf96 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 429137G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn429137G:pvrThinkPadX220:rvnLENOVO:rn429137G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429137G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug vivid -- 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/1469145 Title: Bluetooth device sometimes instantly turns off again after turning it on Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when turning on bluetooth in the gnome bluetooth panel, it is shown as On for like a second and reverts back to Off. This is what I see in dmesg: [1199362.625284] usb 1-1.4: Product: Broadcom Bluetooth Device [1199362.625286] usb 1-1.4: Manufacturer: Broadcom Corp [1199362.625287] usb 1-1.4: SerialNumber: EC55F9EFBB65 [1199362.839031] usb 1-1.4: USB disconnect, device number 10 [1199371.232776] usb 1-1.4: new full-speed USB device number 11 using ehci-pci [1199371.330552] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=217f [1199371.330556] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1199371.330559] usb 1-1.4: Product: Broadcom Bluetooth Device [1199371.330560] usb 1-1.4: Manufacturer: Broadcom Corp [1199371.330562] usb 1-1.4: SerialNumber: EC55F9EFBB65 [1199371.544424] usb 1-1.4: USB disconnect, device number 11 This situation is usually triggered after waking up from suspend, and then permanent up to the next reboot. I would assume the USB disconnect is the problem. I don't have bluetooth disabled in the BIOS settings. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-generic 3.19.0.21.20 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jonas 1889 F...m pulseaudio /dev/snd/controlC0: jonas 1889 F pulseaudio CurrentDesktop: GNOME Date: Fri Jun 26 14:18:56 2015 MachineType: LENOVO 429137G ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic
