[Kernel-packages] [Bug 1560473] Re: Fan doesn't work
Newer kernel definitely change many things (even cpu temperature decrees with same load - that looks strange). But fan issue still present. No matter how high increase the temperature fan remain silent. ** Tags added: kernel-bug-exists-upstream ** 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/1560473 Title: Fan doesn't work Status in linux package in Ubuntu: Confirmed Bug description: There is no fan support for this hardware. Fan speed changing only on reboot and stay the same until reboot. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-34-generic 4.2.0-34.39 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob3618 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 22 18:25:27 2016 HibernationDevice: RESUME=UUID=0d193a72-b3ef-44a7-92c8-ed9df2de9807 InstallationDate: Installed on 2015-12-01 (111 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=82b73f79-8d4f-453e-b9ad-fc07955aaa21 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-34-generic N/A linux-backports-modules-4.2.0-34-generic N/A linux-firmware1.156 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/07/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.13 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.13 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.13 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.13:bd12/07/2015:svnAcer:pnAspireES1-331:pvrV1.13:rvnAcer:rnAspireES1-331:rvrV1.13:cvnAcer:ct10:cvrV1.13: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.13 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1560473/+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 1557298] Re: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly
** Description changed: - Failed to pair low energy(bluetooth smart, 4.0 or 4.1) devices - correctly. + Failed to pair low energy(bluetooth smart, 4.0) keyboard correctly. - 1. bluetooth smart mouse is being listed as "all type" in bluetooth- - wizard, however it is able to be paired and use, even repair(i'm - mentioning this because in some circumstance low energy device can be - only paired once, bug #1515179) - - 2. bluetooth smart keyboard is unable to use after bluetooth-wizard says + Bluetooth smart keyboard is unable to use after bluetooth-wizard says "OK". Also the passcode input is also not acting interactively like when - pairing with bluetooth 3.0 keyboard. + pairing with bluetooth 3.0(LegacyPairing) keyboard. Above scenario also being verified with bluetoothctl and blueman. + + Step to reproduce: + + 1. open Bluetooth Settings + 2. click on Add New Device button + 3. select the bluetooth le keyboard + 4. input the passcode display on GUI + + Expected result: + + After bluetooth-wizard telling user is okay the keyboard should work + + + Actual result: + + Pairing mode stop on keyboard, but still not work. + - More details about versions: Environment: xenial daily (20160307) bluez 5.37-0ubuntu5 gnome-bluetooth 3.18.2-1ubuntu2 blueman 2.0.3-1ubuntu1 bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1) Tested devices: Designer Mouse, bluetooth smart (pairable, work, re-pair work) Designer Keyboard, bluetooth smart (paired, not working) BT3.0 keyboard, bluetooth classic (pair and work) BT3.0 mouse, bluetooth classic (pair and work) - In control environment with the same hardware system and devices: trusty 14.04.1 + dist-upgrade (stay with 3.13 kernel) bluez5 5.35 (ppa: https://launchpad.net/~vidplace7/+archive/ubuntu/bluez5) It works with all above devices but can only be pairing through - bluetoothctl, since the older bluetooth-wizard does not understand bluez - 5.x. Everything seems works fine, although there are a lot more error + bluetoothctl manually, since the older bluetooth-wizard does not + understand bluez 5.x. + + Everything seems works fine, although there are a lot more error messages, but since this bug is more about xenial, please let me know if we need more information about this, I'm able to reproduce this trusty scenario in anytime. - Additional note: A little clarification, since I'm not sure how far the Bluetooth SIG is going to use Bluetooth Smart(Low Energy, or even Smart-Ready) to cover the versioning, I decided to just use what ever I saw on the product box. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 15 11:40:12 2016 InstallationDate: Installed on 2016-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed root=UUID=1079eca4-4293-4e51-ba0e-84f7d681cb2c ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.sys.vendor: Dell Inc. hciconfig: - hci0:Type: BR/EDR Bus: USB - BD Address: 00:71:CC:39:BD:22 ACL MTU: 1022:8 SCO MTU: 183:5 - UP RUNNING PSCAN ISCAN - RX bytes:862538 acl:39687 sco:0 events:2668 errors:0 - TX bytes:26235 acl:904 sco:0 commands:1021 errors:0 + hci0:Type: BR/EDR Bus: USB + BD Address: 00:71:CC:39:BD:22 ACL MTU: 1022:8 SCO MTU: 183:5 + UP RUNNING PSCAN ISCAN + RX bytes:862538 acl:39687 sco:0 events:2668 errors:0 + TX bytes:26235 acl:904 sco:0 commands:1021 errors:0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1557298 Title: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly Status in Unity Control Center: New Status in bluez package in Ubuntu: New Bug description: Failed to pair low energy(bluetooth smart, 4.0) keyboard correctly. Bluetooth smart keyboard is unable to use after bluetooth-wizard says "OK". Also the passcode input is also not acting interactively like when pairing with bluetooth 3.0(LegacyPairing) keyboard. Above scenario also being verified with bluetoothctl an
[Kernel-packages] [Bug 1561902] [NEW] Total system freeze after 3.16.0-38.52
Public bug reported: This should have been reported already last year, but here it goes. Problem: My laptop is a ASUS N71JA and works perfectly in Windows. Everything was fine with Xubuntu 14.04 through kernels 3.13 and 3.16 up to 3.16.0-38.52. Desktop freezes, like totally dies with hard power reset being the only option, every now and then from this kernel and onwards. This affects 3.19 and 4.2.0 kernels released after this date as well. No Magic SysRq possible and I can't see anything fancy in syslog or kern.log. Desktop can die anytime between immediately after boot or after a few hours, but it happens completely randomly and is hard to debug. Workaround: 3.16.0-38.52 was released in May 2015 (https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1452882). 3.16.0-37.51 and 3.16.0-36.48 have NEVER frozen. The only non-upstream change that was made to 3.16.0-38.52 was "vesafb: Set mtrr:3 (write-combining) as default" (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434581). This is probably not implemented in the mainline kernel tree, right? I've been using mainline 3.16.7-ckt24-trusty without any problems now for over a month (http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.16.7-ckt24-trusty/) i.e. it seems like 1434581 is causing the problem. Can this be verified by some other method e.g. by disabling/reverting 1434581 in a "normal" non-mainline kernel? Solution: ? ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1561902 Title: Total system freeze after 3.16.0-38.52 Status in linux-lts-utopic package in Ubuntu: New Bug description: This should have been reported already last year, but here it goes. Problem: My laptop is a ASUS N71JA and works perfectly in Windows. Everything was fine with Xubuntu 14.04 through kernels 3.13 and 3.16 up to 3.16.0-38.52. Desktop freezes, like totally dies with hard power reset being the only option, every now and then from this kernel and onwards. This affects 3.19 and 4.2.0 kernels released after this date as well. No Magic SysRq possible and I can't see anything fancy in syslog or kern.log. Desktop can die anytime between immediately after boot or after a few hours, but it happens completely randomly and is hard to debug. Workaround: 3.16.0-38.52 was released in May 2015 (https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1452882). 3.16.0-37.51 and 3.16.0-36.48 have NEVER frozen. The only non-upstream change that was made to 3.16.0-38.52 was "vesafb: Set mtrr:3 (write-combining) as default" (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434581). This is probably not implemented in the mainline kernel tree, right? I've been using mainline 3.16.7-ckt24-trusty without any problems now for over a month (http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.16.7-ckt24-trusty/) i.e. it seems like 1434581 is causing the problem. Can this be verified by some other method e.g. by disabling/reverting 1434581 in a "normal" non-mainline kernel? Solution: ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1561902/+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 1561830] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1561830/+attachment/4610892/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1561830 Title: Hard disk writes fail in 16.04 daily on nForce 430 Status in linux package in Ubuntu: Incomplete Bug description: I have an old PC I use for testing new operating systems. It has previously had Ubuntu 15.10 installed and working. The motherboard is an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce 6150 GPU. I have installed an Nvidia GT220 card to use for more modern video support. When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop- amd64.iso file downloaded 24/03/2016 18:17), it starts to write to the hard disk (Samsung HD103UJ), and after a short time the install got lots of disk write errors in kern.log. After the errors, the disk was unable to be read either, with "fdisk -l /dev/sda" failing to read a sector, where it had worked before starting the install. Unplugging the SATA cable to the drive and plugging it in again made the drive work again (on /dev/sdc), but another attempt to install failed with the same write errors. I noticed that the log had swap write errors also, so I rebooted the install DVD again, and this time did a "swapoff -a" command before attempting to install, but got the same errors again. So I found my Ubuntu 15.10 install DVD and tried a new install from that, which worked just fine. On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that the DVD based system would run normally, then tried mounting the EXT4 system partition I had just installed using the 15.10 install DVD. That worked, so I tried dd commands to do test writes to that partition. The following commands worked: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k but when I did this command: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k after a while errors started appearing in kern.log, just as with the attempts to install 16.04. It appears that with sustained write activity, the errors will start and then the drive will become unusable until it is unplugged and plugged in again. I have attached the kern.log and syslog files from the 15.10 install that worked, and the 16.04 install attempt that failed. The first error message appears to be this: ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0 dhfis 0x1 dmafis 0x0 sdbfis 0x0 which leads me to suspect a problem with the handling of the SATA controller's interrupts. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2233 F pulseaudio /dev/snd/controlC1: ubuntu 2233 F pulseaudio CasperVersion: 1.368 DistroRelease: Ubuntu 16.04 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. enp2s9no wireless extensions. LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1401:bd08/07/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx:cvnChassisMa
[Kernel-packages] [Bug 1561830] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1561830/+attachment/4610891/+files/JournalErrors.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/1561830 Title: Hard disk writes fail in 16.04 daily on nForce 430 Status in linux package in Ubuntu: Incomplete Bug description: I have an old PC I use for testing new operating systems. It has previously had Ubuntu 15.10 installed and working. The motherboard is an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce 6150 GPU. I have installed an Nvidia GT220 card to use for more modern video support. When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop- amd64.iso file downloaded 24/03/2016 18:17), it starts to write to the hard disk (Samsung HD103UJ), and after a short time the install got lots of disk write errors in kern.log. After the errors, the disk was unable to be read either, with "fdisk -l /dev/sda" failing to read a sector, where it had worked before starting the install. Unplugging the SATA cable to the drive and plugging it in again made the drive work again (on /dev/sdc), but another attempt to install failed with the same write errors. I noticed that the log had swap write errors also, so I rebooted the install DVD again, and this time did a "swapoff -a" command before attempting to install, but got the same errors again. So I found my Ubuntu 15.10 install DVD and tried a new install from that, which worked just fine. On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that the DVD based system would run normally, then tried mounting the EXT4 system partition I had just installed using the 15.10 install DVD. That worked, so I tried dd commands to do test writes to that partition. The following commands worked: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k but when I did this command: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k after a while errors started appearing in kern.log, just as with the attempts to install 16.04. It appears that with sustained write activity, the errors will start and then the drive will become unusable until it is unplugged and plugged in again. I have attached the kern.log and syslog files from the 15.10 install that worked, and the 16.04 install attempt that failed. The first error message appears to be this: ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0 dhfis 0x1 dmafis 0x0 sdbfis 0x0 which leads me to suspect a problem with the handling of the SATA controller's interrupts. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2233 F pulseaudio /dev/snd/controlC1: ubuntu 2233 F pulseaudio CasperVersion: 1.368 DistroRelease: Ubuntu 16.04 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. enp2s9no wireless extensions. LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1401:bd08/07/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr
[Kernel-packages] [Bug 1561830] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1561830/+attachment/4610895/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1561830 Title: Hard disk writes fail in 16.04 daily on nForce 430 Status in linux package in Ubuntu: Incomplete Bug description: I have an old PC I use for testing new operating systems. It has previously had Ubuntu 15.10 installed and working. The motherboard is an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce 6150 GPU. I have installed an Nvidia GT220 card to use for more modern video support. When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop- amd64.iso file downloaded 24/03/2016 18:17), it starts to write to the hard disk (Samsung HD103UJ), and after a short time the install got lots of disk write errors in kern.log. After the errors, the disk was unable to be read either, with "fdisk -l /dev/sda" failing to read a sector, where it had worked before starting the install. Unplugging the SATA cable to the drive and plugging it in again made the drive work again (on /dev/sdc), but another attempt to install failed with the same write errors. I noticed that the log had swap write errors also, so I rebooted the install DVD again, and this time did a "swapoff -a" command before attempting to install, but got the same errors again. So I found my Ubuntu 15.10 install DVD and tried a new install from that, which worked just fine. On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that the DVD based system would run normally, then tried mounting the EXT4 system partition I had just installed using the 15.10 install DVD. That worked, so I tried dd commands to do test writes to that partition. The following commands worked: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k but when I did this command: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k after a while errors started appearing in kern.log, just as with the attempts to install 16.04. It appears that with sustained write activity, the errors will start and then the drive will become unusable until it is unplugged and plugged in again. I have attached the kern.log and syslog files from the 15.10 install that worked, and the 16.04 install attempt that failed. The first error message appears to be this: ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0 dhfis 0x1 dmafis 0x0 sdbfis 0x0 which leads me to suspect a problem with the handling of the SATA controller's interrupts. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2233 F pulseaudio /dev/snd/controlC1: ubuntu 2233 F pulseaudio CasperVersion: 1.368 DistroRelease: Ubuntu 16.04 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. enp2s9no wireless extensions. LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1401:bd08/07/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx
[Kernel-packages] [Bug 1561830] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1561830/+attachment/4610890/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1561830 Title: Hard disk writes fail in 16.04 daily on nForce 430 Status in linux package in Ubuntu: Incomplete Bug description: I have an old PC I use for testing new operating systems. It has previously had Ubuntu 15.10 installed and working. The motherboard is an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce 6150 GPU. I have installed an Nvidia GT220 card to use for more modern video support. When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop- amd64.iso file downloaded 24/03/2016 18:17), it starts to write to the hard disk (Samsung HD103UJ), and after a short time the install got lots of disk write errors in kern.log. After the errors, the disk was unable to be read either, with "fdisk -l /dev/sda" failing to read a sector, where it had worked before starting the install. Unplugging the SATA cable to the drive and plugging it in again made the drive work again (on /dev/sdc), but another attempt to install failed with the same write errors. I noticed that the log had swap write errors also, so I rebooted the install DVD again, and this time did a "swapoff -a" command before attempting to install, but got the same errors again. So I found my Ubuntu 15.10 install DVD and tried a new install from that, which worked just fine. On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that the DVD based system would run normally, then tried mounting the EXT4 system partition I had just installed using the 15.10 install DVD. That worked, so I tried dd commands to do test writes to that partition. The following commands worked: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k but when I did this command: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k after a while errors started appearing in kern.log, just as with the attempts to install 16.04. It appears that with sustained write activity, the errors will start and then the drive will become unusable until it is unplugged and plugged in again. I have attached the kern.log and syslog files from the 15.10 install that worked, and the 16.04 install attempt that failed. The first error message appears to be this: ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0 dhfis 0x1 dmafis 0x0 sdbfis 0x0 which leads me to suspect a problem with the handling of the SATA controller's interrupts. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2233 F pulseaudio /dev/snd/controlC1: ubuntu 2233 F pulseaudio CasperVersion: 1.368 DistroRelease: Ubuntu 16.04 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. enp2s9no wireless extensions. LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1401:bd08/07/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.
[Kernel-packages] [Bug 1561830] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1561830/+attachment/4610897/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1561830 Title: Hard disk writes fail in 16.04 daily on nForce 430 Status in linux package in Ubuntu: Incomplete Bug description: I have an old PC I use for testing new operating systems. It has previously had Ubuntu 15.10 installed and working. The motherboard is an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce 6150 GPU. I have installed an Nvidia GT220 card to use for more modern video support. When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop- amd64.iso file downloaded 24/03/2016 18:17), it starts to write to the hard disk (Samsung HD103UJ), and after a short time the install got lots of disk write errors in kern.log. After the errors, the disk was unable to be read either, with "fdisk -l /dev/sda" failing to read a sector, where it had worked before starting the install. Unplugging the SATA cable to the drive and plugging it in again made the drive work again (on /dev/sdc), but another attempt to install failed with the same write errors. I noticed that the log had swap write errors also, so I rebooted the install DVD again, and this time did a "swapoff -a" command before attempting to install, but got the same errors again. So I found my Ubuntu 15.10 install DVD and tried a new install from that, which worked just fine. On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that the DVD based system would run normally, then tried mounting the EXT4 system partition I had just installed using the 15.10 install DVD. That worked, so I tried dd commands to do test writes to that partition. The following commands worked: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k but when I did this command: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k after a while errors started appearing in kern.log, just as with the attempts to install 16.04. It appears that with sustained write activity, the errors will start and then the drive will become unusable until it is unplugged and plugged in again. I have attached the kern.log and syslog files from the 15.10 install that worked, and the 16.04 install attempt that failed. The first error message appears to be this: ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0 dhfis 0x1 dmafis 0x0 sdbfis 0x0 which leads me to suspect a problem with the handling of the SATA controller's interrupts. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2233 F pulseaudio /dev/snd/controlC1: ubuntu 2233 F pulseaudio CasperVersion: 1.368 DistroRelease: Ubuntu 16.04 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. enp2s9no wireless extensions. LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1401:bd08/07/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx:c
[Kernel-packages] [Bug 1559870] Re: mmc_select_hs400 failed, error -74
I tested Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) and there is no problem now. 3efcd738cff03d2d579e08f55117111d *ubuntu-16.04-beta2-desktop-amd64.iso ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- 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/1559870 Title: mmc_select_hs400 failed, error -74 Status in linux package in Ubuntu: Fix Released Bug description: I used "Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)" from http://cdimage.ubuntu.com/daily-live/current/. But it can not find the built-in eMMC storage and it shows the following messages. [ 12.355182] sdhci-pci :00:1e.4: No vmmc regulator found [ 12.355185] sdhci-pci :00:1e.4: No vqmmc regulator found [ 12.358331] mmc0: SDHCI controller on PCI [:00:1e.4] using ADMA 64-bit [ 12.359549] sdhci-pci :00:1e.6: No vmmc regulator found [ 12.359552] sdhci-pci :00:1e.6: No vqmmc regulator found [ 12.362713] mmc1: SDHCI controller on PCI [:00:1e.6] using ADMA 64-bit [ 12.472768] mmc0: MAN_BKOPS_EN bit is not set [ 12.489132] mmc0: mmc_select_hs400 failed, error -74 [ 12.489134] mmc0: error -74 whilst initialising MMC card [ 12.601333] mmc0: MAN_BKOPS_EN bit is not set [ 12.617263] mmc0: mmc_select_hs400 failed, error -74 [ 12.617280] mmc0: error -74 whilst initialising MMC card [ 12.745957] mmc0: MAN_BKOPS_EN bit is not set [ 12.764502] mmc0: mmc_select_hs400 failed, error -74 [ 12.764519] mmc0: error -74 whilst initialising MMC card [ 12.923969] mmc0: MAN_BKOPS_EN bit is not set [ 12.948561] mmc0: mmc_select_hs400 failed, error -74 [ 12.948580] mmc0: error -74 whilst initialising MMC card ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CasperVersion: 1.367 CurrentDesktop: Unity Date: Mon Mar 21 06:20:39 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.board.name: STCK2MV64CC dmi.product.name: STCK2MV64CC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559870/+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 1561830] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1561830/+attachment/4610889/+files/CRDA.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/1561830 Title: Hard disk writes fail in 16.04 daily on nForce 430 Status in linux package in Ubuntu: Incomplete Bug description: I have an old PC I use for testing new operating systems. It has previously had Ubuntu 15.10 installed and working. The motherboard is an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce 6150 GPU. I have installed an Nvidia GT220 card to use for more modern video support. When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop- amd64.iso file downloaded 24/03/2016 18:17), it starts to write to the hard disk (Samsung HD103UJ), and after a short time the install got lots of disk write errors in kern.log. After the errors, the disk was unable to be read either, with "fdisk -l /dev/sda" failing to read a sector, where it had worked before starting the install. Unplugging the SATA cable to the drive and plugging it in again made the drive work again (on /dev/sdc), but another attempt to install failed with the same write errors. I noticed that the log had swap write errors also, so I rebooted the install DVD again, and this time did a "swapoff -a" command before attempting to install, but got the same errors again. So I found my Ubuntu 15.10 install DVD and tried a new install from that, which worked just fine. On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that the DVD based system would run normally, then tried mounting the EXT4 system partition I had just installed using the 15.10 install DVD. That worked, so I tried dd commands to do test writes to that partition. The following commands worked: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k but when I did this command: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k after a while errors started appearing in kern.log, just as with the attempts to install 16.04. It appears that with sustained write activity, the errors will start and then the drive will become unusable until it is unplugged and plugged in again. I have attached the kern.log and syslog files from the 15.10 install that worked, and the 16.04 install attempt that failed. The first error message appears to be this: ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0 dhfis 0x1 dmafis 0x0 sdbfis 0x0 which leads me to suspect a problem with the handling of the SATA controller's interrupts. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2233 F pulseaudio /dev/snd/controlC1: ubuntu 2233 F pulseaudio CasperVersion: 1.368 DistroRelease: Ubuntu 16.04 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. enp2s9no wireless extensions. LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1401:bd08/07/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx:cvnChassisManu
[Kernel-packages] [Bug 1561830] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1561830/+attachment/4610894/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1561830 Title: Hard disk writes fail in 16.04 daily on nForce 430 Status in linux package in Ubuntu: Incomplete Bug description: I have an old PC I use for testing new operating systems. It has previously had Ubuntu 15.10 installed and working. The motherboard is an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce 6150 GPU. I have installed an Nvidia GT220 card to use for more modern video support. When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop- amd64.iso file downloaded 24/03/2016 18:17), it starts to write to the hard disk (Samsung HD103UJ), and after a short time the install got lots of disk write errors in kern.log. After the errors, the disk was unable to be read either, with "fdisk -l /dev/sda" failing to read a sector, where it had worked before starting the install. Unplugging the SATA cable to the drive and plugging it in again made the drive work again (on /dev/sdc), but another attempt to install failed with the same write errors. I noticed that the log had swap write errors also, so I rebooted the install DVD again, and this time did a "swapoff -a" command before attempting to install, but got the same errors again. So I found my Ubuntu 15.10 install DVD and tried a new install from that, which worked just fine. On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that the DVD based system would run normally, then tried mounting the EXT4 system partition I had just installed using the 15.10 install DVD. That worked, so I tried dd commands to do test writes to that partition. The following commands worked: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k but when I did this command: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k after a while errors started appearing in kern.log, just as with the attempts to install 16.04. It appears that with sustained write activity, the errors will start and then the drive will become unusable until it is unplugged and plugged in again. I have attached the kern.log and syslog files from the 15.10 install that worked, and the 16.04 install attempt that failed. The first error message appears to be this: ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0 dhfis 0x1 dmafis 0x0 sdbfis 0x0 which leads me to suspect a problem with the handling of the SATA controller's interrupts. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2233 F pulseaudio /dev/snd/controlC1: ubuntu 2233 F pulseaudio CasperVersion: 1.368 DistroRelease: Ubuntu 16.04 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. enp2s9no wireless extensions. LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1401:bd08/07/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:r
[Kernel-packages] [Bug 1561830] Re: Hard disk writes fail in 16.04 daily on nForce 430
apport information ** Tags added: apport-collected xenial ** Description changed: I have an old PC I use for testing new operating systems. It has previously had Ubuntu 15.10 installed and working. The motherboard is an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce 6150 GPU. I have installed an Nvidia GT220 card to use for more modern video support. When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop- amd64.iso file downloaded 24/03/2016 18:17), it starts to write to the hard disk (Samsung HD103UJ), and after a short time the install got lots of disk write errors in kern.log. After the errors, the disk was unable to be read either, with "fdisk -l /dev/sda" failing to read a sector, where it had worked before starting the install. Unplugging the SATA cable to the drive and plugging it in again made the drive work again (on /dev/sdc), but another attempt to install failed with the same write errors. I noticed that the log had swap write errors also, so I rebooted the install DVD again, and this time did a "swapoff -a" command before attempting to install, but got the same errors again. So I found my Ubuntu 15.10 install DVD and tried a new install from that, which worked just fine. On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that the DVD based system would run normally, then tried mounting the EXT4 system partition I had just installed using the 15.10 install DVD. That worked, so I tried dd commands to do test writes to that partition. The following commands worked: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k but when I did this command: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k after a while errors started appearing in kern.log, just as with the attempts to install 16.04. It appears that with sustained write activity, the errors will start and then the drive will become unusable until it is unplugged and plugged in again. I have attached the kern.log and syslog files from the 15.10 install that worked, and the 16.04 install attempt that failed. The first error message appears to be this: ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0 dhfis 0x1 dmafis 0x0 sdbfis 0x0 - which leads me to suspect a problem with the handling of the SATA - controller's interrupts. + which leads me to suspect a problem with the handling of the SATA controller's interrupts. + --- + ApportVersion: 2.20-0ubuntu3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 2233 F pulseaudio + /dev/snd/controlC1: ubuntu 2233 F pulseaudio + CasperVersion: 1.368 + DistroRelease: Ubuntu 16.04 + IwConfig: + enp0s20 no wireless extensions. + + lono wireless extensions. + + enp2s9no wireless extensions. + LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) + Lsusb: + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 nouveaufb + ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- + ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.4.0-15-generic N/A + linux-backports-modules-4.4.0-15-generic N/A + linux-firmware1.157 + RfKill: + + Tags: xenial + Uname: Linux 4.4.0-15-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 08/07/2008 + dmi.bios.vendor: Phoenix Technologies, LTD + dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401 + dmi.board.name: M2NPV-VM + dmi.board.vendor: ASUSTek Computer INC. + dmi.board.version: 1.xx + dmi.chassis.asset.tag: 123456789000 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1401:bd08/07/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.name: System Product Name + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1
[Kernel-packages] [Bug 1561830] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1561830/+attachment/4610893/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1561830 Title: Hard disk writes fail in 16.04 daily on nForce 430 Status in linux package in Ubuntu: Incomplete Bug description: I have an old PC I use for testing new operating systems. It has previously had Ubuntu 15.10 installed and working. The motherboard is an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce 6150 GPU. I have installed an Nvidia GT220 card to use for more modern video support. When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop- amd64.iso file downloaded 24/03/2016 18:17), it starts to write to the hard disk (Samsung HD103UJ), and after a short time the install got lots of disk write errors in kern.log. After the errors, the disk was unable to be read either, with "fdisk -l /dev/sda" failing to read a sector, where it had worked before starting the install. Unplugging the SATA cable to the drive and plugging it in again made the drive work again (on /dev/sdc), but another attempt to install failed with the same write errors. I noticed that the log had swap write errors also, so I rebooted the install DVD again, and this time did a "swapoff -a" command before attempting to install, but got the same errors again. So I found my Ubuntu 15.10 install DVD and tried a new install from that, which worked just fine. On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that the DVD based system would run normally, then tried mounting the EXT4 system partition I had just installed using the 15.10 install DVD. That worked, so I tried dd commands to do test writes to that partition. The following commands worked: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k but when I did this command: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k after a while errors started appearing in kern.log, just as with the attempts to install 16.04. It appears that with sustained write activity, the errors will start and then the drive will become unusable until it is unplugged and plugged in again. I have attached the kern.log and syslog files from the 15.10 install that worked, and the 16.04 install attempt that failed. The first error message appears to be this: ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0 dhfis 0x1 dmafis 0x0 sdbfis 0x0 which leads me to suspect a problem with the handling of the SATA controller's interrupts. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2233 F pulseaudio /dev/snd/controlC1: ubuntu 2233 F pulseaudio CasperVersion: 1.368 DistroRelease: Ubuntu 16.04 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. enp2s9no wireless extensions. LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1401:bd08/07/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx
[Kernel-packages] [Bug 1561830] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1561830/+attachment/4610896/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1561830 Title: Hard disk writes fail in 16.04 daily on nForce 430 Status in linux package in Ubuntu: Incomplete Bug description: I have an old PC I use for testing new operating systems. It has previously had Ubuntu 15.10 installed and working. The motherboard is an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce 6150 GPU. I have installed an Nvidia GT220 card to use for more modern video support. When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop- amd64.iso file downloaded 24/03/2016 18:17), it starts to write to the hard disk (Samsung HD103UJ), and after a short time the install got lots of disk write errors in kern.log. After the errors, the disk was unable to be read either, with "fdisk -l /dev/sda" failing to read a sector, where it had worked before starting the install. Unplugging the SATA cable to the drive and plugging it in again made the drive work again (on /dev/sdc), but another attempt to install failed with the same write errors. I noticed that the log had swap write errors also, so I rebooted the install DVD again, and this time did a "swapoff -a" command before attempting to install, but got the same errors again. So I found my Ubuntu 15.10 install DVD and tried a new install from that, which worked just fine. On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that the DVD based system would run normally, then tried mounting the EXT4 system partition I had just installed using the 15.10 install DVD. That worked, so I tried dd commands to do test writes to that partition. The following commands worked: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k but when I did this command: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k after a while errors started appearing in kern.log, just as with the attempts to install 16.04. It appears that with sustained write activity, the errors will start and then the drive will become unusable until it is unplugged and plugged in again. I have attached the kern.log and syslog files from the 15.10 install that worked, and the 16.04 install attempt that failed. The first error message appears to be this: ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0 dhfis 0x1 dmafis 0x0 sdbfis 0x0 which leads me to suspect a problem with the handling of the SATA controller's interrupts. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2233 F pulseaudio /dev/snd/controlC1: ubuntu 2233 F pulseaudio CasperVersion: 1.368 DistroRelease: Ubuntu 16.04 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. enp2s9no wireless extensions. LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1401:bd08/07/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx:cvnChassis
[Kernel-packages] [Bug 1557298] Re: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly
Those error won't effecting bluetooth mouse(both 4.0 and 2.0 device) functionalities here. Verified by following steps: (thru bluetooth-wizard) Bluetooth off Bluetooth on Mouse paired System suspend System resume(Bluetooth resume itself too) Mouse reconnected Bluetooth off Bluetooth on Mouse reconnected(around 10s for bt2.0 but bt4.0 reconnect instantly) ** Attachment added: "syslog-bt4-mouse" https://bugs.launchpad.net/unity-control-center/+bug/1557298/+attachment/4610887/+files/syslog-bt4-mouse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1557298 Title: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly Status in Unity Control Center: New Status in bluez package in Ubuntu: New Bug description: Failed to pair low energy(bluetooth smart, 4.0) keyboard correctly. Bluetooth smart keyboard is unable to use after bluetooth-wizard says "OK". Also the passcode input is also not acting interactively like when pairing with bluetooth 3.0(LegacyPairing) keyboard. Above scenario also being verified with bluetoothctl and blueman. Step to reproduce: 1. open Bluetooth Settings 2. click on Add New Device button 3. select the bluetooth le keyboard 4. input the passcode display on GUI Expected result: After bluetooth-wizard telling user is okay the keyboard should work Actual result: Pairing mode stop on keyboard, but still not work. - More details about versions: Environment: xenial daily (20160307) bluez 5.37-0ubuntu5 gnome-bluetooth 3.18.2-1ubuntu2 blueman 2.0.3-1ubuntu1 bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1) Tested devices: Designer Mouse, bluetooth smart (pairable, work, re-pair work) Designer Keyboard, bluetooth smart (paired, not working) BT3.0 keyboard, bluetooth classic (pair and work) BT3.0 mouse, bluetooth classic (pair and work) - In control environment with the same hardware system and devices: trusty 14.04.1 + dist-upgrade (stay with 3.13 kernel) bluez5 5.35 (ppa: https://launchpad.net/~vidplace7/+archive/ubuntu/bluez5) It works with all above devices but can only be pairing through bluetoothctl manually, since the older bluetooth-wizard does not understand bluez 5.x. Everything seems works fine, although there are a lot more error messages, but since this bug is more about xenial, please let me know if we need more information about this, I'm able to reproduce this trusty scenario in anytime. - Additional note: A little clarification, since I'm not sure how far the Bluetooth SIG is going to use Bluetooth Smart(Low Energy, or even Smart-Ready) to cover the versioning, I decided to just use what ever I saw on the product box. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 15 11:40:12 2016 InstallationDate: Installed on 2016-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed root=UUID=1079eca4-4293-4e51-ba0e-84f7d681cb2c ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:71:CC:39:BD:22 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:862538 acl:39687 sco:0 events:2668 errors:0 TX bytes:26235 acl:904 sco:0 commands:1021 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-control-center/+bug/1557298/+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 1561830] Re: Hard disk writes fail in 16.04 daily on nForce 430
apport-collect got an error when running dpkg-query on the linux package, presumably due to this being a live DVD boot. Here is the output of "uname -a": Linux ubuntu 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:08:31 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ** 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/1561830 Title: Hard disk writes fail in 16.04 daily on nForce 430 Status in linux package in Ubuntu: Confirmed Bug description: I have an old PC I use for testing new operating systems. It has previously had Ubuntu 15.10 installed and working. The motherboard is an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce 6150 GPU. I have installed an Nvidia GT220 card to use for more modern video support. When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop- amd64.iso file downloaded 24/03/2016 18:17), it starts to write to the hard disk (Samsung HD103UJ), and after a short time the install got lots of disk write errors in kern.log. After the errors, the disk was unable to be read either, with "fdisk -l /dev/sda" failing to read a sector, where it had worked before starting the install. Unplugging the SATA cable to the drive and plugging it in again made the drive work again (on /dev/sdc), but another attempt to install failed with the same write errors. I noticed that the log had swap write errors also, so I rebooted the install DVD again, and this time did a "swapoff -a" command before attempting to install, but got the same errors again. So I found my Ubuntu 15.10 install DVD and tried a new install from that, which worked just fine. On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that the DVD based system would run normally, then tried mounting the EXT4 system partition I had just installed using the 15.10 install DVD. That worked, so I tried dd commands to do test writes to that partition. The following commands worked: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k but when I did this command: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k after a while errors started appearing in kern.log, just as with the attempts to install 16.04. It appears that with sustained write activity, the errors will start and then the drive will become unusable until it is unplugged and plugged in again. I have attached the kern.log and syslog files from the 15.10 install that worked, and the 16.04 install attempt that failed. The first error message appears to be this: ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0 dhfis 0x1 dmafis 0x0 sdbfis 0x0 which leads me to suspect a problem with the handling of the SATA controller's interrupts. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2233 F pulseaudio /dev/snd/controlC1: ubuntu 2233 F pulseaudio CasperVersion: 1.368 DistroRelease: Ubuntu 16.04 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. enp2s9no wireless extensions. LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalia
[Kernel-packages] [Bug 1561902] Re: Total system freeze after 3.16.0-38.52
I'm unable to run 'apport-collect 1561902', as it says "Package linux- lts-utopic not installed and no hook available, ignoring". Any help? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1561902 Title: Total system freeze after 3.16.0-38.52 Status in linux-lts-utopic package in Ubuntu: New Bug description: This should have been reported already last year, but here it goes. Problem: My laptop is a ASUS N71JA and works perfectly in Windows. Everything was fine with Xubuntu 14.04 through kernels 3.13 and 3.16 up to 3.16.0-38.52. Desktop freezes, like totally dies with hard power reset being the only option, every now and then from this kernel and onwards. This affects 3.19 and 4.2.0 kernels released after this date as well. No Magic SysRq possible and I can't see anything fancy in syslog or kern.log. Desktop can die anytime between immediately after boot or after a few hours, but it happens completely randomly and is hard to debug. Workaround: 3.16.0-38.52 was released in May 2015 (https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1452882). 3.16.0-37.51 and 3.16.0-36.48 have NEVER frozen. The only non-upstream change that was made to 3.16.0-38.52 was "vesafb: Set mtrr:3 (write-combining) as default" (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434581). This is probably not implemented in the mainline kernel tree, right? I've been using mainline 3.16.7-ckt24-trusty without any problems now for over a month (http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.16.7-ckt24-trusty/) i.e. it seems like 1434581 is causing the problem. Can this be verified by some other method e.g. by disabling/reverting 1434581 in a "normal" non-mainline kernel? Solution: ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1561902/+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 1491340] Re: Bluetooth keyboard is configured with wrong keyboard layout
** Changed in: canonical-pocket-desktop Status: In Progress => Fix Committed ** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1491340 Title: Bluetooth keyboard is configured with wrong keyboard layout Status in The Avila project: In Progress Status in Canonical System Image: Fix Committed Status in Canonical Pocket Desktop: Fix Committed Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: Phone: Meizu MX4 (15.04 r4) OS Language: German What you expected to happen: When connecting a Bluetooth keyboard I expect that the keyboard layout is the same as the keyboard hardware key layout (German) or that it is possible to change the keyboard layout in the Bluetooth setting for the connected Bluetooth device. What happened instead: The Bluetooth keyboard worked, but wasn't set to German key layout. In the Bluetooth device setting I couldn't find any option to change the Bluetooth keyboard key layout. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1491340/+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 1527643] Re: use after free of task_struct->numa_faults in task_numa_find_cpu
** Tags removed: verification-needed-trusty verification-needed-vivid verification-needed-wily ** Tags added: verification-done-trusty verification-done-vivid verification-done-wily -- 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/1527643 Title: use after free of task_struct->numa_faults in task_numa_find_cpu Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: [Impact] The use-after-free invalid read bug, which happens in really tricky case, would use the numa_faults data already freed for the NUMA balance to make a decision to migrate the exiting process. The bug was found by the Ubuntu-3.13.0-65 with KASan backported. binary package: http://kernel.ubuntu.com/~gavinguo/kasan/Ubuntu-3.13.0-65.105/ source code: http://kernel.ubuntu.com/git/gavinguo/ubuntu-trusty-amd64.git/log/?h=Ubuntu-3.13.0-65-kasan == BUG: KASan: use after free in task_numa_find_cpu+0x64c/0x890 at addr 880dd393ecd8 Read of size 8 by task qemu-system-x86/3998900 = BUG kmalloc-128 (Tainted: G B ): kasan: bad access detected - INFO: Allocated in task_numa_fault+0xc1b/0xed0 age=41980 cpu=18 pid=3998890 __slab_alloc+0x4f8/0x560 __kmalloc+0x1eb/0x280 task_numa_fault+0xc1b/0xed0 do_numa_page+0x192/0x200 handle_mm_fault+0x808/0x1160 __do_page_fault+0x218/0x750 do_page_fault+0x1a/0x70 page_fault+0x28/0x30 SyS_poll+0x66/0x1a0 system_call_fastpath+0x1a/0x1f INFO: Freed in task_numa_free+0x1d2/0x200 age=62 cpu=18 pid=0 __slab_free+0x2ab/0x3f0 kfree+0x161/0x170 task_numa_free+0x1d2/0x200 finish_task_switch+0x1d2/0x210 __schedule+0x5d4/0xc60 schedule_preempt_disabled+0x40/0xc0 cpu_startup_entry+0x2da/0x340 start_secondary+0x28f/0x360 INFO: Slab 0xea00374e4f00 objects=37 used=17 fp=0x880dd393ecb0 flags=0x6004080 INFO: Object 0x880dd393ecb0 @offset=11440 fp=0x880dd393f700 Bytes b4 880dd393eca0: 0c 00 00 00 18 00 00 00 af 63 3a 04 01 00 00 00 .c:. Object 880dd393ecb0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Object 880dd393ecc0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Object 880dd393ecd0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Object 880dd393ece0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Object 880dd393ecf0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Object 880dd393ed00: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Object 880dd393ed10: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Object 880dd393ed20: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 kkk. CPU: 61 PID: 3998900 Comm: qemu-system-x86 Tainted: G B 3.13.0-65-generic #105 Hardware name: Supermicro X8QB6/X8QB6, BIOS 2.0c 06/11/2 ea00374e4f00 8816c572b420 81a6ce35 88045f00f500 8816c572b450 81244aed 88045f00f500 ea00374e4f00 880dd393ecb0 0012 8816c572b478 8124ac36 Call Trace: [] dump_stack+0x45/0x56 [] print_trailer+0xfd/0x170 [] object_err+0x36/0x40 [] kasan_report_error+0x1e9/0x3a0 [] kasan_report+0x40/0x50 [] ? task_numa_find_cpu+0x64c/0x890 [] __asan_load8+0x69/0xa0 [] ? find_next_bit+0xd8/0x120 [] task_numa_find_cpu+0x64c/0x890 [] task_numa_migrate+0x4ac/0x7b0 [] numa_migrate_preferred+0xb3/0xc0 [] task_numa_fault+0xb88/0xed0 [] do_numa_page+0x192/0x200 [] handle_mm_fault+0x808/0x1160 [] ? sched_clock_cpu+0x10d/0x160 [] ? native_load_tls+0x82/0xa0 [] __do_page_fault+0x218/0x750 [] ? hrtimer_try_to_cancel+0x76/0x160 [] ? schedule_hrtimeout_range_clock.part.24+0xf7/0x1c0 [] do_page_fault+0x1a/0x70 [] page_fault+0x28/0x30 [] ? do_sys_poll+0x1c4/0x6d0 [] ? enqueue_task_fair+0x4b6/0xaa0 [] ? sched_clock+0x9/0x10 [] ? resched_task+0x7a/0xc0 [] ? check_preempt_curr+0xb3/0x130 [] ? poll_select_copy_remaining+0x170/0x170 [] ? wake_up_state+0x10/0x20 [] ? drop_futex_key_refs.isra.14+0x1f/0x90 [] ? futex_requeue+0x3de/0xba0 [] ? do_futex+0xbe/0x8f0 [] ? read_tsc+0x9/0x20 [] ? ktime_get_ts+0x12d/0x170 [] ? timespec_add_safe+0x59/0xe0 [] SyS_poll+0x66/0x1a0 [] sys
[Kernel-packages] [Bug 1561727] Re: linux: 4.4.0-16.32 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: New => Fix Released ** Changed in: kernel-development-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) ** Changed in: kernel-development-workflow/prepare-package-meta Status: New => Fix Released ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft (apw) ** Changed in: kernel-development-workflow/prepare-package-signed Status: New => Fix Released ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) ** Description changed: This bug is for tracking the 4.4.0-16.32 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 24. March 2016 20:30 UTC kernel-phase-changed:Thursday, 24. March 2016 20:30 UTC kernel-phase:Prepare + kernel-stable-Promote-to-proposed-end:Friday, 25. March 2016 09:59 UTC -- 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/1561727 Title: linux: 4.4.0-16.32 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-16.32 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 24. March 2016 20:30 UTC kernel-phase-changed:Thursday, 24. March 2016 20:30 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Friday, 25. March 2016 09:59 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1561727/+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 1561727] Re: linux: 4.4.0-16.32 -proposed tracker
** Changed in: kernel-development-workflow/promote-to-proposed Status: New => Fix Released ** Changed in: kernel-development-workflow/promote-to-proposed Assignee: Canonical Kernel Team (canonical-kernel-team) => Adam Conrad (adconrad) -- 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/1561727 Title: linux: 4.4.0-16.32 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-16.32 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 24. March 2016 20:30 UTC kernel-phase-changed:Thursday, 24. March 2016 20:30 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Friday, 25. March 2016 09:59 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1561727/+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 1561943] [NEW] Stylus coordinates wrong when screen is rotated on Dell Venue 11 Pro 7140
Public bug reported: I am using the pre-release 16.04 Ubuntu Xenial Xerus (development branch) with kernel 4.4.0-15-generic on a Dell Venue 11 Pro 7140. Touchscreen and Stylus are recognised out of the box: xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Synaptics T Pad V 01.31 Touchpad id=9[slave pointer (2)] ⎜ ↳ SYNA7500:00 06CB:780E Pen id=13 [slave pointer (2)] ⎜ ↳ SYNA7500:00 06CB:780E id=14 [slave pointer (2)] When I am manually rotating the screen by 90° using the System Settings option (automatic screen rotation does not work), the touchscreen and touchpad work as expected, however, the stylus is not using the correct coordinates and the cursor is not following the stylus position. When I move the stylus left/right, the cursor moves up/down, and vice versa. I had hoped to get a work around by disabling and re-enabling the stylus after rotating the screen using xinput --disable "SYNA7500:00 06CB:780E Pen" xinput --enable "SYNA7500:00 06CB:780E Pen" but this didn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 [modified: boot/vmlinuz-4.4.0-15-generic] ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asvin 1800 F pulseaudio /dev/snd/controlC1: asvin 1800 F pulseaudio CurrentDesktop: Unity Date: Fri Mar 25 11:21:35 2016 HibernationDevice: RESUME=UUID=f716048f-ce0e-4825-b3c4-563fa743242a InstallationDate: Installed on 2016-03-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) MachineType: Dell Inc. Venue 11 Pro 7140 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=a9cb1c53-fcf1-4691-a246-24b90dd908c6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd10/27/2015:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- 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/1561943 Title: Stylus coordinates wrong when screen is rotated on Dell Venue 11 Pro 7140 Status in linux package in Ubuntu: Confirmed Bug description: I am using the pre-release 16.04 Ubuntu Xenial Xerus (development branch) with kernel 4.4.0-15-generic on a Dell Venue 11 Pro 7140. Touchscreen and Stylus are recognised out of the box: xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Synaptics T Pad V 01.31 Touchpadid=9[slave pointer (2)] ⎜ ↳ SYNA7500:00 06CB:780E Pen id=13 [slave pointer (2)] ⎜ ↳ SYNA7500:00 06CB:780E id=14 [slave pointer (2)] When I am manually rotating the screen by 90° using the System Settings option (automatic screen rotation does not work), the touchscreen and touchpad work as expected, however, the stylus is not using the correct coordinates and the cursor is not following the stylus position. When I move the stylus left/right, the cursor moves up/down, and vice versa. I had hoped to get a work around by disabling and re-enabling the stylus after rotating the screen using xinput --disable "SYNA7500:00 06CB:780E Pen" xinput --enable "SYNA7500:00 06CB:780E Pen" but this didn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 [modified: boot/vmlinuz-4.4.0-15-generic] ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asvin 1800 F pulseaudio /dev/snd/controlC1: asvin 1800 F pulseaudio CurrentDesktop: Unity Date: Fri Mar 25 11:21:35 2016 HibernationDevice: RESUME=UUID=f716048f-ce0e-48
[Kernel-packages] [Bug 1561943] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1561943 Title: Stylus coordinates wrong when screen is rotated on Dell Venue 11 Pro 7140 Status in linux package in Ubuntu: Confirmed Bug description: I am using the pre-release 16.04 Ubuntu Xenial Xerus (development branch) with kernel 4.4.0-15-generic on a Dell Venue 11 Pro 7140. Touchscreen and Stylus are recognised out of the box: xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Synaptics T Pad V 01.31 Touchpadid=9[slave pointer (2)] ⎜ ↳ SYNA7500:00 06CB:780E Pen id=13 [slave pointer (2)] ⎜ ↳ SYNA7500:00 06CB:780E id=14 [slave pointer (2)] When I am manually rotating the screen by 90° using the System Settings option (automatic screen rotation does not work), the touchscreen and touchpad work as expected, however, the stylus is not using the correct coordinates and the cursor is not following the stylus position. When I move the stylus left/right, the cursor moves up/down, and vice versa. I had hoped to get a work around by disabling and re-enabling the stylus after rotating the screen using xinput --disable "SYNA7500:00 06CB:780E Pen" xinput --enable "SYNA7500:00 06CB:780E Pen" but this didn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 [modified: boot/vmlinuz-4.4.0-15-generic] ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asvin 1800 F pulseaudio /dev/snd/controlC1: asvin 1800 F pulseaudio CurrentDesktop: Unity Date: Fri Mar 25 11:21:35 2016 HibernationDevice: RESUME=UUID=f716048f-ce0e-4825-b3c4-563fa743242a InstallationDate: Installed on 2016-03-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) MachineType: Dell Inc. Venue 11 Pro 7140 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=a9cb1c53-fcf1-4691-a246-24b90dd908c6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd10/27/2015:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561943/+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 1561729] Re: Screen flickering on i915_bpo
** Description changed: Hey Guys, i am encountering some random screen flickering after i launched google- - chrome. this persists even after clsoing chrome. + chrome. this persists even after closing chrome. it is like the screen + wents black for a fracture of a second. - dmesg reports: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] - *ERROR* CPU pipe A FIFO underrun + when it happens dmesg reports: [drm:intel_cpu_fifo_underrun_irq_handler + [i915_bpo]] *ERROR* CPU pipe A FIFO underrun + + I am currently on Ubuntu 1604 Daily: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 - PS: its an dell XPS 13 with no external display attached. internal - display is an FHD one + PS: It is a Dell XPS 13 9530 with no external display attached. + The internal display is an FHD one -- 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/1561729 Title: Screen flickering on i915_bpo Status in linux package in Ubuntu: Confirmed Bug description: Hey Guys, i am encountering some random screen flickering after i launched google-chrome. this persists even after closing chrome. it is like the screen wents black for a fracture of a second. when it happens dmesg reports: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe A FIFO underrun I am currently on Ubuntu 1604 Daily: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 PS: It is a Dell XPS 13 9530 with no external display attached. The internal display is an FHD one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561729/+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 1559914] Re: [Bug]Disable multi-record PEBS on Merom
perf/x86: Move perf_event.c ... => x86/events/core.c perf/x86: Move perf_event_amd.c ... => x86/events/amd/core.c perf/x86: Move perf_event_amd_ibs.c ... => x86/events/amd/ibs.c perf/x86: Move perf_event_amd_iommu.[ch] .. => x86/events/amd/iommu.[ch] perf/x86: Move perf_event_amd_uncore.c => x86/events/amd/uncore.c perf/x86: Move perf_event_intel_bts.c => x86/events/intel/bts.c perf/x86: Move perf_event_intel.c => x86/events/intel/core.c perf/x86: Move perf_event_intel_cqm.c => x86/events/intel/cqm.c perf/x86: Move perf_event_intel_cstate.c . => x86/events/intel/cstate.c perf/x86: Move perf_event_intel_ds.c . => x86/events/intel/ds.c perf/x86: Move perf_event_intel_lbr.c => x86/events/intel/lbr.c perf/x86: Move perf_event_intel_pt.[ch] .. => x86/events/intel/pt.[ch] perf/x86: Move perf_event_intel_rapl.c ... => x86/events/intel/rapl.c perf/x86: Move perf_event_intel_uncore.[ch] .. => x86/events/intel/uncore.[ch] perf/x86: Move perf_event_intel_uncore_nhmex.c => x86/events/intel/uncore_nmhex.c perf/x86: Move perf_event_intel_uncore_snb.c => x86/events/intel/uncore_snb.c perf/x86: Move perf_event_intel_uncore_snbep.c => x86/events/intel/uncore_snbep.c perf/x86: Move perf_event_knc.c .. => x86/events/intel/knc.c perf/x86: Move perf_event_p4.c ... => x86/events/intel/p4.c perf/x86: Move perf_event_p6.c ... => x86/events/intel/p6.c perf/x86: Move perf_event_msr.c .. => x86/events/msr.c perf/x86: Move perf_event.h to its new home perf/x86/intel: Use PAGE_SIZE for PEBS buffer size on Core2 ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1559914 Title: [Bug]Disable multi-record PEBS on Merom Status in intel: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: As reported, multi record pebs does not work on Merom. This is fixed by one patch in v4.6, please back port it to 16.04. e72daf3 perf/x86/intel: Use PAGE_SIZE for PEBS buffer size on Core2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1559914/+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 1561974] [NEW] [Lenovo T460s] freeze on battery + lid close
Public bug reported: The laptop freezes when on battery power and the lid is closed. Relevant bug: https://bugzilla.kernel.org/show_bug.cgi?id=113551 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: luki 1021 F...m pulseaudio /dev/snd/controlC0: luki 1021 F pulseaudio CurrentDesktop: X-Cinnamon Date: Fri Mar 25 13:46:30 2016 InstallationDate: Installed on 2016-03-09 (15 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) MachineType: LENOVO 20FAA01200 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=9137cae3-ceaa-4c5f-a4bd-4e0473140061 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET37W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAA01200 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET37W(1.05):bd01/15/2016:svnLENOVO:pn20FAA01200:pvrThinkPadT460s:rvnLENOVO:rn20FAA01200:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FAA01200 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1561974 Title: [Lenovo T460s] freeze on battery + lid close Status in linux package in Ubuntu: New Bug description: The laptop freezes when on battery power and the lid is closed. Relevant bug: https://bugzilla.kernel.org/show_bug.cgi?id=113551 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: luki 1021 F...m pulseaudio /dev/snd/controlC0: luki 1021 F pulseaudio CurrentDesktop: X-Cinnamon Date: Fri Mar 25 13:46:30 2016 InstallationDate: Installed on 2016-03-09 (15 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) MachineType: LENOVO 20FAA01200 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=9137cae3-ceaa-4c5f-a4bd-4e0473140061 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET37W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAA01200 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET37W(1.05):bd01/15/2016:svnLENOVO:pn20FAA01200:pvrThinkPadT460s:rvnLENOVO:rn20FAA01200:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FAA01200 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561974/+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 1561974] Re: [Lenovo T460s] freeze on battery + lid close
On the mainline bugtracker, there is a bugfix suggestion [1]. I tried to apply this patch on the ubuntu 4.4.0-15 kernel and it does _not_ solve the issue. Applying the same patch to mainline 4.5 does fix the issue. [1] https://bugzilla.kernel.org/attachment.cgi?id=209371&action=diff -- 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/1561974 Title: [Lenovo T460s] freeze on battery + lid close Status in linux package in Ubuntu: New Bug description: The laptop freezes when on battery power and the lid is closed. Relevant bug: https://bugzilla.kernel.org/show_bug.cgi?id=113551 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: luki 1021 F...m pulseaudio /dev/snd/controlC0: luki 1021 F pulseaudio CurrentDesktop: X-Cinnamon Date: Fri Mar 25 13:46:30 2016 InstallationDate: Installed on 2016-03-09 (15 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) MachineType: LENOVO 20FAA01200 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=9137cae3-ceaa-4c5f-a4bd-4e0473140061 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET37W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAA01200 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET37W(1.05):bd01/15/2016:svnLENOVO:pn20FAA01200:pvrThinkPadT460s:rvnLENOVO:rn20FAA01200:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FAA01200 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561974/+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 1561604] Re: x-gene2: add SoC v2 support to clock
** Summary changed: - x-gene2: fix rtc load error during kernel boot + x-gene2: add SoC v2 support to clock ** Description changed: - This error "[ 0.981954] hctosys: unable to open rtc device (rtc0)" is - seen while booting a new xgene2 board. This causes issues with any - service (like MAAS) who tries to get the system time early in the - booting process. The fix for this is two patches, one of which is - already in the xenial kernel, the other is upstream in Linus's linux - tree already, and changing a kernel module to be built-in for arm64. + Need an upstream patch to add support for the clock on the X-Gene 2 + platform. -- 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/1561604 Title: x-gene2: add SoC v2 support to clock Status in linux package in Ubuntu: In Progress Bug description: Need an upstream patch to add support for the clock on the X-Gene 2 platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561604/+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 1561974] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1561974 Title: [Lenovo T460s] freeze on battery + lid close Status in linux package in Ubuntu: Confirmed Bug description: The laptop freezes when on battery power and the lid is closed. Relevant bug: https://bugzilla.kernel.org/show_bug.cgi?id=113551 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: luki 1021 F...m pulseaudio /dev/snd/controlC0: luki 1021 F pulseaudio CurrentDesktop: X-Cinnamon Date: Fri Mar 25 13:46:30 2016 InstallationDate: Installed on 2016-03-09 (15 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) MachineType: LENOVO 20FAA01200 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=9137cae3-ceaa-4c5f-a4bd-4e0473140061 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET37W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAA01200 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET37W(1.05):bd01/15/2016:svnLENOVO:pn20FAA01200:pvrThinkPadT460s:rvnLENOVO:rn20FAA01200:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FAA01200 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561974/+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 1557379] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] noticed during compilation of CUDA Toolkit
** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- 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/1557379 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] noticed during compilation of CUDA Toolkit Status in linux package in Ubuntu: New Bug description: == Comment: #0 - SANTWANA SAMANTRAY - 2016-01-18 05:50:42 == During compilation of NVIDIA_CUDA-7.5 Toolkit Samples, in Ubuntu14.04.04 Guest, the below BUG is noticed. [1.077464] NVRM: loading NVIDIA UNIX ppc64le Kernel Module 352.39 Fri Aug 14 17:10:41 PDT 2015 [1.211127] init: failsafe main process (498) killed by TERM signal [1.307135] audit: type=1400 audit(1453110711.213:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=697 comm="apparmor_parser" [1.307458] audit: type=1400 audit(1453110711.213:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=695 comm="apparmor_parser" [1.307467] audit: type=1400 audit(1453110711.213:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=695 comm="apparmor_parser" [1.560244] init: plymouth-upstart-bridge main process ended, respawning [ 1600.099759] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] [ 1600.100531] Modules linked in: nvidia(POE) drm pseries_rng rtc_generic [ 1600.100611] CPU: 0 PID: 15164 Comm: cicc Tainted: P OE 4.2.0-23-generic #28~14.04.1-Ubuntu [ 1600.100613] task: c390d3e0 ti: c39c8000 task.ti: c39c8000 [ 1600.100615] NIP: 103eadc8 LR: 103eb5e0 CTR: 103eb5a0 [ 1600.100622] REGS: c39cbea0 TRAP: 0901 Tainted: P OE (4.2.0-23-generic) [ 1600.100623] MSR: 80010280f033 CR: 4848 XER: [ 1600.100646] CFAR: 103eb5dc SOFTE: 1 [ 1600.100646] GPR00: 103eb5e0 3fffc0d01300 10ed2838 01000459e250 [ 1600.100646] GPR04: 0061 0100098e3ae0 [ 1600.100646] GPR08: 090c 0100045d8c00 01000459e308 07ff [ 1600.100646] GPR12: 4824 1006d750 [ 1600.100657] NIP [103eadc8] 0x103eadc8 [ 1600.100658] LR [103eb5e0] 0x103eb5e0 [ 1600.100659] Call Trace: [ 1672.099724] NMI watchdog: BUG: soft lockup - CPU#4 stuck for 32s! [cicc:15182] [ 1672.100995] Modules linked in: nvidia(POE) drm pseries_rng rtc_generic [ 1672.101033] CPU: 4 PID: 15182 Comm: cicc Tainted: P OEL 4.2.0-23-generic #28~14.04.1-Ubuntu [ 1672.101035] task: c0009c5328a0 ti: c306 task.ti: c306 [ 1672.101037] NIP: 11266b0c LR: 11266af4 CTR: 11266a70 [ 1672.101038] REGS: c3063ea0 TRAP: 0901 Tainted: P OEL (4.2.0-23-generic) [ 1672.101039] MSR: 80010280f033 CR: 28222422 XER: [ 1672.101046] CFAR: 112637b4 SOFTE: 1 [ 1672.101046] GPR00: 11266af4 37275860 11392800 01001e07e370 [ 1672.101046] GPR04: 0100 11389fb0 ff0c 01001e07e360 [ 1672.101046] GPR08: 0051 0001 01001b64b230 [ 1672.101046] GPR12: 2200 1006d750 [ 1672.101055] NIP [11266b0c] 0x11266b0c [ 1672.101056] LR [11266af4] 0x11266af4 [ 1672.101057] Call Trace: The nouveau modules are disabled, and nvidia drivers are loaded in the guest. # lsmod | grep nvidia nvidia 11484644 0 drm 447733 2 nvidia After downloading the CUDA Developer tool-kit, during the compilation the BUG is noticed. This issue is intermittently occurring, at some instances this issues isn't noticed. == Guest Details == # uname -a Linux ubuntu 4.2.0-23-generic #28~14.04.1-Ubuntu SMP Thu Dec 31 13:41:19 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux # lspci -nn 00:01.0 Ethernet controller [0200]: Red Hat, Inc Virtio network device [1af4:1000] 00:02.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f] 00:03.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block device [1af4:1001] 00:04.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon [1af4:1002] 00:05.0 3D controller [0302]: NVIDIA Corporation GK210GL [Tesla K80] [10de:102d] (rev a1) # cat /proc/driver/nvidia/version NVRM version: NVIDIA UNIX ppc64le Kernel Module 352.39 Fri Aug 14 17:10:41 PDT 2015 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) # nvcc -V nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 2005-20
[Kernel-packages] [Bug 1557379] new dmesg
Default Comment by Bridge ** Attachment added: "new dmesg" https://bugs.launchpad.net/bugs/1557379/+attachment/4611220/+files/dmesg -- 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/1557379 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] noticed during compilation of CUDA Toolkit Status in linux package in Ubuntu: New Bug description: == Comment: #0 - SANTWANA SAMANTRAY - 2016-01-18 05:50:42 == During compilation of NVIDIA_CUDA-7.5 Toolkit Samples, in Ubuntu14.04.04 Guest, the below BUG is noticed. [1.077464] NVRM: loading NVIDIA UNIX ppc64le Kernel Module 352.39 Fri Aug 14 17:10:41 PDT 2015 [1.211127] init: failsafe main process (498) killed by TERM signal [1.307135] audit: type=1400 audit(1453110711.213:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=697 comm="apparmor_parser" [1.307458] audit: type=1400 audit(1453110711.213:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=695 comm="apparmor_parser" [1.307467] audit: type=1400 audit(1453110711.213:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=695 comm="apparmor_parser" [1.560244] init: plymouth-upstart-bridge main process ended, respawning [ 1600.099759] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] [ 1600.100531] Modules linked in: nvidia(POE) drm pseries_rng rtc_generic [ 1600.100611] CPU: 0 PID: 15164 Comm: cicc Tainted: P OE 4.2.0-23-generic #28~14.04.1-Ubuntu [ 1600.100613] task: c390d3e0 ti: c39c8000 task.ti: c39c8000 [ 1600.100615] NIP: 103eadc8 LR: 103eb5e0 CTR: 103eb5a0 [ 1600.100622] REGS: c39cbea0 TRAP: 0901 Tainted: P OE (4.2.0-23-generic) [ 1600.100623] MSR: 80010280f033 CR: 4848 XER: [ 1600.100646] CFAR: 103eb5dc SOFTE: 1 [ 1600.100646] GPR00: 103eb5e0 3fffc0d01300 10ed2838 01000459e250 [ 1600.100646] GPR04: 0061 0100098e3ae0 [ 1600.100646] GPR08: 090c 0100045d8c00 01000459e308 07ff [ 1600.100646] GPR12: 4824 1006d750 [ 1600.100657] NIP [103eadc8] 0x103eadc8 [ 1600.100658] LR [103eb5e0] 0x103eb5e0 [ 1600.100659] Call Trace: [ 1672.099724] NMI watchdog: BUG: soft lockup - CPU#4 stuck for 32s! [cicc:15182] [ 1672.100995] Modules linked in: nvidia(POE) drm pseries_rng rtc_generic [ 1672.101033] CPU: 4 PID: 15182 Comm: cicc Tainted: P OEL 4.2.0-23-generic #28~14.04.1-Ubuntu [ 1672.101035] task: c0009c5328a0 ti: c306 task.ti: c306 [ 1672.101037] NIP: 11266b0c LR: 11266af4 CTR: 11266a70 [ 1672.101038] REGS: c3063ea0 TRAP: 0901 Tainted: P OEL (4.2.0-23-generic) [ 1672.101039] MSR: 80010280f033 CR: 28222422 XER: [ 1672.101046] CFAR: 112637b4 SOFTE: 1 [ 1672.101046] GPR00: 11266af4 37275860 11392800 01001e07e370 [ 1672.101046] GPR04: 0100 11389fb0 ff0c 01001e07e360 [ 1672.101046] GPR08: 0051 0001 01001b64b230 [ 1672.101046] GPR12: 2200 1006d750 [ 1672.101055] NIP [11266b0c] 0x11266b0c [ 1672.101056] LR [11266af4] 0x11266af4 [ 1672.101057] Call Trace: The nouveau modules are disabled, and nvidia drivers are loaded in the guest. # lsmod | grep nvidia nvidia 11484644 0 drm 447733 2 nvidia After downloading the CUDA Developer tool-kit, during the compilation the BUG is noticed. This issue is intermittently occurring, at some instances this issues isn't noticed. == Guest Details == # uname -a Linux ubuntu 4.2.0-23-generic #28~14.04.1-Ubuntu SMP Thu Dec 31 13:41:19 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux # lspci -nn 00:01.0 Ethernet controller [0200]: Red Hat, Inc Virtio network device [1af4:1000] 00:02.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f] 00:03.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block device [1af4:1001] 00:04.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon [1af4:1002] 00:05.0 3D controller [0302]: NVIDIA Corporation GK210GL [Tesla K80] [10de:102d] (rev a1) # cat /proc/driver/nvidia/version NVRM version: NVIDIA UNIX ppc64le Kernel Module 352.39 Fri Aug 14 17:10:41 PDT 2015 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) # nvcc -V nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 20
[Kernel-packages] [Bug 1560482] Re: perf: 24x7: Eliminate domain name suffix in event names
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- 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/1560482 Title: perf: 24x7: Eliminate domain name suffix in event names Status in linux package in Ubuntu: Triaged Bug description: Events in the 24x7 counters can belong to different domains like core, chip, virtual CPU home core, etc. To monitor an event, the user must specify the required parameters for the event, which include its name, the chip/core on which to monitor the event as well as the domain. Currently the event is specified to the perf tool as: 'hv_24x7/HPM_0THRD_NON_IDLE_CCYC__PHYS_CORE,core=1/' \ where the event name is 'HPM_0THRD_NON_IDLE_CCYC', the suffix '__PHYS_CORE' specifies the domain, and 'core=1' specifies the core. This is inconsistent in that one parameter is specified as a suffix and the other in a parameter=value format. To simplify the usage, we can eliminate the suffix and let the user specify the domain also in the param=value format. While the domain indices are "well known" or nearly fixed in value, we could display the domain indices in sysfs as a reference for the users: $ cat /sys/bus/event_source/devices/hv_24x7/interface/domains 1: Physical Chip 2: Physical Core 3: VCPU Home Core 4: VCPU Home Chip 5: VCPU Home Node 6: VCPU Remote Node Using these the perf event can now be identified as hv_24x7/HPM_0THRD_NON_IDLE_CCYC,domain=2,core=1 . This feature is implemented by the following commits which have now been merged into mainline: d34171e: powerpc/perf/hv-24x7: Display domain indices in sysfs 8f69dc7: powerpc/perf/24x7: Eliminate domain suffix in event names == Comment: #1 - Sukadev Bhattiprolu - 2016-03-21 15:26:33 == Following two upstream commits are also related 24x7 and could be included in this feature: e5a5886: powerpc/perf/hv-24x7: Fix usage with chip events. 2b206ee: powerpc/perf/hv-24x7: Display change in counter values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1560482/+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 1561998] [NEW] package linux-headers-3.19.0-47 (not installed) failed to install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2
Public bug reported: updgrade error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-headers-3.19.0-47 (not installed) ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10 Uname: Linux 3.19.0-47-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Fri Mar 25 14:48:04 2016 DuplicateSignature: package:linux-headers-3.19.0-47:(not installed):il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 ErrorMessage: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 InstallationDate: Installed on 2015-10-18 (159 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: linux-lts-vivid Title: package linux-headers-3.19.0-47 (not installed) failed to install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1561998 Title: package linux-headers-3.19.0-47 (not installed) failed to install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 Status in linux-lts-vivid package in Ubuntu: New Bug description: updgrade error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-headers-3.19.0-47 (not installed) ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10 Uname: Linux 3.19.0-47-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Fri Mar 25 14:48:04 2016 DuplicateSignature: package:linux-headers-3.19.0-47:(not installed):il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 ErrorMessage: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 InstallationDate: Installed on 2015-10-18 (159 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: linux-lts-vivid Title: package linux-headers-3.19.0-47 (not installed) failed to install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1561998/+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 1560514] Re: Predictable naming mechanism is leading to issues in DLPAR operations of NICs
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- 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/1560514 Title: Predictable naming mechanism is leading to issues in DLPAR operations of NICs Status in linux package in Ubuntu: Triaged Bug description: Recent kernels are using predictable naming for network interfaces, so the network stack is more tied to PCI naming. This can be a problem in hotplug scenarios, because PCI addresses will change if devices are removed and then re-added. This situation seems unusual, but it can happen if a user wants to replace a NIC without rebooting the machine, for example. The patch attached here should deal with this situation, since it makes PHB/domain number fixed based on device-tree properties. The problem can be reproduced by removing and re-adding a PCI network adapter, so its address will change and, per predictable naming scheme, so is the interface name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1560514/+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 1561998] Re: package linux-headers-3.19.0-47 (not installed) failed to install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1561998 Title: package linux-headers-3.19.0-47 (not installed) failed to install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 Status in linux-lts-vivid package in Ubuntu: New Bug description: updgrade error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-headers-3.19.0-47 (not installed) ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10 Uname: Linux 3.19.0-47-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Fri Mar 25 14:48:04 2016 DuplicateSignature: package:linux-headers-3.19.0-47:(not installed):il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 ErrorMessage: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 InstallationDate: Installed on 2015-10-18 (159 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: linux-lts-vivid Title: package linux-headers-3.19.0-47 (not installed) failed to install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1561998/+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 1562004] [NEW] S390: glibc does not use direct socket-syscalls, but the multiplexer-socket-syscall.
You have been subscribed to a public bug: == Comment: #0 - Stefan Liebler - 2016-03-24 11:16:16 == Hi, the glibc socket functions, like connect(), bind(), socket(), ... do currently use svc 102 (multiplexer-socket-syscall: see /usr/include/s390x-linux-gnu/asm/unistd.h: #define __NR_socketcall 102) The direct socketsyscalls are also available for s390 since kernel 4.3: #define __NR_connect362 #define __NR_bind 361 #define __NR_socket 359 ... The kernel in my used ubuntu alpha is 4.4.0-15 and the glibc 2.23. This glibc release can use these direct socket-syscalls, if glibc is configured with "--enable-kernel=4.3.0". Or even better, use the kernel-level, which will be used in the first release for s390. Here is the kernel commit: "s390: wire up separate socketcalls system calls" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=977108f89c989b1eeb5c8d938e1e71913391eb5f and the glibc commit: "S390: Call direct system calls for socket operations." https://sourceware.org/git/?p=glibc.git;a=commit;h=016495b818cb61df7d0d10e6db54074271b3e3a5 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-139627 severity-high targetmilestone-inin1604 -- S390: glibc does not use direct socket-syscalls, but the multiplexer-socket-syscall. https://bugs.launchpad.net/bugs/1562004 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1557379] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] noticed during compilation of CUDA Toolkit
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key performing-bisect -- 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/1557379 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] noticed during compilation of CUDA Toolkit Status in linux package in Ubuntu: New Bug description: == Comment: #0 - SANTWANA SAMANTRAY - 2016-01-18 05:50:42 == During compilation of NVIDIA_CUDA-7.5 Toolkit Samples, in Ubuntu14.04.04 Guest, the below BUG is noticed. [1.077464] NVRM: loading NVIDIA UNIX ppc64le Kernel Module 352.39 Fri Aug 14 17:10:41 PDT 2015 [1.211127] init: failsafe main process (498) killed by TERM signal [1.307135] audit: type=1400 audit(1453110711.213:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=697 comm="apparmor_parser" [1.307458] audit: type=1400 audit(1453110711.213:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=695 comm="apparmor_parser" [1.307467] audit: type=1400 audit(1453110711.213:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=695 comm="apparmor_parser" [1.560244] init: plymouth-upstart-bridge main process ended, respawning [ 1600.099759] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] [ 1600.100531] Modules linked in: nvidia(POE) drm pseries_rng rtc_generic [ 1600.100611] CPU: 0 PID: 15164 Comm: cicc Tainted: P OE 4.2.0-23-generic #28~14.04.1-Ubuntu [ 1600.100613] task: c390d3e0 ti: c39c8000 task.ti: c39c8000 [ 1600.100615] NIP: 103eadc8 LR: 103eb5e0 CTR: 103eb5a0 [ 1600.100622] REGS: c39cbea0 TRAP: 0901 Tainted: P OE (4.2.0-23-generic) [ 1600.100623] MSR: 80010280f033 CR: 4848 XER: [ 1600.100646] CFAR: 103eb5dc SOFTE: 1 [ 1600.100646] GPR00: 103eb5e0 3fffc0d01300 10ed2838 01000459e250 [ 1600.100646] GPR04: 0061 0100098e3ae0 [ 1600.100646] GPR08: 090c 0100045d8c00 01000459e308 07ff [ 1600.100646] GPR12: 4824 1006d750 [ 1600.100657] NIP [103eadc8] 0x103eadc8 [ 1600.100658] LR [103eb5e0] 0x103eb5e0 [ 1600.100659] Call Trace: [ 1672.099724] NMI watchdog: BUG: soft lockup - CPU#4 stuck for 32s! [cicc:15182] [ 1672.100995] Modules linked in: nvidia(POE) drm pseries_rng rtc_generic [ 1672.101033] CPU: 4 PID: 15182 Comm: cicc Tainted: P OEL 4.2.0-23-generic #28~14.04.1-Ubuntu [ 1672.101035] task: c0009c5328a0 ti: c306 task.ti: c306 [ 1672.101037] NIP: 11266b0c LR: 11266af4 CTR: 11266a70 [ 1672.101038] REGS: c3063ea0 TRAP: 0901 Tainted: P OEL (4.2.0-23-generic) [ 1672.101039] MSR: 80010280f033 CR: 28222422 XER: [ 1672.101046] CFAR: 112637b4 SOFTE: 1 [ 1672.101046] GPR00: 11266af4 37275860 11392800 01001e07e370 [ 1672.101046] GPR04: 0100 11389fb0 ff0c 01001e07e360 [ 1672.101046] GPR08: 0051 0001 01001b64b230 [ 1672.101046] GPR12: 2200 1006d750 [ 1672.101055] NIP [11266b0c] 0x11266b0c [ 1672.101056] LR [11266af4] 0x11266af4 [ 1672.101057] Call Trace: The nouveau modules are disabled, and nvidia drivers are loaded in the guest. # lsmod | grep nvidia nvidia 11484644 0 drm 447733 2 nvidia After downloading the CUDA Developer tool-kit, during the compilation the BUG is noticed. This issue is intermittently occurring, at some instances this issues isn't noticed. == Guest Details == # uname -a Linux ubuntu 4.2.0-23-generic #28~14.04.1-Ubuntu SMP Thu Dec 31 13:41:19 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux # lspci -nn 00:01.0 Ethernet controller [0200]: Red Hat, Inc Virtio network device [1af4:1000] 00:02.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f] 00:03.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block device [1af4:1001] 00:04.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon [1af4:1002] 00:05.0 3D controller [0302]: NVIDIA Corporation GK210GL [Tesla K80] [10de:102d] (rev a1) # cat /proc/driver/nvidia/version NVRM version: NVIDIA UNIX ppc64le Kernel Module 352.39 Fri Aug 14 17:10:41 PDT 2015 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) # nvcc -V nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 2005-2015 NVIDIA Corporat
[Kernel-packages] [Bug 1562004] Re: S390: glibc does not use direct socket-syscalls, but the multiplexer-socket-syscall.
** Package changed: ubuntu => linux (Ubuntu) -- 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/1562004 Title: S390: glibc does not use direct socket-syscalls, but the multiplexer- socket-syscall. Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Stefan Liebler - 2016-03-24 11:16:16 == Hi, the glibc socket functions, like connect(), bind(), socket(), ... do currently use svc 102 (multiplexer-socket-syscall: see /usr/include/s390x-linux-gnu/asm/unistd.h: #define __NR_socketcall 102) The direct socketsyscalls are also available for s390 since kernel 4.3: #define __NR_connect 362 #define __NR_bind 361 #define __NR_socket 359 ... The kernel in my used ubuntu alpha is 4.4.0-15 and the glibc 2.23. This glibc release can use these direct socket-syscalls, if glibc is configured with "--enable-kernel=4.3.0". Or even better, use the kernel-level, which will be used in the first release for s390. Here is the kernel commit: "s390: wire up separate socketcalls system calls" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=977108f89c989b1eeb5c8d938e1e71913391eb5f and the glibc commit: "S390: Call direct system calls for socket operations." https://sourceware.org/git/?p=glibc.git;a=commit;h=016495b818cb61df7d0d10e6db54074271b3e3a5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562004/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
Verified that the test case from comment #3 passes with 4.2.0-35.40. ** Tags removed: verification-needed-wily ** Tags added: verification-done-wily -- 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1560552] [NEW] ISST-LTE: pVM:high cpus number need a high crashkernel value in kdump
You have been subscribed to a public bug: The kdump kernel will be booted with "maxcpus=1", so no matter how many cpus this system has, only one cpu will be brought up during kdump I think. But on LPAR thymelp2, if we allocate 40 cpus on it, then kdump works just fine with 512M as crashkernel value. But if we allocate 200 cpus on it, kdump fails by trggering OOM. It has been proved that in latter situation we need 1.5G RAM reserved for kdump to let it works. Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com ---uname output--- Linux thymelp2 4.2.0-23-generic #28~14.04.1-Ubuntu SMP Thu Dec 31 13:41:19 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L, LPAR ---Debugger--- A debugger was configured, however the system did not enter into the debugger ---Steps to Reproduce--- 1. configure kdump with crashkernel=512M on thymelp2 2. allcoate 40 cpus on thymelp2 and trigger kdump 3. allocate 200 cpus on thymelp2 then do kdump again *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #1 - Nadia N. Fry - 2016-02-19 13:53:02 == Any update? == Comment: #2 - Hari Krishna Bathini - 2016-02-22 03:40:05 == Mahesh posted a patch upstream which should take care of this problem http://patchwork.ozlabs.org/patch/577193/ Thanks Hari ** Affects: linux (Ubuntu) Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged ** Tags: architecture-ppc64le bot-comment bugnameltc-137281 severity-high targetmilestone-inin--- -- ISST-LTE: pVM:high cpus number need a high crashkernel value in kdump https://bugs.launchpad.net/bugs/1560552 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1561507] [NEW] NVMe io requests gets broken down to 64k block requests
You have been subscribed to a public bug: == Comment: #0 - Breno Henrique Leitao - 2016-03-24 08:20:06 == The io requests to the NVMe device gets broken down to 64k requests I would like to ask Canonical to cherry pick the followng patch: commit 5f009d3f8e6685fe8c6215082c1696a08b411220 Author: Keith Busch Date: Wed Feb 10 16:52:47 2016 -0700 block: Initialize max_dev_sectors to 0 The new queue limit is not used by the majority of block drivers, and should be initialized to 0 for the driver's requested settings to be used. ** Affects: linux (Ubuntu) Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged ** Tags: architecture-ppc64 bot-comment bugnameltc-139617 severity-critical targetmilestone-inin--- -- NVMe io requests gets broken down to 64k block requests https://bugs.launchpad.net/bugs/1561507 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1562004] Re: S390: glibc does not use direct socket-syscalls, but the multiplexer-socket-syscall.
** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Dimitri John Ledkov (xnox) ** Package changed: linux (Ubuntu) => glibc (Ubuntu) -- 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/1562004 Title: S390: glibc does not use direct socket-syscalls, but the multiplexer- socket-syscall. Status in glibc package in Ubuntu: New Bug description: == Comment: #0 - Stefan Liebler - 2016-03-24 11:16:16 == Hi, the glibc socket functions, like connect(), bind(), socket(), ... do currently use svc 102 (multiplexer-socket-syscall: see /usr/include/s390x-linux-gnu/asm/unistd.h: #define __NR_socketcall 102) The direct socketsyscalls are also available for s390 since kernel 4.3: #define __NR_connect 362 #define __NR_bind 361 #define __NR_socket 359 ... The kernel in my used ubuntu alpha is 4.4.0-15 and the glibc 2.23. This glibc release can use these direct socket-syscalls, if glibc is configured with "--enable-kernel=4.3.0". Or even better, use the kernel-level, which will be used in the first release for s390. Here is the kernel commit: "s390: wire up separate socketcalls system calls" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=977108f89c989b1eeb5c8d938e1e71913391eb5f and the glibc commit: "S390: Call direct system calls for socket operations." https://sourceware.org/git/?p=glibc.git;a=commit;h=016495b818cb61df7d0d10e6db54074271b3e3a5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1562004/+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 1560552] Re: ISST-LTE: pVM:high cpus number need a high crashkernel value in kdump
** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- 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/1560552 Title: ISST-LTE: pVM:high cpus number need a high crashkernel value in kdump Status in linux package in Ubuntu: Triaged Bug description: The kdump kernel will be booted with "maxcpus=1", so no matter how many cpus this system has, only one cpu will be brought up during kdump I think. But on LPAR thymelp2, if we allocate 40 cpus on it, then kdump works just fine with 512M as crashkernel value. But if we allocate 200 cpus on it, kdump fails by trggering OOM. It has been proved that in latter situation we need 1.5G RAM reserved for kdump to let it works. Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com ---uname output--- Linux thymelp2 4.2.0-23-generic #28~14.04.1-Ubuntu SMP Thu Dec 31 13:41:19 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L, LPAR ---Debugger--- A debugger was configured, however the system did not enter into the debugger ---Steps to Reproduce--- 1. configure kdump with crashkernel=512M on thymelp2 2. allcoate 40 cpus on thymelp2 and trigger kdump 3. allocate 200 cpus on thymelp2 then do kdump again *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #1 - Nadia N. Fry - 2016-02-19 13:53:02 == Any update? == Comment: #2 - Hari Krishna Bathini - 2016-02-22 03:40:05 == Mahesh posted a patch upstream which should take care of this problem http://patchwork.ozlabs.org/patch/577193/ Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1560552/+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 1561507] Re: NVMe io requests gets broken down to 64k block requests
** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- 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/1561507 Title: NVMe io requests gets broken down to 64k block requests Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Breno Henrique Leitao - 2016-03-24 08:20:06 == The io requests to the NVMe device gets broken down to 64k requests I would like to ask Canonical to cherry pick the followng patch: commit 5f009d3f8e6685fe8c6215082c1696a08b411220 Author: Keith Busch Date: Wed Feb 10 16:52:47 2016 -0700 block: Initialize max_dev_sectors to 0 The new queue limit is not used by the majority of block drivers, and should be initialized to 0 for the driver's requested settings to be used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561507/+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 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
uname -a Linux 4.5.0-040500rc7-generic #201603061830 SMP Sun Mar 6 23:33:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux the issue (massive flickering, turning off) is still very much a problem. I'm on dell xps 13 with two dell monitors daisy chained. The second one is getting most of the flickering. -- 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/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: On a recent intel NUC using i915 graphics, I get the following errors in dmesg: [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! There are two monitors connected to this box, one with mini- HDMI->HDMI, one with mini-DP->HDMI cable. Maybe related: https://bugs.freedesktop.org/show_bug.cgi?id=80896 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic 3.19.0.26.25 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Wed Aug 26 10:07:31 2015 InstallationDate: Installed on 2015-08-01 (24 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+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 1546260] Re: kexec/kdump not working in ubuntu 16.04
** Also affects: kexec-tools (Ubuntu Xenial) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: Confirmed ** Changed in: kexec-tools (Ubuntu Xenial) Status: Confirmed => In Progress ** No longer affects: kexec-tools (Ubuntu Xenial) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1546260 Title: kexec/kdump not working in ubuntu 16.04 Status in kexec-tools package in Ubuntu: In Progress Bug description: == Comment: #0 - Praveen K. Pandey - 2016-02-04 04:11:48 == Hi I installed Ubuntu16.04 as PowerVM/KVM/PowerNV and setup kdump as well use PPA build to resolve sym link problem broken installed kdump- tools 1:1.5.9-4~lp1536904, and trigger kdump .While dumping process console hung not able to get vmcore. Reproducible Step: 1- Installed Ubuntu16.04 2- Installed PPA build of Kdump mentioned in bug135822 3- Start kdump service 4- Trigger a panic Expected Result : Able to generate kdump Actual Result : System halt on dump process , seems me having initrd issue LOG: root@ubuntu:~# kdump-config load Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic root=UUID=9d1662d4-db2a-4a1a-b8d7-8b0d4e7872dd ro splash quiet irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=156288K * loaded kdump kernel root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-2-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.4.0-2-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic root=UUID=2a78d070-4b73-4da6-b7eb-d41164c909fa ro splash quiet irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@ubuntu:~# root@ubuntu:~# kdump-config status current state : ready to kdump root@ubuntu:~# root@ubuntu:~# echo 1 > /proc/sys/kernel/sysrq root@ubuntu:~# echo c > /proc/sysrq-trigger [ 164.495349] sysrq: SysRq : Trigger a crash [ 164.495360] Unable to handle kernel paging request for data at address 0x [ 164.495364] Faulting instruction address: 0xc0654db4 [ 164.495368] Oops: Kernel access of bad area, sig: 11 [#1] [ 164.495370] SMP NR_CPUS=2048 NUMA pSeries [ 164.495374] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc uas usb_storage pseries_rng rtc_generic autofs4 ibmvscsi ibmveth [ 164.495389] CPU: 0 PID: 1281 Comm: bash Not tainted 4.4.0-2-generic #16-Ubuntu [ 164.495393] task: c003f1f2a200 ti: c6ef8000 task.ti: c6ef8000 [ 164.495396] NIP: c0654db4 LR: c0655e68 CTR: c0654d80 [ 164.495399] REGS: c6efb990 TRAP: 0300 Not tainted (4.4.0-2-generic) [ 164.495401] MSR: 80009033 CR: 2824 XER: 0001 [ 164.495410] CFAR: c0008468 DAR: DSISR: 4200 SOFTE: 1 GPR00: c0655e68 c6efbc10 c1583800 0063 GPR04: c003ff609c50 c003ff61b4f0 c003ffe6c200 015b GPR08: 0007 0001 c003ffe72710 GPR12: c0654d80 c7ae 2200 GPR16: 10170710 01002c890608 101406f0 100c7100 GPR20: 1017df98 10140588 GPR24: 10153440 1017b848 c14c8540 0004 GPR28: c14c8900 0063 c14810bc [ 164.495451] NIP [c0654db4] sysrq_handle_crash+0x34/0x50 [ 164.495454] LR [c0655e68] __handle_sysrq+0xe8/0x270 [ 164.495456] Call Trace: [ 164.495460] [c6efbc10] [c0de3008] _fw_tigon_tg3_bin_name+0x2cc30/0x33d18 (unreliable) [ 164.495464] [c6efbc30] [c0655e68] __handle_sysrq+0xe8/0x270 [ 164.495468] [c6efbcd0] [c0656608] write_sysrq_trigger+0x78/0xa0 [ 164.495472] [c6efbd00] [c0374e70] proc_reg_write+0xb0/0x110 [ 164.495476] [c6efbd50] [c02dcabc] __vfs_write+0x6c/0xe0 [ 164.495480] [c6efbd90] [c02dd7f0] vfs_write+0xc0/0x230 [ 164.495484] [c6efbde0] [c02de82c] SyS_write+0x6c/0x110 [ 164.495488] [c6efbe30] [c0009204] system_call+0x38/0xb4 [ 164.495490] Instruction dump: [ 164.495493] 3842ea80 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 394956e4 [ 164.495499] 3921 912a 7c0004ac 3940 <
[Kernel-packages] [Bug 1348890] Re: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event
Workaround for X455LB-WX034D: The keyboard has no backlight, but Fn+F3 & Fn+F4 generates keyboard brightness events which can be remapped to replace Fn+F5 & Fn+F6. -- 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/1348890 Title: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello Community, It seems brightness keys don't work with latest Ubuntu 14.04 LTS for laptop Asus Zenbook UX32LN. sudo dmidecode -s bios-version UX32LN.203 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1348890/+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 1546260] Re: kexec/kdump not working in ubuntu 16.04
Hello, I have a new test package ready for testing if you are able to verify. I included the three upstream commits. I haven't identified the changes made to the purgatory/arch/ppc64/Makefile file (part of the rebase tarfile) so those are not included. Since you are already using the PPA that contains kdump-tools 1:1.5.9-4~lp1536904, I can make the test package available there so you can test without having to add a new PPA. You should be aware though that you should no longer use that PPA. The modifications made to kexec-tools are now present in the public archive. in the 1:1.5.9-5 package. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1546260 Title: kexec/kdump not working in ubuntu 16.04 Status in kexec-tools package in Ubuntu: In Progress Bug description: == Comment: #0 - Praveen K. Pandey - 2016-02-04 04:11:48 == Hi I installed Ubuntu16.04 as PowerVM/KVM/PowerNV and setup kdump as well use PPA build to resolve sym link problem broken installed kdump- tools 1:1.5.9-4~lp1536904, and trigger kdump .While dumping process console hung not able to get vmcore. Reproducible Step: 1- Installed Ubuntu16.04 2- Installed PPA build of Kdump mentioned in bug135822 3- Start kdump service 4- Trigger a panic Expected Result : Able to generate kdump Actual Result : System halt on dump process , seems me having initrd issue LOG: root@ubuntu:~# kdump-config load Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic root=UUID=9d1662d4-db2a-4a1a-b8d7-8b0d4e7872dd ro splash quiet irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=156288K * loaded kdump kernel root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-2-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.4.0-2-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic root=UUID=2a78d070-4b73-4da6-b7eb-d41164c909fa ro splash quiet irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@ubuntu:~# root@ubuntu:~# kdump-config status current state : ready to kdump root@ubuntu:~# root@ubuntu:~# echo 1 > /proc/sys/kernel/sysrq root@ubuntu:~# echo c > /proc/sysrq-trigger [ 164.495349] sysrq: SysRq : Trigger a crash [ 164.495360] Unable to handle kernel paging request for data at address 0x [ 164.495364] Faulting instruction address: 0xc0654db4 [ 164.495368] Oops: Kernel access of bad area, sig: 11 [#1] [ 164.495370] SMP NR_CPUS=2048 NUMA pSeries [ 164.495374] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc uas usb_storage pseries_rng rtc_generic autofs4 ibmvscsi ibmveth [ 164.495389] CPU: 0 PID: 1281 Comm: bash Not tainted 4.4.0-2-generic #16-Ubuntu [ 164.495393] task: c003f1f2a200 ti: c6ef8000 task.ti: c6ef8000 [ 164.495396] NIP: c0654db4 LR: c0655e68 CTR: c0654d80 [ 164.495399] REGS: c6efb990 TRAP: 0300 Not tainted (4.4.0-2-generic) [ 164.495401] MSR: 80009033 CR: 2824 XER: 0001 [ 164.495410] CFAR: c0008468 DAR: DSISR: 4200 SOFTE: 1 GPR00: c0655e68 c6efbc10 c1583800 0063 GPR04: c003ff609c50 c003ff61b4f0 c003ffe6c200 015b GPR08: 0007 0001 c003ffe72710 GPR12: c0654d80 c7ae 2200 GPR16: 10170710 01002c890608 101406f0 100c7100 GPR20: 1017df98 10140588 GPR24: 10153440 1017b848 c14c8540 0004 GPR28: c14c8900 0063 c14810bc [ 164.495451] NIP [c0654db4] sysrq_handle_crash+0x34/0x50 [ 164.495454] LR [c0655e68] __handle_sysrq+0xe8/0x270 [ 164.495456] Call Trace: [ 164.495460] [c6efbc10] [c0de3008] _fw_tigon_tg3_bin_name+0x2cc30/0x33d18 (unreliable) [ 164.495464] [c6efbc30] [c0655e68] __handle_sysrq+0xe8/0x270 [ 164.495468] [c6efbcd0] [c0656608] write_sysrq_trigger+0x78/0xa0 [ 164.495472] [c6efbd00] [c0374e70] proc_reg_write+0xb0/0x110 [ 164.495476] [c6efbd50] [c02dcabc] __vfs_write+0x6c/0xe0 [ 164.495480] [c6efbd90] [c02dd7f0] vfs_write+0xc0/0x230 [ 164.495
[Kernel-packages] [Bug 1557379] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] noticed during compilation of CUDA Toolkit
It sounds like this is a regression based on Comment 15 in the description: - SUDIPTO GHOSH - 2016-02-16 03:23:34 == Based on the last 2 comments, it seems that the issue exists with Ubuntu 14.04.04 (as per Santwana's tests) & does not exist in 14.04.03 (per Sam's test). Since this is a regression and now fixed in 14.04.4, We should be able to perform a reverse bisect to identify the commit(s) that fix this bug. Can you test the following kernels and post back back? We need to identify the last kernel that had the bug, and the first kernel that does not have the bug: 4.0: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/ 4.1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-wily/ 4.2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-wily/ -- 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/1557379 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] noticed during compilation of CUDA Toolkit Status in linux package in Ubuntu: New Bug description: == Comment: #0 - SANTWANA SAMANTRAY - 2016-01-18 05:50:42 == During compilation of NVIDIA_CUDA-7.5 Toolkit Samples, in Ubuntu14.04.04 Guest, the below BUG is noticed. [1.077464] NVRM: loading NVIDIA UNIX ppc64le Kernel Module 352.39 Fri Aug 14 17:10:41 PDT 2015 [1.211127] init: failsafe main process (498) killed by TERM signal [1.307135] audit: type=1400 audit(1453110711.213:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=697 comm="apparmor_parser" [1.307458] audit: type=1400 audit(1453110711.213:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=695 comm="apparmor_parser" [1.307467] audit: type=1400 audit(1453110711.213:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=695 comm="apparmor_parser" [1.560244] init: plymouth-upstart-bridge main process ended, respawning [ 1600.099759] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] [ 1600.100531] Modules linked in: nvidia(POE) drm pseries_rng rtc_generic [ 1600.100611] CPU: 0 PID: 15164 Comm: cicc Tainted: P OE 4.2.0-23-generic #28~14.04.1-Ubuntu [ 1600.100613] task: c390d3e0 ti: c39c8000 task.ti: c39c8000 [ 1600.100615] NIP: 103eadc8 LR: 103eb5e0 CTR: 103eb5a0 [ 1600.100622] REGS: c39cbea0 TRAP: 0901 Tainted: P OE (4.2.0-23-generic) [ 1600.100623] MSR: 80010280f033 CR: 4848 XER: [ 1600.100646] CFAR: 103eb5dc SOFTE: 1 [ 1600.100646] GPR00: 103eb5e0 3fffc0d01300 10ed2838 01000459e250 [ 1600.100646] GPR04: 0061 0100098e3ae0 [ 1600.100646] GPR08: 090c 0100045d8c00 01000459e308 07ff [ 1600.100646] GPR12: 4824 1006d750 [ 1600.100657] NIP [103eadc8] 0x103eadc8 [ 1600.100658] LR [103eb5e0] 0x103eb5e0 [ 1600.100659] Call Trace: [ 1672.099724] NMI watchdog: BUG: soft lockup - CPU#4 stuck for 32s! [cicc:15182] [ 1672.100995] Modules linked in: nvidia(POE) drm pseries_rng rtc_generic [ 1672.101033] CPU: 4 PID: 15182 Comm: cicc Tainted: P OEL 4.2.0-23-generic #28~14.04.1-Ubuntu [ 1672.101035] task: c0009c5328a0 ti: c306 task.ti: c306 [ 1672.101037] NIP: 11266b0c LR: 11266af4 CTR: 11266a70 [ 1672.101038] REGS: c3063ea0 TRAP: 0901 Tainted: P OEL (4.2.0-23-generic) [ 1672.101039] MSR: 80010280f033 CR: 28222422 XER: [ 1672.101046] CFAR: 112637b4 SOFTE: 1 [ 1672.101046] GPR00: 11266af4 37275860 11392800 01001e07e370 [ 1672.101046] GPR04: 0100 11389fb0 ff0c 01001e07e360 [ 1672.101046] GPR08: 0051 0001 01001b64b230 [ 1672.101046] GPR12: 2200 1006d750 [ 1672.101055] NIP [11266b0c] 0x11266b0c [ 1672.101056] LR [11266af4] 0x11266af4 [ 1672.101057] Call Trace: The nouveau modules are disabled, and nvidia drivers are loaded in the guest. # lsmod | grep nvidia nvidia 11484644 0 drm 447733 2 nvidia After downloading the CUDA Developer tool-kit, during the compilation the BUG is noticed. This issue is intermittently occurring, at some instances this issues isn't noticed. == Guest Details == # uname -a Linux ubuntu 4.2.0-23-generic #28~14.04.1-Ubuntu SMP Thu Dec 31 13:41:19 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux # lspci -nn 00:01.0 Ethernet controller [0200]: Red Hat, Inc Virti
[Kernel-packages] [Bug 1561998] Re: package linux-headers-3.19.0-47 (not installed) failed to install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: fsys-tarfile-error ** Changed in: linux-lts-vivid (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1561998 Title: package linux-headers-3.19.0-47 (not installed) failed to install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 Status in linux-lts-vivid package in Ubuntu: Invalid Bug description: updgrade error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-headers-3.19.0-47 (not installed) ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10 Uname: Linux 3.19.0-47-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Fri Mar 25 14:48:04 2016 DuplicateSignature: package:linux-headers-3.19.0-47:(not installed):il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 ErrorMessage: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 InstallationDate: Installed on 2015-10-18 (159 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: linux-lts-vivid Title: package linux-headers-3.19.0-47 (not installed) failed to install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1561998/+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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
I tested CentOS 7 with LIS 4.0.11 overnight, and it also did not exhibit the bug. I will test LIS 4.1 next. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+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 1562076] [NEW] Ubuntu freezes a few seconds after plugin a screen
Public bug reported: Hello, I'm running the latest beta of Ubuntu 16.04 Xenial on an ASUS UX303LA (Intel i5 6200U, Intel HD 520) and each time I plug a screen, using either HDMI or Mini DisplayPort, my laptop freezes after a few seconds. Alt + Function keys doesn't work, sound stops and I'm forced to shutdown the computer by long-pressing its Power button. I attached syslog, kern.log and Xorg.0.log for further information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 1632 F pulseaudio CurrentDesktop: GNOME Date: Fri Mar 25 17:34:54 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2acdb9a2-2923-4550-9019-32e79d136c4d InstallationDate: Installed on 2016-02-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303UA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=de727ab1-db17-453b-a371-4a143f37dcad ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-25 (28 days ago) dmi.bios.date: 08/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303UA.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303UA.202:bd08/27/2015:svnASUSTeKCOMPUTERINC.:pnUX303UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1562076/+attachment/4611412/+files/syslog -- 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/1562076 Title: Ubuntu freezes a few seconds after plugin a screen Status in linux package in Ubuntu: New Bug description: Hello, I'm running the latest beta of Ubuntu 16.04 Xenial on an ASUS UX303LA (Intel i5 6200U, Intel HD 520) and each time I plug a screen, using either HDMI or Mini DisplayPort, my laptop freezes after a few seconds. Alt + Function keys doesn't work, sound stops and I'm forced to shutdown the computer by long-pressing its Power button. I attached syslog, kern.log and Xorg.0.log for further information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 1632 F pulseaudio CurrentDesktop: GNOME Date: Fri Mar 25 17:34:54 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2acdb9a2-2923-4550-9019-32e79d136c4d InstallationDate: Installed on 2016-02-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303UA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=de727ab1-db17-453b-a371-4a143f37dcad ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-25 (28 days ago) dmi.bios.date: 08/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303UA.202 dmi.board.asset.tag: ATN12345678901234567 dm
[Kernel-packages] [Bug 1562076] Re: Ubuntu freezes a few seconds after plugin a screen
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562076/+attachment/4611427/+files/kern.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/1562076 Title: Ubuntu freezes a few seconds after plugin a screen Status in linux package in Ubuntu: New Bug description: Hello, I'm running the latest beta of Ubuntu 16.04 Xenial on an ASUS UX303LA (Intel i5 6200U, Intel HD 520) and each time I plug a screen, using either HDMI or Mini DisplayPort, my laptop freezes after a few seconds. Alt + Function keys doesn't work, sound stops and I'm forced to shutdown the computer by long-pressing its Power button. I attached syslog, kern.log and Xorg.0.log for further information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 1632 F pulseaudio CurrentDesktop: GNOME Date: Fri Mar 25 17:34:54 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2acdb9a2-2923-4550-9019-32e79d136c4d InstallationDate: Installed on 2016-02-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303UA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=de727ab1-db17-453b-a371-4a143f37dcad ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-25 (28 days ago) dmi.bios.date: 08/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303UA.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303UA.202:bd08/27/2015:svnASUSTeKCOMPUTERINC.:pnUX303UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562076/+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 1562076] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1562076 Title: Ubuntu freezes a few seconds after plugin a screen Status in linux package in Ubuntu: Confirmed Bug description: Hello, I'm running the latest beta of Ubuntu 16.04 Xenial on an ASUS UX303LA (Intel i5 6200U, Intel HD 520) and each time I plug a screen, using either HDMI or Mini DisplayPort, my laptop freezes after a few seconds. Alt + Function keys doesn't work, sound stops and I'm forced to shutdown the computer by long-pressing its Power button. I attached syslog, kern.log and Xorg.0.log for further information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 1632 F pulseaudio CurrentDesktop: GNOME Date: Fri Mar 25 17:34:54 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2acdb9a2-2923-4550-9019-32e79d136c4d InstallationDate: Installed on 2016-02-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303UA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=de727ab1-db17-453b-a371-4a143f37dcad ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-25 (28 days ago) dmi.bios.date: 08/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303UA.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303UA.202:bd08/27/2015:svnASUSTeKCOMPUTERINC.:pnUX303UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562076/+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 1562093] [NEW] [Dell Inc. XPS 13 9350] hibernate/resume failure
Public bug reported: sudo pm-hibernate failed. ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1491 F pulseaudio johan 2042 F pulseaudio Date: Fri Mar 25 18:30:46 2016 DuplicateSignature: hibernate/resume:Dell Inc. XPS 13 9350:1.2.3 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=d7490964-39a3-44ea-aded-1cceaead466d InstallationDate: Installed on 2016-01-10 (74 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterpreterPath: /usr/bin/python3.5 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=sv_SE.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic root=/dev/mapper/lvm--vg-ubuntu--root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux Title: [Dell Inc. XPS 13 9350] hibernate/resume failure UpgradeStatus: Upgraded to xenial on 2016-02-09 (44 days ago) UserGroups: dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0VM5NC dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops hibernate resume xenial -- 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/1562093 Title: [Dell Inc. XPS 13 9350] hibernate/resume failure Status in linux package in Ubuntu: New Bug description: sudo pm-hibernate failed. ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1491 F pulseaudio johan 2042 F pulseaudio Date: Fri Mar 25 18:30:46 2016 DuplicateSignature: hibernate/resume:Dell Inc. XPS 13 9350:1.2.3 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=d7490964-39a3-44ea-aded-1cceaead466d InstallationDate: Installed on 2016-01-10 (74 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterpreterPath: /usr/bin/python3.5 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=sv_SE.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic root=/dev/mapper/lvm--vg-ubuntu--root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux Title: [Dell Inc. XPS 13 9350] hibernate/resume failure UpgradeStatus: Upgraded to xenial on 2016-02-09 (44 days ago) UserGroups: dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.
[Kernel-packages] [Bug 1562093] Re: [Dell Inc. XPS 13 9350] hibernate/resume failure
Computer does not power down after pm-hibernate command. After reboot I created this report. -- 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/1562093 Title: [Dell Inc. XPS 13 9350] hibernate/resume failure Status in linux package in Ubuntu: New Bug description: sudo pm-hibernate failed. ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1491 F pulseaudio johan 2042 F pulseaudio Date: Fri Mar 25 18:30:46 2016 DuplicateSignature: hibernate/resume:Dell Inc. XPS 13 9350:1.2.3 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=d7490964-39a3-44ea-aded-1cceaead466d InstallationDate: Installed on 2016-01-10 (74 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterpreterPath: /usr/bin/python3.5 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=sv_SE.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic root=/dev/mapper/lvm--vg-ubuntu--root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux Title: [Dell Inc. XPS 13 9350] hibernate/resume failure UpgradeStatus: Upgraded to xenial on 2016-02-09 (44 days ago) UserGroups: dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0VM5NC dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562093/+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 1562093] Re: [Dell Inc. XPS 13 9350] hibernate/resume failure
** Tags removed: need-duplicate-check -- 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/1562093 Title: [Dell Inc. XPS 13 9350] hibernate/resume failure Status in linux package in Ubuntu: New Bug description: sudo pm-hibernate failed. ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1491 F pulseaudio johan 2042 F pulseaudio Date: Fri Mar 25 18:30:46 2016 DuplicateSignature: hibernate/resume:Dell Inc. XPS 13 9350:1.2.3 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=d7490964-39a3-44ea-aded-1cceaead466d InstallationDate: Installed on 2016-01-10 (74 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterpreterPath: /usr/bin/python3.5 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=sv_SE.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic root=/dev/mapper/lvm--vg-ubuntu--root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux Title: [Dell Inc. XPS 13 9350] hibernate/resume failure UpgradeStatus: Upgraded to xenial on 2016-02-09 (44 days ago) UserGroups: dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0VM5NC dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562093/+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 1562093] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1562093 Title: [Dell Inc. XPS 13 9350] hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: sudo pm-hibernate failed. ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1491 F pulseaudio johan 2042 F pulseaudio Date: Fri Mar 25 18:30:46 2016 DuplicateSignature: hibernate/resume:Dell Inc. XPS 13 9350:1.2.3 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=d7490964-39a3-44ea-aded-1cceaead466d InstallationDate: Installed on 2016-01-10 (74 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterpreterPath: /usr/bin/python3.5 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=sv_SE.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic root=/dev/mapper/lvm--vg-ubuntu--root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux Title: [Dell Inc. XPS 13 9350] hibernate/resume failure UpgradeStatus: Upgraded to xenial on 2016-02-09 (44 days ago) UserGroups: dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0VM5NC dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562093/+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 1558897] Re: guest vm hangs
apport information ** Tags added: apport-collected xenial ** Description changed: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc s
[Kernel-packages] [Bug 1558897] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1558897/+attachment/4611594/+files/JournalErrors.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/1558897 Title: guest vm hangs Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp coretemp punit_atom_debug crc
[Kernel-packages] [Bug 1558897] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1558897/+attachment/4611590/+files/CRDA.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/1558897 Title: guest vm hangs Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32
[Kernel-packages] [Bug 1558897] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1558897/+attachment/4611597/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1558897 Title: guest vm hangs Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10d
[Kernel-packages] [Bug 1558897] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1558897/+attachment/4611591/+files/Card0.Codecs.codec.0.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/1558897 Title: guest vm hangs Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp coretemp punit_
[Kernel-packages] [Bug 1558897] Card0.Codecs.codec.2.txt
apport information ** Attachment added: "Card0.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/1558897/+attachment/4611592/+files/Card0.Codecs.codec.2.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/1558897 Title: guest vm hangs Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp coretemp punit_
[Kernel-packages] [Bug 1558897] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1558897/+attachment/4611596/+files/PciMultimedia.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/1558897 Title: guest vm hangs Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp coretemp punit_atom_debug crc
[Kernel-packages] [Bug 1558897] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1558897/+attachment/4611593/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1558897 Title: guest vm hangs Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct1
[Kernel-packages] [Bug 1558897] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1558897/+attachment/4611595/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1558897 Title: guest vm hangs Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc
[Kernel-packages] [Bug 1558897] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1558897/+attachment/4611602/+files/WifiSyslog.txt ** 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/1558897 Title: guest vm hangs Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ge
[Kernel-packages] [Bug 1558897] RelatedPackageVersions.txt
apport information ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/1558897/+attachment/4611600/+files/RelatedPackageVersions.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/1558897 Title: guest vm hangs Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp coretemp pu
[Kernel-packages] [Bug 1558897] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1558897/+attachment/4611601/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1558897 Title: guest vm hangs Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul c
[Kernel-packages] [Bug 1558897] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1558897/+attachment/4611598/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1558897 Title: guest vm hangs Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp coretemp punit_atom_debug c
[Kernel-packages] [Bug 1558897] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1558897/+attachment/4611599/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1558897 Title: guest vm hangs Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at /build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 vmx_handle_exit+0x9ed/0xc30 [kvm_intel]() Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3 Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack i pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_ generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core snd_soc_rt5670 snd_soc_rl6 231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 dw_dmac_core rfkill _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sy sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015 Mar 18 09:52:55 OUVS1 kernel: [67330.365525] 0286 6642abe7 88007610bc10 813e2483 Mar 18 09:52:55 OUVS1 kernel: [67330.365549] 88007610bc58 c0356528 88007610bc48 8107fe12 Mar 18 09:52:55 OUVS1 kernel: [67330.365575] 0003 880076958000 88007695b1a0 Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace: Mar 18 09:52:55 OUVS1 kernel: [67330.365635] [] dump_stack+0x63/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.365657] [] warn_slowpath_common+0x82/0xc0 Mar 18 09:52:55 OUVS1 kernel: [67330.365680] [] warn_slowpath_fmt+0x5c/0x80 Mar 18 09:52:55 OUVS1 kernel: [67330.365734] [] ? kvm_sched_in+0x39/0x40 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365745] [] vmx_handle_exit+0x9ed/0xc30 [kvm_intel] Mar 18 09:52:55 OUVS1 kernel: [67330.365785] [] ? kvm_write_guest_cached+0x68/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365817] [] ? kvm_lapic_sync_from_vapic+0xac/0x180 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365846] [] vcpu_enter_guest+0x79d/0x1060 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365877] [] ? kvm_apic_has_interrupt+0x45/0xc0 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365907] [] kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365935] [] kvm_vcpu_ioctl+0x33d/0x620 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.365943] [] ? do_futex+0x107/0x500 Mar 18 09:52:55 OUVS1 kernel: [67330.365967] [] ? wake_up_q+0x70/0x70 Mar 18 09:52:55 OUVS1 kernel: [67330.365993] [] do_vfs_ioctl+0x29f/0x490 Mar 18 09:52:55 OUVS1 kernel: [67330.366039] [] ? kvm_on_user_return+0x6f/0x80 [kvm] Mar 18 09:52:55 OUVS1 kernel: [67330.366048] [] ? fire_user_return_notifiers+0x3b/0x50 Mar 18 09:52:55 OUVS1 kernel: [67330.366070] [] SyS_ioctl+0x79/0x90 Mar 18 09:52:55 OUVS1 kernel: [67330.366098] [] entry_SYSCALL_64_fastpath+0x16/0x71 Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 ]--- Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [qemu-system-x86:5187] Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp coretemp punit_atom_debug crct10d
[Kernel-packages] [Bug 1562135] [NEW] Restore ti-connectivity/wl18xx-conf.bin in trusty
Public bug reported: This was removed in 1.127.21 but should not have been. Put it back. ** Affects: linux-firmware (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: Invalid ** Affects: linux-firmware (Ubuntu Trusty) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: linux-firmware (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux-firmware (Ubuntu Trusty) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Trusty) Assignee: (unassigned) => Seth Forshee (sforshee) -- 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/1562135 Title: Restore ti-connectivity/wl18xx-conf.bin in trusty Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Trusty: In Progress Bug description: This was removed in 1.127.21 but should not have been. Put it back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1562135/+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 1549354] Re: After upgrading to 4.2.0.30 Elantech touchpad not detected
I confirm that commit a7dbd2e3268627cedc6b10adc39b5e544a71655f works. -- 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/1549354 Title: After upgrading to 4.2.0.30 Elantech touchpad not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Bug description: Elan Touchpad not listed as "Elan Touchpad" after "xinput list" or "cat /proc/bus/input/devices" . Not detected properly? For sure it does not work. External mouse working well. Downgrading to 4.2.0-27-generic kernel solves problem(touchpad works). My computer model is Toshiba Chromebook 2 with Gnome ubuntu 15.10 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-30-generic 4.2.0-30.35 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: siulkilulki909 F pulseaudio CurrentDesktop: GNOME Date: Wed Feb 24 16:55:47 2016 InstallationDate: Installed on 2015-12-06 (80 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 04f2:b48b Chicony Electronics Co., Ltd Bus 001 Device 002: ID 1ea7:0011 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Swanky ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=20463b36-edda-428c-a236-f715f1d7bb85 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-30-generic N/A linux-backports-modules-4.2.0-30-generic N/A linux-firmware1.149.3 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: 08/22/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/22/2014:svnGOOGLE:pnSwanky:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Swanky dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1549354/+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 1562135] Re: Restore ti-connectivity/wl18xx-conf.bin in trusty
** Description changed: - This was removed in 1.127.21 but should not have been. Put it back. + This was removed by an upstream commit cherry-picked for lts-xenial. + It's unclear whether or not it's really needed, but we should put it + back to avoid any potential for SRU regressions. -- 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/1562135 Title: Restore ti-connectivity/wl18xx-conf.bin in trusty Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Trusty: In Progress Bug description: This was removed by an upstream commit cherry-picked for lts-xenial. It's unclear whether or not it's really needed, but we should put it back to avoid any potential for SRU regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1562135/+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 1376581] Re: DisplayPort monitor not properly detected via HP ultraslim docking station 2013
Seems to be fixed in the 16.04 (Xenial Xerus) Beta 1. I assume the fix will make its way through the final release. Hooray! :) -- 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/1376581 Title: DisplayPort monitor not properly detected via HP ultraslim docking station 2013 Status in linux package in Ubuntu: Confirmed Bug description: DisplayPort monitor not properly detected via HP ultraslim docking station 2013 My configuration: - Ubuntu 14.04, with all updates (3.13.0-36.63-generic 3.13.11.6) - EliteBook 850 G1 connected to a HP ultraslim docking station 2013. - 1 Dell 2209WA connected to the VGA port of the docking - 1 Dell P2414H connected to the DP of the docking Currently I have the lateste fglrx (14.301.1001), but if was the same with the version from Ubuntu repo. This is the output from xrandr: Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192 eDP1 connected (normal left inverted right x axis y axis) 1920x1080 60.4 + 59.9 40.3 1680x1050 60.0 59.9 1600x1024 60.2 1400x1050 60.0 1280x1024 60.0 1440x900 59.9 1280x960 60.0 1360x768 59.8 60.0 1152x864 60.0 1024x768 60.0 800x60060.3 56.2 640x48059.9 DP1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) DP2 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm 1680x1050 60.0*+ 1280x1024 75.0 60.0 1152x864 75.0 1024x768 75.1 60.0 800x60075.0 60.3 640x48075.0 60.0 720x40070.1 HDMI2 disconnected (normal left inverted right x axis y axis) There is some scrambled image displayed on the DP monitor like in the attached image. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: amaguran 2383 F pulseaudio /dev/snd/controlC2: amaguran 2383 F pulseaudio /dev/snd/controlC0: amaguran 2383 F pulseaudio /dev/snd/controlC1: amaguran 2383 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-08 (135 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP EliteBook 850 G1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=UUID=26de6228-15cb-4089-8788-f4a0fd918347 ro splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: Oct 22 09:44:23 amaguran-laptop kernel: [ 1602.950963] [UFW BLOCK] IN=eth0 OUT= MAC=28:80:23:04:15:1e:f0:1f:af:66:73:e1:08:00 SRC=10.240.11.1 DST=10.240.11.52 LEN=139 TOS=0x00 PREC=0x00 TTL=128 ID=32371 PROTO=UDP SPT=34761 DPT=29889 LEN=119 Oct 22 09:44:29 amaguran-laptop kernel: [ 1608.999016] [UFW BLOCK] IN=eth0 OUT= MAC=28:80:23:04:15:1e:f0:1f:af:66:73:e1:08:00 SRC=10.240.11.1 DST=10.240.11.52 LEN=139 TOS=0x00 PREC=0x00 TTL=128 ID=32385 PROTO=UDP SPT=34761 DPT=29889 LEN=119 _MarkForUpload: True dmi.bios.date: 07/28/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.20 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.55 dmi.chassis.asset.tag: CNU4199369 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.20:bd07/28/2014:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.55:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 850 G1 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: amaguran 2383 F pulseaudio /dev/snd/controlC2: amaguran 2383 F pulseaudio /dev/snd/controlC0: amaguran 2383 F pulseaudio /dev/snd/controlC1: amaguran 2383 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-08 (135 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP EliteBook 850 G1 Package: linux (not i
[Kernel-packages] [Bug 1562155] [NEW] Touchpad stopped functioning after kernel update for Dell Chromebook "Candy"
Public bug reported: Upon successful installation of Ubuntu 15.10, I ran the usual updates and after restarting, the touchpad stopped working. I booted into kernel version 4.2.0-16 instead of the updated kernel 4.2.0-34, and the touchpad that had stopped working functioned as usual once more. Changing back into the latest kernel disabled the touchpad once more. I am installing Ubuntu on the Dell Chromebook 11 "Candy" running Intel Celeron(R) CPU N2840 (Baytrail) processor. This deployment is being used for several lab machines of the same model. Steps to reproduce: 1. Install Ubuntu 15.10. 2. Run update. Expected: 1. All hardware to work prior to update. Instead: 1. Touchpad stopped working. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-34-generic 4.2.0-34.39 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: unllife121l980 F pulseaudio Date: Fri Mar 25 15:33:10 2016 HibernationDevice: RESUME=UUID=44e6cef0-6fe7-4afe-a5f9-0a8d60224b28 InstallationDate: Installed on 2016-03-24 (0 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: GOOGLE Candy ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic root=UUID=a7c1001c-8167-4541-b62e-e2cf805003d8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-34-generic N/A linux-backports-modules-4.2.0-34-generic N/A linux-firmware1.149.3 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: 11/20/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd11/20/2014:svnGOOGLE:pnCandy:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Candy dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1562155 Title: Touchpad stopped functioning after kernel update for Dell Chromebook "Candy" Status in linux package in Ubuntu: New Bug description: Upon successful installation of Ubuntu 15.10, I ran the usual updates and after restarting, the touchpad stopped working. I booted into kernel version 4.2.0-16 instead of the updated kernel 4.2.0-34, and the touchpad that had stopped working functioned as usual once more. Changing back into the latest kernel disabled the touchpad once more. I am installing Ubuntu on the Dell Chromebook 11 "Candy" running Intel Celeron(R) CPU N2840 (Baytrail) processor. This deployment is being used for several lab machines of the same model. Steps to reproduce: 1. Install Ubuntu 15.10. 2. Run update. Expected: 1. All hardware to work prior to update. Instead: 1. Touchpad stopped working. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-34-generic 4.2.0-34.39 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: unllife121l980 F pulseaudio Date: Fri Mar 25 15:33:10 2016 HibernationDevice: RESUME=UUID=44e6cef0-6fe7-4afe-a5f9-0a8d60224b28 InstallationDate: Installed on 2016-03-24 (0 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: GOOGLE Candy ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic root=UUID=a7c1001c-8167-4541-b62e-e2cf805003d8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-34-generic N/A linux-backports-modules-4.2.0-34-generic N/A linux-firmware1.149.3 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: 11/20/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd11/20/2014:svnGOOG
[Kernel-packages] [Bug 1562155] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1562155 Title: Touchpad stopped functioning after kernel update for Dell Chromebook "Candy" Status in linux package in Ubuntu: Confirmed Bug description: Upon successful installation of Ubuntu 15.10, I ran the usual updates and after restarting, the touchpad stopped working. I booted into kernel version 4.2.0-16 instead of the updated kernel 4.2.0-34, and the touchpad that had stopped working functioned as usual once more. Changing back into the latest kernel disabled the touchpad once more. I am installing Ubuntu on the Dell Chromebook 11 "Candy" running Intel Celeron(R) CPU N2840 (Baytrail) processor. This deployment is being used for several lab machines of the same model. Steps to reproduce: 1. Install Ubuntu 15.10. 2. Run update. Expected: 1. All hardware to work prior to update. Instead: 1. Touchpad stopped working. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-34-generic 4.2.0-34.39 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: unllife121l980 F pulseaudio Date: Fri Mar 25 15:33:10 2016 HibernationDevice: RESUME=UUID=44e6cef0-6fe7-4afe-a5f9-0a8d60224b28 InstallationDate: Installed on 2016-03-24 (0 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: GOOGLE Candy ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic root=UUID=a7c1001c-8167-4541-b62e-e2cf805003d8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-34-generic N/A linux-backports-modules-4.2.0-34-generic N/A linux-firmware1.149.3 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: 11/20/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd11/20/2014:svnGOOGLE:pnCandy:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Candy dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562155/+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 1552155] Re: linux-firmware: need to look at what if any updates needed for lts-xenial in trusty
I did some preliminary testing on a Skylake machine running Trusty with the lts-xenial kernel. With both the 1.127.20 and 1.127.21 versions of linux-firmware I was able to suspend/resume and there were no warnings or BUG() in dmesg. -- 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/1552155 Title: linux-firmware: need to look at what if any updates needed for lts- xenial in trusty Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Trusty: Fix Committed Bug description: We are now publishing a beta version of lts-xenial in trusty. This normally means we need to think about linux-firmware updates to support this. Track that activity here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1552155/+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 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported
Dennis Do you still use the skip_otp=Y parameter with kernel 4.5? -- 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/1520343 Title: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported Status in linux package in Ubuntu: Confirmed Bug description: --- STATUS 2016-03-17: == WARNING: You need at least kernel 4.5.0 for the following new fix to work, else refer to the old method described in post #22 == The support for this card has now been merged to https://github.com/kvalo/ath10k-firmware. The repository now contains the required board.bin, board-2.bin and firmware-4.bin files for the card to initialize and connect to a bgn-access point (5GHz (ac- protocol) is still untested, feel free to modify this if you can confirm it works). Here are the new commands to get you online: sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/ sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true Reboot or reload the ath10k_pci module and you should be able to connect! --- STATUS 2015-12-22: Currently there is a fix for this problem in post #22 (originally post #19, but reposted due to command typos!) which seems to have fixed the issue for many. This bug is unique to revision 32 of the card [168c:003e], fixes for older revisions don't seem to work. There are a couple of issues regarding the fix for some people (not all): 1. Wireless works, but network throughput stops some time after connecting to access point 2. Bluetooth communications take a noticeable performance hit when transferring something over WiFi --- Original description: I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card doesn't work in it or 16.04. The card has the device id 168c:003e as many other cards, for example the Qualcomm Atheros Killer (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a newer revision number (32) and the suggested fixes work only partially and the wireless is unusable. The computer has just been released this summer and is Intel Skylake -based. I've tried the patch from bug 1383184, which has a fix for the card revision 20: Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch files: board.bin firmware-4.bin notice_ath10k_firmware-4.txt ath10k_pci succeeds in loading the firmware, but it seems that the firmware is not working correctly: dmesg | grep ath [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [5.678420] ath10k_pci :07:00.0: Direct firmware load for ath10k/cal-pci-:07:00.0.bin failed with error -2 [5.678773] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2 [5.678781] ath10k_pci :07:00.0: failed to load spec board file, falling back to generic: -2 [5.679445] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32 [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [8.200607] ath: EEPROM regdomain: 0x6c [8.200614] ath: EEPROM indicates we should expect a direct regpair map [8.200619] ath: Country alpha2 being used: 00 [8.200621] ath: Regpair used: 0x6c [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0 [ 13.462029] ath10k_pci :07:00.0: failed to enable dynamic BW: -11 [ 16.461416] ath10k_pci :07:00.0: could not suspend target (-11) [ 24.760062] ath10k_pci :07:00.0: failed to enable dynamic BW: -11 [ 27.759534] ath10k_pci :07:00.0: could not suspend target (-11) [ 36.046205] ath10k_pci :07:00.0: failed to set arp ac override parameter: -11 [ 39.045
[Kernel-packages] [Bug 1561604] Re: x-gene2: add SoC v2 support to clock
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Craig Magina (craig.magina) Status: In Progress ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1561604 Title: x-gene2: add SoC v2 support to clock Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Need an upstream patch to add support for the clock on the X-Gene 2 platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561604/+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 1556676] Re: In 14.04.04, r8169.ko cannot recover wired Ethernet connection after resume from suspend
lsmod shows that r8169 is still in use: r8169 81920 0 mii16384 1 r8169 -- 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/1556676 Title: In 14.04.04, r8169.ko cannot recover wired Ethernet connection after resume from suspend Status in linux package in Ubuntu: Triaged Bug description: Whenever my laptop suspends (desirable) and then resumes, the r8169 module cannot reconnect the wired Ethernet line. This is consistent. I can see network_manager trying over and over to get a reconnection. WORKAROUND: After resume: sudo rmmod r8169 sudo insmod /lib/modules/`uname --kernel-release`/kernel/drivers/net/ethernet/realtek/r8169.ko --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elkins 1902 F pulseaudio /dev/snd/controlC0: elkins 1902 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=869e6cc9-952c-4e2a-9714-d8412bbc6dd1 InstallationDate: Installed on 2016-02-21 (27 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Hewlett-Packard HP Pavilion dv3 Notebook PC NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=2a7c05c7-3728-4f32-aac3-9dbd721a4fa0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 RelatedPackageVersions: linux-restricted-modules-3.13.0-83-generic N/A linux-backports-modules-3.13.0-83-generic N/A linux-firmware 1.127.20 Tags: trusty Uname: Linux 3.13.0-83-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1506 dmi.board.vendor: Compal dmi.board.version: 14.31 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.15:bd08/25/2009:svnHewlett-Packard:pnHPPaviliondv3NotebookPC:pvr1:rvnCompal:rn1506:rvr14.31:cvnCompal:ct10:cvrN/A: dmi.product.name: HP Pavilion dv3 Notebook PC dmi.product.version: 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556676/+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 1556676] Re: In 14.04.04, r8169.ko cannot recover wired Ethernet connection after resume from suspend
Finished my project. Upgraded same laptop (HP Pavilion dv3-1075us Laptop) to 16.04 Beta-2. Issue still present. uname -a: Linux hplaptop 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:08:31 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556676 Title: In 14.04.04, r8169.ko cannot recover wired Ethernet connection after resume from suspend Status in linux package in Ubuntu: Triaged Bug description: Whenever my laptop suspends (desirable) and then resumes, the r8169 module cannot reconnect the wired Ethernet line. This is consistent. I can see network_manager trying over and over to get a reconnection. WORKAROUND: After resume: sudo rmmod r8169 sudo insmod /lib/modules/`uname --kernel-release`/kernel/drivers/net/ethernet/realtek/r8169.ko --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elkins 1902 F pulseaudio /dev/snd/controlC0: elkins 1902 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=869e6cc9-952c-4e2a-9714-d8412bbc6dd1 InstallationDate: Installed on 2016-02-21 (27 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Hewlett-Packard HP Pavilion dv3 Notebook PC NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=2a7c05c7-3728-4f32-aac3-9dbd721a4fa0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 RelatedPackageVersions: linux-restricted-modules-3.13.0-83-generic N/A linux-backports-modules-3.13.0-83-generic N/A linux-firmware 1.127.20 Tags: trusty Uname: Linux 3.13.0-83-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1506 dmi.board.vendor: Compal dmi.board.version: 14.31 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.15:bd08/25/2009:svnHewlett-Packard:pnHPPaviliondv3NotebookPC:pvr1:rvnCompal:rn1506:rvr14.31:cvnCompal:ct10:cvrN/A: dmi.product.name: HP Pavilion dv3 Notebook PC dmi.product.version: 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556676/+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 1561507] Re: NVMe io requests gets broken down to 64k block requests
This patch was released with Ubuntu-4.4.0-13.29 ** Also affects: linux (Ubuntu Xenial) Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Xenial) Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) -- 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/1561507 Title: NVMe io requests gets broken down to 64k block requests Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: == Comment: #0 - Breno Henrique Leitao - 2016-03-24 08:20:06 == The io requests to the NVMe device gets broken down to 64k requests I would like to ask Canonical to cherry pick the followng patch: commit 5f009d3f8e6685fe8c6215082c1696a08b411220 Author: Keith Busch Date: Wed Feb 10 16:52:47 2016 -0700 block: Initialize max_dev_sectors to 0 The new queue limit is not used by the majority of block drivers, and should be initialized to 0 for the driver's requested settings to be used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561507/+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 1556562] Re: VIA C7-D machine "kernel NULL pointer dereference" in skcipher_recvmsg_async
I wanted to provide some feedback, if interested. Using Kamal's test kernel and asynchronus test vectors from Taruk's GitHub (https://github.com/tstruk/afalg_async_test)... The SKCIPHER asynchronous test program passed. However, the the AEAD asynchronous test program failed with: $ cd aead $ make $ ... $ ./test $ doing copy, $ bind error 2 HASH, MAC, etc were not tested. --- I also noticed Torvalds has some tests at: linux$ find . -name '*tcrypt*' ./crypto/tcrypt.c ./crypto/tcrypt.h I'm going to try and get them running on this kernel tonight or tomorrow. -- 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/1556562 Title: VIA C7-D machine "kernel NULL pointer dereference" in skcipher_recvmsg_async Status in linux package in Ubuntu: Confirmed Status in linux source package in Wily: In Progress Bug description: I'm working on an Lubuntu 15 machine. It was chosen because it supports VIA C7-D processor and the VIA PM400 chipset without crashing (also see ). Lubuntu 15 uses the 4.2 kernel: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename: wily And: $ uname -a Linux via 4.2.0-30-generic #36-Ubuntu SMP Fri Feb 26 00:57:19 UTC 2016 i686 i686 i686 GNU/Linux When running a particular program (details below), it hangs in syscall 248 and results in the following dmesg/syslog output. The process cannot be killed, the machine does not respond to a 'shutdown -r now', and the machine requires a hard reset. ... [ 4505.429577] BUG: unable to handle kernel NULL pointer dereference at 0008 [ 4505.429593] IP: [] skcipher_recvmsg_async.isra.13+0x4b2/0x500 [algif_skcipher] [ 4505.429607] *pdpt = 34ee3001 *pde = [ 4505.429614] Oops: [#3] SMP [ 4505.429621] Modules linked in: jitterentropy_rng drbg ansi_cprng algif_skcipher af_alg snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi padlock_sha snd_seq padlock_aes snd_seq_device via_cputemp snd_timer hwmon_vid via_rng snd input_leds serio_raw soundcore i2c_viapro shpchp 8250_fintek mac_hid parport_pc ppdev lp parport autofs4 pata_acpi hid_generic usbhid hid psmouse r8169 pata_via sata_via mii [ 4505.429689] CPU: 0 PID: 1532 Comm: afalgtest Tainted: G D 4.2.0-30-generic #36-Ubuntu [ 4505.429695] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Weibu, BIOS 080014 11/17/2011 [ 4505.429700] task: f4e0e040 ti: f4e3c000 task.ti: f4e3c000 [ 4505.429705] EIP: 0060:[] EFLAGS: 00010202 CPU: 0 [ 4505.429712] EIP is at skcipher_recvmsg_async.isra.13+0x4b2/0x500 [algif_skcipher] [ 4505.429717] EAX: f3f97c00 EBX: f3f3ee00 ECX: f3f97c00 EDX: [ 4505.429722] ESI: f3f3ee00 EDI: 0ff0 EBP: f4e3ddc8 ESP: f4e3dd70 [ 4505.429726] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 4505.429731] CR0: 80050033 CR2: 0008 CR3: 3247a520 CR4: 06b0 [ 4505.429735] Stack: [ 4505.429738] f3f97df4 f3f97c00 f3f97de0 f3f97c04 0020 f4e3dd00 0018 [ 4505.429750] 1ff0 f3fb4400 f3f97c04 0ff0 f4e3de40 f3f97de8 f4e3de38 f3fa [ 4505.429761] 0002 0002 f3f97c00 f1f58180 c1210510 f4e3de38 f4e3ddf4 f8a6cd6b [ 4505.429772] Call Trace: [ 4505.429788] [] ? free_ioctx_users+0xa0/0xa0 [ 4505.429795] [] skcipher_recvmsg+0x2b/0x1f0 [algif_skcipher] [ 4505.429803] [] ? skcipher_check_key.isra.8+0x2a/0xb0 [algif_skcipher] [ 4505.429810] [] skcipher_recvmsg_nokey+0x31/0x40 [algif_skcipher] [ 4505.429820] [] sock_recvmsg+0x3d/0x50 [ 4505.429826] [] sock_read_iter+0x84/0xd0 [ 4505.429833] [] ? sock_recvmsg+0x50/0x50 [ 4505.429839] [] aio_run_iocb+0x110/0x2c0 [ 4505.429846] [] ? sock_recvmsg+0x50/0x50 [ 4505.429854] [] ? error_code+0x67/0x6c [ 4505.429865] [] ? kmem_cache_alloc+0x1b4/0x1e0 [ 4505.429875] [] ? __fdget+0x12/0x20 [ 4505.429881] [] do_io_submit+0x1ef/0x4a0 [ 4505.429893] [] ? security_file_alloc+0x2f/0x50 [ 4505.429900] [] SyS_io_submit+0x20/0x30 [ 4505.429911] [] sysenter_do_call+0x12/0x12 [ 4505.429915] Code: 00 00 00 75 24 8b 45 ac ff 52 0c 89 c7 83 ff 8d 75 8f 8b 45 e4 3e ff 80 fc 01 00 00 bf ef fd ff ff e9 62 fc ff ff 8d 76 00 89 c8 52 08 89 c7 eb db 8b 45 e4 31 d2 8b 80 20 02 00 00 8b 58 1c [ 4505.429982] EIP: [] skcipher_recvmsg_async.isra.13+0x4b2/0x500 [algif_skcipher] SS:ESP 0068:f4e3dd70 [ 4505.429991] CR2: 0008 [ 4505.429997] ---[ end trace 3cce7cc6be0ad960 ]--- ** The process details is this is a failed self test for the upcoming OpenSSL 1.1.0. The OpenSSL RT bug report for this issue is at http://rt.openssl.org/Ticket/Display.html?id=4411. Two attempts to debug it resulted i
[Kernel-packages] [Bug 1556676] Re: In 14.04.04, r8169.ko cannot recover wired Ethernet connection after resume from suspend
Comment #31 was in error. Finished my project. Upgraded same laptop (HP Pavilion dv3-1075us Laptop) to 16.04 Beta-2. This issue is no longer present. I can only guess that this was not a kernel issue but in upstart/pm or elsewhere because I previously tried the upstream 4.5 kernel in a 14.04.04 environment without success. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- 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/1556676 Title: In 14.04.04, r8169.ko cannot recover wired Ethernet connection after resume from suspend Status in linux package in Ubuntu: Fix Released Bug description: Whenever my laptop suspends (desirable) and then resumes, the r8169 module cannot reconnect the wired Ethernet line. This is consistent. I can see network_manager trying over and over to get a reconnection. WORKAROUND: After resume: sudo rmmod r8169 sudo insmod /lib/modules/`uname --kernel-release`/kernel/drivers/net/ethernet/realtek/r8169.ko --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elkins 1902 F pulseaudio /dev/snd/controlC0: elkins 1902 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=869e6cc9-952c-4e2a-9714-d8412bbc6dd1 InstallationDate: Installed on 2016-02-21 (27 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Hewlett-Packard HP Pavilion dv3 Notebook PC NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=2a7c05c7-3728-4f32-aac3-9dbd721a4fa0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 RelatedPackageVersions: linux-restricted-modules-3.13.0-83-generic N/A linux-backports-modules-3.13.0-83-generic N/A linux-firmware 1.127.20 Tags: trusty Uname: Linux 3.13.0-83-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1506 dmi.board.vendor: Compal dmi.board.version: 14.31 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.15:bd08/25/2009:svnHewlett-Packard:pnHPPaviliondv3NotebookPC:pvr1:rvnCompal:rn1506:rvr14.31:cvnCompal:ct10:cvrN/A: dmi.product.name: HP Pavilion dv3 Notebook PC dmi.product.version: 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556676/+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 1559595] Re: xenial fresh installs boot to command line no desktop
This problem occurred with Xenial Daily Live Current. Daily Live Pending did not have the problem so I'm installed and running O.K. -- 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/1559595 Title: xenial fresh installs boot to command line no desktop Status in linux package in Ubuntu: Confirmed Bug description: Fresh install 19 March daily build "current" .iso, apt-get update, apt-get dist-upgrade booted to command line no desktop Fresh install 19 March daily live "pending" same thing from command line did ubuntu-bug, saved file Booted xenial in another partition, this one a month old updated daily runs fine did ubuntu-bug on the /tmp/apport* from the failing ubuntu pDISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" Linux Lenovo2 4.4.0-14-generic #30-Ubuntu SMP Tue Mar 15 13:04:17 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux model name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz model name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) artition This is from the updated xenial partition which works: DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" Linux Lenovo2 4.4.0-14-generic #30-Ubuntu SMP Tue Mar 15 13:04:17 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux model name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz model name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 [modified: boot/vmlinuz-4.4.0-14-generic] ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 19:03:28 2016 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160319) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic root=UUID=0e841aaf-ae9d-4313-a5b5-6ebf1caeedcf ro quiet splash vt.handoff=7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559595/+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 1562230] [NEW] [Hewlett-Packard HP ENVY 17 Notebook PC] hibernate/resume failure
Public bug reported: Notebook cannot resume from hibernation. ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zh 2098 F pulseaudio /dev/snd/controlC0: zh 2098 F pulseaudio Date: Sat Mar 26 07:41:25 2016 DuplicateSignature: hibernate/resume:Hewlett-Packard HP ENVY 17 Notebook PC:F.65 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=378e2e05-278e-45c4-a558-68a1e8b83eab InterpreterPath: /usr/bin/python3.5 MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=c8951135-cb49-43fc-b142-4b426e3a988b ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux Title: [Hewlett-Packard HP ENVY 17 Notebook PC] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/20/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1966 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG3456NSY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.65:bd11/20/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1966:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops hibernate resume xenial -- 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/1562230 Title: [Hewlett-Packard HP ENVY 17 Notebook PC] hibernate/resume failure Status in linux package in Ubuntu: New Bug description: Notebook cannot resume from hibernation. ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zh 2098 F pulseaudio /dev/snd/controlC0: zh 2098 F pulseaudio Date: Sat Mar 26 07:41:25 2016 DuplicateSignature: hibernate/resume:Hewlett-Packard HP ENVY 17 Notebook PC:F.65 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=378e2e05-278e-45c4-a558-68a1e8b83eab InterpreterPath: /usr/bin/python3.5 MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=c8951135-cb49-43fc-b142-4b426e3a988b ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux Title: [Hewlett-Packard HP ENVY 17 Notebook PC] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/20/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1966 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG3456NSY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.65:bd11/20/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1966:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENV
[Kernel-packages] [Bug 1562230] Re: [Hewlett-Packard HP ENVY 17 Notebook PC] hibernate/resume failure
** Tags removed: need-duplicate-check -- 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/1562230 Title: [Hewlett-Packard HP ENVY 17 Notebook PC] hibernate/resume failure Status in linux package in Ubuntu: New Bug description: Notebook cannot resume from hibernation. ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zh 2098 F pulseaudio /dev/snd/controlC0: zh 2098 F pulseaudio Date: Sat Mar 26 07:41:25 2016 DuplicateSignature: hibernate/resume:Hewlett-Packard HP ENVY 17 Notebook PC:F.65 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=378e2e05-278e-45c4-a558-68a1e8b83eab InterpreterPath: /usr/bin/python3.5 MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=c8951135-cb49-43fc-b142-4b426e3a988b ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux Title: [Hewlett-Packard HP ENVY 17 Notebook PC] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/20/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1966 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG3456NSY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.65:bd11/20/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1966:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562230/+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 1562135] Re: Restore ti-connectivity/wl18xx-conf.bin in trusty
Hello Seth, or anyone else affected, Accepted linux-firmware into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.127.22 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: linux-firmware (Ubuntu Trusty) Status: In Progress => Fix Committed -- 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/1562135 Title: Restore ti-connectivity/wl18xx-conf.bin in trusty Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Trusty: Fix Committed Bug description: This was removed by an upstream commit cherry-picked for lts-xenial. It's unclear whether or not it's really needed, but we should put it back to avoid any potential for SRU regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1562135/+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 1562230] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1562230 Title: [Hewlett-Packard HP ENVY 17 Notebook PC] hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: Notebook cannot resume from hibernation. ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zh 2098 F pulseaudio /dev/snd/controlC0: zh 2098 F pulseaudio Date: Sat Mar 26 07:41:25 2016 DuplicateSignature: hibernate/resume:Hewlett-Packard HP ENVY 17 Notebook PC:F.65 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=378e2e05-278e-45c4-a558-68a1e8b83eab InterpreterPath: /usr/bin/python3.5 MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=c8951135-cb49-43fc-b142-4b426e3a988b ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux Title: [Hewlett-Packard HP ENVY 17 Notebook PC] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/20/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1966 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG3456NSY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.65:bd11/20/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1966:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562230/+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 1447909] Re: external mic not detected on machines with alc256 codec
Now the "Headset Microphone" is shown in the sound settings, but it doesn't seem to capture any sound. -- 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/1447909 Title: external mic not detected on machines with alc256 codec Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This bug is used for tracking, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1447909/+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 1537469] Re: package linux-generic 4.2.0.25.27 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1537469 Title: package linux-generic 4.2.0.25.27 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Expired Bug description: ubuntu freezed during an update ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-generic 4.2.0.25.27 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 2891 F pulseaudio /dev/snd/controlC1: philippe 2891 F pulseaudio Date: Sun Jan 24 11:07:23 2016 DuplicateSignature: package:linux-generic:4.2.0.25.27:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=632ceabf-013d-4a63-bd6d-cdf6af3609c4 InstallationDate: Installed on 2015-09-12 (133 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Acer Aspire E5-771G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic root=UUID=c0497b34-9ef1-4397-84f3-e749ddeaa421 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-29ubuntu0.3 SourcePackage: linux Title: package linux-generic 4.2.0.25.27 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-11-18 (66 days ago) dmi.bios.date: 11/10/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.15:bd11/10/2014:svnAcer:pnAspireE5-771G:pvrTBDbyOEM:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-771G dmi.product.version: TBD by OEM dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1537469/+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 1534138] Re: USB devices not mounted with kernel 3.13.0-62
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1534138 Title: USB devices not mounted with kernel 3.13.0-62 Status in linux package in Ubuntu: Expired Bug description: I am sorry bu no any USB port are working after the last ubuntu's update. No mouse, no pendrive, no photomachine connection. Tuchpad works. My laptop is an ACER Aspire E1-532. The problem was with 3.13.0-62-generic version. The problem was with the 3.13.0-62-generic version. Today I upgrade to the 3.13.0-63-generic version with the same USB problems. It is working only by the 3.13.0-61-generic. Updates arrived to 3.13.0-74 and the problem is the same - I have to work under 3.13.0-61 version. --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: milankovics 1364 F pulseaudio /dev/snd/controlC1: milankovics 1364 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f2623db5-4cd9-45a1-8e85-cae8126b9c21 InstallationDate: Installed on 2014-03-16 (670 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E1-532 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic root=UUID=3d362c7e-b5ab-40b1-97da-c83f468ab029 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 RelatedPackageVersions: linux-restricted-modules-3.13.0-74-generic N/A linux-backports-modules-3.13.0-74-generic N/A linux-firmware 1.127.19 Tags: trusty Uname: Linux 3.13.0-74-generic i686 UpgradeStatus: Upgraded to trusty on 2014-05-07 (618 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/21/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HW dmi.board.vendor: Acer dmi.board.version: V2.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd05/21/2013:svnAcer:pnAspireE1-532:pvrV2.04:rvnAcer:rnEA50_HW:rvrV2.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Aspire E1-532 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1534138/+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 1532909] Re: Dell XPS 13 - 9333 Kernel problems after update to wily
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1532909 Title: Dell XPS 13 - 9333 Kernel problems after update to wily Status in linux package in Ubuntu: Expired Bug description: Immediately after upgrade to wily faced several problems on Dell XPS 13 - 9333: - standard boot does not complete - need to manually select upstart or recovery as home partition is LUKS encrypted using cryptsetup and standard boot does not prompt for password any more. Instead of password prompt fsck.xfs (/ is on xfs) is shown. - repetedly get kernel oops - USB mouse and USB keyboard have irregular hangs omitting mouse movement and strokes Jan 11 10:28:31 cygnus kernel: [ 8814.972861] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) Jan 11 10:28:31 cygnus kernel: [ 8814.972866] [ cut here ] Jan 11 10:28:31 cygnus kernel: [ 8814.972888] WARNING: CPU: 0 PID: 3225 at /build/linux-AFqQDb/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12328 check_crtc_state+0x2c5/0x440 [i915]() Jan 11 10:28:31 cygnus kernel: [ 8814.972890] pipe state doesn't match! Jan 11 10:28:31 cygnus kernel: [ 8814.972891] Modules linked in: nls_iso8859_1 uas usb_storage rfcomm ctr ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables bnep binfmt_misc drbg ansi_cprng algif_skcipher af_alg ax88179_178a usbnet mii joydev hid_rmi dell_wmi sparse_keymap arc4 uvcvideo dell_laptop dcdbas dell_smm_hwmon videobuf2_vmalloc videobuf2_memops dm_crypt intel_rapl videobuf2_core iosf_mbi v4l2_common btusb x86_pkg_temp_thermal btrtl intel_powerclamp btbcm btintel coretemp bluetooth kvm_intel videodev media kvm hid_multitouch crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd iwlmvm mac80211 input_leds serio_raw iwlwifi snd_hda_codec_hdmi lpc_ich snd_hda_codec_realtek snd_hda_codec_generic cfg80211 shpchp snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_soc_rt5640 snd_soc_rl6231 snd_soc_core snd_compress a c97_bus snd_pcm_dmaengine snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq acpi_als kfifo_buf industrialio snd_seq_device snd_timer snd soundcore dw_dmac dw_dmac_core snd_soc_sst_acpi i2c_designware_platform 8250_dw spi_pxa2xx_platform i2c_designware_core dell_rbtn intel_smartconnect mac_hid parport_pc ppdev lp parport xfs libcrc32c hid_generic i915 i2c_algo_bit drm_kms_helper psmouse drm ahci wmi libahci video sdhci_acpi sdhci i2c_hid usbhid hid Jan 11 10:28:31 cygnus kernel: [ 8814.972974] CPU: 0 PID: 3225 Comm: Xorg Tainted: GW OE 4.2.0-23-generic #28-Ubuntu Jan 11 10:28:31 cygnus kernel: [ 8814.972975] Hardware name: Dell Inc. XPS13 9333/0D13CR, BIOS A05 09/11/2014 Jan 11 10:28:31 cygnus kernel: [ 8814.972977] a86f54fd 880215f277c8 817e94c9 Jan 11 10:28:31 cygnus kernel: [ 8814.972980] 880215f27820 880215f27808 8107b3d6 Jan 11 10:28:31 cygnus kernel: [ 8814.972983] 880215f27848 880215f278b0 88021255f000 0001 Jan 11 10:28:31 cygnus kernel: [ 8814.972986] Call Trace: Jan 11 10:28:31 cygnus kernel: [ 8814.972992] [] dump_stack+0x45/0x57 Jan 11 10:28:31 cygnus kernel: [ 8814.972997] [] warn_slowpath_common+0x86/0xc0 Jan 11 10:28:31 cygnus kernel: [ 8814.973000] [] warn_slowpath_fmt+0x55/0x70 Jan 11 10:28:31 cygnus kernel: [ 8814.973020] [] ? intel_pipe_config_compare+0xb31/0xc60 [i915] Jan 11 10:28:31 cygnus kernel: [ 8814.973034] [] check_crtc_state+0x2c5/0x440 [i915] Jan 11 10:28:31 cygnus kernel: [ 8814.973053] [] intel_modeset_check_state+0x21d/0x6d0 [i915] Jan 11 10:28:31 cygnus kernel: [ 8814.973068] [] intel_crtc_set_config+0x4c7/0x580 [i915] Jan 11 10:28:31 cygnus kernel: [ 8814.973082] [] ? drm_mode_create+0x25/0x60 [drm] Jan 11 10:28:31 cygnus kernel: [ 8814.973094] [] drm_mode_set_config_internal+0x66/0x100 [drm] Jan 11 10:28:31 cygnus kernel: [ 8814.973105] [] drm_mode_setcrtc+0x3e9/0x500 [drm] Jan 11 10:28:31 cygnus kernel: [ 8814.973113] [] drm_ioctl+0x125/0x610 [drm] Jan 11 10:28:31 cygnus kernel: [ 8814.973123] [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] Jan 11 10:28:31 cygnus kernel: [ 8814.973127] [] do_vfs_ioctl+0x295/0x480 Jan 11 10:28:31 cygnus kernel: [ 8814.973131] [] ? __audit_syscall_entry+0xab/0xf0 Jan 11 10:28:31 cygnus kernel: [ 8814.973134] [] ? do_audit_syscall_entry+0x4b/0x70 Jan 11 10:28:31 cygnus kernel: [ 8814.973137] [] SyS_ioctl+0x79/0x90 Jan 11 10:28:31 cygnus kernel: [ 8814.973139] [] ? syscall_trace_leave+
[Kernel-packages] [Bug 1534948] Re: Ubuntu 15.10 fails to boot from Sandisk USB stick
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1534948 Title: Ubuntu 15.10 fails to boot from Sandisk USB stick Status in linux package in Ubuntu: Expired Bug description: Booting from Sandisk USB stick fails and stops on "device descriptor read/64, error -71" and "device not accepting address 6, error -71" on Dell Latitude E5420 Laptop. I tried every USB socket but without success. Booting with "rootwait" parameter does not help either. [5.190746] ata5: SATA link down (SStatus 0 SControl 300) [5.510923] ata6: SATA link down (SStatus 0 SControl 300) [ 18.414128] usb 2-1.4: device descriptor read/64, error -110 [ 23.601028] usb 2-1.4: device descriptor read/64, error -71 [ 23.777126] usb 2-1.4: new high-speed USB device number 4 using ehci-pci [ 23.861176] usb 2-1.4: device descriptor read/64, error -71 [ 24.049280] usb 2-1.4: device descriptor read/64, error -71 [ 24.225377] usb 2-1.4: new high-speed USB device number 5 using ehci-pci [ 24.641614] usb 2-1.4: device not accepting address 5, error -71 [ 24.713649] usb 2-1.4: new high-speed USB device number 6 using ehci-pci [ 25.129882] usb 2-1.4: device not accepting address 6, error -71 [ 25.131599] usb 2-1-port4: unable to enumerate USB device [ 25.205925] usb 2-1.6: new full-speed USB device number 7 using ehci-pci [ 25.303424] usb 2-1.6: New USB device found, idVendor=413c, idProduct=8187 [ 25.304928] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 25.306409] usb 2-1.6: Product: DW375 Bluetooth Module [ 25.307864] usb 2-1.6: Manufacturer: Dell Computer Corp [ 25.309305] usb 2-1.6: SerialNumber: 90004EDB8100 however unpluging and repluging usb stick makes booting process go further [ 35.799849] usb 2-1.4: new high-speed USB device number 8 using ehci-pci [ 35.893824] usb 2-1.4: New USB device found, idVendor=0781, idProduct=5583 [ 35.895294] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 35.896728] usb 2-1.4: Product: Ultra Fit [ 35.898129] usb 2-1.4: Manufacturer: SanDisk [ 35.899521] usb 2-1.4: SerialNumber: 4C530001160413113001 [ 35.905302] usb-storage 2-1.4:1.0: USB Mass Storage device detected [ 35.907051] scsi host6: usb-storage 2-1.4:1.0 [ 35.908544] usbcore: registered new interface driver usb-storage [ 35.911586] usbcore: registered new interface driver uas [ 36.909422] scsi 6:0:0:0: Direct-Access SanDisk Ultra Fit1.00 PQ: 0 ANSI: 6 [ 36.911179] sd 6:0:0:0: Attached scsi generic sg2 type 0 [ 36.913169] sd 6:0:0:0: [sdb] 60751872 512-byte logical blocks: (31.1 GB/28.9 GiB) [ 36.915880] sd 6:0:0:0: [sdb] Write Protect is off [ 36.917297] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 36.918317] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 36.950274] sdb: sdb1 sdb2 < sdb5 > [ 36.955479] sd 6:0:0:0: [sdb] Attached SCSI removable disk [ 37.254029] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) My system: darek@LAPTOP-PORTABLE:~$ lsb_release -rd Description: Ubuntu 15.10 Release: 15.10 darek@LAPTOP-PORTABLE:~$ uname -a Linux LAPTOP-PORTABLE 4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1534948/+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 1533804] Re: CPU fan speed regression since 15.04
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1533804 Title: CPU fan speed regression since 15.04 Status in linux package in Ubuntu: Expired Bug description: When running 14.04 my CPU fan speed increases relative to the CPU temperature, which keeps the temperature fairly constant. When running 15.04 or 15.10 the CPU fan speed is locked to the minimum until the temperature reaches 81 degrees, then it switches to maximum until the temperature falls below 72 degrees. Then it goes back to the minimum. This is both annoying and causes unnecessary stress to the hardware. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-23-generic 4.2.0-23.28 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 13 19:13:51 2016 HibernationDevice: RESUME=UUID=5a0bdae5-ddc6-4b6f-aead-360c2949313a InstallationDate: Installed on 2015-07-12 (185 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic root=UUID=283ec8d4-031f-4703-9de4-8dfe31132378 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.2.0-23-generic N/A linux-backports-modules-4.2.0-23-generic N/A linux-firmware1.149.3 RfKill: 1: hci1: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-12-31 (12 days ago) dmi.bios.date: 11/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79XTD EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0X dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533804/+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 1533304] Re: Kernel Bug: IPv6 Neighbor Discovery
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1533304 Title: Kernel Bug: IPv6 Neighbor Discovery Status in linux package in Ubuntu: Expired Bug description: We have discovered what appears to be a bug with the handling of ICMP6 router solicitations on tun interfaces in the Linux kernel. In particular, if an application is not immediately bound to the tun interface, router solicitations are never sent out of the interface. This issue can be replicated easily using the attached scripts. First, a tun interface is created with permissions for the local user, sudo is used so the script will prompt for the user password. $ bash rftun0_create.sh rftun0 created 16: rftun0: mtu 1500 qdisc noop state DOWN group default qlen 500 link/none Then the interface is configured, given an address, and brought "up" however since there is no application bound to the interface yet there is no carrier. $ bash rftun0_up.sh net.ipv6.conf.rftun0.forwarding = 0 net.ipv6.conf.rftun0.accept_ra = 1 net.ipv6.conf.rftun0.autoconf = 1 net.ipv6.conf.rftun0.accept_ra_rt_info_max_plen = 128 net.ipv6.conf.rftun0.accept_ra_rtr_pref = 1 net.ipv6.conf.rftun0.router_solicitation_delay = 1 net.ipv6.conf.rftun0.router_solicitation_interval = 2 net.ipv6.conf.rftun0.router_solicitations = 200 rftun0 up 16: rftun0: mtu 1400 qdisc pfifo_fast state DOWN group default qlen 500 link/none inet6 fe80::600:4339:125f:760c/64 scope link valid_lft forever preferred_lft forever A simple client is then run to bind to the tun interface and read the first three packets. If things are going well we should see 3 router solicitations, however we instead see no traffic. $ python simple_tun_client.py Timed out... Timed out... Timed out... If we bring the interface down and try again with no delay between bringing the interface up and binding the application we see things work as expected. $ bash rftun0_down.sh rftun0 down 16: rftun0: mtu 1400 qdisc pfifo_fast state DOWN group default qlen 500 link/none $ bash rftun0_up.sh && python simple_tun_client.py net.ipv6.conf.rftun0.forwarding = 0 net.ipv6.conf.rftun0.accept_ra = 1 net.ipv6.conf.rftun0.autoconf = 1 net.ipv6.conf.rftun0.accept_ra_rt_info_max_plen = 128 net.ipv6.conf.rftun0.accept_ra_rtr_pref = 1 net.ipv6.conf.rftun0.router_solicitation_delay = 1 net.ipv6.conf.rftun0.router_solicitation_interval = 2 net.ipv6.conf.rftun0.router_solicitations = 200 rftun0 up 16: rftun0: mtu 1400 qdisc pfifo_fast state DOWN group default qlen 500 link/none inet6 fe80::600:1512:6243:38fe/64 scope link valid_lft forever preferred_lft forever Read packet from tunnel. 48 bytes. 60083afffe8006001512624338feff0200028500c6e3 Read packet from tunnel. 48 bytes. 60083afffe8006001512624338feff0200028500c6e3 Read packet from tunnel. 48 bytes. 60083afffe8006001512624338feff0200028500c6e3 Furthermore, I can rerun the simple client and continue to receive router solicitations. Attempting the same procedure again with a small delay replicates the original issue. Notice the sleep statement in between the rftun0_up script and the simple tun client. $ bash rftun0_down.sh rftun0 down 16: rftun0: mtu 1400 qdisc pfifo_fast state DOWN group default qlen 500 link/none $ bash rftun0_up.sh && sleep 5 && python simple_tun_client.py net.ipv6.conf.rftun0.forwarding = 0 net.ipv6.conf.rftun0.accept_ra = 1 net.ipv6.conf.rftun0.autoconf = 1 net.ipv6.conf.rftun0.accept_ra_rt_info_max_plen = 128 net.ipv6.conf.rftun0.accept_ra_rtr_pref = 1 net.ipv6.conf.rftun0.router_solicitation_delay = 1 net.ipv6.conf.rftun0.router_solicitation_interval = 2 net.ipv6.conf.rftun0.router_solicitations = 200 rftun0 up 16: rftun0: mtu 1400 qdisc pfifo_fast state DOWN group default qlen 500 link/none inet6 fe80::600:25f2:67d0:37fc/64 scope link valid_lft forever preferred_lft forever Timed out... Timed out... Timed out... This test can be repeated as necessary. On my system, sleep times of 2 seconds or larger seem to always produce the issue, while sleep times of 1 second seem to work most of the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-p
[Kernel-packages] [Bug 1535790] Re: Random desktop freezes and restarting and shut down hangs
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1535790 Title: Random desktop freezes and restarting and shut down hangs Status in linux package in Ubuntu: Expired Bug description: not much to tell i have no idea whats wrong right after i installed ubuntu theses problems keep on happening please help ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-23-generic 4.2.0-23.28 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: image64labs 1397 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 19 11:03:56 2016 HibernationDevice: RESUME=UUID=0c7bdaad-bfb4-4bf3-939f-19a13a205748 InstallationDate: Installed on 2016-01-19 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire ES1-512 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic root=UUID=2960e315-ddb6-487f-a23e-83ba19bf4cf8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-23-generic N/A linux-backports-modules-4.2.0-23-generic N/A linux-firmware1.149.3 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: 07/20/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Aspire ES1-512 dmi.board.vendor: Acer dmi.board.version: V1.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.15:bd07/20/2015:svnAcer:pnAspireES1-512:pvrV1.15:rvnAcer:rnAspireES1-512:rvrV1.15:cvnAcer:ct10:cvrV1.15: dmi.product.name: Aspire ES1-512 dmi.product.version: V1.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535790/+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 1534911] Re: TouchPad not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1534911 Title: TouchPad not working Status in linux package in Ubuntu: Expired Bug description: I have a DELL 5547 laptop. I have dual OS: Ubuntu 14.04 and Windows 8.1. In Ubuntu the TouchPad is not working although an external mouse is working well. The touchpad is working in windows. Help me fix this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-74-generic 3.13.0-74.118 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nmcsk 1892 F pulseaudio /dev/snd/controlC0: nmcsk 1892 F pulseaudio CurrentDesktop: Unity Date: Sat Jan 16 16:05:50 2016 HibernationDevice: RESUME=UUID=f0aa5b0e-d5cf-4def-8347-06c0c8d478f7 InstallationDate: Installed on 2016-01-03 (12 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic.efi.signed root=UUID=72aa1fd6-3fb4-4e4d-a00e-5e2b7e74a5e8 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-74-generic N/A linux-backports-modules-3.13.0-74-generic N/A linux-firmware 1.127.19 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 06X5CY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd01/23/2015:svnDellInc.:pnInspiron5547:pvrA07:rvnDellInc.:rn06X5CY:rvrA00:cvnDellInc.:ct8:cvrA07: dmi.product.name: Inspiron 5547 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1534911/+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
