[Kernel-packages] [Bug 1447485] Re: serial: 8250_pci: Add support for 16 port Exar boards
I can confirm that the changes is working as expected. Tag has been changed Thanks a lot. -- Soeren ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1447485 Title: serial: 8250_pci: Add support for 16 port Exar boards Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Bug description: This is a request to add support for boards using two EXAR XR17V8358 chips in Master-Slave mode. The patch has also been send upstream, but is not reviewed yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447485/+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 1518457] Re: kswapd0 100% CPU usage
Is this known to affect paravirtualized instances, or is it restricted to hvm? Can anyone tell me what conditions I need to create this in a fresh instance? I'll spin up a PV t2.nano and see if I can reproduce it there. -- 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/1518457 Title: kswapd0 100% CPU usage Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: As per bug 721896 and various others: I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory). Occasionally (about once a day), kswapd0 falls into a busy loop and spins on 100% CPU usage indefinitely. This can be provoked by copying/writing large files (e.g. dding a 256MB file), but it happens occasionally otherwise. System memory usage (not including buffers/caches) currently sits at 36%, which is typical[1]. Initially I had no swap space configured; I've since tried enabling a 256MB swap file, but the problem continues to occur and no swap space is used. The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`. Happy to provide further information/take further debugging actions. [1] Full output from `free`: total used free sharedbuffers cached Mem: 1014936 483448 531488 28556 9756 112700 -/+ buffers/cache: 360992 653944 Swap: 262140 0 262140 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 19:40 seq crw-rw 1 root audio 116, 33 Nov 19 19:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Nov 20 20:44:30 2015 Ec2AMI: ami-1c552a76 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1518457/+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 1609227] 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/1609227 Title: Issues on kernel/pid.c file . Status in linux package in Ubuntu: Confirmed Bug description: For more info run perf report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu4646 F pulseaudio CurrentDesktop: LXDE Date: Wed Aug 3 07:53:32 2016 InstallationDate: Installed on 2016-04-29 (95 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609227/+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 1609225] [NEW] Issue on arch/x86/lib/delay.c file .
Public bug reported: For more info run perf report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu4646 F pulseaudio CurrentDesktop: LXDE Date: Wed Aug 3 07:53:21 2016 InstallationDate: Installed on 2016-04-29 (95 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial ** Patch added: "Tested on linux-4.6.2" https://bugs.launchpad.net/bugs/1609225/+attachment/4712782/+files/0001-Issue-on-arch-x86-lib-delay.c-file-.c.patch -- 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/1609225 Title: Issue on arch/x86/lib/delay.c file . Status in linux package in Ubuntu: Confirmed Bug description: For more info run perf report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu4646 F pulseaudio CurrentDesktop: LXDE Date: Wed Aug 3 07:53:21 2016 InstallationDate: Installed on 2016-04-29 (95 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609225/+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 1609225] 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/1609225 Title: Issue on arch/x86/lib/delay.c file . Status in linux package in Ubuntu: Confirmed Bug description: For more info run perf report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu4646 F pulseaudio CurrentDesktop: LXDE Date: Wed Aug 3 07:53:21 2016 InstallationDate: Installed on 2016-04-29 (95 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609225/+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 1609226] 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/1609226 Title: Issues on arch/x86/include/asm/apic.h file . Status in linux package in Ubuntu: Confirmed Bug description: For more info run perf report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu4646 F pulseaudio CurrentDesktop: LXDE Date: Wed Aug 3 07:53:11 2016 InstallationDate: Installed on 2016-04-29 (95 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609226/+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 1609226] [NEW] Issues on arch/x86/include/asm/apic.h file .
Public bug reported: For more info run perf report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu4646 F pulseaudio CurrentDesktop: LXDE Date: Wed Aug 3 07:53:11 2016 InstallationDate: Installed on 2016-04-29 (95 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial ** Patch added: "Tested on linux-4.6.2" https://bugs.launchpad.net/bugs/1609226/+attachment/4712797/+files/0001-Issues-on-arch-x86-include-asm-apic.h-file.patch -- 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/1609226 Title: Issues on arch/x86/include/asm/apic.h file . Status in linux package in Ubuntu: Confirmed Bug description: For more info run perf report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu4646 F pulseaudio CurrentDesktop: LXDE Date: Wed Aug 3 07:53:11 2016 InstallationDate: Installed on 2016-04-29 (95 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609226/+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 1609227] [NEW] Issues on kernel/pid.c file .
Public bug reported: For more info run perf report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu4646 F pulseaudio CurrentDesktop: LXDE Date: Wed Aug 3 07:53:32 2016 InstallationDate: Installed on 2016-04-29 (95 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial ** Patch added: "Tested on linux-4.6.2" https://bugs.launchpad.net/bugs/1609227/+attachment/4712812/+files/0001-Issues-on-kernel-pid.c-file.patch -- 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/1609227 Title: Issues on kernel/pid.c file . Status in linux package in Ubuntu: Confirmed Bug description: For more info run perf report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu4646 F pulseaudio CurrentDesktop: LXDE Date: Wed Aug 3 07:53:32 2016 InstallationDate: Installed on 2016-04-29 (95 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609227/+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 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea
4.1.29 seems to be working, at least it didn't freeze for 2 days and still work now, but intel_idle.max_cstate=1 is enabled. I'll remove it and see will the system be stable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1575467 Title: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts- utopic-vy2yyy/linux-lts- utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i915]() Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: After upgrading from stock Ubuntu 14.04 to 16.04 my laptop consistently freezes up and is unresponsive to keyboard or mouse. The only way is to do a hard shutdown. I'm usually in a browser when this happens, and often watching a video or two. It seems to happen more often in Google Chrome than Firefox, but it happens with both. It has happened at least once with no videos loaded. I haven’t observed it freeze / hang when I’m not in a browser, but that's mainly what i use my laptop for, so that's where most of my time is spent. Call trace: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrew 1949 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020 InstallationDate: Installed on 2015-08-08 (263 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 3451 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0H4MK6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3451 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+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 1609204] Re: Power Menu does not display after press the Power Button
>From Win 8.1+, BIOS might use the new way to handle the power button, it's >called intel virtual button. BIOS should switch to the new way while detecting there is a driver which supports it, but in this case, BIOS switches to the new way no matter there is a driver for it or not. And once this case happens, the power button emits the keyevent only after pressing it for 6 seconds. To fix it, we need this driver to be loaded and emits the keyevent once it's pressed. -- 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/1609204 Title: Power Menu does not display after press the Power Button Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Bug description: Steps: 1) Install BTO and boot into OS 2) Press the Power Button Expected results: Power Menu should display after press the Power Button Actual results: Power Menu does not display after press the Power Button Manufacturer: Dell Inc. ProductName: XPS 13 BiosVersion: 0.1.4 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1609204/+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 1609204] Re: Power Menu does not display after press the Power Button
This commit fixes this issue. commit 332e081225fc2a657aa587c42943d5f5a7dae88b Author: AceLan Kao Date: Fri Jul 1 09:51:49 2016 +0800 intel-vbtn: new driver for Intel Virtual Button This driver supports power button event in Intel Virtual Button currently. New Dell XPS 13 requires this driver for the power button. This driver is copied/modified from intel-hid.c Most credit goes to the author of intel-hid.c, Alex Hung Signed-off-by: AceLan Kao Signed-off-by: Darren Hart ** Changed in: hwe-next Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: hwe-next Status: New => In Progress -- 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/1609204 Title: Power Menu does not display after press the Power Button Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Bug description: Steps: 1) Install BTO and boot into OS 2) Press the Power Button Expected results: Power Menu should display after press the Power Button Actual results: Power Menu does not display after press the Power Button Manufacturer: Dell Inc. ProductName: XPS 13 BiosVersion: 0.1.4 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1609204/+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 1609204] [NEW] Power Menu does not display after press the Power Button
Public bug reported: Steps: 1) Install BTO and boot into OS 2) Press the Power Button Expected results: Power Menu should display after press the Power Button Actual results: Power Menu does not display after press the Power Button Manufacturer: Dell Inc. ProductName: XPS 13 BiosVersion: 0.1.4 ** Affects: hwe-next Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress -- 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/1609204 Title: Power Menu does not display after press the Power Button Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Bug description: Steps: 1) Install BTO and boot into OS 2) Press the Power Button Expected results: Power Menu should display after press the Power Button Actual results: Power Menu does not display after press the Power Button Manufacturer: Dell Inc. ProductName: XPS 13 BiosVersion: 0.1.4 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1609204/+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 1607571] Re: No network devices after suspend and resume
I installed http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/ generic amd64 However, there is no /sys/power/pm_trace. Do I need to do something else? From the article, it seems that the kernel should have that already. Any advice on how to turn it on? or install it? My google-fu didn't return any pointers on how to achieve it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1607571 Title: No network devices after suspend and resume Status in linux package in Ubuntu: Incomplete Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+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 1607571] Re: No network devices after suspend and resume
adin, it looks like you didn't attach the files while using the latest mainline kernel (which is now 4.7), as the article advises. -- 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/1607571 Title: No network devices after suspend and resume Status in linux package in Ubuntu: Incomplete Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+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 1609136] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1609136 Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: Computer froze mid-update to 16.04 and this package has been causing issues ever since. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: conor 3396 F pulseaudio /dev/snd/controlC0: conor 3396 F pulseaudio Date: Tue Aug 2 13:43:11 2016 DuplicateSignature: package:linux-image-4.4.0-31-generic:4.4.0-31.50 Setting up linux-image-4.4.0-31-generic (4.4.0-31.50) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-31-generic) dpkg: error processing package linux-image-4.4.0-31-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=f1ae685c-aae5-45b9-aa80-306721d24f95 InstallationDate: Installed on 2015-01-06 (573 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/ubuntu--vg-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: grub-pc 2.02~beta2-36ubuntu3.1 SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-08-01 (1 days ago) dmi.bios.date: 06/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3624 dmi.board.vendor: Quanta dmi.board.version: 18.37 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.24:bd06/12/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.37:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609136/+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 1528230] Re: [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py -- ONEXEC - check current 'unconfined' != expected
I've thoroughly tested apparmor 2.10.95-0ubuntu2.2 in xenial-proposed. I've verified that this bug is fixed (via QRT's test-apparmor.py, as mentioned in Test Case in the description) and I've also went through the AppArmor Test Plan (excluding the Ubuntu Touch specific tests): https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor The Test Plan includes running the entire set of upstream AppArmor tests, a number of integration tests, libvirt tests, LXC/LXD tests, docker.io tests, Snappy confinement tests, etc. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1528230 Title: [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py -- ONEXEC - check current 'unconfined' != expected Status in AppArmor: Fix Committed Status in QA Regression Testing: Invalid Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in apparmor source package in Xenial: Fix Committed Status in linux source package in Xenial: Invalid Bug description: [Impact] The AppArmor regression tests are ran as part of the kernel SRU verification process. One of the tests, onexec.sh, contains a racy section that introduces intermittent failures. Such failures introduce doubt in the kernel SRU process and generate additional work to verify that the failures can be ignored. [Test Case] Since the fix is to the onexec.sh test itself, the best test case is to simply run the test. The QRT test-apparmor.py script runs this test, among many others, and should be used for verification. [Regression Potential] None. The fix is to the test and does not affect code that is user- facing. [Original Report] New ADT test failure in Vivid: running onexec ONEXEC - check current 'unconfined' != expected '/tmp/testlibIUFsmN/source/vivid/apparmor-2.9.1/tests/regression/apparmor/onexec' Fatal Error (onexec): Unable to run test sub-executable Full log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid/vivid/ppc64el/l/linux/20151218_175610@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1528230/+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 1607571] Re: No network devices after suspend and resume
** Attachment added: "dmesg_devices.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+attachment/4712656/+files/dmesg_devices.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/1607571 Title: No network devices after suspend and resume Status in linux package in Ubuntu: Incomplete Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+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 1607571] Re: No network devices after suspend and resume
** Attachment added: "wakeup.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+attachment/4712662/+files/wakeup.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/1607571 Title: No network devices after suspend and resume Status in linux package in Ubuntu: Incomplete Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+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 1605433] Re: [Dell Alienware 17R3] enable/disable touchpad not working
** Attachment added: "udev-db.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605433/+attachment/4712665/+files/udev-db.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/1605433 Title: [Dell Alienware 17R3] enable/disable touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: The touchpad does not work as expected. It can't be enabled or disabled through FN+F11 combination. The light (in the pad) always turns on, regardless of its non functionality. The problem seems related to bug #1523738, and some say solution #24 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523738/comments/24) works, but it didn't for me. I'm not even sure if it is the same as the version of the hardware is different. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Jul 21 21:07:42 2016 InstallationDate: Installed on 2016-07-03 (18 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2016-07-16T11:29:07.694480 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 4247 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (24 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 Tags: xenial Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605433/+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 1605433] Re: [Dell Alienware 17R3] enable/disable touchpad not working
Attaching them again. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605433/+attachment/4712663/+files/dmesg.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/1605433 Title: [Dell Alienware 17R3] enable/disable touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: The touchpad does not work as expected. It can't be enabled or disabled through FN+F11 combination. The light (in the pad) always turns on, regardless of its non functionality. The problem seems related to bug #1523738, and some say solution #24 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523738/comments/24) works, but it didn't for me. I'm not even sure if it is the same as the version of the hardware is different. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Jul 21 21:07:42 2016 InstallationDate: Installed on 2016-07-03 (18 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2016-07-16T11:29:07.694480 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 4247 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (24 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 Tags: xenial Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605433/+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 1605433] Re: [Dell Alienware 17R3] enable/disable touchpad not working
** Attachment added: "lsinput.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605433/+attachment/4712664/+files/lsinput.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/1605433 Title: [Dell Alienware 17R3] enable/disable touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: The touchpad does not work as expected. It can't be enabled or disabled through FN+F11 combination. The light (in the pad) always turns on, regardless of its non functionality. The problem seems related to bug #1523738, and some say solution #24 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523738/comments/24) works, but it didn't for me. I'm not even sure if it is the same as the version of the hardware is different. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Jul 21 21:07:42 2016 InstallationDate: Installed on 2016-07-03 (18 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2016-07-16T11:29:07.694480 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 4247 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (24 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 Tags: xenial Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605433/+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 1607571] Re: No network devices after suspend and resume
** Attachment added: "suspend_stats.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+attachment/4712661/+files/suspend_stats.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/1607571 Title: No network devices after suspend and resume Status in linux package in Ubuntu: Incomplete Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+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 1607571] Re: No network devices after suspend and resume
** Attachment added: "dmesg_processors.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+attachment/4712660/+files/dmesg_processors.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/1607571 Title: No network devices after suspend and resume Status in linux package in Ubuntu: Incomplete Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+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 1607571] Re: No network devices after suspend and resume
I'm completing the log report: Which part of the process does the issue occur with, the suspend to ram, or resuming from? The network interface is not showing, thus no networks appear in the network manager. Consequently, there is no internet. Please advise how you suspended specifically. For example: Shutting the lid of the laptop, which is set to suspend on close. Please advise how you resumed specifically. For example: Lifted the lid I'm going to attach the log files in the next posts (the interface allows one attachment and the instructions ask for not compressed files) ** Attachment added: "dmesg_core.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+attachment/4712655/+files/dmesg_core.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/1607571 Title: No network devices after suspend and resume Status in linux package in Ubuntu: Incomplete Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+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 1607571] Re: No network devices after suspend and resume
** Attachment added: "dmesg_none.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+attachment/4712658/+files/dmesg_none.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/1607571 Title: No network devices after suspend and resume Status in linux package in Ubuntu: Incomplete Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+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 1607571] Re: No network devices after suspend and resume
** Attachment added: "dmesg_platform.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+attachment/4712659/+files/dmesg_platform.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/1607571 Title: No network devices after suspend and resume Status in linux package in Ubuntu: Incomplete Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+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 1607571] Re: No network devices after suspend and resume
** Attachment added: "dmesg_freezer.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+attachment/4712657/+files/dmesg_freezer.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/1607571 Title: No network devices after suspend and resume Status in linux package in Ubuntu: Incomplete Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+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 1609143] [NEW] "lsluns" does not display ds8k lun information and unable to activate ds8k storage luns in host
Public bug reported: == Comment: #2 - Steffen Maier - 2016-08-01 09:54:09 == While LTC bug 139096 - LP1567602 : FCP devices are not detected correctly nor deterministically did successfully fix the attachment of "regular" LUNs of (peripheral device) type disk, it seems the attachment of the (report luns) WLUN 0xc101 (49409) still shows issues with the ALUA device handler: [ 105.049479] scsi 0:0:7:49409: Well-known LUNIBM 2107900 .470 PQ: 0 ANSI: 5 [ 105.050109] scsi 0:0:7:49409: alua: disable for non-disk devices [ 105.050112] scsi 0:0:7:49409: alua: Attach failed (-22) [ 105.050114] scsi 0:0:7:49409: failed to add device handler: -22 After this failed attempt to attach such LUN (here triggered by the "lsluns" tool from s390-tools to discover LUNs from out of user space), the corresponding SCSI device is INvisible from user space, but still exists in-kernel in some broken state. In our case here, the attachment should have been successful (or the scsi_device been unregistered completely in maybe other cases). On the next attempt to run lsluns against the same target remote port and thus the same WLUN SCSI device, we get the following kernel warning as a follow-on error: [ 572.079588] scsi 0:0:7:49409: Well-known LUNIBM 2107900 .470 PQ: 0 ANSI: 5 [ 572.080354] sysfs: cannot create duplicate filename '/bus/scsi/devices/0:0:7:49409' [ 572.080380] [ cut here ] [ 572.080381] WARNING: at /build/linux-0ECIDW/linux-4.4.0/fs/sysfs/dir.c:31 [ 572.080381] Modules linked in: qeth_l3 chsc_sch eadm_sch qeth ccwgroup ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc btrfs zlib_deflate raid10 raid456 async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_round_robin ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common dasd_eckd_mod dasd_mod zfcp qdio scsi_transport_fc scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 572.080404] CPU: 1 PID: 8494 Comm: sh Not tainted 4.4.0-31-generic #50-Ubuntu [ 572.080405] task: 0001d7740af0 ti: 0001d8144000 task.ti: 0001d8144000 [ 572.080406] Krnl PSW : 0704c0018000 003a35fc (sysfs_warn_dup+0x7c/0x98) [ 572.080415]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 EA:3 Krnl GPRS: 00cf7034 0006 0047 [ 572.080417]003a35f8 02c6 0001da805400 0001d8f2f178 [ 572.080417]00c1d0e0 0001e8cd3ab8 0001 0001e8cd3ab8 [ 572.080418]0001d8cac4b0 7b7c8000 003a35f8 0001d81479b8 [ 572.080425] Krnl Code: 003a35ec: c020002f33f3larl %r2,989dd2 003a35f2: c0e5fff6bf0bbrasl %r14,27b408 #003a35f8: a7f40001brc 15,3a35fa >003a35fc: b904002dlgr %r2,%r13 003a3600: ebbff0a4lmg %r11,%r15,160(%r15) 003a3606: c0f4fffa5999brcl 15,2ee938 003a360c: a739lghi%r3,0 003a3610: a7f4ffecbrc 15,3a35e8 [ 572.080438] Call Trace: [ 572.080440] ([<003a35f8>] sysfs_warn_dup+0x78/0x98) [ 572.080443] [<003a3b10>] sysfs_do_create_link_sd.isra.0+0xf8/0x108 [ 572.080447] [<005c4004>] bus_add_device+0x13c/0x230 [ 572.080448] [<005c1718>] device_add+0x398/0x680 [ 572.080453] [<005f79bc>] scsi_sysfs_add_sdev+0xcc/0x2a8 [ 572.080456] [<005f4198>] scsi_probe_and_add_lun+0xcc0/0xe18 [ 572.080457] [<005f4be2>] __scsi_scan_target+0xba/0x268 [ 572.080458] [<005f4e92>] scsi_scan_target+0x102/0x120 [ 572.080468] [<03ff800765f6>] zfcp_unit_scsi_scan+0x7e/0x90 [zfcp] [ 572.080471] [<03ff80076948>] zfcp_unit_add+0x168/0x1f0 [zfcp] [ 572.080474] [<03ff80075564>] zfcp_sysfs_unit_add_store+0x54/0x70 [zfcp] [ 572.080476] [<003a1d7a>] kernfs_fop_write+0x13a/0x190 [ 572.080480] [<0030fc94>] vfs_write+0x94/0x1a0 [ 572.080482] [<003109a6>] SyS_write+0x66/0xd8 [ 572.080484] [<007b844e>] system_call+0xd6/0x264 [ 572.080485] [<03ff9fc5f6e8>] 0x3ff9fc5f6e8 [ 572.080486] Last Breaking-Event-Address: [ 572.080487] [<003a35f8>] sysfs_warn_dup+0x78/0x98 [ 572.080487] ---[ end trace 622dfcc1a25e342e ]--- [ 572.080504] scsi 0:0:7:49409: failed to add device: -17 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-144325
[Kernel-packages] [Bug 1609143] [NEW] "lsluns" does not display ds8k lun information and unable to activate ds8k storage luns in host
You have been subscribed to a public bug: == Comment: #2 - Steffen Maier - 2016-08-01 09:54:09 == While LTC bug 139096 - LP1567602 : FCP devices are not detected correctly nor deterministically did successfully fix the attachment of "regular" LUNs of (peripheral device) type disk, it seems the attachment of the (report luns) WLUN 0xc101 (49409) still shows issues with the ALUA device handler: [ 105.049479] scsi 0:0:7:49409: Well-known LUNIBM 2107900 .470 PQ: 0 ANSI: 5 [ 105.050109] scsi 0:0:7:49409: alua: disable for non-disk devices [ 105.050112] scsi 0:0:7:49409: alua: Attach failed (-22) [ 105.050114] scsi 0:0:7:49409: failed to add device handler: -22 After this failed attempt to attach such LUN (here triggered by the "lsluns" tool from s390-tools to discover LUNs from out of user space), the corresponding SCSI device is INvisible from user space, but still exists in-kernel in some broken state. In our case here, the attachment should have been successful (or the scsi_device been unregistered completely in maybe other cases). On the next attempt to run lsluns against the same target remote port and thus the same WLUN SCSI device, we get the following kernel warning as a follow-on error: [ 572.079588] scsi 0:0:7:49409: Well-known LUNIBM 2107900 .470 PQ: 0 ANSI: 5 [ 572.080354] sysfs: cannot create duplicate filename '/bus/scsi/devices/0:0:7:49409' [ 572.080380] [ cut here ] [ 572.080381] WARNING: at /build/linux-0ECIDW/linux-4.4.0/fs/sysfs/dir.c:31 [ 572.080381] Modules linked in: qeth_l3 chsc_sch eadm_sch qeth ccwgroup ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc btrfs zlib_deflate raid10 raid456 async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_round_robin ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common dasd_eckd_mod dasd_mod zfcp qdio scsi_transport_fc scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 572.080404] CPU: 1 PID: 8494 Comm: sh Not tainted 4.4.0-31-generic #50-Ubuntu [ 572.080405] task: 0001d7740af0 ti: 0001d8144000 task.ti: 0001d8144000 [ 572.080406] Krnl PSW : 0704c0018000 003a35fc (sysfs_warn_dup+0x7c/0x98) [ 572.080415]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 EA:3 Krnl GPRS: 00cf7034 0006 0047 [ 572.080417]003a35f8 02c6 0001da805400 0001d8f2f178 [ 572.080417]00c1d0e0 0001e8cd3ab8 0001 0001e8cd3ab8 [ 572.080418]0001d8cac4b0 7b7c8000 003a35f8 0001d81479b8 [ 572.080425] Krnl Code: 003a35ec: c020002f33f3larl %r2,989dd2 003a35f2: c0e5fff6bf0bbrasl %r14,27b408 #003a35f8: a7f40001brc 15,3a35fa >003a35fc: b904002dlgr %r2,%r13 003a3600: ebbff0a4lmg %r11,%r15,160(%r15) 003a3606: c0f4fffa5999brcl 15,2ee938 003a360c: a739lghi%r3,0 003a3610: a7f4ffecbrc 15,3a35e8 [ 572.080438] Call Trace: [ 572.080440] ([<003a35f8>] sysfs_warn_dup+0x78/0x98) [ 572.080443] [<003a3b10>] sysfs_do_create_link_sd.isra.0+0xf8/0x108 [ 572.080447] [<005c4004>] bus_add_device+0x13c/0x230 [ 572.080448] [<005c1718>] device_add+0x398/0x680 [ 572.080453] [<005f79bc>] scsi_sysfs_add_sdev+0xcc/0x2a8 [ 572.080456] [<005f4198>] scsi_probe_and_add_lun+0xcc0/0xe18 [ 572.080457] [<005f4be2>] __scsi_scan_target+0xba/0x268 [ 572.080458] [<005f4e92>] scsi_scan_target+0x102/0x120 [ 572.080468] [<03ff800765f6>] zfcp_unit_scsi_scan+0x7e/0x90 [zfcp] [ 572.080471] [<03ff80076948>] zfcp_unit_add+0x168/0x1f0 [zfcp] [ 572.080474] [<03ff80075564>] zfcp_sysfs_unit_add_store+0x54/0x70 [zfcp] [ 572.080476] [<003a1d7a>] kernfs_fop_write+0x13a/0x190 [ 572.080480] [<0030fc94>] vfs_write+0x94/0x1a0 [ 572.080482] [<003109a6>] SyS_write+0x66/0xd8 [ 572.080484] [<007b844e>] system_call+0xd6/0x264 [ 572.080485] [<03ff9fc5f6e8>] 0x3ff9fc5f6e8 [ 572.080486] Last Breaking-Event-Address: [ 572.080487] [<003a35f8>] sysfs_warn_dup+0x78/0x98 [ 572.080487] ---[ end trace 622dfcc1a25e342e ]--- [ 572.080504] scsi 0:0:7:49409: failed to add device: -17 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s390
[Kernel-packages] [Bug 1609136] Re: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** 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/1609136 Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: New Bug description: Computer froze mid-update to 16.04 and this package has been causing issues ever since. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: conor 3396 F pulseaudio /dev/snd/controlC0: conor 3396 F pulseaudio Date: Tue Aug 2 13:43:11 2016 DuplicateSignature: package:linux-image-4.4.0-31-generic:4.4.0-31.50 Setting up linux-image-4.4.0-31-generic (4.4.0-31.50) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-31-generic) dpkg: error processing package linux-image-4.4.0-31-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=f1ae685c-aae5-45b9-aa80-306721d24f95 InstallationDate: Installed on 2015-01-06 (573 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/ubuntu--vg-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: grub-pc 2.02~beta2-36ubuntu3.1 SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-08-01 (1 days ago) dmi.bios.date: 06/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3624 dmi.board.vendor: Quanta dmi.board.version: 18.37 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.24:bd06/12/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.37:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609136/+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 1609137] Re: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
*** This bug is a duplicate of bug 1609136 *** https://bugs.launchpad.net/bugs/1609136 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1609136, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1609136 package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 -- 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/1609137 Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: New Bug description: Computer froze mid-update to 16.04 and this package has been causing issues ever since. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: conor 3396 F pulseaudio /dev/snd/controlC0: conor 3396 F pulseaudio Date: Tue Aug 2 13:43:11 2016 DuplicateSignature: package:linux-image-4.4.0-31-generic:4.4.0-31.50 Setting up linux-image-4.4.0-31-generic (4.4.0-31.50) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-31-generic) dpkg: error processing package linux-image-4.4.0-31-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=f1ae685c-aae5-45b9-aa80-306721d24f95 InstallationDate: Installed on 2015-01-06 (573 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/ubuntu--vg-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: grub-pc 2.02~beta2-36ubuntu3.1 SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-08-01 (1 days ago) dmi.bios.date: 06/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3624 dmi.board.vendor: Quanta dmi.board.version: 18.37 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.24:bd06/12/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.37:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609137/+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 1609136] [NEW] package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: Computer froze mid-update to 16.04 and this package has been causing issues ever since. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: conor 3396 F pulseaudio /dev/snd/controlC0: conor 3396 F pulseaudio Date: Tue Aug 2 13:43:11 2016 DuplicateSignature: package:linux-image-4.4.0-31-generic:4.4.0-31.50 Setting up linux-image-4.4.0-31-generic (4.4.0-31.50) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-31-generic) dpkg: error processing package linux-image-4.4.0-31-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=f1ae685c-aae5-45b9-aa80-306721d24f95 InstallationDate: Installed on 2015-01-06 (573 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/ubuntu--vg-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: grub-pc 2.02~beta2-36ubuntu3.1 SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-08-01 (1 days ago) dmi.bios.date: 06/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3624 dmi.board.vendor: Quanta dmi.board.version: 18.37 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.24:bd06/12/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.37:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1609136 Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: New Bug description: Computer froze mid-update to 16.04 and this package has been causing issues ever since. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: conor 3396 F pulseaudio /dev/snd/controlC0: conor 3396 F pulseaudio Date: Tue Aug 2 13:43:11 2016 DuplicateSignature: package:linux-image-4.4.0-31-generic:4.4.0-31.50 Setting up linux-image-4.4.0-31-generic (4.4.0-31.50) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-31-generic) dpkg: error processing package linux-image-4.4.0-31-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=f1ae685c-aae5-45b9-aa80-306721d24f95 InstallationDate: Installed on 2015-01-06 (573 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/ubuntu--vg-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: grub-pc 2.02~beta2-36ubuntu3.1 SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-08-01 (1 days ago) dmi.bios.date: 06/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3624 dmi.board.vendor: Quanta dmi.board.version: 18.37 dmi.chassis.type: 10 dmi.chassis
[Kernel-packages] [Bug 1609137] [NEW] package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
*** This bug is a duplicate of bug 1609136 *** https://bugs.launchpad.net/bugs/1609136 Public bug reported: Computer froze mid-update to 16.04 and this package has been causing issues ever since. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: conor 3396 F pulseaudio /dev/snd/controlC0: conor 3396 F pulseaudio Date: Tue Aug 2 13:43:11 2016 DuplicateSignature: package:linux-image-4.4.0-31-generic:4.4.0-31.50 Setting up linux-image-4.4.0-31-generic (4.4.0-31.50) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-31-generic) dpkg: error processing package linux-image-4.4.0-31-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=f1ae685c-aae5-45b9-aa80-306721d24f95 InstallationDate: Installed on 2015-01-06 (573 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/ubuntu--vg-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: grub-pc 2.02~beta2-36ubuntu3.1 SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-08-01 (1 days ago) dmi.bios.date: 06/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3624 dmi.board.vendor: Quanta dmi.board.version: 18.37 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.24:bd06/12/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.37:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1609137 Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: New Bug description: Computer froze mid-update to 16.04 and this package has been causing issues ever since. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: conor 3396 F pulseaudio /dev/snd/controlC0: conor 3396 F pulseaudio Date: Tue Aug 2 13:43:11 2016 DuplicateSignature: package:linux-image-4.4.0-31-generic:4.4.0-31.50 Setting up linux-image-4.4.0-31-generic (4.4.0-31.50) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-31-generic) dpkg: error processing package linux-image-4.4.0-31-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=f1ae685c-aae5-45b9-aa80-306721d24f95 InstallationDate: Installed on 2015-01-06 (573 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/ubuntu--vg-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: grub-pc 2.02~beta2-36ubuntu3.1 SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-08-01 (1 days ago) dmi.bios.date: 06/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 362
[Kernel-packages] [Bug 1604814] Re: Newest kernel update disables wireless and touchpad
** Also affects: linux Importance: Undecided Status: New -- 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/1604814 Title: Newest kernel update disables wireless and touchpad Status in Linux: New Status in linux package in Ubuntu: Invalid Bug description: Issue: kernel 3.13.0-91: both wireless and touchpad worked as expected (report was generated using this kernel) after updating to kernel 3.13.0-92: neither wireless nor touchpad work. Network does not even show to enable wifi, so no SSID-s are seen. Touchpad simply not reacts, no mouse symbol. Computer: Lenovo Flex 2 14" Wireless card: Broadcom Corporation BCM43142 802.11b/g/n, Driver: using Broadcom 802.11 Linux STA wireless driver source from bcmwl-kernel-source (proprietary) Touchpad: I: Bus=0011 Vendor=0002 Product=000e Version= N: Name="ETPS/2 Elantech Touchpad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input18 U: Uniq= H: Handlers=mouse0 event4 B: PROP=5 B: EV=b B: KEY=e420 1 0 0 0 0 B: ABS=66180001103 OS: Ubuntu 14.04 x64 /proc/version_signature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-91-generic 3.13.0-91.138 ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39 Uname: Linux 3.13.0-91-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kj 1726 F pulseaudio /dev/snd/controlC0: kj 1726 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 20 14:49:43 2016 HibernationDevice: RESUME=UUID=c434037e-9055-4781-9625-3f59f90ef7bd InstallationDate: Installed on 2014-12-07 (591 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0446 Elan Microelectronics Corp. Bus 001 Device 003: ID 105b:e065 Foxconn International, Inc. BCM43142A0 Bluetooth module Bus 001 Device 002: ID 0bda:579c Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20404 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed root=UUID=774a220e-0926-4480-84aa-32c562f2062b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-91-generic N/A linux-backports-modules-3.13.0-91-generic N/A linux-firmware 1.127.22 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A0CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Flex 2-14 dmi.board.vendor: LENOVO dmi.board.version: 31900058 Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Flex 2-14 dmi.modalias: dmi:bvnLENOVO:bvrA0CN31WW:bd10/08/2014:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoFlex2-14: dmi.product.name: 20404 dmi.product.version: Lenovo Flex 2-14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1604814/+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 1583738] Re: arm64: statically link rtc-efi
ubuntu@ubuntu:~$ cat /proc/version Linux version 3.19.0-66-generic (buildd@bos01-arm64-026) (gcc version 4.9.2 (Ubuntu/Linaro 4.9.2-10ubuntu13) ) #74-Ubuntu SMP Tue Jul 19 15:05:47 UTC 2016 ubuntu@ubuntu:~$ dmesg | grep rtc [0.707709] rtc-efi rtc-efi: rtc core: registered rtc-efi as rtc0 [0.740633] rtc-efi rtc-efi: setting system clock to 2016-08-02 15:33:58 UTC (1470152038) ** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1583738 Title: arm64: statically link rtc-efi Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: [Impact] The rtc-hctosys driver currently fails to set the system clock on arm64/efi platforms because rtc-efi is built as a module. [Test Case] if dmesg | grep -q 'rtc-efi: setting system clock'; then PASS else FAIL fi [Regression Risk] This is just a config change, and one that we used to ship in utopic and trusty w/ no known regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1583738/+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 1609107] [NEW] Ota13
Public bug reported: Without ota13 bluetooth doesn't work anymore in my m10 tablet anymore. Keyboard and mouse donut connct and bluetooth switches itself off all the time. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1609107 Title: Ota13 Status in bluez package in Ubuntu: New Bug description: Without ota13 bluetooth doesn't work anymore in my m10 tablet anymore. Keyboard and mouse donut connct and bluetooth switches itself off all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1609107/+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 1494225] Re: Call audio is not routed to headset with HFP
@John I think, yes. N-Com BT3 is mono headset. Other car bt set work properly. -- 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/1494225 Title: Call audio is not routed to headset with HFP Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in media-hub package in Ubuntu: Invalid Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: With bluez 5.33 on Nexus 4 and silo 43 installed: * pair and connect a headset over HFP * Establish an outgoing call or accept an incoming one * Once the call is established the call audio isn't routed through the handsfree device To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+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 1477466] Re: Low performance when using vlan over VxLan
Closing as incomplete since we are missing required information ** Changed in: linux (Ubuntu) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Vivid) Status: In Progress => Incomplete -- 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/1477466 Title: Low performance when using vlan over VxLan Status in linux package in Ubuntu: Incomplete Status in linux source package in Vivid: Incomplete Bug description: We see a performance issue when running traffic over vlan interface that created over VxLAN interface. We reach 24 Gbps over the VxLan interface while we reach only 4 Gbps over the VLAN interface. Turned out that GRO isn't supported for VLAN over VxLAN. The following upstream commits fix this issue. commit 66e5133f19e901a044fa5eaeeb6ecff4545839e5 Author: Toshiaki Makita Date: Mon Jun 1 21:55:06 2015 +0900 vlan: Add GRO support for non hardware accelerated vlan Currently packets with non-hardware-accelerated vlan cannot be handled by GRO. This causes low performance for 802.1ad and stacked vlan, as their vlan tags are currently not stripped by hardware. This patch adds GRO support for non-hardware-accelerated vlan and improves receive performance of them. commit 9b174d88c257150562b0101fcc6cb6c3cb74275c Author: Jesse Gross Date: Tue Dec 30 19:10:15 2014 -0800 net: Add Transparent Ethernet Bridging GRO support. Currently the only tunnel protocol that supports GRO with encapsulated Ethernet is VXLAN. This pulls out the Ethernet code into a proper layer so that it can be used by other tunnel protocols such as GRE and Geneve. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477466/+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 1554371] Re: [Regression] Volume keys not working after suspend/resume
I just got the same problem with my Ubuntu 16.04. Suddenly the volume keys stopped working. All the other keys works, but the volume keys don't. Even 'xev' show them. All the rest work fine. -- 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/1554371 Title: [Regression] Volume keys not working after suspend/resume Status in linux package in Ubuntu: Invalid Bug description: I have a Microsoft Sculpt Ergonomic Desktop (keyboard/mouse combo). It was working great with Ubuntu 15.10. After upgrading to 16.04, the media keys stop working after suspending and resuming. This seems to be the relevant error from Xorg.log: [ 176.121] (EE) evdev: Microsoft Microsoft® 2.4GHz Transceiver v9.0: Unable to open evdev device "/dev/input/event6". The USB receiver creates 5 devices: lrwxrwxrwx 1 root root 9 Mar 7 20:17 usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-event-kbd -> ../event4 lrwxrwxrwx 1 root root 9 Mar 7 20:17 usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if01-event-mouse -> ../event5 lrwxrwxrwx 1 root root 9 Mar 7 20:17 usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if01-mouse -> ../mouse1 lrwxrwxrwx 1 root root 9 Mar 7 20:17 usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if02-event-kbd -> ../event6 lrwxrwxrwx 1 root root 6 Mar 7 20:17 usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if02-kbd -> ../js0 After suspending and resuming, the last 2 devices (event6 and js0) disappear. I have tried booting up into the Vivid and Trusty kernels, and the problem persists, so at first glance it doesn't seem to be an issue with the kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-4-generic 4.4.0-4.19 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: furkan 2733 F pulseaudio /dev/snd/controlC1: furkan 2733 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 7 20:17:56 2016 HibernationDevice: RESUME=UUID=a8eb7091-e848-4e63-82a1-8fa9562a3a61 InstallationDate: Installed on 2014-06-06 (640 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic root=UUID=d254b01f-2bf2-4b57-acdc-c796786f4c4c ro RelatedPackageVersions: linux-restricted-modules-4.4.0-4-generic N/A linux-backports-modules-4.4.0-4-generic N/A linux-firmware 1.156 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-01-04 (63 days ago) dmi.bios.date: 05/30/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-970A-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554371/+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 1609074] 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/1609074 Title: Screen flicker on 16.04 Status in linux package in Ubuntu: Confirmed Bug description: The computer running Ubuntu is being used as HTPC connected via HDMI to a screen projector. After upgrading to 16.04, it's unusable under production kernel. The screen starts flickering after a while (it's easily triggered by fast scrolling e.g. terminal's window). The whole screen get's filled with a noise, and then the projector gets disconnected for a while. The computer runs fine on an older kernel (4.2.0-35), it's still broken on the mainline kernel 4.7.0. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pwiecz 3977 F pulseaudio /dev/snd/controlC1: pwiecz 3977 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 2 19:40:29 2016 InstallationDate: Installed on 2014-02-02 (912 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. H87N-WIFI ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=98e2c9a3-1a1a-4d21-b370-79d0cde7b5f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-27 (97 days ago) dmi.bios.date: 08/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87N-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd08/18/2015:svnGigabyteTechnologyCo.,Ltd.:pnH87N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H87N-WIFI dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609074/+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 1609074] [NEW] Screen flicker on 16.04
Public bug reported: The computer running Ubuntu is being used as HTPC connected via HDMI to a screen projector. After upgrading to 16.04, it's unusable under production kernel. The screen starts flickering after a while (it's easily triggered by fast scrolling e.g. terminal's window). The whole screen get's filled with a noise, and then the projector gets disconnected for a while. The computer runs fine on an older kernel (4.2.0-35), it's still broken on the mainline kernel 4.7.0. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pwiecz 3977 F pulseaudio /dev/snd/controlC1: pwiecz 3977 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 2 19:40:29 2016 InstallationDate: Installed on 2014-02-02 (912 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. H87N-WIFI ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=98e2c9a3-1a1a-4d21-b370-79d0cde7b5f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-27 (97 days ago) dmi.bios.date: 08/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87N-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd08/18/2015:svnGigabyteTechnologyCo.,Ltd.:pnH87N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H87N-WIFI dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** 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/1609074 Title: Screen flicker on 16.04 Status in linux package in Ubuntu: New Bug description: The computer running Ubuntu is being used as HTPC connected via HDMI to a screen projector. After upgrading to 16.04, it's unusable under production kernel. The screen starts flickering after a while (it's easily triggered by fast scrolling e.g. terminal's window). The whole screen get's filled with a noise, and then the projector gets disconnected for a while. The computer runs fine on an older kernel (4.2.0-35), it's still broken on the mainline kernel 4.7.0. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pwiecz 3977 F pulseaudio /dev/snd/controlC1: pwiecz 3977 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 2 19:40:29 2016 InstallationDate: Installed on 2014-02-02 (912 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. H87N-WIFI ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=98e2c9a3-1a1a-4d21-b370-79d0cde7b5f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-27 (97 days ago) dmi.bios.date: 08/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87N-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd08/18/2015:svnGigabyteTechnologyCo.,Ltd.:pnH87N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H87N-WIFI dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte T
[Kernel-packages] [Bug 1413008] Re: Kernel BUG shortly after mounting btrfs filesystem
Please test. If no test occurs by August 15th I will close the bug. -- 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/1413008 Title: Kernel BUG shortly after mounting btrfs filesystem Status in linux package in Ubuntu: Incomplete Bug description: This bug happens entirely reproducibly after mounting a multi-disc btrfs filesystem I have. It is reproducible on the current Vivid 3.18 kernel and the mainline 3.19-rc5 build; I recall this bug also happening on Utopic's 3.16 kernel, but don't have logs. All processes that touch the filesystem then hang indefinitely in the kernel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 21 10:03 seq crw-rw+ 1 root audio 116, 33 Jan 21 10:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jan 21 10:05:37 2015 InstallationDate: Installed on 2015-01-20 (0 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Alpha amd64 (20150116) IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: HP ProLiant MicroServer PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic root=UUID=b5d97f60-81e7-4dd8-a8a7-b2bfef3eeb52 ro rootflags=subvol=@ init=/lib/systemd/systemd RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2013 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd10/01/2013:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413008/+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 1608652] Re: [Ubuntu 16.04] FCoE Lun not visible in OS with inbox driver - Issue with ioremap() call on 32bit kernel
Yes I will update the bz with the commit ID after we push it upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1608652 Title: [Ubuntu 16.04] FCoE Lun not visible in OS with inbox driver - Issue with ioremap() call on 32bit kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Broadcom has a fix for this issue that it will be sending upstream on/by 8/15/16 BUG REPRODUCTION DETAILS Test Case Instance- Reproducibility of Bug- Always Last Known Working Build - NA Time to Reproduce Bug - 5 Minutes Steps To Reproduce Bug- == 1. Map a LUN and make sure the FCoE Lun is visible in the UEFI/ as well as Legacy BIOS 2. Boot to OS, and check "fdisk -l" the Lun is not listed. Logs ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ modinfo lpfc|grep -i version version:0:11.0.0.10. srcversion: 77EBC3EEDF32DABDDF14B7F vermagic: 4.4.0-22-generic SMP mod_unload modversions 686 ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ lsmod|grep lpfc lpfc 614400 0 scsi_transport_fc 57344 1 lpfc ubuntu_sl@dhcp-10-227-71-12:~$ cd /sys/class/fc_host ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ ls ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ dmesg logs == ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ dmesg|grep lpfc [ 12.521665] Modules linked in: hid_generic ahci crc32_pclmul lpfc(+) igb be2net aesni_intel ptp aes_i586 vxlan xts pps_core libahci usbhid lrw scsi_transport_fc gf128mul megaraid_sas ablk_helper wmi ip6_udp_tunnel cryptd hid i2c_algo_bit udp_tunnel fjes [ 13.532543] [] ? lpfc_pci_probe_one_s4.isra.38+0x207/0x970 [lpfc] [ 13.581554] [] ? lpfc_pci_probe_one_s4.isra.38+0x207/0x970 [lpfc] [ 13.675661] [] ? lpfc_pci_probe_one_s4.isra.38+0x207/0x970 [lpfc] [ 13.723254] [] lpfc_pci_probe_one_s4.isra.38+0x207/0x970 [lpfc] [ 13.770876] [] lpfc_pci_probe_one+0xa2/0xe40 [lpfc] [ 14.551773] [] lpfc_init+0xe4/0x1000 [lpfc] [ 15.046636] lpfc :1b:00.2: ioremap failed for SLI4 PCI config registers. [ 15.082558] lpfc :1b:00.2: 0:1410 Failed to set up pci memory space. [ 15.118685] lpfc :1b:00.3: ioremap failed for SLI4 PCI config registers. [ 15.155054] lpfc :1b:00.3: 0:1410 Failed to set up pci memory space. [ 592.495893] lpfc :1b:00.2: ioremap failed for SLI4 PCI config registers. [ 592.495900] lpfc :1b:00.2: 0:1410 Failed to set up pci memory space. [ 592.496028] lpfc :1b:00.3: ioremap failed for SLI4 PCI config registers. [ 592.496030] lpfc :1b:00.3: 0:1410 Failed to set up pci memory space. Setup Details = SUT: 10.227.65.215(IMM IP) (USERID/PASSW0RD) OS IP: 10.227.73.172(ubuntu_sl/Swamiji001) Switch: 10.227.65.35(admin/Pass1234, Port no: 6,17) IBM Target: 10.227.65.50(emulex/passw0rd) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608652/+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 1566221] Re: linux: Enforce signed module loading when UEFI secure boot
** Changed in: linux (Ubuntu Trusty) Status: In Progress => 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/1566221 Title: linux: Enforce signed module loading when UEFI secure boot Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: This work is authorized by an approved UOS spec and blueprint at https://wiki.ubuntu.com/Spec/InstallingUnsignedSecureBoot Add code to implement secure boot checks. Unsigned or incorrectly signed modules will continue to install while tainting the kernel _until_ EFI_SECURE_BOOT_SIG_ENFORCE is enabled. When EFI_SECURE_BOOT_SIG_ENFORCE is enabled, then the only recourse for platforms booting in secure boot mode with a DKMS dependency is to disable secure boot using mokutil: sudo mokutil --disable-validation sudo reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566221/+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 1604313] Re: Ubuntu 16.04: system freezes instead of suspend after undocking
Regarding the "bios-outdated" tag: I did a BIOS update, it now is BIOS Information Vendor: LENOVO Version: JBET60WW (1.24 ) Release Date: 05/25/2016 but the problem persists. -- 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/1604313 Title: Ubuntu 16.04: system freezes instead of suspend after undocking Status in linux package in Ubuntu: Incomplete Bug description: I'm using a Lenovo ThinkPad T450s. When the system was docked and then undocked, suspend won't work. Instead, the screen goes black, the system freezes and the fan runs on high speed. This problem persists with the (as of today) most recent kernel 4.4.0-31-generic #50. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buerger3534 F pulseaudio /dev/snd/pcmC1D0p: buerger3534 F...m pulseaudio /dev/snd/controlC1: buerger3534 F pulseaudio CurrentDesktop: Unity Date: Tue Jul 19 11:13:41 2016 HibernationDevice: RESUME=UUID=21eeaf61-c437-45dc-80e3-e581eb6f795c InstallationDate: Installed on 2015-09-15 (307 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20BX000XGE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (87 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: JBET57WW (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX000XGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET57WW(1.22):bd03/23/2016:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BX000XGE dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604313/+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 1609048] [NEW] Broadcom43142 work only for short distance and with low rate
Public bug reported: On Ubuntu 16.04.1 , the Broadcom 43142 don't work correctly , it require to be very near of the router ( 5 m and in the same floor ) , can't get full bandwidth comparing with windows 10 the performance are acceptable and on my old laptop ( broadcom 4313 Ubuntu 16.04 and ar from the router ). The attachement file contain the info about the wifi , hope this problem will be resolved . ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Attachment added: "wireless-info.txt" https://bugs.launchpad.net/bugs/1609048/+attachment/4712476/+files/wireless-info.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1609048 Title: Broadcom43142 work only for short distance and with low rate Status in bcmwl package in Ubuntu: New Bug description: On Ubuntu 16.04.1 , the Broadcom 43142 don't work correctly , it require to be very near of the router ( 5 m and in the same floor ) , can't get full bandwidth comparing with windows 10 the performance are acceptable and on my old laptop ( broadcom 4313 Ubuntu 16.04 and ar from the router ). The attachement file contain the info about the wifi , hope this problem will be resolved . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1609048/+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 1604313] Re: Ubuntu 16.04: system freezes instead of suspend after undocking
I can try that. If you could point out how I can install previous kernels? Just installing various linux-image-4.4.0. didn't to the trick as there seem to be drivers missing (sound, graphic accel., etc.). -- 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/1604313 Title: Ubuntu 16.04: system freezes instead of suspend after undocking Status in linux package in Ubuntu: Incomplete Bug description: I'm using a Lenovo ThinkPad T450s. When the system was docked and then undocked, suspend won't work. Instead, the screen goes black, the system freezes and the fan runs on high speed. This problem persists with the (as of today) most recent kernel 4.4.0-31-generic #50. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buerger3534 F pulseaudio /dev/snd/pcmC1D0p: buerger3534 F...m pulseaudio /dev/snd/controlC1: buerger3534 F pulseaudio CurrentDesktop: Unity Date: Tue Jul 19 11:13:41 2016 HibernationDevice: RESUME=UUID=21eeaf61-c437-45dc-80e3-e581eb6f795c InstallationDate: Installed on 2015-09-15 (307 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20BX000XGE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (87 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: JBET57WW (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX000XGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET57WW(1.22):bd03/23/2016:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BX000XGE dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604313/+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 1586418] Re: exercising ptys causes a kernel oops
Even though I'm on vacation I still managed to squeeze in some time to
test this on trusty before the 5 days deadline ran out. I have
exercised the kernel with a 20 minutes soak test and was unable to trip
the bug with the trusty -proposed kernel. Without the fix, the issue
can be triggered, with the fix, I can't trigger the issue.
Marking it as verification-done-trusty
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1586418
Title:
exercising ptys causes a kernel oops
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:
Won't Fix
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Released
Bug description:
[SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]
Running stress-ng --pty 1 with a very low vmalloc memory available can
trip an oops. This can be generally only be reproduced when memory is
under a high amount of pressure. I was able to reproduce reliably by
forcefully injecting vmalloc to return NULL when the stress-ng pty was
running.
[FIX]
Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null
pointer dereference on failed memory allocation"). This needs backporting to
Yakkey, Xenial, Wily and Trusty because of changes in variable names.
[TEST]
Forcefully inject vmalloc to return NULL when running the pty stressor.
Without the fix, an oops can be tripped, with the fix, no issues occur.
--
running: "stress-ng --pty 1" and this occurs in less than 1 second:
[ 67.753230] alloc_vmap_area: 9 callbacks suppressed
[ 67.753233] vmap allocation for size 16384 failed: use vmalloc= to
increase size.
[ 67.753235] vmalloc: allocation failure: 8844 bytes
[ 67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
[ 67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted
4.4.0-23-generic #41-Ubuntu
[ 67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
Ubuntu-1.8.2-1ubuntu1 04/01/2014
[ 67.753243] c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c
0001 f2497cbc
[ 67.753248] c1177396 c19cc624 f506b5f0 024000c2 f2497cd0
c19ce22c f2497ca4
[ 67.753252] 0832d3cc 228c f2497cec c11ad2ff 024000c2
c19ce22c
[ 67.753256] Call Trace:
[ 67.753264] [] dump_stack+0x58/0x79
[ 67.753267] [] warn_alloc_failed+0xd6/0x110
[ 67.753272] [] __vmalloc_node_range+0x1ef/0x210
[ 67.753276] [] ? tty_get_pgrp+0x40/0x40
[ 67.753278] [] __vmalloc_node+0x66/0x70
[ 67.753280] [] ? n_tty_open+0x16/0xc0
[ 67.753283] [] vmalloc+0x38/0x40
[ 67.753284] [] ? n_tty_open+0x16/0xc0
[ 67.753290] [] n_tty_open+0x16/0xc0
[ 67.753293] [] tty_ldisc_open.isra.2+0x28/0x60
[ 67.753295] [] tty_ldisc_setup+0x1c/0x70
[ 67.753297] [] tty_init_dev+0x7c/0x180
[ 67.753301] [] ? devpts_new_index+0xf1/0x120
[ 67.753303] [] ptmx_open+0x75/0x160
[ 67.753306] [] chrdev_open+0xa4/0x180
[ 67.753310] [] do_dentry_open+0x1ec/0x300
[ 67.753312] [] ? cdev_put+0x20/0x20
[ 67.753314] [] vfs_open+0x4f/0x60
[ 67.753316] [] path_openat+0x509/0x1140
[ 67.753318] [] ? putname+0x54/0x60
[ 67.753321] [] do_filp_open+0x68/0xe0
[ 67.753324] [] ? __alloc_fd+0x36/0x150
[ 67.753326] [] do_sys_open+0x128/0x2b0
[ 67.753329] [] SyS_open+0x22/0x30
[ 67.753332] [] do_fast_syscall_32+0x8d/0x150
[ 67.753336] [] sysenter_past_esp+0x3d/0x61
[ 67.753338] Mem-Info:
[ 67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
active_file:30258 inactive_file:14843 isolated_file:0
unevictable:856 dirty:46 writeback:0 unstable:0
slab_reclaimable:4643 slab_unreclaimable:5952
mapped:5271 shmem:1380 pagetables:193 bounce:0
free:166082 free_pcp:1176 free_cma:0
[ 67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
[ 67.753350] lowmem_reserve[]: 0 818 949 949
[ 67.753357] Normal free:567248kB min:41608kB low:52008kB high:62412kB
active_anon:18440kB inactive_anon:2992kB active_file:101312kB
inactive_file:4760
[Kernel-packages] [Bug 1585742] Comment bridged from LTC Bugzilla
--- Comment From drbr...@us.ibm.com 2016-08-02 11:57 EDT--- Canonical - any outlook here for including the patchset in daily build? -- 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/1585742 Title: [ubuntu 16.10] Enable perf to probe and record on SDT events present in binaries Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: This is a feature request for 16.10: SDT events are markers placed at important places in the binaries. When they are probed and traced, they can give valuable information about the userspace application. This feature aims to enable perf to probe/record on SDT events. Patches are being currently sent : https://lkml.org/lkml/2016/5/14/107 patchset for probe-cache and initial SDT support https://lkml.org/lkml/2016/5/3/810 patch to directly record on SDT events. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585742/+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 1599562] Re: linux: Homogenize changelog format across releases
** Tags removed: verification-needed-precise verification-needed-trusty verification-needed-vivid ** Tags added: verification-done-precise verification-done-trusty verification-done-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1599562 Title: linux: Homogenize changelog format across releases Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Committed 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: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: Kernel changelogs should have the same format across all releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599562/+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 1608993] 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/1608993 Title: package linux-image-extra-4.4.0-31-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: Confirmed Bug description: Aus einem von mir nicht nachvollziehbarem Grund ist das Problem aufgetreten. Beste Grüße Gerd Lemberger ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-31-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gerd 3120 F pulseaudio /dev/snd/controlC0: gerd 3120 F pulseaudio Date: Tue Aug 2 14:51:18 2016 DpkgHistoryLog: Start-Date: 2016-08-02 14:51:01 Requested-By: gerd (1000) Upgrade: snap-confine:amd64 (1.0.38-0ubuntu0.16.04.3, 1.0.38-0ubuntu0.16.04.4), libapparmor1:amd64 (2.10.95-0ubuntu2.1, 2.10.95-0ubuntu2.2), gnome-maps:amd64 (3.18.2-1, 3.18.3-0ubuntu1), libapparmor-perl:amd64 (2.10.95-0ubuntu2.1, 2.10.95-0ubuntu2.2), ubuntu-core-launcher:amd64 (1.0.38-0ubuntu0.16.04.3, 1.0.38-0ubuntu0.16.04.4), apparmor:amd64 (2.10.95-0ubuntu2.1, 2.10.95-0ubuntu2.2) DuplicateSignature: package:linux-image-extra-4.4.0-31-generic:(not installed) Processing triggers for libglib2.0-0:amd64 (2.48.1-1~ubuntu16.04.1) ... dpkg: error processing package linux-image-extra-4.4.0-31-generic (--configure): package linux-image-extra-4.4.0-31-generic is not ready for configuration ErrorMessage: package linux-image-extra-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=80fd521c-394f-4014-8539-6f4423b94601 InstallationDate: Installed on 2016-07-21 (11 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire E1-522 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=e8bb14ae-f416-4fc2-a8d6-4d3d7d0af013 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-36ubuntu3.2 SourcePackage: linux Title: package linux-image-extra-4.4.0-31-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire E1-522 dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/19/2013:svnAcer:pnAspireE1-522:pvrV2.09:rvnAcer:rnAspireE1-522:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.name: Aspire E1-522 dmi.product.version: V2.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608993/+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 1599491] Re: kdump-tools install script uses deprecated syntax
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1599491 Title: kdump-tools install script uses deprecated syntax Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Bug description: [SRU justification] Error message polluting the installation [Impact] Wrongfully implies a problem with the installation [Fix] Remove unneeded dh_installinit override [Test Case] Install kdump-tools on Xenial. Without the fix, the installation will complain with : update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults This message does not appear with the fix [Regression] None expected. update-rc.d default is used as a fallback. [Original description of the problem] When installing kdump-tools, the apt-get outputs: Setting up kdump-tools (1:1.5.9-5) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Full log: jayman@jayman-kubuntu:~$ sudo apt-get install kdump-tools Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: crash kexec-tools libdw1 makedumpfile The following NEW packages will be installed: crash kdump-tools kexec-tools libdw1 makedumpfile 0 upgraded, 5 newly installed, 0 to remove and 10 not upgraded. Need to get 0 B/2,962 kB of archives. After this operation, 9,379 kB of additional disk space will be used. Do you want to continue? [Y/n] Preconfiguring packages ... Selecting previously unselected package crash. (Reading database ... 235512 files and directories currently installed.) Preparing to unpack .../crash_7.1.4-1ubuntu4_amd64.deb ... Unpacking crash (7.1.4-1ubuntu4) ... Selecting previously unselected package libdw1:amd64. Preparing to unpack .../libdw1_0.165-3ubuntu1_amd64.deb ... Unpacking libdw1:amd64 (0.165-3ubuntu1) ... Selecting previously unselected package makedumpfile. Preparing to unpack .../makedumpfile_1%3a1.5.9-5_amd64.deb ... Unpacking makedumpfile (1:1.5.9-5) ... Selecting previously unselected package kexec-tools. Preparing to unpack .../kexec-tools_1%3a2.0.10-1ubuntu2_amd64.deb ... Unpacking kexec-tools (1:2.0.10-1ubuntu2) ... Selecting previously unselected package kdump-tools. Preparing to unpack .../kdump-tools_1%3a1.5.9-5_all.deb ... Unpacking kdump-tools (1:1.5.9-5) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... Processing triggers for systemd (229-4ubuntu6) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up crash (7.1.4-1ubuntu4) ... Setting up libdw1:amd64 (0.165-3ubuntu1) ... Setting up makedumpfile (1:1.5.9-5) ... Setting up kexec-tools (1:2.0.10-1ubuntu2) ... Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0-28-generic Found initrd image: /boot/initrd.img-4.4.0-28-generic Found linux image: /boot/vmlinuz-4.4.0-24-generic Found initrd image: /boot/initrd.img-4.4.0-24-generic Found memtest86+ image: /boot/memtest86+.elf Found memtest86+ image: /boot/memtest86+.bin grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map. Found Windows 7 (loader) on /dev/sda1 done Setting up kdump-tools (1:1.5.9-5) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Processing triggers for libc-bin (2.23-0ubuntu3) ... jayman@jayman-kubuntu:~$ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: kdump-tools 1:1.5.9-5 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Jul 6 08:02:53 2016 InstallationDate: Installed on 2016-06-16 (19 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: makedumpfile UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1599491/+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 1608993] [NEW] package linux-image-extra-4.4.0-31-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-31-generic is not ready for configuration ca
Public bug reported: Aus einem von mir nicht nachvollziehbarem Grund ist das Problem aufgetreten. Beste Grüße Gerd Lemberger ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-31-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gerd 3120 F pulseaudio /dev/snd/controlC0: gerd 3120 F pulseaudio Date: Tue Aug 2 14:51:18 2016 DpkgHistoryLog: Start-Date: 2016-08-02 14:51:01 Requested-By: gerd (1000) Upgrade: snap-confine:amd64 (1.0.38-0ubuntu0.16.04.3, 1.0.38-0ubuntu0.16.04.4), libapparmor1:amd64 (2.10.95-0ubuntu2.1, 2.10.95-0ubuntu2.2), gnome-maps:amd64 (3.18.2-1, 3.18.3-0ubuntu1), libapparmor-perl:amd64 (2.10.95-0ubuntu2.1, 2.10.95-0ubuntu2.2), ubuntu-core-launcher:amd64 (1.0.38-0ubuntu0.16.04.3, 1.0.38-0ubuntu0.16.04.4), apparmor:amd64 (2.10.95-0ubuntu2.1, 2.10.95-0ubuntu2.2) DuplicateSignature: package:linux-image-extra-4.4.0-31-generic:(not installed) Processing triggers for libglib2.0-0:amd64 (2.48.1-1~ubuntu16.04.1) ... dpkg: error processing package linux-image-extra-4.4.0-31-generic (--configure): package linux-image-extra-4.4.0-31-generic is not ready for configuration ErrorMessage: package linux-image-extra-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=80fd521c-394f-4014-8539-6f4423b94601 InstallationDate: Installed on 2016-07-21 (11 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire E1-522 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=e8bb14ae-f416-4fc2-a8d6-4d3d7d0af013 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-36ubuntu3.2 SourcePackage: linux Title: package linux-image-extra-4.4.0-31-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire E1-522 dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/19/2013:svnAcer:pnAspireE1-522:pvrV2.09:rvnAcer:rnAspireE1-522:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.name: Aspire E1-522 dmi.product.version: V2.09 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1608993 Title: package linux-image-extra-4.4.0-31-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: New Bug description: Aus einem von mir nicht nachvollziehbarem Grund ist das Problem aufgetreten. Beste Grüße Gerd Lemberger ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-31-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gerd 3120 F pulseaudio /dev/snd/controlC0: gerd 3120 F pulseaudio Date: Tue Aug 2 14:51:18 2016 DpkgHistoryLog: Start-Date: 2016-08-02 14:51:01 Requested-By: gerd (1000) Upgrade: snap-confine:amd64 (1.0.38-0ubuntu0.16.04.3, 1.0.38-0ubuntu0.16.04.4), libapparmor1:amd64 (2.10.95-0ubuntu2.1, 2.10.95-0ubuntu2.2), gnome-maps:amd64 (3.18.2-1, 3.18.3-0ubuntu1), libapparmor-perl:amd64 (2.10.95-0ubuntu2.1, 2.10.95-0ubuntu2.2), ubuntu-core-launcher:amd64 (1.0.38-0ubuntu0.16.04.3, 1.0.38-0ubuntu0.16.04.4), apparmor:amd64 (2.10.95-0ubuntu2.1, 2.10.95-0ubuntu2.2) DuplicateSignature: package:linux-image-extra-4.4.0-31-generic:(not installed) Processing triggers for libglib2.0-0:amd64 (2.48.1-1~ubuntu16.04.1) ... dpkg: error processing package linux-image-extra-4.4.0-31-generic (--configure): package linux-image-extra-4.4.0-31-generic is not ready for configuration ErrorMessage: package linux-image-extra-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: R
[Kernel-packages] [Bug 1554299] Re: drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb0210614, found 0x00000000)
The GL freezes still occur when using Ubuntu kernel 4.5.3. I wanted to try newer kernels (those tagged with yakkety), but the 14.04 LTS wouldn't boot to desktop with them. ** Changed in: linux (Ubuntu) Status: Expired => Incomplete -- 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/1554299 Title: drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb0210614, found 0x) Status in linux package in Ubuntu: Incomplete Bug description: This is a followup of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501260 . Basically, running OpenGL applications (e.g. glxgears) on the primary display handled by Intel 915 card results in display freeze. The error message from the title of this bug is written to a VT console if I switch to it. It seems this bug only appears when multiple monitors are connected. Switching to a VT (Ctrl+Alt+F1) and back unfreezes the screen for a while. The screen only looks frozen, but normally reacts to mouse and keyboard events. This only happens if the GL window is displayed on my primary display (which is handled by the intel integrated chip). The notebook has 2 video outputs and a discrete AMD graphics, and I think only one of the outputs is handled by the AMD card, so I think one of the outputs is handled by the intel card and does not get frozen. Ubuntu 14.04.3 64bit. I think that before upgrading from 14.04.2 to 14.04.3 this did not happen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.2.0-30-generic 4.2.0-30.36~14.04.1 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 8 02:43:37 2016 InstallationDate: Installed on 2013-11-05 (853 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: linux-lts-wily UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago) --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peci1 3018 F pulseaudio /dev/snd/controlC1: peci1 3018 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c InstallationDate: Installed on 2013-11-05 (853 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E6540 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 RelatedPackageVersions: linux-restricted-modules-4.2.0-27-generic N/A linux-backports-modules-4.2.0-27-generic N/A linux-firmware1.127.20 Tags: trusty Uname: Linux 4.2.0-27-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago) UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0CYT5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554299/+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 1608993] Re: package linux-image-extra-4.4.0-31-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-31-generic is not ready for configuration cann
** 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/1608993 Title: package linux-image-extra-4.4.0-31-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: New Bug description: Aus einem von mir nicht nachvollziehbarem Grund ist das Problem aufgetreten. Beste Grüße Gerd Lemberger ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-31-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gerd 3120 F pulseaudio /dev/snd/controlC0: gerd 3120 F pulseaudio Date: Tue Aug 2 14:51:18 2016 DpkgHistoryLog: Start-Date: 2016-08-02 14:51:01 Requested-By: gerd (1000) Upgrade: snap-confine:amd64 (1.0.38-0ubuntu0.16.04.3, 1.0.38-0ubuntu0.16.04.4), libapparmor1:amd64 (2.10.95-0ubuntu2.1, 2.10.95-0ubuntu2.2), gnome-maps:amd64 (3.18.2-1, 3.18.3-0ubuntu1), libapparmor-perl:amd64 (2.10.95-0ubuntu2.1, 2.10.95-0ubuntu2.2), ubuntu-core-launcher:amd64 (1.0.38-0ubuntu0.16.04.3, 1.0.38-0ubuntu0.16.04.4), apparmor:amd64 (2.10.95-0ubuntu2.1, 2.10.95-0ubuntu2.2) DuplicateSignature: package:linux-image-extra-4.4.0-31-generic:(not installed) Processing triggers for libglib2.0-0:amd64 (2.48.1-1~ubuntu16.04.1) ... dpkg: error processing package linux-image-extra-4.4.0-31-generic (--configure): package linux-image-extra-4.4.0-31-generic is not ready for configuration ErrorMessage: package linux-image-extra-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=80fd521c-394f-4014-8539-6f4423b94601 InstallationDate: Installed on 2016-07-21 (11 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire E1-522 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=e8bb14ae-f416-4fc2-a8d6-4d3d7d0af013 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-36ubuntu3.2 SourcePackage: linux Title: package linux-image-extra-4.4.0-31-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire E1-522 dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/19/2013:svnAcer:pnAspireE1-522:pvrV2.09:rvnAcer:rnAspireE1-522:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.name: Aspire E1-522 dmi.product.version: V2.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608993/+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 1496290] Re: 10de:0a3c System freeze due to "angry" nouveau driver
As Vivid has reached its "End of Life", this bug can be safely closed. -- 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/1496290 Title: 10de:0a3c System freeze due to "angry" nouveau driver Status in linux package in Ubuntu: Triaged Bug description: Starting with the 3.19 kernels (Vivid), the system frequently freezes in the nouveau driver, with the following lines (w/ out timestamp and hostname) always being reported in "/var/log/kern.log" and/or "/var/log/syslog" just before the system becomes unresponsive and a hard reset becomes necessary. nouveau E[ PFIFO][:01:00.0] still angry after 101 spins, halt The bug is also reported in https://bugs.freedesktop.org/show_bug.cgi?id=87244, and the fix seems to be to cherry pick https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=adc346b133c952ec6988d90f6fa79cbe0a3eb7ef which is included in Linux 4.0 (if I am not mistaken). Here's some more info: lsb_release -rd: Description: Ubuntu 14.04.3 LTS Release: 14.04 Affected package: linux-generic-lts-vivid-3.19.0.28.15 (As the affected package breaks my system reliably several times a day, I reverted to linux-generic-lts-utopic.) --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: de107192 2480 F pulseaudio /dev/snd/controlC0: de107192 2480 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-07-17 (61 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 43892DG Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-50-generic root=/dev/mapper/SETEC-UBUNTU ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16 RelatedPackageVersions: linux-restricted-modules-3.16.0-50-generic N/A linux-backports-modules-3.16.0-50-generic N/A linux-firmware 1.127.15 Tags: trusty Uname: Linux 3.16.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 43892DG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn43892DG:pvrThinkPadW510:rvnLENOVO:rn43892DG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 43892DG dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496290/+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 1510570] Re: BLE pairing fail
Thanks for this. I managed to get my Arc Touch SE mouse to work with an otherwise stock 16.04 system by changing the setting as mentioned in #25, COMMENTING OUT the rule in #27 (merely changing it didn't seem to work) and then connecting as in #16. Very grateful, as the mouse was a Christmas present that I asked for and I felt bad that I wasn't able to use it! -- 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/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+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 1570775] Re: makekdump should re-exec with cio_ignore on s390x
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1570775 Title: makekdump should re-exec with cio_ignore on s390x Status in Ubuntu on IBM z Systems: Fix Released Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Bug description: [SRU justification] kernel crash dump fails to work without the modification. [Impact] Broken functionality. [Fix] Add cio_ignore -k -y output to the kexec command. [Test Case] Follow indication in comment #2 to reproduce. With the fix, kdump will function as expected. [Regression] A regression situation is outlined in comment #16. Newer channel devices may not be visible because of the added cio_ignore output. This may be worked around with a single command. The resolution outweights this limitation that can be easily worked around. [Original description of the problem] As per https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/comments/19 We should re-exec with cio_ignore lines. As per report there, it should result in lowered required crashdump setting. Hypothetically, one should be able to test this imperially by lowering crashdump memory settings until kdump does not succeed anymore. And then generated and append `cio_ignore -k -u` to the KDUMP_CMDLINE_APPEND= and see that kdump starts working again with a lower memory usage. Once this is developed / verified / tested, we should probably SRU this back to xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1570775/+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 1546603] Re: Bluetooth mouse connects but doesn't work
I took a different approach to getting my mouse working: I installed blueman and used that to configure it. I guess it enables experimental features itself. -- 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/1546603 Title: Bluetooth mouse connects but doesn't work Status in bluez package in Ubuntu: Confirmed Bug description: I have a bluetooth mouse that I can get to connect via the gnome bluetooth settings panel, but even after it's connected it doesn't move the pointer or register any clicks. the following shows up in the journal : $ $ journalctl -b 0 |grep bluetooth Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth daemon 5.36 Feb 17 07:18:22 spiny bluetoothd[1009]: Starting SDP server Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth management interface 1.10 initialized Feb 17 07:18:22 spiny bluetoothd[1009]: Failed to obtain handles for "Service Changed" characteristic Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Error adding Link Loss service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Current Time Service could not be registered Feb 17 07:18:22 spiny bluetoothd[1009]: gatt-time-server: Input/output error (5) Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Sap driver initialization failed. Feb 17 07:18:22 spiny bluetoothd[1009]: sap-server: Operation not permitted (1) Feb 17 07:18:22 spiny NetworkManager[1062]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSource Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSink Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSource Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSink Feb 17 07:18:42 spiny bluetoothd[1009]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher gufw (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher landscape-client-settings (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher language-selector (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher ubuntuone-installer (missing desktop file) Feb 17 07:19:00 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 'str != NULL' failed Feb 17 07:19:01 spiny bluetoothd[1009]: No cache for F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x000c for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x001b for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x003f for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Report Map read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Protocol Mode characteristic read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: HID Information read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): GLib-CRITICAL **: g_a
[Kernel-packages] [Bug 1571590] Re: pVM:pinelp2:ubuntu 16.04: Network is unreachable when using ssh in kdump
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1571590 Title: pVM:pinelp2:ubuntu 16.04: Network is unreachable when using ssh in kdump Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Bug description: [SRU justification] Without this fix, networked enabled kernel dump will fail to complete. [Impact] Broken networked functionality [Fix] Add a Wants target to the systemd unit. [Test Case] Follow "Test to reproduce" in Original Problem description. [Regression] None expected, the existing systemd unit setup remains but is improved by proposed fix. [Description of the problem] Original problem Description When dumping to ssh target , kdump failed: Starting Kernel crash dump capture service... [ 18.542292] kdump-tools[2748]: Starting kdump-tools: ssh: connect to host 10.33.31.113 port 22: Network is unreachable [ 18.542894] kdump-tools[2748]: * kdump-tools: Unable to reach remote server root@10.33.31.113. No reason to continue [ 18.613376] kdump-tools[2748]: Mon, 11 Apr 2016 01:23:55 -0500 [ 19.310893] kdump-tools[2748]: Rebooting. [ 19.652714] reboot: Restarting system But the weired thing is that nfs target works on the same system. ---uname output--- Linux pinelp2 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:00:30 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Steps to Reproduce === 1. install latest ubuntu 16.04 on pinelp2 2. config kdump to use ssh: SSH="root@10.33.31.113" 3. run "kdump-config propagate" as root 4. trigger kdump Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: version 1:1.5.9-5 == Comment: #8 - Ping Tian Han - 2016-04-17 21:58:52 == (In reply to comment #6) > I am able to reproduce this issue as well. > Ping, what is you try to dump on some other machine with ssh ? Does it still > complain the same ? Is the ssh failing to connect to the network ? I saw the same problem when dumping to medlp4 with ssh: Starting Kernel crash dump capture service... [ 17.293028] kdump-tools[2733]: Starting kdump-tools: ssh: connect to host 10.33.7.181 port 22: Network is unreachable [ 17.293692] kdump-tools[2733]: * kdump-tools: Unable to reach remote server root@10.33.7.181. No reason to continue [ 17.405333] kdump-tools[2733]: Sun, 17 Apr 2016 20:56:59 -0500 [ 18.536587] kdump-tools[2733]: Rebooting. [ 18.903280] reboot: Restarting system but I can ssh log noto medlp4 before triggering kdump. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1571590/+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 1608854] Re: [arm64] nova instances can't boot with 3.13.0-92
** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress -- 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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
Could someone on the ubuntu development team update the bluez package to 5.39? The bluez website states there are A2DP fixes in the next release. http://www.bluez.org/release-of-bluez-5-39/ -- 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/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1566221] Re: linux: Enforce signed module loading when UEFI secure boot
** Changed in: linux (Ubuntu Trusty) Status: Fix Released => In Progress -- 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/1566221 Title: linux: Enforce signed module loading when UEFI secure boot Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: This work is authorized by an approved UOS spec and blueprint at https://wiki.ubuntu.com/Spec/InstallingUnsignedSecureBoot Add code to implement secure boot checks. Unsigned or incorrectly signed modules will continue to install while tainting the kernel _until_ EFI_SECURE_BOOT_SIG_ENFORCE is enabled. When EFI_SECURE_BOOT_SIG_ENFORCE is enabled, then the only recourse for platforms booting in secure boot mode with a DKMS dependency is to disable secure boot using mokutil: sudo mokutil --disable-validation sudo reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566221/+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 1608762] Re: OptiPlex 7450 AIO hangs when rebooting
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Alex Hung (alexhung) ** 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/1608762 Title: OptiPlex 7450 AIO hangs when rebooting Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: Dell Optiplex 7450 AIO works with BOOT_ACPI; however, the quirk for "OptiPlex 745" changes its boot method to BOOT_BIOS and causes 7450 AIO hangs when rebooting. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1608762/+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 1049466] Re: Need support of Ralink RT3290 wifi support
The bug still exists in Ubuntu 16.04. The rt3290 card is disabled by default and the Rfkill output shows "hardware blocked"..which isn't blocked at all whenever i try to enable it doesn't work. None of the solutions worked on ubuntu 16.04. Sadly i reverted to Linux mint with 3.16 kernel because i don't have any option left. ** Tags added: 16.04 bug exists ubuntu -- 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/1049466 Title: Need support of Ralink RT3290 wifi support Status in Linux: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Precise: Invalid Status in linux-firmware source package in Precise: Fix Released Status in linux source package in Quantal: Invalid Status in linux-firmware source package in Quantal: Won't Fix Status in linux source package in Raring: Fix Released Status in linux-firmware source package in Raring: Fix Released Status in linux package in Baltix: Opinion Status in linux package in Gentoo Linux: New Bug description: RT3290 wifi chip is becoming common on consumer notebooks. Its support starts from 3.6 so support on 12.10 may need lbm-cw. commit a89534edaaa7008992b878680490e9b02a665563 Author: Woody Hung Date: Wed Jun 13 15:01:16 2012 +0800 rt2x00 : RT3290 chip support v4 This patch support the new chipset rt3290 wifi implementation in rt2x00. It initailize the related mac, bbp and rf register in startup phase. And this patch modify the efuse read/write method for the different efuse data offset of rt3290. Signed-off-by: Woody Hung Signed-off-by: John W. Linville To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1049466/+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 1601831] Re: qeth: delete napi struct when removing a qeth device
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1601831
Title:
qeth: delete napi struct when removing a qeth device
Status in Linux:
New
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Committed
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Vivid:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Released
Bug description:
== Comment: #0 - Hendrik Brueckner - 2016-07-08
10:59:08 ==
Please backport:
commit 7831b4ff0d926e0deeaabef9db8800ed069a2757
Author: Ursula Braun
Date: Mon Jul 4 14:07:16 2016 +0200
qeth: delete napi struct when removing a qeth device
A qeth_card contains a napi_struct linked to the net_device during
device probing. This struct must be deleted when removing the qeth
device, otherwise Panic on oops can occur when qeth devices are
repeatedly removed and added.
Fixes: a1c3ed4c9ca ("qeth: NAPI support for l2 and l3 discipline")
Cc: sta...@vger.kernel.org # v2.6.37+
Signed-off-by: Ursula Braun
Tested-by: Alexander Klein
Signed-off-by: David S. Miller
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1601831/+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 1586418] Re: exercising ptys causes a kernel oops
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1586418
Title:
exercising ptys causes a kernel oops
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:
Won't Fix
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Released
Bug description:
[SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]
Running stress-ng --pty 1 with a very low vmalloc memory available can
trip an oops. This can be generally only be reproduced when memory is
under a high amount of pressure. I was able to reproduce reliably by
forcefully injecting vmalloc to return NULL when the stress-ng pty was
running.
[FIX]
Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null
pointer dereference on failed memory allocation"). This needs backporting to
Yakkey, Xenial, Wily and Trusty because of changes in variable names.
[TEST]
Forcefully inject vmalloc to return NULL when running the pty stressor.
Without the fix, an oops can be tripped, with the fix, no issues occur.
--
running: "stress-ng --pty 1" and this occurs in less than 1 second:
[ 67.753230] alloc_vmap_area: 9 callbacks suppressed
[ 67.753233] vmap allocation for size 16384 failed: use vmalloc= to
increase size.
[ 67.753235] vmalloc: allocation failure: 8844 bytes
[ 67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
[ 67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted
4.4.0-23-generic #41-Ubuntu
[ 67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
Ubuntu-1.8.2-1ubuntu1 04/01/2014
[ 67.753243] c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c
0001 f2497cbc
[ 67.753248] c1177396 c19cc624 f506b5f0 024000c2 f2497cd0
c19ce22c f2497ca4
[ 67.753252] 0832d3cc 228c f2497cec c11ad2ff 024000c2
c19ce22c
[ 67.753256] Call Trace:
[ 67.753264] [] dump_stack+0x58/0x79
[ 67.753267] [] warn_alloc_failed+0xd6/0x110
[ 67.753272] [] __vmalloc_node_range+0x1ef/0x210
[ 67.753276] [] ? tty_get_pgrp+0x40/0x40
[ 67.753278] [] __vmalloc_node+0x66/0x70
[ 67.753280] [] ? n_tty_open+0x16/0xc0
[ 67.753283] [] vmalloc+0x38/0x40
[ 67.753284] [] ? n_tty_open+0x16/0xc0
[ 67.753290] [] n_tty_open+0x16/0xc0
[ 67.753293] [] tty_ldisc_open.isra.2+0x28/0x60
[ 67.753295] [] tty_ldisc_setup+0x1c/0x70
[ 67.753297] [] tty_init_dev+0x7c/0x180
[ 67.753301] [] ? devpts_new_index+0xf1/0x120
[ 67.753303] [] ptmx_open+0x75/0x160
[ 67.753306] [] chrdev_open+0xa4/0x180
[ 67.753310] [] do_dentry_open+0x1ec/0x300
[ 67.753312] [] ? cdev_put+0x20/0x20
[ 67.753314] [] vfs_open+0x4f/0x60
[ 67.753316] [] path_openat+0x509/0x1140
[ 67.753318] [] ? putname+0x54/0x60
[ 67.753321] [] do_filp_open+0x68/0xe0
[ 67.753324] [] ? __alloc_fd+0x36/0x150
[ 67.753326] [] do_sys_open+0x128/0x2b0
[ 67.753329] [] SyS_open+0x22/0x30
[ 67.753332] [] do_fast_syscall_32+0x8d/0x150
[ 67.753336] [] sysenter_past_esp+0x3d/0x61
[ 67.753338] Mem-Info:
[ 67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
active_file:30258 inactive_file:14843 isolated_file:0
unevictable:856 dirty:46 writeback:0 unstable:0
slab_reclaimable:4643 slab_unreclaimable:5952
mapped:5271 shmem:1380 pagetables:193 bounce:0
free:166082 free_pcp:1176 free_cma:0
[ 67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
[ 67.753350] lowmem_reserve[]: 0 818 949 949
[ 67.753357] Normal free:567248kB min:41608kB low:52008kB high:62412kB
act
[Kernel-packages] [Bug 1599562] Re: linux: Homogenize changelog format across releases
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1599562 Title: linux: Homogenize changelog format across releases Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Committed 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: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: Kernel changelogs should have the same format across all releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599562/+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 1598197] Re: deadlock on balloon deflation
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1598197
Title:
deadlock on balloon deflation
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Trusty:
Fix Committed
Bug description:
Latest Ubuntu trusty with kernel 3.13.0-91-generic run in a KVM
virtual machine with virtio_balloon hangs when the previously inflated
balloon is deflated.
The problem is in the recently committed backport:
commit 838478a8496ef9677256f53710144abe2ea49625
Author: Konstantin Khlebnikov
AuthorDate: Mon May 16 14:43:10 2016 +0800
Commit: Kamal Mostafa
CommitDate: Fri Jun 10 07:15:37 2016 -0700
mm/balloon_compaction: redesign ballooned pages management
BugLink: http://bugs.launchpad.net/bugs/1572562
Sasha Levin reported KASAN splash inside isolate_migratepages_range().
Problem is in the function __is_movable_balloon_page() which tests
AS_BALLOON_MAP in page->mapping->flags. This function has no protection
against anonymous pages. As result it tried to check address space flags
inside struct anon_vma.
Further investigation shows more problems in current implementation:
* Special branch in __unmap_and_move() never works:
balloon_page_movable() checks page flags and page_count. In
__unmap_and_move() page is locked, reference counter is elevated, thus
balloon_page_movable() always fails. As a result execution goes to the
normal migration path. virtballoon_migratepage() returns
MIGRATEPAGE_BALLOON_SUCCESS instead of MIGRATEPAGE_SUCCESS,
move_to_new_page() thinks this is an error code and assigns
newpage->mapping to NULL. Newly migrated page lose connectivity with
balloon an all ability for further migration.
* lru_lock erroneously required in isolate_migratepages_range() for
isolation ballooned page. This function releases lru_lock periodically,
this makes migration mostly impossible for some pages.
* balloon_page_dequeue have a tight race with balloon_page_isolate:
balloon_page_isolate could be executed in parallel with dequeue between
picking page from list and locking page_lock. Race is rare because they
use trylock_page() for locking.
This patch fixes all of them.
Instead of fake mapping with special flag this patch uses special state of
page->_mapcount: PAGE_BALLOON_MAPCOUNT_VALUE = -256. Buddy allocator uses
PAGE_BUDDY_MAPCOUNT_VALUE = -128 for similar purpose. Storing mark
directly in struct page makes everything safer and easier.
PagePrivate is used to mark pages present in page list (i.e. not
isolated, like PageLRU for normal pages). It replaces special rules for
reference counter and makes balloon migration similar to migration of
normal pages. This flag is protected by page_lock together with link to
the balloon device.
Signed-off-by: Konstantin Khlebnikov
Reported-by: Sasha Levin
Link: http://lkml.kernel.org/p/53e6ceaa.9020...@oracle.com
Cc: Rafael Aquini
Cc: Andrey Ryabinin
Cc: [3.8+]
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
(backported from commit d6d86c0a7f8ddc5b38cf089222cb1d9540762dc2)
Signed-off-by: Gavin Guo
Conflicts:
mm/balloon_compaction.c
mm/migrate.c
Acked-by: Stefan Bader
Signed-off-by: Kamal Mostafa
It was applied after another backport:
commit 47618e32c2a729554bf56b8ee7b541b63aadad97
Author: Minchan Kim
AuthorDate: Mon Dec 28 08:35:13 2015 +0900
Commit: Luis Henriques
CommitDate: Mon Feb 22 19:31:53 2016 +
virtio_balloon: fix race between migration and ballooning
BugLink: http://bugs.launchpad.net/bugs/1542497
commit 21ea9fb69e7c4b1b1559c3e410943d3ff248ffcb upstream.
In balloon_page_dequeue, pages_lock should cover the loop
(ie, list_for_each_entry_safe). Otherwise, the cursor page could
be isolated by compaction and then list_del by isolation could
poison the page->lru.{prev,next} so the loop finally could
access wrong address like this. This patch fixes the bug.
[Kernel-packages] [Bug 1447485] Re: serial: 8250_pci: Add support for 16 port Exar boards
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1447485 Title: serial: 8250_pci: Add support for 16 port Exar boards Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Bug description: This is a request to add support for boards using two EXAR XR17V8358 chips in Master-Slave mode. The patch has also been send upstream, but is not reviewed yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447485/+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 1603476] Re: Boot failure with EFI stub
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1603476 Title: Boot failure with EFI stub Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Bug description: After updating kernel to 3.13.0-92 system cannot startup with these errors: Failed to get file info size Failed to alloc highmem for files I've found patch fixing it here — http://kernel.opensuse.org/cgit/kernel/commit/?h=v3.15.9&id=396f1a08db212138418b38f784e4bbe516d2fdb2 Works like a charm. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-92-generic 3.13.0-92.139 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2236 F pulseaudio /dev/snd/controlC1: andrei 2236 F pulseaudio CurrentDesktop: KDE Date: Fri Jul 15 17:41:11 2016 InstallationDate: Installed on 2014-11-26 (596 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: root=UUID=33a02342-70da-4f8d-9868-2f8e7330ec90 ro rootfstype=ext4 add_efi_memmap initrd=\EFI\ubuntu\initrd.img RelatedPackageVersions: linux-restricted-modules-3.13.0-92-generic N/A linux-backports-modules-3.13.0-92-generic N/A linux-firmware 1.127.22 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M 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.:bvr3901:bd09/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-M: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/1603476/+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 1510570] Re: BLE pairing fail
Hi Guys, thank you all for the effort, I can confirm that post #25 & #27 works as expected! (including the step of removing/renaming file 50 -bluetooth-hci-auto-poweron.rules) Many thanks! -- 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/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+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 1607571] Re: No network devices after suspend and resume
adin, could you please provide the missing information from https://wiki.ubuntu.com/DebuggingKernelSuspend ? -- 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/1607571 Title: No network devices after suspend and resume Status in linux package in Ubuntu: Incomplete Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+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 1608854] Re: [arm64] nova instances can't boot with 3.13.0-92
I think all the files are here ? ** 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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: Confirmed Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1608854 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: Incomplete Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608820] Re: Cannot use BT speaker - sink is suspended
** Summary changed: - Cannot use BT speaker after resume from suspend + Cannot use BT speaker - sink is suspended ** Description changed: - After resuming from suspend it is possible to connect to a BT speaker but not possible to play anything. + After a fresh boot or resuming from suspend it is possible to connect to a BT speaker but not possible to play anything. Furthermore, if I play a video from youtube, the stream plays fine if the output is the internal speaker, but as soon as I select the BT speaker the stream hangs. It resumes immediately if I switch back to the internal speaker. When I play something over the BT speaker the following lines are logged in the journal: pulseaudio[5340]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile bluetoothd[3230]: /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1: fd(24) ready rtkit-daemon[3950]: Supervising 5 threads of 1 processes of 1 users. rtkit-daemon[3950]: Successfully made thread 28532 of process 5340 (n/a) owned by '1000' RT at priority 5. rtkit-daemon[3950]: Supervising 6 threads of 1 processes of 1 users. pulseaudio[5340]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1 (Operation Not Authorized) kernel: input: B8:69:C2:3D:56:CE as /devices/virtual/input/input26 pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. gnome-session[5383]: ** (zeitgeist-datahub:5874): WARNING **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required wpa_supplicant[3556]: wlan0: WPA: Group rekeying completed with 14:0c:76:71:a1:f4 [GTK=CCMP] pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. - - A reboot of the laptop usually clears the problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 2 09:09:18 2016 InstallationDate: Installed on 2013-09-03 (1063 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. UX32VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic.efi.signed root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: - hci0:Type: BR/EDR Bus: USB - BD Address: C4:85:08:A7:45:76 ACL MTU: 310:10 SCO MTU: 64:8 - UP RUNNING - RX bytes:3492 acl:70 sco:0 events:137 errors:0 - TX bytes:4838 acl:64 sco:0 commands:57 errors:0 + hci0:Type: BR/EDR Bus: USB + BD Address: C4:85:08:A7:45:76 ACL MTU: 310:10 SCO MTU: 64:8 + UP RUNNING + RX bytes:3492 acl:70 sco:0 events:137 errors:0 + TX bytes:4838 acl:64 sco:0 commands:57 errors:0 upstart.bluetooth.override: manual -- 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/1608820 Title: Cannot use BT speaker - sink is suspended Status in bluez package in Ubuntu: New Bug description: After a fresh boot or resuming from suspend it is possible to connect to a BT speaker but not possible to play anything. Furthermore, if I play a video from youtube, the stream plays fine if the output is the internal speaker, but as soon as I select the BT speaker the stream hangs. It resumes immediately if I switch back to the internal speaker. When I play something over the BT speaker the following lines are logged in the journal: pulseaudio[5340]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profil
[Kernel-packages] [Bug 1605433] Re: [Dell Alienware 17R3] enable/disable touchpad not working
adin, as the article advises, could you please attach your files separately, uncompressed, and untarred? -- 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/1605433 Title: [Dell Alienware 17R3] enable/disable touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: The touchpad does not work as expected. It can't be enabled or disabled through FN+F11 combination. The light (in the pad) always turns on, regardless of its non functionality. The problem seems related to bug #1523738, and some say solution #24 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523738/comments/24) works, but it didn't for me. I'm not even sure if it is the same as the version of the hardware is different. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Jul 21 21:07:42 2016 InstallationDate: Installed on 2016-07-03 (18 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2016-07-16T11:29:07.694480 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 4247 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (24 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 Tags: xenial Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605433/+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
Re: [Kernel-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from...
Yes, having gone away for 15.10, I'm getting this problem again. Less frequently, but the only way I've found to fix it is a reboot. On 2 August 2016 at 08:06, Eric wrote: > Confirming bug still present with kernel 4.4.0-31 on 16.04. My wifi > actually goes 'dormant'. > > On Aug 2, 2016 00:41, "mxyzptlk" <1408...@bugs.launchpad.net> wrote: > > > As Gena said -- happens multiple times a day on 16.04 with kernel > > 4.4.0-31. Still occurred with kernel 4.4.0-28, but less frequently. > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1408963 > > > > Title: > > [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 > > :03:00.0: BSM uCode verification failed at addr ...; wlan0: > > deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING), > > > > Status in linux-firmware package in Ubuntu: > > Confirmed > > Status in network-manager package in Ubuntu: > > Confirmed > > > > Bug description: > > From time to time, the system loses all wireles networks and kubuntu > > network manager applet goes blank - not even one network is shown. All > > wifi connections are broken. Rebooting fixes the issue, switching to > > WICD on-the-fly enables to continue browsing without rebooting, so it > > seems to be no hardware issue or iwl3945 issue. > > > > What to expect: stable connections and flawless network managing. > > What happens: so above. > > > > Further informations about the system, the network configuration, the > > package version can be found in the attachment, also parts of rsyslog > > and dmesg. > > > > Interesting, according to some helpers, are the following lines: > > dmesg: wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice > > (Reason: 3=DEAUTH_LEAVING) > > > > lsb_release -a > > No LSB modules are available. > > Distributor ID: Ubuntu > > Description:Ubuntu 14.10 > > Release:14.10 > > Codename: utopic > > > > apt-cache policy network-manager > > network-manager: > > Installiert: 0.9.8.8-0ubuntu28 > > Installationskandidat: 0.9.8.8-0ubuntu28 > > Versionstabelle: > >*** 0.9.8.8-0ubuntu28 0 > > 500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 > > Packages > > 100 /var/lib/dpkg/status > > > > To manage notifications about this bug go to: > > > > > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1408963/+subscriptions > > > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1408963 > > Title: > [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 > :03:00.0: BSM uCode verification failed at addr ...; wlan0: > deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING), > > Status in linux-firmware package in Ubuntu: > Confirmed > Status in network-manager package in Ubuntu: > Confirmed > > Bug description: > From time to time, the system loses all wireles networks and kubuntu > network manager applet goes blank - not even one network is shown. All > wifi connections are broken. Rebooting fixes the issue, switching to > WICD on-the-fly enables to continue browsing without rebooting, so it > seems to be no hardware issue or iwl3945 issue. > > What to expect: stable connections and flawless network managing. > What happens: so above. > > Further informations about the system, the network configuration, the > package version can be found in the attachment, also parts of rsyslog > and dmesg. > > Interesting, according to some helpers, are the following lines: > dmesg: wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice > (Reason: 3=DEAUTH_LEAVING) > > lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu > Description:Ubuntu 14.10 > Release:14.10 > Codename: utopic > > apt-cache policy network-manager > network-manager: > Installiert: 0.9.8.8-0ubuntu28 > Installationskandidat: 0.9.8.8-0ubuntu28 > Versionstabelle: >*** 0.9.8.8-0ubuntu28 0 > 500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 > Packages > 100 /var/lib/dpkg/status > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1408963/+subscriptions > -- 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/1408963 Title: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 :03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING), Status in linux-firmware package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: From time to time
[Kernel-packages] [Bug 1608854] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712258/+files/UdevLog.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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712256/+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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712255/+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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712259/+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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712257/+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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] Re: [arm64] nova instances can't boot with 3.13.0-92
apport information ** Tags added: apport-collected ec2-images trusty ** Description changed: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. + --- + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.21 + Architecture: arm64 + ArecordDevices: Error: [Errno 2] No such file or directory + CRDA: Error: [Errno 2] No such file or directory + CurrentDmesg: + [ 27.314355] random: nonblocking pool is initialized + [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 + DistroRelease: Ubuntu 14.04 + Ec2AMI: ami-08ce + Ec2AMIManifest: FIXME + Ec2AvailabilityZone: nova + Ec2InstanceType: m1.medium + Ec2Kernel: None + Ec2Ramdisk: None + IwConfig: + lono wireless extensions. + + eth0 no wireless extensions. + Lspci: + + Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk + ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-85-generic N/A + linux-backports-modules-3.13.0-85-generic N/A + linux-firmware 1.127.22 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty ec2-images + Uname: Linux 3.13.0-85-generic aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712252/+files/AudioDevicesInUse.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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+subscriptions -- Mailing
[Kernel-packages] [Bug 1608854] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712253/+files/BootDmesg.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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1608854] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1608854/+attachment/4712254/+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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-08ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1435040] Re: Ubuntu Phone does not connect to car-bluetooth
GTriderXC, I reported this behaviour here: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1596028 - it´s also happening with other devices than carkits... -- 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/1435040 Title: Ubuntu Phone does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1608854] [NEW] [arm64] nova instances can't boot with 3.13.0-92
Public bug reported: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in linux package in Ubuntu: New Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+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 1537737] Re: Since Bluez5, headsets don't reconnect audio when reconnecting
Here some logs in attachment (I think in the first 10 minutes) Explanation : How it works : 1. Turn on the headset --> bluetooth connects automatically the headset (already paired in the past) 2. Make a call --> dialer-app show the bluetooth icon by default 3. No sound for the call (even in internal phone speaker), if you switch back to phone speaker option the sound is back in internal phone speaker 4. Switch back to bluetooth --> still no sound 5. Disconnect manually from headset and reconnect (in settings>Bluetooth>device name) 6. Make a call --> The sound is now routed to headset How it should work : 1. Turn on the headset --> bluetooth connects automatically the headset (already paired in the past) 2. Make a call --> dialer-app shows the bluetooth icon by default 3. The sound is routed to the bluetooth headset Alexandre, ** Attachment added: "log-bug-1537737 .zip" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537737/+attachment/4712251/+files/log-bug-1537737%20.zip -- 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/1537737 Title: Since Bluez5, headsets don't reconnect audio when reconnecting Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Pairing a Bluetooth headset (A2DP) seems to work fine. After pairing, the phone successfully switches to transmit audio over Bluetooth. When disconnecting the Headset again, the phone successfully switches audio back to the integrated speaker. However, on a reconnect without pairing, the headset seems to connect properly, but it doesn't route audio any more to the headset. Despite the headset being connected, audio is still routed to the integrated speaker. A reboot does not seem to help. The only way to get back to Bluetooth audio streaming is to delete the device from the settings, and pair it again, which makes it work once again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537737/+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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
Here is the logs with an other headset Doing a call --> lot of noise / saturated sound in headset Playing music --> sound is good in headset At the beginning of the log, I had to disconnect manually from the headset and reconnect because the sound was not redirected to headset (I think this is an other bug like here --> #1537737 [1]) [1] : https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537737 Alexandre, ** Attachment added: "log-bug-1590844.zip" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+attachment/4712228/+files/log-bug-1590844.zip -- 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/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
Hi Joseph, I tried the 4.7, but it made the compute node unbootable : https://paste.ubuntu.com/21865889/ >From the initramfs shell, I had to manually load a few modules (ahci_xgene, >sd_mod and ext4) so I could mount the root filesystem and get back to the >previous working version (4.2). Was that expected ? Will the same thing happen with the 4.6 based yakkety kernel you pasted above ? Thanks -- 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/1602577 Title: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Hi, In order to investigate bug LP#1531768, we upgraded some arm64 compute nodes (swirlices) to a 4.4 kernel. I think it made the VMs work better, but the hosts became extremely unstable. After some time, getting a shell on them would be impossible. Connecting on the VSP, you'd get a prompt, and once you typed your username and password, you'd see the motd but the shell would never spawn. Because of these instability issues, all the arm64 compute nodes are now back on 4.2. However, we managed to capture "perf record" data when a host was failing. I'll attach it to the bug. Perhaps it will give you hints as to what we can do to help you troubleshoot this bug further. Once we have your instructions, we'll happily reboot one (or a few) nodes to 4.4 to continue troubleshooting. Thanks ! --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 12 12:54 seq crw-rw 1 root audio 116, 33 Jul 12 12:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 RelatedPackageVersions: linux-restricted-modules-4.2.0-41-generic N/A linux-backports-modules-4.2.0-41-generic N/A linux-firmware1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.2.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1608820] [NEW] Cannot use BT speaker after resume from suspend
Public bug reported: After resuming from suspend it is possible to connect to a BT speaker but not possible to play anything. Furthermore, if I play a video from youtube, the stream plays fine if the output is the internal speaker, but as soon as I select the BT speaker the stream hangs. It resumes immediately if I switch back to the internal speaker. When I play something over the BT speaker the following lines are logged in the journal: pulseaudio[5340]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile bluetoothd[3230]: /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1: fd(24) ready rtkit-daemon[3950]: Supervising 5 threads of 1 processes of 1 users. rtkit-daemon[3950]: Successfully made thread 28532 of process 5340 (n/a) owned by '1000' RT at priority 5. rtkit-daemon[3950]: Supervising 6 threads of 1 processes of 1 users. pulseaudio[5340]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1 (Operation Not Authorized) kernel: input: B8:69:C2:3D:56:CE as /devices/virtual/input/input26 pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. gnome-session[5383]: ** (zeitgeist-datahub:5874): WARNING **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required wpa_supplicant[3556]: wlan0: WPA: Group rekeying completed with 14:0c:76:71:a1:f4 [GTK=CCMP] pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. A reboot of the laptop usually clears the problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 2 09:09:18 2016 InstallationDate: Installed on 2013-09-03 (1063 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. UX32VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic.efi.signed root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: C4:85:08:A7:45:76 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:3492 acl:70 sco:0 events:137 errors:0 TX bytes:4838 acl:64 sco:0 commands:57 errors:0 upstart.bluetooth.override: manual ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1608820 Title: Cannot use BT speaker after resume from suspend Status in bluez package in Ubuntu: New Bug description: After resuming from suspend it is possible to connect to a BT speaker but not possible to play anything. Furthermore, if I play a video from youtube, the stream plays fine if the output is the internal speaker, but as soon as I select the BT speaker the stream hangs. It resumes immediately if I switch back to the internal speaker. When I play something over the BT speaker the following lines are logged in the journal: pulseaudio[5340]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile bluetoothd[3230]: /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1: fd(24) ready rtkit-daemon[3950]: Supervising 5 threads of 1 processes of 1 users. rtkit-daemon[3950]: Successfully made thread 28532 of process 5340 (n/a) owned by '1000' RT at priority 5. rtkit-daemon[3950]: Supervising 6 threads of 1 processes of 1 users. pulseaudio[5340]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1 (Operation Not
Re: [Kernel-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from...
Confirming bug still present with kernel 4.4.0-31 on 16.04. My wifi actually goes 'dormant'. On Aug 2, 2016 00:41, "mxyzptlk" <1408...@bugs.launchpad.net> wrote: > As Gena said -- happens multiple times a day on 16.04 with kernel > 4.4.0-31. Still occurred with kernel 4.4.0-28, but less frequently. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1408963 > > Title: > [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 > :03:00.0: BSM uCode verification failed at addr ...; wlan0: > deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING), > > Status in linux-firmware package in Ubuntu: > Confirmed > Status in network-manager package in Ubuntu: > Confirmed > > Bug description: > From time to time, the system loses all wireles networks and kubuntu > network manager applet goes blank - not even one network is shown. All > wifi connections are broken. Rebooting fixes the issue, switching to > WICD on-the-fly enables to continue browsing without rebooting, so it > seems to be no hardware issue or iwl3945 issue. > > What to expect: stable connections and flawless network managing. > What happens: so above. > > Further informations about the system, the network configuration, the > package version can be found in the attachment, also parts of rsyslog > and dmesg. > > Interesting, according to some helpers, are the following lines: > dmesg: wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice > (Reason: 3=DEAUTH_LEAVING) > > lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu > Description:Ubuntu 14.10 > Release:14.10 > Codename: utopic > > apt-cache policy network-manager > network-manager: > Installiert: 0.9.8.8-0ubuntu28 > Installationskandidat: 0.9.8.8-0ubuntu28 > Versionstabelle: >*** 0.9.8.8-0ubuntu28 0 > 500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 > Packages > 100 /var/lib/dpkg/status > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1408963/+subscriptions > -- 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/1408963 Title: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 :03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING), Status in linux-firmware package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: From time to time, the system loses all wireles networks and kubuntu network manager applet goes blank - not even one network is shown. All wifi connections are broken. Rebooting fixes the issue, switching to WICD on-the-fly enables to continue browsing without rebooting, so it seems to be no hardware issue or iwl3945 issue. What to expect: stable connections and flawless network managing. What happens: so above. Further informations about the system, the network configuration, the package version can be found in the attachment, also parts of rsyslog and dmesg. Interesting, according to some helpers, are the following lines: dmesg: wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice (Reason: 3=DEAUTH_LEAVING) lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename: utopic apt-cache policy network-manager network-manager: Installiert: 0.9.8.8-0ubuntu28 Installationskandidat: 0.9.8.8-0ubuntu28 Versionstabelle: *** 0.9.8.8-0ubuntu28 0 500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1408963/+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
