[Kernel-packages] [Bug 1579596] Re: [amdgpu] [TOPAZ 1002:6900] System failed to resume from suspend with amdgpu loaded.
** Changed in: hwe-next Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu) Status: Invalid => Won't Fix ** Changed in: hwe-next Status: Invalid => Won't Fix -- 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/1579596 Title: [amdgpu] [TOPAZ 1002:6900] System failed to resume from suspend with amdgpu loaded. Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in xserver-xorg-video-amdgpu package in Ubuntu: Won't Fix Bug description: The system failed to resume from S3. But the issue can be quickly resolved after blacklisting amdgpu. The system can resume if "pm_test" is "devices", there are various error messages pop out nonetheless. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1579596/+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 1599068] Re: Add support for Intel 8265 Bluetooth ([8087:0A2B])
** Changed in: hwe-next Status: New => 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/1599068 Title: Add support for Intel 8265 Bluetooth ([8087:0A2B]) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Backport supports for Intel 8265 Bluetooth from upstream The support is introduced in v4.7 so yakkety doesn't need this backport To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1599068/+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 1614496] Re: Computer doesn't fully shut down
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1614496 Title: Computer doesn't fully shut down Status in linux package in Ubuntu: Expired Bug description: Sometimes when I turn off the computer it doesn't fully shut down. The splash screen is displayed, then disappears but the lights and fan keep turned on. Then if I don't notice it, the next day I have no battery left. My version is Ubuntu 4.4.0-34.53-generic 4.4.15 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 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/controlC0: andremw3760 F pulseaudio CurrentDesktop: MATE Date: Thu Aug 18 08:39:16 2016 HibernationDevice: RESUME=UUID=3c474d99-e2ed-48f6-872b-e079cc02bae9 InstallationDate: Installed on 2016-07-15 (33 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude 3440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=9a9185cc-07ba-40d6-82ac-6985ce7e4ff4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 031P68 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/11/2014:svnDellInc.:pnLatitude3440:pvrNotSpecified:rvnDellInc.:rn031P68:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 3440 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614496/+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 1641049] Re: NFSv4 do not invalidate cached information about deleted files
All information should be added now. ** 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/1641049 Title: NFSv4 do not invalidate cached information about deleted files Status in linux package in Ubuntu: Confirmed Bug description: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed
[Kernel-packages] [Bug 1618952] Re: Display brightness keys not registered by ~$acpi_listen
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1618952 Title: Display brightness keys not registered by ~$acpi_listen Status in linux package in Ubuntu: Expired Bug description: Brightness keys donot repond, Brightness controls on xfce4_power_manager behave as expected. Either kernel is not recognizing the fn+f5/f6 commands or their is a problem with my configuration. here is the event output of all of my fn+(f keys): ~ $ acpi_listen button/volumeup VOLUP 0080 K button/volumedown VOLDN 0080 K button/mute MUTE 0080 K button/mute MUTE 0080 K PNP0C14:00 00ff PNP0C14:00 00ff PNP0C14:00 00ff button/sleep SBTN 0080 button/sleep PNP0C0E:00 0080 0001 (As a side note, my bios has no configuration options for the function keys.) (On another note, it is worth noting the fn+f2 does not respond with an event calling for airplane mode either, which is not important to me but may be important for others, if this is fixed by any solution here I will make note, though airplane mode may be a feature request and not a bug.) I have tried several options in the etc/default/grub file, these include: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video.use_native_backlight=1" GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video.use_native_backlight=0" GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=intel_backlight" GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=" GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Linux" I am using Mint XFCE Sarah (Ubuntu Xenial) 64-bit, xfce4_power_manager was tested with all above configurations to both handle and not handle display brightness keys. My Computer is an ASUS model is X540LA. I am attaching a few files to help with this bug report. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Linux 18 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-10 (92 days ago) InstallationMedia: Linux Mint 17.2 "Rafaela" - Release amd64 20150723 Package: linux (not installed) Tags: sarah Uname: Linux 4.8.0-040800rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618952/+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 1609598] Re: iMac 7, 1 Screen "Bleached"/Corrupted after Waking from Suspend
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1609598 Title: iMac 7,1 Screen "Bleached"/Corrupted after Waking from Suspend Status in linux package in Ubuntu: Expired Bug description: I've had this issue on my iMac 7,1 A1224 ever since I've installed Ubuntu 16.04. When waking from suspend, the screen will be washed out. Rebooting the system fixes this issue. I am aware that this issue happens for this machine across other versions of Ubuntu and the Linux kernel (is that a thing? I'm pretty inept), but I have been unable to find a resolution. This issue has also been discussed on the Free Desktops site: https://bugs.freedesktop.org/show_bug.cgi?id=90843 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: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1884 F pulseaudio CurrentDesktop: GNOME Date: Wed Aug 3 08:15:39 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8c3c66ec-44dd-4529-b552-ea8363ccc781 InstallationDate: Installed on 2016-07-30 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. iMac7,1 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=31f3cd66-85f4-415f-bafb-9d68c2e6597e 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: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM71.88Z.007A.B03.0803051705 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238CC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238CC8 dmi.modalias: dmi:bvnAppleInc.:bvrIM71.88Z.007A.B03.0803051705:bd03/05/08:svnAppleInc.:pniMac7,1:pvr1.0:rvnAppleInc.:rnMac-F4238CC8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F4238CC8: dmi.product.name: iMac7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609598/+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 1641083] Re: linux: 4.8.0-28.30 -proposed tracker
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp6g002__4.8.0-27.29__2016-11-12_03-17-00/results-index.html ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques (henrix) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques (henrix) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the 4.8.0-28.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Uploaded + kernel-stable-phase-changed:Saturday, 12. November 2016 03:16 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the 4.8.0-28.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true derivative-trackers-created: true phase: Uploaded - kernel-stable-phase-changed:Saturday, 12. November 2016 03:16 UTC - kernel-stable-phase:Uploaded -- 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/1641083 Title: linux: 4.8.0-28.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-28.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1641083/+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 1641083] Re: linux: 4.8.0-28.30 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques (henrix) ** Description changed: This bug is for tracking the 4.8.0-28.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Friday, 11. November 2016 10:30 UTC - -- swm properties -- derivative-trackers-created: true phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Saturday, 12. November 2016 01:16 UTC ** Description changed: This bug is for tracking the 4.8.0-28.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Saturday, 12. November 2016 01:16 UTC + phase: Uploaded -- 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/1641083 Title: linux: 4.8.0-28.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-28.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1641083/+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 1640921] modoc (ppc64el) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-49.70/modoc__4.4.0-49.70__2016-11-11_23-52-00/results-index.html -- 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/1640921 Title: linux: 4.4.0-49.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1640921/+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 1641244] 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/1641244 Title: Ubuntu 16.04 suspend works only twice or thrice in a row Status in linux package in Ubuntu: Confirmed Bug description: This problem was introduced with Ubuntu 16.04 or rather with kernel 4.4; I never had this problem on Ubuntu 14.04 and kernels from 3.x line. Suspend works only twice in a row, sometimes three times, the next attempt of suspending results in basically dead machine but system fans are spinning, monitor back light is on etc. My problem is similar to #1634446, #1566302, #1574125, symptoms are basically the same. I tried more recent kernels: 4.6, 4.8, but its all the same. The problem existed after upgrading my system from 14.04 to 16.04 and after fresh installation of 16.04. If I recall correctly the problem existed with proprietary graphic drivers (nvidia-367 for my GTX770) and also for default open source graphic drivers. I have an encrypted home folder, 8GB of RAM and 16GB swap partition. I'll try to provide every information needed so please inform me if you know how could I make this bug report better. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marek 1962 F pulseaudio /dev/snd/controlC0: marek 1962 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 11 23:45:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=efc7d3d0-4d67-4835-acc7-651d70791aed InstallationDate: Installed on 2016-11-06 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P67-DS3-B3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=a4f5390e-8590-4868-a259-6bafb52a2901 ro quiet splash nomodeset vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: P67-DS3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67-DS3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67-DS3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67-DS3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641244/+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 1641244] Re: Ubuntu 16.04 suspend works only twice or thrice in a row
** Description changed: This problem was introduced with Ubuntu 16.04 or rather with kernel 4.4; I never had this problem on Ubuntu 14.04 and kernels from 3.x line. Suspend works only twice in a row, sometimes three times, the next attempt of suspending results in basically dead machine but system fans are spinning, monitor back light is on etc. My problem is similar to #1634446, #1566302, #1574125, symptoms are basically the same. I tried more recent kernels: 4.6, 4.8, but its all the same. The problem existed after upgrading my system from 14.04 to 16.04 and after fresh installation of 16.04. If I recall correctly the problem existed with - proprietary graphic drivers (nvidia-367 for my GTX770) and for default - open source graphic drivers. I have an encrypted home partition, 8GB or - RAM and 16GB swap partition. + proprietary graphic drivers (nvidia-367 for my GTX770) and also for + default open source graphic drivers. I have an encrypted home folder, + 8GB of RAM and 16GB swap partition. I'll try to provide every information needed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: marek 1962 F pulseaudio - /dev/snd/controlC0: marek 1962 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: marek 1962 F pulseaudio + /dev/snd/controlC0: marek 1962 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 11 23:45:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=efc7d3d0-4d67-4835-acc7-651d70791aed InstallationDate: Installed on 2016-11-06 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: - lono wireless extensions. - - enp3s0no wireless extensions. + lono wireless extensions. + + enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P67-DS3-B3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=a4f5390e-8590-4868-a259-6bafb52a2901 ro quiet splash nomodeset vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.4.0-47-generic N/A - linux-backports-modules-4.4.0-47-generic N/A - linux-firmware1.157.4 + linux-restricted-modules-4.4.0-47-generic N/A + linux-backports-modules-4.4.0-47-generic N/A + linux-firmware1.157.4 RfKill: - + SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: P67-DS3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67-DS3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67-DS3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67-DS3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Description changed: This problem was introduced with Ubuntu 16.04 or rather with kernel 4.4; I never had this problem on Ubuntu 14.04 and kernels from 3.x line. Suspend works only twice in a row, sometimes three times, the next attempt of suspending results in basically dead machine but system fans are spinning, monitor back light is on etc. My problem is similar to #1634446, #1566302, #1574125, symptoms are basically the same. I tried more recent kernels: 4.6, 4.8, but its all the same. The problem existed after upgrading my system from 14.04 to 16.04 and after fresh installation of 16.04. If I recall correctly the problem existed with proprietary graphic drivers (nvidia-367 for my GTX770) and also for default open source graphic drivers. I have an encrypted home folder, 8GB of RAM and 16GB swap partition. - I'll try to provide every information needed + I'll try to provide every information needed so please inform me if you + know how could I make this bug report better. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marek 1962 F pulseaudio /dev/snd/controlC0: marek 1962 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 11 23:45:45 2016 EcryptfsInUse: Yes
[Kernel-packages] [Bug 1640921] Re: linux: 4.4.0-49.70 -proposed tracker
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-47.68/kernel01__4.4.0-47.68__2016-11-11_23-20-00/results-index.html ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques (henrix) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the 4.4.0-49.70 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Uploaded + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Friday, 11. November 2016 23:18 UTC ** Description changed: This bug is for tracking the 4.4.0-49.70 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true derivative-trackers-created: true phase: Uploaded - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Friday, 11. November 2016 23:18 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1640921/+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 1640921] s2lp3 (s390x.LPAR) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-47.68/s2lp3__4.4.0-47.68__2016-11-11_23-20-00/results-index.html -- 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/1640921 Title: linux: 4.4.0-49.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1640921/+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 1640921] Re: linux: 4.4.0-49.70 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques (henrix) -- 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/1640921 Title: linux: 4.4.0-49.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1640921/+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 1641244] [NEW] Ubuntu 16.04 suspend works only twice or thrice in a row
Public bug reported: This problem was introduced with Ubuntu 16.04 or rather with kernel 4.4; I never had this problem on Ubuntu 14.04 and kernels from 3.x line. Suspend works only twice in a row, sometimes three times, the next attempt of suspending results in basically dead machine but system fans are spinning, monitor back light is on etc. My problem is similar to #1634446, #1566302, #1574125, symptoms are basically the same. I tried more recent kernels: 4.6, 4.8, but its all the same. The problem existed after upgrading my system from 14.04 to 16.04 and after fresh installation of 16.04. If I recall correctly the problem existed with proprietary graphic drivers (nvidia-367 for my GTX770) and for default open source graphic drivers. I have an encrypted home partition, 8GB or RAM and 16GB swap partition. I'll try to provide every information needed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marek 1962 F pulseaudio /dev/snd/controlC0: marek 1962 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 11 23:45:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=efc7d3d0-4d67-4835-acc7-651d70791aed InstallationDate: Installed on 2016-11-06 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P67-DS3-B3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=a4f5390e-8590-4868-a259-6bafb52a2901 ro quiet splash nomodeset vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: P67-DS3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67-DS3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67-DS3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67-DS3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1641244/+attachment/4776178/+files/version.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/1641244 Title: Ubuntu 16.04 suspend works only twice or thrice in a row Status in linux package in Ubuntu: New Bug description: This problem was introduced with Ubuntu 16.04 or rather with kernel 4.4; I never had this problem on Ubuntu 14.04 and kernels from 3.x line. Suspend works only twice in a row, sometimes three times, the next attempt of suspending results in basically dead machine but system fans are spinning, monitor back light is on etc. My problem is similar to #1634446, #1566302, #1574125, symptoms are basically the same. I tried more recent kernels: 4.6, 4.8, but its all the same. The problem existed after upgrading my system from 14.04 to 16.04 and after fresh installation of 16.04. If I recall correctly the problem existed with proprietary graphic drivers (nvidia-367 for my GTX770) and for default open source graphic drivers. I have an encrypted home partition, 8GB or RAM and 16GB swap partition. I'll try to provide every information needed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marek 1962 F pulseaudio /dev/snd/controlC0: marek 1962 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 11 23:45:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=efc7d3d0-4d67-4835-acc7-651d70791aed InstallationDate: Installed on 2016-11-06 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte
[Kernel-packages] [Bug 1641235] Latest crashdump console logs
Default Comment by Bridge ** Attachment added: "Latest crashdump console logs" https://bugs.launchpad.net/bugs/1641235/+attachment/4776156/+files/kdump_console_logs_Latest ** Changed in: ubuntu Assignee: (unassigned) => Taco Screen team (taco-screen-team) ** Package changed: ubuntu => makedumpfile (Ubuntu) -- 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/1641235 Title: Ubuntu 16.10: kdump over nfs did not generate complete vmcore Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - HARSHA THYAGARAJA - 2016-11-03 08:05:59 == ---Problem Description--- kdump over nfs did not generate complete vmcore ---uname output--- Linux ltciofvtr-firestone1 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:41:40 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV (Baremetal) - Firestone ---Steps to Reproduce--- 1. Setup NFS 2. Trigger crash: echo c > /proc/sysrq-trigger == Comment: #6 - Kevin W. Rudd - 2016-11-04 16:30:49 == Hi Harsha. It looks like the base kdump NFS functionality works just fine. The known issue with makedumpfile is causing it to drop back to using "cp" to transfer the entire, non-compressed /proc/vmcore image. That's a rather large amount of data to send over to the remote server, and it appears to be sending back an I/O error after the first 122G. Further debug would need to be done to determine if this is a client- side or server-side issue. I recommend first bringing your remote NFS server up to the current release as it is currently a bit down-rev. == Comment: #8 - HARSHA THYAGARAJA - 2016-11-10 02:02:31 == Hi Kevin, I updated my peer to Ubuntu 16.10 and still saw the same observation. A snippet of the problem at hand is pasted below. [ 20.610748] kdump-tools[4559]: Starting kdump-tools: * Mounting NFS mountpoint 150.1.1.20:/home/tools ... [ 53.400516] kdump-tools[4559]: * Dumping to NFS mountpoint 150.1.1.20:/home/tools/201611100158 [ 53.409242] kdump-tools[4559]: * running makedumpfile -c -d 31 /proc/vmcore /mnt/var/crash/9.47.84.18-201611100158/dump-incomplete [ 53.526593] kdump-tools[4559]: get_mem_map: Can't distinguish the memory type. [ 53.527154] kdump-tools[4559]: The kernel version is not supported. [ 53.527488] kdump-tools[4559]: The makedumpfile operation may be incomplete. [ 53.527813] kdump-tools[4559]: makedumpfile Failed. [ 53.528117] kdump-tools[4559]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 90.754092] kdump-tools[4559]: cp: error writing '/mnt/var/crash/9.47.84.18-201611100158/vmcore-incomplete': Input/output error [ 90.754857] kdump-tools[4559]: * kdump-tools: failed to save vmcore in /mnt/var/crash/9.47.84.18-201611100158 [ 90.756155] kdump-tools[4559]: * running makedumpfile --dump-dmesg /proc/vmcore /mnt/var/crash/9.47.84.18-201611100158/dmesg.201611100158 [ 90.758731] kdump-tools[4559]: get_mem_map: Can't distinguish the memory type. [ 90.759089] kdump-tools[4559]: The kernel version is not supported. [ 90.759436] kdump-tools[4559]: The makedumpfile operation may be incomplete. [ 90.759780] kdump-tools[4559]: makedumpfile Failed. [ 90.760094] kdump-tools[4559]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 90.760668] kdump-tools[4559]: * kdump-tools: failed to save dmesg content in /mnt/var/crash/9.47.84.18-201611100158 [ 90.846117] kdump-tools[4559]: Thu, 10 Nov 2016 01:59:56 -0500 [ 90.886629] kdump-tools[4559]: Failed to read reboot parameter file: No such file or directory [ 90.887070] kdump-tools[4559]: Rebooting. == Comment: #13 - Kevin W. Rudd - 2016-11-11 17:12:33 == I was able to replicate this with debugging at both the kdump client and remote NFS server. The server was perfectly happy with the data coming at it, and appeared to be processing a COMMIT request from the client when the client shut down the connection. Looking at the client-side logs after a failure showed that it was logging "server ... not responding" messages, and bailed on the connection within the span of just a few seconds. This appears to be due to a very over-aggressive timeout being specified in /usr/sbin/kdump-config: mount -t nfs -o nolock -o tcp -o soft -o timeo=5 -o retrans=5 $NFS $KDUMP_COREDIR The timeo value is deciseconds, and "5" is far too aggressive for this type of connection. From my observations, the COMMIT was not issued until about 60G was transferred, and most remote servers will take a lot longer than 5 tenths of a second to flush that amount of data and respond to the COMMIT. I'm not sure what problem specifying this timeo value was supposed to address, but it would be better to leave the timeo value at its default for a tcp
[Kernel-packages] [Bug 1641235] [NEW] Ubuntu 16.10: kdump over nfs did not generate complete vmcore
You have been subscribed to a public bug: == Comment: #0 - HARSHA THYAGARAJA - 2016-11-03 08:05:59 == ---Problem Description--- kdump over nfs did not generate complete vmcore ---uname output--- Linux ltciofvtr-firestone1 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:41:40 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV (Baremetal) - Firestone ---Steps to Reproduce--- 1. Setup NFS 2. Trigger crash: echo c > /proc/sysrq-trigger == Comment: #6 - Kevin W. Rudd - 2016-11-04 16:30:49 == Hi Harsha. It looks like the base kdump NFS functionality works just fine. The known issue with makedumpfile is causing it to drop back to using "cp" to transfer the entire, non-compressed /proc/vmcore image. That's a rather large amount of data to send over to the remote server, and it appears to be sending back an I/O error after the first 122G. Further debug would need to be done to determine if this is a client- side or server-side issue. I recommend first bringing your remote NFS server up to the current release as it is currently a bit down-rev. == Comment: #8 - HARSHA THYAGARAJA - 2016-11-10 02:02:31 == Hi Kevin, I updated my peer to Ubuntu 16.10 and still saw the same observation. A snippet of the problem at hand is pasted below. [ 20.610748] kdump-tools[4559]: Starting kdump-tools: * Mounting NFS mountpoint 150.1.1.20:/home/tools ... [ 53.400516] kdump-tools[4559]: * Dumping to NFS mountpoint 150.1.1.20:/home/tools/201611100158 [ 53.409242] kdump-tools[4559]: * running makedumpfile -c -d 31 /proc/vmcore /mnt/var/crash/9.47.84.18-201611100158/dump-incomplete [ 53.526593] kdump-tools[4559]: get_mem_map: Can't distinguish the memory type. [ 53.527154] kdump-tools[4559]: The kernel version is not supported. [ 53.527488] kdump-tools[4559]: The makedumpfile operation may be incomplete. [ 53.527813] kdump-tools[4559]: makedumpfile Failed. [ 53.528117] kdump-tools[4559]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 90.754092] kdump-tools[4559]: cp: error writing '/mnt/var/crash/9.47.84.18-201611100158/vmcore-incomplete': Input/output error [ 90.754857] kdump-tools[4559]: * kdump-tools: failed to save vmcore in /mnt/var/crash/9.47.84.18-201611100158 [ 90.756155] kdump-tools[4559]: * running makedumpfile --dump-dmesg /proc/vmcore /mnt/var/crash/9.47.84.18-201611100158/dmesg.201611100158 [ 90.758731] kdump-tools[4559]: get_mem_map: Can't distinguish the memory type. [ 90.759089] kdump-tools[4559]: The kernel version is not supported. [ 90.759436] kdump-tools[4559]: The makedumpfile operation may be incomplete. [ 90.759780] kdump-tools[4559]: makedumpfile Failed. [ 90.760094] kdump-tools[4559]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 90.760668] kdump-tools[4559]: * kdump-tools: failed to save dmesg content in /mnt/var/crash/9.47.84.18-201611100158 [ 90.846117] kdump-tools[4559]: Thu, 10 Nov 2016 01:59:56 -0500 [ 90.886629] kdump-tools[4559]: Failed to read reboot parameter file: No such file or directory [ 90.887070] kdump-tools[4559]: Rebooting. == Comment: #13 - Kevin W. Rudd - 2016-11-11 17:12:33 == I was able to replicate this with debugging at both the kdump client and remote NFS server. The server was perfectly happy with the data coming at it, and appeared to be processing a COMMIT request from the client when the client shut down the connection. Looking at the client-side logs after a failure showed that it was logging "server ... not responding" messages, and bailed on the connection within the span of just a few seconds. This appears to be due to a very over-aggressive timeout being specified in /usr/sbin/kdump-config: mount -t nfs -o nolock -o tcp -o soft -o timeo=5 -o retrans=5 $NFS $KDUMP_COREDIR The timeo value is deciseconds, and "5" is far too aggressive for this type of connection. From my observations, the COMMIT was not issued until about 60G was transferred, and most remote servers will take a lot longer than 5 tenths of a second to flush that amount of data and respond to the COMMIT. I'm not sure what problem specifying this timeo value was supposed to address, but it would be better to leave the timeo value at its default for a tcp connection (let the TCP protocol handle any communication timeouts on its own). When I modified kdump-config to use the default timeo of 600, the kdump process transferred the entire vmcore without error. ** Affects: makedumpfile (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-148148 severity-high targetmilestone-inin1610 -- Ubuntu 16.10: kdump over nfs did not generate complete vmcore https://bugs.launchpad.net/bugs/1641235 You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1638990] Re: nvidia-367 with kernel 4.4.0-45-generic won't boot
Can confirm the problem: started to occur after the update to kernel 4.4.0-45 and nvidia 367.57 and it is the combination of kernel version and nvidia-driver that causes the problem. There are no problems when the nvidia-driver is purged and nouveau is used instead. I am using full disk description. Last working kernel with nvidia 367.57 is 4.4.0-43. Kernel 4.4.0-47 does not fix the problem. Symptoms are either a black screen with blinking underline-prompt in the topleft corner (no fde password prompt, no possibility to switch to console) or a low-res graphical screen for fde password entry, but no way to actually type the password. Setting GRUB_CMDLINE_LINUX_DEFAULT="nomodeset" works for me (it is important to remove "quiet splash" if "nomodeset" is inserted into an existing line) – with this setting, the fde password can be entered in the console and the system boots normally with nvidia 367.57 and kernels 4.4.0-45 and 4.4.-0-47. -- 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/1638990 Title: nvidia-367 with kernel 4.4.0-45-generic won't boot Status in linux package in Ubuntu: Confirmed Bug description: ~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 ~$ apt-cache policy linux-image-4.4.0.45-generic linux-image-4.4.0-45-generic: Installed: 4.4.0-45.66 Candidate: 4.4.0-45.66 Version table: *** 4.4.0-45.66 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status After hitting bug 1633172 and the workaround putting me in a worse state than the initial bug, I started from scratch with Xenial. That worked for a short 24 hours. Then this morning, I got an update for my nvidia drivers. After I upgraded the drivers, I could no longer boot into ubuntu with kernel 4.4.0-45-generic. If I booted with kernel 4.4.0-31-generic, I no longer had an issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lost 2248 F pulseaudio /dev/snd/controlC0: lost 2248 F pulseaudio /dev/snd/controlC1: lost 2248 F pulseaudio CurrentDesktop: XFCE Date: Thu Nov 3 12:12:55 2016 HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6 InstallationDate: Installed on 2016-11-01 (1 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 11361Q0 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/xubuntu--vg-root ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: A3KT57AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: 573921 dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE: dmi.product.name: 11361Q0 dmi.product.version: ThinkStation C30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638990/+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 1640921] Re: linux: 4.4.0-49.70 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques (henrix) ** Description changed: This bug is for tracking the 4.4.0-49.70 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Thursday, 10. November 2016 20:02 UTC - -- swm properties -- derivative-trackers-created: true phase: Packaging + kernel-stable-phase-changed:Friday, 11. November 2016 22:03 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the 4.4.0-49.70 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true - phase: Packaging - kernel-stable-phase-changed:Friday, 11. November 2016 22:03 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- 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/1640921 Title: linux: 4.4.0-49.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1640921/+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 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
@gnidorah done. :] @peter-biely Your welcome. My fans also spin like crazy "when" they spin. My CPU temp is hi because i'm on Brazil (38C avg). But just for consideration, I only use the nvidia card with optimus and my battery life is really good, like 3h to 4h good (only needing to lower the brightness). And I work with game dev and heavy digital illustration! I think it might be related to i7, but Dell also sells that here with Ubuntu. Maybe they use a ISO a bit different for that? -- 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/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 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.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+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 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
Installed Ubuntu 14.04 from filsd (thank you for sharing that btw) on my i7 Inspiron and: - in powertop cpu lowest level is C3 as the kernel 3.19 does not fully support Skylake power management - psensor shows that fan were spinning crazy at 5k rpm but cpu/gpu temp was about +28C even after hour of idle system Maybe there are some drivers need to be installed (list of drivers is pretty huge) but I didn't know what to install, I'll try to play with that, but I'm getting pretty skeptic. Overall I am wondering how this distro can work smoothly with such old kernel which does not fully support Skylake powermanagement on such new HW, but as I've mentioned somewhere: a friend of mine he has this laptop with i5 and even newer kernels work just fine and fans are switching off, although not as often as on windows so it might be really something with i7 vs i5 cpu. -- 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/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 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.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+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 1520519] Re: ASUS ROG GL552 TouchPad not detected
Does the fan issue is really due to backlight=native ? It should be better with Option "DRI" "false" No ? -- 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/1520519 Title: ASUS ROG GL552 TouchPad not detected Status in linux package in Ubuntu: Confirmed Bug description: Laptop Model : ASUS ROG GL552 DH71 First Appearance : Got laptop yesterday. dual booted with ubuntu 14.04. Touchpad never detected. Manufacturer : ASUS ( as listed under windows 10 ) * xinput list * ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=10 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Power Buttonid=7[slave keyboard (3)] ↳ Logitech USB Keyboard id=8[slave keyboard (3)] ↳ Logitech USB Keyboard id=9[slave keyboard (3)] * List of devices * : Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=c05a Version=0111 N: Name="Logitech USB Optical Mouse" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C05A.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Asus WMI hotkeys" P: Phys=asus-nb-wmi/input0 S: Sysfs=/devices/platform/asus-nb-wmi/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=100013 B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0 B: MSC=10 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04f2 Product=b424 Version=6969 N: Name="USB2.0 HD UVC WebCam" P: Phys=usb-:00:14.0-4/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input8 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 please find Xorg.log attached. --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sameer 1813 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice:
[Kernel-packages] [Bug 1640297] Re: 16.04.1 LTS hang during boot 4.4.0-45-generic with /etc/crypttab. Boots fine in 4.4.0-42-generic and older
wget -nH -r --cut-dirs=2 -l1 -A.deb -e robots=off http://kernel.ubuntu.com/~jsalisbury/lp1640297/ sudo dpkg -i *.deb sudo reboot Choose 4.4.0-43 custom kernel wait wait :) .. hangs like before. Next! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640297 Title: 16.04.1 LTS hang during boot 4.4.0-45-generic with /etc/crypttab. Boots fine in 4.4.0-42-generic and older Status in linux package in Ubuntu: Triaged Bug description: System hangs during boot with 4.4.0-45-generic if /etc/crypptab contains a valid entry. Passphrase prompt never seen. Black screen with blinking underscore in upper left corner. Repeated attempts to type passphrase have no effect. There are two workarounds: 1) Comment out line referring the encrypted partition in /etc/crypttab and /etc/fstab. Mount the partition manually after boot completes 2) Boot in 4.4.0-42-generic which works as do earlier versions. i.e. the user provides passphrase at the prompt during boot and the system finishes booting robert@kalymnos:~$ cat /etc/crypttab spare2 UUID=498b08bb-5e6b-4ddf-8b37-e059665a34e6 none luks robert@kalymnos:~$ grep mapper /etc/fstab /dev/mapper/spare2/spare2 ext4 defaults 0 2 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2413 F pulseaudio /dev/snd/controlC0: robert 2413 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=291e75f9-3814-499b-bbb2-f385c164b942 InstallationDate: Installed on 2016-08-18 (83 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-42-generic root=UUID=24166ab8-327a-4477-96d2-3f57b4a47657 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 RfKill: Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/29/2013 dmi.bios.vendor: Intel Corp. dmi.bios.version: SOX5810J.86A.5600.2013.0729.2250 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DX58SO dmi.board.vendor: Intel Corporation dmi.board.version: AAE29331-701 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrSOX5810J.86A.5600.2013.0729.2250:bd07/29/2013:svn:pn:pvr:rvnIntelCorporation:rnDX58SO:rvrAAE29331-701:cvn:ct2:cvr: --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2413 F pulseaudio /dev/snd/controlC0: robert 2413 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=291e75f9-3814-499b-bbb2-f385c164b942 InstallationDate: Installed on 2016-08-18 (83 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-42-generic root=UUID=24166ab8-327a-4477-96d2-3f57b4a47657 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 RfKill: Tags: xenial Uname: Linux 4.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog:
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
@filsd Whoops, sorry. Fixed that. Please share :-) -- 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/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 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.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Since this affects all audio, and not only a specific output, I think this bug should have a higher importance. ** Changed in: linux (Ubuntu) Importance: Medium => High ** Changed in: alsa-driver (Ubuntu) Importance: Undecided => High -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-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/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10
In my case removing intel-microcode (propietary driver) the ram drops to 900MB (but loses performance and video in hd frezes) ** Attachment added: "Captura de pantalla de 2016-11-11 16-25-05.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+attachment/4776084/+files/Captura%20de%20pantalla%20de%202016-11-11%2016-25-05.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1572801 Title: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: Ubuntu 16.04 64bit ISO number 20160420.1 unity version 7.4.0+16.04.20160415-0ubuntu1 Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10 Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 21 01:44:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] GsettingsChanges: b'org.compiz.core' b'outputs' b"['1920x1080+0+0']" b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 'unityshell']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Apr 21 01:37:17 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+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 1641078] Re: System cannot be booted up when root filesystem is on an LVM on two disks
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Tags added: s390x
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
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/1641078
Title:
System cannot be booted up when root filesystem is on an LVM on two
disks
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
---Problem Description---
LVMed root file system acrossing multiple disks cannot be booted up
---uname output---
Linux ntc170 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 UTC 2016
s390x s390x s390x GNU/Linux
---Patches Installed---
n/a
Machine Type = z13
---System Hang---
cannot boot up the system after shutdown or reboot
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Created root file system on an LVM and the LVM crosses two disks. After shut
down or reboot the system, the system cannot be up.
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
Device driver error code:
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
lvmetad is not active yet, using direct activation during sysinit
Couldn't find device with uuid 7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V.
-Attach sysctl -a output output to the bug.
More detailed installation description:
The installation was on a FCP SCSI SAN volumes each with two active
paths. Multipath was involved. The system IPLed fine up to the point
that we expanded the /root filesystem to span volumes. At boot time,
the system was unable to locate the second segment of the /root
filesystem. The error message indicated this was due to lvmetad not
being not active.
Error message:
Begin: Running /scripts/local-block ... lvmetad is not active yet,
using direct activation during sysinit
Couldn't find device with uuid 7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V
Failed to find logical volume "ub01-vg/root"
PV Volume information:
physical_volumes {
pv0 {
id = "L2qixM-SKkF-rQsp-ddao-gagl-LwKV-7Bw1Dz"
device = "/dev/sdb5"# Hint only
status = ["ALLOCATABLE"]
flags = []
dev_size = 208713728# 99.5225 Gigabytes
pe_start = 2048
pe_count = 25477# 99.5195 Gigabytes
}
pv1 {
id = "7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V"
device = "/dev/sda"# Hint only
status = ["ALLOCATABLE"]
flags = []
dev_size = 209715200# 100 Gigabytes
pe_start = 2048
pe_count = 25599# 99.9961 Gigabytes
LV Volume Information:
logical_volumes {
root {
id = "qWuZeJ-Libv-DrEs-9b1a-p0QF-2Fj0-qgGsL8"
status = ["READ", "WRITE", "VISIBLE"]
flags = []
creation_host = "ub01"
creation_time = 1477515033# 2016-10-26
16:50:33 -0400
segment_count = 2
segment1 {
start_extent = 0
extent_count = 921# 3.59766 Gigabytes
type = "striped"
stripe_count = 1# linear
stripes = [
"pv0", 0
]
}
segment2 {
start_extent = 921
extent_count = 25344# 99 Gigabytes
type = "striped"
stripe_count = 1# linear
stripes = [
"pv1", 0
]
}
}
Additional testing has been done with CKD volumes and we see the same
behavior. Only the UUID of the fist volume in the VG can be located at boot,
and the same message: lvmetad is not active yet, using direct activation
during sysinit
Couldn't find device with uuid x is displayed for CKD disks.
Just a different UUID is listed.
If the file /root file system only has one segment on the first
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
@penalvch: I can confirm the problem still exists on 4.9.0-040900rc4-generic I also can confirm that taking the bottom of the laptop off and blowing cool air in there shuts off the fans. Monitoring CPU temp while doing this, it's around 25c - but it seems to vary, sometimes 26c, sometimes 24c. It's strange. Once I stop blowing cool air into it, the fans eventually start again. However, under Windows using HWInfo, another temp sensor shows up - PCH (platform controller hub). Under Windows this usually seems to run warmer than the CPU. Under Linux, I've never found a way to report the temp for the PCH. I wonder if this could actually be heating up under Linux (due to poor power management) thereby causing the BIOS to run the fans. Just something I noticed so thought i'd throw it out 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/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 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.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+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 1641197] 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/1641197 Title: package linux-headers-4.8.0-27 (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-4.8.0-27/arch/frv/include/uapi/asm/sigcontext.h.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.8.0-26.28-generic 4.8.0 sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) Subsystem: Gigabyte Technology Co., Ltd 82G33/G31/P35/P31 Express DRAM Controller [1458:5000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Gigabyte Technology Co., Ltd 82G33/G31/P35/P31 Express PCI Express Root Port [1458:5000] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0f00c Data: 41d1 Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Exit Latency L0s <256ns, L1 <64us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #32, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Off, PwrInd On, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [140 v1] Root Complex Link Desc: PortNumber=02 ComponentID=01 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: fed19000 Kernel driver in use: pcieport Kernel modules: shpchp 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI]) Subsystem: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB UHCI Controller [1458:5004] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes,
[Kernel-packages] [Bug 1641197] [NEW] package linux-headers-4.8.0-27 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.8.0-27/arch/frv/include/uapi/asm/sigcontext.h.d
Public bug reported: Ubuntu 4.8.0-26.28-generic 4.8.0 sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) Subsystem: Gigabyte Technology Co., Ltd 82G33/G31/P35/P31 Express DRAM Controller [1458:5000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Gigabyte Technology Co., Ltd 82G33/G31/P35/P31 Express PCI Express Root Port [1458:5000] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0f00c Data: 41d1 Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Exit Latency L0s <256ns, L1 <64us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #32, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Off, PwrInd On, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [140 v1] Root Complex Link Desc: PortNumber=02 ComponentID=01 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: fed19000 Kernel driver in use: pcieport Kernel modules: shpchp 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI]) Subsystem: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB UHCI Controller [1458:5004] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp-
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
Same problem with a fresh install of Lubuntu 16.10. No problem at all with Lubuntu 16.04. I've tried a live Kubuntu 16.10: same problem. It seems to be a bug related to kernel 4.8, since live Fedora 24 (kernel 4.7) is fine but live beta Fedora 25 (kernel 4.8) doesn't shut down. It seems that the computer (Dell Optiplex 9010 with SSD) is trying to access the disk after the line "Reached target shutdown", since it gives some errors like "ata1.00: exception Emask...", "ata1.00: failed command..." and the like. After a while, it prints "ata1: reset failed, giving up" and finally a "reboot: Power down" and then turn the power off (5 to 10 minutes after having printed the line "Reached target shutdown"). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641168] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1641168 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/1641168 Title: packaging error in yakkety kernel source causing failure to build Status in linux package in Ubuntu: Incomplete Bug description: When I try to build the kernel source from yakkety-updates locally, I get failure like: cc1: fatal error: /home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641168/+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 1641168] Re: packaging error in yakkety kernel source causing failure to build
** Tags added: bot-stop-nagging ** 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/1641168 Title: packaging error in yakkety kernel source causing failure to build Status in linux package in Ubuntu: Confirmed Bug description: When I try to build the kernel source from yakkety-updates locally, I get failure like: cc1: fatal error: /home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641168/+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 1641168] [NEW] packaging error in yakkety kernel source causing failure to build
Public bug reported: When I try to build the kernel source from yakkety-updates locally, I get failure like: cc1: fatal error: /home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h: No such file or directory ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Tim Gardner (timg-tpi) 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/1641168 Title: packaging error in yakkety kernel source causing failure to build Status in linux package in Ubuntu: New Bug description: When I try to build the kernel source from yakkety-updates locally, I get failure like: cc1: fatal error: /home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641168/+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 1639961] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1636330 *** https://bugs.launchpad.net/bugs/1636330 --- Comment From brsri...@in.ibm.com 2016-11-11 11:23 EDT--- *** This bug has been marked as a duplicate of bug 132390 *** -- 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/1639961 Title: NMI watchdog: BUG: soft lockup during KVM guest migration test suite Status in linux package in Ubuntu: New Bug description: Hello Canonical. We would like the changes in Commit 8117ac6a6c2f pulled into the Ubuntu 16.10 stream to address the following issue: == Comment: #0 - Balamuruhan S - 2016-09-23 08:48:52 == ---Problem Description--- Softlock up and call trace observed from libvirtd during guest migration test suite ---uname output--- # uname -a Linux ltc-hab1 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [libvirtd:50800] message is continuous and recovered the machine with reboot 84050.059159] INFO: rcu_sched self-detected stall on CPU [84050.059339]24-...: (5659 ticks this GP) idle=fa5/141/0 softirq=549845/07 fqs=2176 [84050.059453] (t=5250 jiffies g=690268 c=690267 q=484) [84055.126993] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [libvirtd:50800] [84104.509395] INFO: rcu_sched self-detected stall on CPU [84104.509591]24-...: (5659 ticks this GP) idle=5df/141/0 softirq=562249/562249 fqs=2364 [84104.509820] (t=5250 jiffies g=690387 c=690386 q=351) [84107.125310] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [virsh:56627] [84163.387536] INFO: rcu_sched self-detected stall on CPU [84163.387716]24-...: (5250 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=2354 [84163.387960] (t=5251 jiffies g=690488 c=690487 q=297) [84167.123420] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [virsh:56633] [84226.401597] INFO: rcu_sched self-detected stall on CPU [84226.401769]24-...: (21004 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=9697 [84226.402012] (t=21005 jiffies g=690488 c=690487 q=1145) [84289.415706] INFO: rcu_sched self-detected stall on CPU [84289.415879]24-...: (36758 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=16889 [84289.416137] (t=36759 jiffies g=690488 c=690487 q=15499) [84352.429857] INFO: rcu_sched self-detected stall on CPU [84352.430038]24-...: (52512 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=23975 [84352.430269] (t=52513 jiffies g=690488 c=690487 q=16027) [84415.444044] INFO: rcu_sched self-detected stall on CPU [84415.444222]24-...: (68266 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=31005 [84415.34] (t=68267 jiffies g=690488 c=690487 q=16554) [84478.458262] INFO: rcu_sched self-detected stall on CPU [84478.458421]24-...: (84020 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=38023 [84478.458677] (t=84021 jiffies g=690488 c=690487 q=17030) [84541.472510] INFO: rcu_sched self-detected stall on CPU [84541.472680]24-...: (99774 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=45068 [84541.472939] (t=99775 jiffies g=690488 c=690487 q=17512) [84604.486783] INFO: rcu_sched self-detected stall on CPU Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639961/+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 1636330] Comment bridged from LTC Bugzilla
--- Comment From brsri...@in.ibm.com 2016-11-11 11:23 EDT--- *** Bug 146681 has been marked as a duplicate of this 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/1636330 Title: guest experiencing Transmit Timeouts on CX4 Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: This patch fixes a race condition that was reintroduced in the 4.8 kernel, as part of the P9 changes, after having been originally fixed in 3.19. The effect of the race condition is that a secondary thread can start trying to execute code from the guest while the thread is still in hypervisor mode, so it can cause many different symptoms, one of which seems to be the timebase corruption that leads to the lockup in ktime_get_ts64. It could cause other problems such as CPU cores locking up hard or memory corruption. This patch is only needed on the host. It should be applied to any 4.8 kernel being used as a host, including the Ubuntu 16.10 kernel. Hi Paul I built a kernel with your patch and put at the host and in the guest. I can still see some ktime_get_ts64 at the host. The guest dmesg is clean. This patch fixes another race condition I found in the fastsleep code. Please apply this patch as well and test. Sure will do and provide feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636330/+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 1641152] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1641152 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/1641152 Title: Text in the Unity windows disappears/mixed after the resume Status in linux package in Ubuntu: Incomplete Bug description: Text in Unity windows becomes total mess after suspending and waking up Ubuntu 16.04. I had this issue a few times, but it is not always reproducable. The screenshot is attached, where there is disappeared or mixed text on buttons and window panels (though the copy-paste from such broken terminal works fine). $ uname -a Linux A2XLab 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Note, that there is enoguht RAM and no any external monitors are plugged. KiB Mem : 7830196 total, 278792 free, 5922752 used, 1628652 buff/cache KiB Swap: 11999228 total, 8749084 free, 3250144 used. 755228 avail Mem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641152/+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 1641139] Re: Infiniband driver (kernel module) needed for Azure
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641139 Title: Infiniband driver (kernel module) needed for Azure Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: The Infiniband driver (kernel module) needed for Azure A8/A9, H-series, and NC24/NV24 instances is different than the typical upstream Infiniband driver. Also, the WALA agent must be customized to ensure that the host driver for IB and the guest driver for IB match. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641139/+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 1641152] [NEW] Text in the Unity windows disappears/mixed after the resume
Public bug reported: Text in Unity windows becomes total mess after suspending and waking up Ubuntu 16.04. I had this issue a few times, but it is not always reproducable. The screenshot is attached, where there is disappeared or mixed text on buttons and window panels (though the copy-paste from such broken terminal works fine). $ uname -a Linux A2XLab 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Note, that there is enoguht RAM and no any external monitors are plugged. KiB Mem : 7830196 total, 278792 free, 5922752 used, 1628652 buff/cache KiB Swap: 11999228 total, 8749084 free, 3250144 used. 755228 avail Mem ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: brokentext brokenwindows ubuntu16 unity ** Attachment added: "BrokenWindows.png" https://bugs.launchpad.net/bugs/1641152/+attachment/4775976/+files/BrokenWindows.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641152 Title: Text in the Unity windows disappears/mixed after the resume Status in linux package in Ubuntu: New Bug description: Text in Unity windows becomes total mess after suspending and waking up Ubuntu 16.04. I had this issue a few times, but it is not always reproducable. The screenshot is attached, where there is disappeared or mixed text on buttons and window panels (though the copy-paste from such broken terminal works fine). $ uname -a Linux A2XLab 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Note, that there is enoguht RAM and no any external monitors are plugged. KiB Mem : 7830196 total, 278792 free, 5922752 used, 1628652 buff/cache KiB Swap: 11999228 total, 8749084 free, 3250144 used. 755228 avail Mem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641152/+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 1641141] 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/1641141 Title: package linux-image-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in linux package in Ubuntu: Confirmed Bug description: dpkg has problem. tip me reinstall before any sysem modification. How do it ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: linux-image-4.4.0-47-generic: Configure NULL: ConfigurePending Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cleberson 1388 F pulseaudio Date: Fri Nov 11 13:29:45 2016 DpkgTerminalLog: dpkg: erro ao processar o pacote linux-image-4.4.0-47-generic (--configure): O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. HibernationDevice: RESUME=UUID=d3bf9b79-ac3a-4ee9-96ca-b5ec8f79d1f3 InstallationDate: Installed on 2016-11-04 (6 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) IwConfig: lono wireless extensions. enp0s6no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 1a2c:0c21 China Resource Semico Co., Ltd Bus 002 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=588ca326-da4b-4af0-880b-8cec8256a09d ro locale=pt_BR quiet splash 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 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd05/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-X:rvrRevx.xx: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/1641141/+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 1641129] Re: aio completions are dropped
https://lists.ubuntu.com/archives/kernel-team/2016-November/080877.html ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641129 Title: aio completions are dropped Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: In Progress Bug description: In 3.13.0-100-generic (14.04 stable kernel), we are hitting an old AIO bug, described in this thread http://www.gossamer-threads.com/lists/linux/kernel/1993181 reproduced by this http://www.kvack.org/~bcrl/20140824-aio_bug.c The bug was introduced by f8567a3845ac05bb28f3c1b478ef752762bd39ef and I believe it was fixed by d856f32a86b2b015ab180ab7a55e455ed8d3ccc5 I'm not certain if there were follow-on fixes after that. The bug is affecting Ceph OSD daemons, which hit this pretty reliably when using the new BlueStore backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641129/+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 1641129] Re: aio completions are dropped
** 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/1641129 Title: aio completions are dropped Status in linux package in Ubuntu: Confirmed Bug description: In 3.13.0-100-generic (14.04 stable kernel), we are hitting an old AIO bug, described in this thread http://www.gossamer-threads.com/lists/linux/kernel/1993181 reproduced by this http://www.kvack.org/~bcrl/20140824-aio_bug.c The bug was introduced by f8567a3845ac05bb28f3c1b478ef752762bd39ef and I believe it was fixed by d856f32a86b2b015ab180ab7a55e455ed8d3ccc5 I'm not certain if there were follow-on fixes after that. The bug is affecting Ceph OSD daemons, which hit this pretty reliably when using the new BlueStore backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641129/+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 1641141] [NEW] package linux-image-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar con
Public bug reported: dpkg has problem. tip me reinstall before any sysem modification. How do it ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: linux-image-4.4.0-47-generic: Configure NULL: ConfigurePending Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cleberson 1388 F pulseaudio Date: Fri Nov 11 13:29:45 2016 DpkgTerminalLog: dpkg: erro ao processar o pacote linux-image-4.4.0-47-generic (--configure): O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. HibernationDevice: RESUME=UUID=d3bf9b79-ac3a-4ee9-96ca-b5ec8f79d1f3 InstallationDate: Installed on 2016-11-04 (6 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) IwConfig: lono wireless extensions. enp0s6no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 1a2c:0c21 China Resource Semico Co., Ltd Bus 002 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=588ca326-da4b-4af0-880b-8cec8256a09d ro locale=pt_BR quiet splash 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 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd05/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-X:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 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/1641141 Title: package linux-image-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in linux package in Ubuntu: New Bug description: dpkg has problem. tip me reinstall before any sysem modification. How do it ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: linux-image-4.4.0-47-generic: Configure NULL: ConfigurePending Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cleberson 1388 F pulseaudio Date: Fri Nov 11 13:29:45 2016 DpkgTerminalLog: dpkg: erro ao processar o pacote linux-image-4.4.0-47-generic (--configure): O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. HibernationDevice: RESUME=UUID=d3bf9b79-ac3a-4ee9-96ca-b5ec8f79d1f3 InstallationDate: Installed on 2016-11-04 (6 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) IwConfig: lono wireless extensions. enp0s6no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 1a2c:0c21 China Resource Semico Co., Ltd Bus 002 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic
[Kernel-packages] [Bug 1641129] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1641129 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/1641129 Title: aio completions are dropped Status in linux package in Ubuntu: Incomplete Bug description: In 3.13.0-100-generic (14.04 stable kernel), we are hitting an old AIO bug, described in this thread http://www.gossamer-threads.com/lists/linux/kernel/1993181 reproduced by this http://www.kvack.org/~bcrl/20140824-aio_bug.c The bug was introduced by f8567a3845ac05bb28f3c1b478ef752762bd39ef and I believe it was fixed by d856f32a86b2b015ab180ab7a55e455ed8d3ccc5 I'm not certain if there were follow-on fixes after that. The bug is affecting Ceph OSD daemons, which hit this pretty reliably when using the new BlueStore backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641129/+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 1641139] Re: Infiniband driver (kernel module) needed for Azure
https://lists.ubuntu.com/archives/kernel-team/2016-November/080872.html -- 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/1641139 Title: Infiniband driver (kernel module) needed for Azure Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: The Infiniband driver (kernel module) needed for Azure A8/A9, H-series, and NC24/NV24 instances is different than the typical upstream Infiniband driver. Also, the WALA agent must be customized to ensure that the host driver for IB and the guest driver for IB match. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641139/+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 1641129] Re: aio completions are dropped
** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1641129 Title: aio completions are dropped Status in linux package in Ubuntu: Incomplete Bug description: In 3.13.0-100-generic (14.04 stable kernel), we are hitting an old AIO bug, described in this thread http://www.gossamer-threads.com/lists/linux/kernel/1993181 reproduced by this http://www.kvack.org/~bcrl/20140824-aio_bug.c The bug was introduced by f8567a3845ac05bb28f3c1b478ef752762bd39ef and I believe it was fixed by d856f32a86b2b015ab180ab7a55e455ed8d3ccc5 I'm not certain if there were follow-on fixes after that. The bug is affecting Ceph OSD daemons, which hit this pretty reliably when using the new BlueStore backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641129/+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 1641139] [NEW] Infiniband driver (kernel module) needed for Azure
Public bug reported: The Infiniband driver (kernel module) needed for Azure A8/A9, H-series, and NC24/NV24 instances is different than the typical upstream Infiniband driver. Also, the WALA agent must be customized to ensure that the host driver for IB and the guest driver for IB match. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) 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/1641139 Title: Infiniband driver (kernel module) needed for Azure Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: The Infiniband driver (kernel module) needed for Azure A8/A9, H-series, and NC24/NV24 instances is different than the typical upstream Infiniband driver. Also, the WALA agent must be customized to ensure that the host driver for IB and the guest driver for IB match. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641139/+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 1641127] Re: Network interface is not coming up
Added apport logs ** Attachment added: "apport.linux-image-4.4.0-45-generic.pdmij_pa.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641127/+attachment/4775956/+files/apport.linux-image-4.4.0-45-generic.pdmij_pa.apport ** 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/1641127 Title: Network interface is not coming up Status in linux package in Ubuntu: Confirmed Bug description: Fresh installation of Ubuntu 16.04 and even after executing ifconfig up, the network interface is not coming up. Below are the kernel and driver details: lsb_release -rd Description:Ubuntu 16.04 Release:16.04 cat /proc/version_signature Ubuntu 4.4.0-47.68-generic 4.4.24 sudo lspci -vnvn > lspci-vnvn.log Attached the .log file Basically bnxt_en driver needs to be updated with latest HWRM spec. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641127/+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 1641129] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1641129 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 ** 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/1641129 Title: aio completions are dropped Status in linux package in Ubuntu: Incomplete Bug description: In 3.13.0-100-generic (14.04 stable kernel), we are hitting an old AIO bug, described in this thread http://www.gossamer-threads.com/lists/linux/kernel/1993181 reproduced by this http://www.kvack.org/~bcrl/20140824-aio_bug.c The bug was introduced by f8567a3845ac05bb28f3c1b478ef752762bd39ef and I believe it was fixed by d856f32a86b2b015ab180ab7a55e455ed8d3ccc5 I'm not certain if there were follow-on fixes after that. The bug is affecting Ceph OSD daemons, which hit this pretty reliably when using the new BlueStore backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641129/+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 1641127] [NEW] Network interface is not coming up
Public bug reported: Fresh installation of Ubuntu 16.04 and even after executing ifconfig up, the network interface is not coming up. Below are the kernel and driver details: lsb_release -rd Description:Ubuntu 16.04 Release:16.04 cat /proc/version_signature Ubuntu 4.4.0-47.68-generic 4.4.24 sudo lspci -vnvn > lspci-vnvn.log Attached the .log file Basically bnxt_en driver needs to be updated with latest HWRM spec. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1641127/+attachment/4775942/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641127 Title: Network interface is not coming up Status in linux package in Ubuntu: Incomplete Bug description: Fresh installation of Ubuntu 16.04 and even after executing ifconfig up, the network interface is not coming up. Below are the kernel and driver details: lsb_release -rd Description:Ubuntu 16.04 Release:16.04 cat /proc/version_signature Ubuntu 4.4.0-47.68-generic 4.4.24 sudo lspci -vnvn > lspci-vnvn.log Attached the .log file Basically bnxt_en driver needs to be updated with latest HWRM spec. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641127/+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 1641129] [NEW] aio completions are dropped
Public bug reported: In 3.13.0-100-generic (14.04 stable kernel), we are hitting an old AIO bug, described in this thread http://www.gossamer-threads.com/lists/linux/kernel/1993181 reproduced by this http://www.kvack.org/~bcrl/20140824-aio_bug.c The bug was introduced by f8567a3845ac05bb28f3c1b478ef752762bd39ef and I believe it was fixed by d856f32a86b2b015ab180ab7a55e455ed8d3ccc5 I'm not certain if there were follow-on fixes after that. The bug is affecting Ceph OSD daemons, which hit this pretty reliably when using the new BlueStore backend. ** 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/1641129 Title: aio completions are dropped Status in linux package in Ubuntu: New Bug description: In 3.13.0-100-generic (14.04 stable kernel), we are hitting an old AIO bug, described in this thread http://www.gossamer-threads.com/lists/linux/kernel/1993181 reproduced by this http://www.kvack.org/~bcrl/20140824-aio_bug.c The bug was introduced by f8567a3845ac05bb28f3c1b478ef752762bd39ef and I believe it was fixed by d856f32a86b2b015ab180ab7a55e455ed8d3ccc5 I'm not certain if there were follow-on fixes after that. The bug is affecting Ceph OSD daemons, which hit this pretty reliably when using the new BlueStore backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641129/+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 1641127] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1641127 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/1641127 Title: Network interface is not coming up Status in linux package in Ubuntu: Incomplete Bug description: Fresh installation of Ubuntu 16.04 and even after executing ifconfig up, the network interface is not coming up. Below are the kernel and driver details: lsb_release -rd Description:Ubuntu 16.04 Release:16.04 cat /proc/version_signature Ubuntu 4.4.0-47.68-generic 4.4.24 sudo lspci -vnvn > lspci-vnvn.log Attached the .log file Basically bnxt_en driver needs to be updated with latest HWRM spec. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641127/+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 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
Ok guys, I'm gonna send it. I ask you guys to not make it public. I'm only giving this to help find the bug that plagues this awesome laptop. Thanks. :] PS: @gnidorah I didnt sent you the download. I dont have access to your email. -- 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/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 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.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+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 1638526] Re: Unable to install AMD Radeon HD 6950 driver
Sorry for pasting incomplete logs, didn't realize they got truncated. Get:3 file:/var/opt/amdgpu-pro-local ./ libdrm-amdgpu-pro-amdgpu1 1:2.4.66-348864 [20.0 kB] Get:4 file:/var/opt/amdgpu-pro-local ./ libdrm-amdgpu-pro-utils 1:2.4.66-348864 [57.3 kB] Get:5 file:/var/opt/amdgpu-pro-local ./ libgbm1-amdgpu-pro-base 16.40-348864 [3,068 B] Get:6 file:/var/opt/amdgpu-pro-local ./ libgbm1-amdgpu-pro 16.40-348864 [73.5 kB] Get:7 file:/var/opt/amdgpu-pro-local ./ libgl1-amdgpu-pro-appprofiles 16.40-348864 [15.1 kB] Get:8 file:/var/opt/amdgpu-pro-local ./ libgl1-amdgpu-pro-glx 16.40-348864 [125 kB] Get:9 file:/var/opt/amdgpu-pro-local ./ libgl1-amdgpu-pro-ext 16.40-348864 [68.2 kB] Get:10 file:/var/opt/amdgpu-pro-local ./ libgl1-amdgpu-pro-dri 16.40-348864 [8,424 kB] Get:11 file:/var/opt/amdgpu-pro-local ./ libegl1-amdgpu-pro 16.40-348864 [4,932 B] Get:12 file:/var/opt/amdgpu-pro-local ./ libgles2-amdgpu-pro 16.40-348864 [15.0 kB] Get:13 file:/var/opt/amdgpu-pro-local ./ vulkan-amdgpu-pro 16.40-348864 [2,489 kB] Get:14 file:/var/opt/amdgpu-pro-local ./ libvdpau-amdgpu-pro 1:11.2.2-348864 [11.0 MB] Get:15 file:/var/opt/amdgpu-pro-local ./ libopencl1-amdgpu-pro 16.40-348864 [8,992 B] Get:16 file:/var/opt/amdgpu-pro-local ./ clinfo-amdgpu-pro 16.40-348864 [148 kB] Get:17 file:/var/opt/amdgpu-pro-local ./ opencl-amdgpu-pro-icd 16.40-348864 [23.9 MB] Get:18 file:/var/opt/amdgpu-pro-local ./ xserver-xorg-video-glamoregl-amdgpu-pro 1.18.3-348864 [84.0 kB] Get:19 file:/var/opt/amdgpu-pro-local ./ xserver-xorg-video-amdgpu-pro 1:1.1.99-348864 [51.8 kB] Get:20 file:/var/opt/amdgpu-pro-local ./ amdgpu-pro 16.40-348864 [1,308 B] Get:21 file:/var/opt/amdgpu-pro-local ./ libdrm2-amdgpu-pro 1:2.4.66-348864 [31.9 kB] Get:22 file:/var/opt/amdgpu-pro-local ./ libdrm-amdgpu-pro-amdgpu1 1:2.4.66-348864 [24.6 kB] Get:23 file:/var/opt/amdgpu-pro-local ./ libgbm1-amdgpu-pro 16.40-348864 [81.0 kB] Get:24 file:/var/opt/amdgpu-pro-local ./ libgl1-amdgpu-pro-glx 16.40-348864 [116 kB] Get:25 file:/var/opt/amdgpu-pro-local ./ libgl1-amdgpu-pro-dri 16.40-348864 [8,073 kB] Get:26 file:/var/opt/amdgpu-pro-local ./ libegl1-amdgpu-pro 16.40-348864 [4,344 B] Get:27 file:/var/opt/amdgpu-pro-local ./ libgles2-amdgpu-pro 16.40-348864 [10.2 kB] Get:28 file:/var/opt/amdgpu-pro-local ./ vulkan-amdgpu-pro 16.40-348864 [2,439 kB] Get:29 file:/var/opt/amdgpu-pro-local ./ libvdpau-amdgpu-pro 1:11.2.2-348864 [12.3 MB] Get:30 file:/var/opt/amdgpu-pro-local ./ libopencl1-amdgpu-pro 16.40-348864 [9,772 B] Get:31 file:/var/opt/amdgpu-pro-local ./ opencl-amdgpu-pro-icd 16.40-348864 [24.4 MB] Get:32 file:/var/opt/amdgpu-pro-local ./ amdgpu-pro-lib32 16.40-348864 [1,282 B] Extracting templates from packages: 100% Selecting previously unselected package amdgpu-pro-dkms. (Reading database ... 204420 files and directories currently installed.) Preparing to unpack .../00-amdgpu-pro-dkms_16.40-348864_all.deb ... Unpacking amdgpu-pro-dkms (16.40-348864) ... Selecting previously unselected package libdrm2-amdgpu-pro:amd64. Preparing to unpack .../01-libdrm2-amdgpu-pro_2.4.66-348864_amd64.deb ... Unpacking libdrm2-amdgpu-pro:amd64 (1:2.4.66-348864) ... Selecting previously unselected package libdrm-amdgpu-pro-amdgpu1:amd64. Preparing to unpack .../02-libdrm-amdgpu-pro-amdgpu1_2.4.66-348864_amd64.deb ... Unpacking libdrm-amdgpu-pro-amdgpu1:amd64 (1:2.4.66-348864) ... Selecting previously unselected package libdrm-amdgpu-pro-utils. Preparing to unpack .../03-libdrm-amdgpu-pro-utils_2.4.66-348864_amd64.deb ... Unpacking libdrm-amdgpu-pro-utils (1:2.4.66-348864) ... Selecting previously unselected package libgbm1-amdgpu-pro-base. Preparing to unpack .../04-libgbm1-amdgpu-pro-base_16.40-348864_all.deb ... Unpacking libgbm1-amdgpu-pro-base (16.40-348864) ... Selecting previously unselected package libgbm1-amdgpu-pro:amd64. Preparing to unpack .../05-libgbm1-amdgpu-pro_16.40-348864_amd64.deb ... Unpacking libgbm1-amdgpu-pro:amd64 (16.40-348864) ... Selecting previously unselected package libgl1-amdgpu-pro-appprofiles. Preparing to unpack .../06-libgl1-amdgpu-pro-appprofiles_16.40-348864_all.deb ... Unpacking libgl1-amdgpu-pro-appprofiles (16.40-348864) ... Selecting previously unselected package libgl1-amdgpu-pro-glx:amd64. Preparing to unpack .../07-libgl1-amdgpu-pro-glx_16.40-348864_amd64.deb ... Unpacking libgl1-amdgpu-pro-glx:amd64 (16.40-348864) ... Selecting previously unselected package libgl1-amdgpu-pro-ext:amd64. Preparing to unpack .../08-libgl1-amdgpu-pro-ext_16.40-348864_amd64.deb ... Unpacking libgl1-amdgpu-pro-ext:amd64 (16.40-348864) ... Selecting previously unselected package libgl1-amdgpu-pro-dri:amd64. Preparing to unpack .../09-libgl1-amdgpu-pro-dri_16.40-348864_amd64.deb ... Unpacking libgl1-amdgpu-pro-dri:amd64 (16.40-348864) ... Selecting previously unselected package libegl1-amdgpu-pro:amd64. Preparing to unpack .../10-libegl1-amdgpu-pro_16.40-348864_amd64.deb ... Unpacking libegl1-amdgpu-pro:amd64 (16.40-348864) ... Selecting
[Kernel-packages] [Bug 1641078] Re: System cannot be booted up when root filesystem is on an LVM on two disks
--- Comment From ma...@de.ibm.com 2016-11-11 08:24 EDT---
(In reply to comment #2)
> (In reply to comment #1)
> The installation was on a FCP SCSI SAN volumes each with two active paths.
> Multipath was involved. The system IPLed fine up to the point that we
> expanded the /root filesystem to span volumes. At boot time, the system
> was unable to locate the second segment of the /root filesystem. The error
> message indicated this was due to lvmetad not being not active.
For the zfcp case, did you use the chzdev tool to activate the paths of your
new additional LVM physical volume (PV)?
This is the only supported post-install method to (dynamically and)
persistently activate zfcp-attached FCP LUNs. See also
http://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ludd/ludd_t_fcp_wrk_addu.html.
> PV Volume information:
> physical_volumes {
>
>pv0 {
>device = "/dev/sdb5"# Hint only
>pv1 {
>device = "/dev/sda"# Hint only
This does not look very good, having single path scsi disk devices
mentioned by LVM. With zfcp-attached SCSI disks, LVM must be on top of
multipathing. Could you please double check if your installation with
LVM and multipathing does the correct layering? If not, this would be an
independent bug. See also [1, slide 28 "Multipathing for Disks ? LVM on
Top"].
> Additional testing has been done with CKD volumes and we see the same
> behavior.
> Because of this behavior, I do not
> believe the problem is related to SAN disk or multipath. I think it is due
> to the system not being able to read the UUID on any PV in the VG other then
> the IPL disk.
For any disk device type, the initrd must contain all information how to
enable/activate all paths of the entire block device dependency tree required
to mount the root file system. An example for a dependency tree is in [1, slide
37] and such example is independent of any particular Linux distribution.
I don't know how much automatic dependency tracking Ubuntu does for the user,
especially regarding additional z-specific device activation steps ("setting
online" as for DASD or zFCP). Potentially the user must take care of the
dependency tree himself and ensure the necessary information lands in the
initrd.
Once the dependency tree of the root-fs has changed (such as adding a PV to an
LVM containing the root-fs as in your case), you must re-create the initrd with
the following command before any reboot:
$ update-initramfs -u
On z Systems, this also contains the necessary step to re-write the boot record
(using the zipl bootloader management tool) so it correctly points to the new
initrd.
See also
http://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ludd/ludd_t_fcp_wrk_on.html.
In your case on reboot, it only activated 2 paths to FCP LUN 0x4000400e
(I cannot determine the target port WWPN(s) from below output because it does
not convey this info) from two different FCP devices 0.0.e300 and 0.0.e100.
>From attachment 113696:
[6.666977] scsi host0: zfcp
[6.671670] random: nonblocking pool is initialized
[6.672622] qdio: 0.0.e300 ZFCP on SC 2cc5 using AI:1 QEBSM:0 PRI:1 TDD:1
SIGA: W AP
[6.722312] scsi host1: zfcp
[6.724547] scsi 0:0:0:1074675712: Direct-Access IBM 2107900
1.69 PQ: 0 ANSI: 5
[6.725159] sd 0:0:0:1074675712: alua: supports implicit TPGS
[6.725164] sd 0:0:0:1074675712: alua: device
naa.6005076306ffd70e port group 0 rel port 303
[6.725287] sd 0:0:0:1074675712: Attached scsi generic sg0 type 0
[6.728234] qdio: 0.0.e100 ZFCP on SC 2c85 using AI:1 QEBSM:0 PRI:1 TDD:1
SIGA: W AP
[6.747662] sd 0:0:0:1074675712: alua: transition timeout set to 60 seconds
[6.747667] sd 0:0:0:1074675712: alua: port group 00 state A preferred
supports tolusnA
[6.747801] sd 0:0:0:1074675712: [sda] 209715200 512-byte logical blocks:
(107 GB/100 GiB)
[6.748652] sd 0:0:0:1074675712: [sda] Write Protect is off
[6.749024] sd 0:0:0:1074675712: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[6.752076] sda: sda1 sda2 < sda5 >
[6.754107] sd 0:0:0:1074675712: [sda] Attached SCSI disk
[6.760935] scsi 1:0:0:1074675712: Direct-Access IBM 2107900
1.69 PQ: 0 ANSI: 5
[6.761444] sd 1:0:0:1074675712: alua: supports implicit TPGS
[6.761448] sd 1:0:0:1074675712: alua: device
naa.6005076306ffd70e port group 0 rel port 231
[6.761514] sd 1:0:0:1074675712: Attached scsi generic sg1 type 0
[6.787710] sd 1:0:0:1074675712: [sdb] 209715200 512-byte logical blocks:
(107 GB/100 GiB)
[6.787770] sd 1:0:0:1074675712: alua: port group 00 state A preferred
supports tolusnA
[6.788464] sd 1:0:0:1074675712: [sdb] Write Protect is off[6.788728] sd
1:0:0:1074675712: [sdb] Write cache: enabled, read cache: enabled, doesn't
support DPO
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth
I cannot imagine that the car manufactors have to maintain databases of their cars. There are so many mobile phones coming and leaving the market. A car manufactor cannot know and maintain them all. My car from 2011 worked fine with a new Windows Phone from 2014. I have never heard of a phone database update for my or other cars. Here it is more a question of ensuring the bluetouth standard behaviour of our Ubuntu Phones. -- 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 1535802] Re: Bluetooth 04ca:3011 [Asus Aspire V3-371] doesn't work
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Yakkety)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1535802
Title:
Bluetooth 04ca:3011 [Asus Aspire V3-371] doesn't work
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Yakkety:
Fix Committed
Bug description:
USB device 04ca:3011 is a combo Atheros device's bluetooth adapter.
In back of laptop the adapter's label states as: PPD-QCNFA34AC
WORKAROUND for kernel 4.4:
wget
https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1535802-dkms_0.1_all.deb
sudo dpkg -i btusb-lp1535802-dkms_0.1_all.deb
By default my kernel recognize as generic Bluetooth,
I can switch on/off, make it visible,
BUT actually it cannot see anything and no other devices can see it.
However
It works well (tested) as "QCA ROME chipset" so adding a line:
{ USB_DEVICE(0x04ca, 0x3011), .driver_info = BTUSB_QCA_ROME },
in btusb.c (compile, install as module, and modprobe) made the trick.
lsusb:
Bus 003 Device 004: ID 04ca:3011 Lite-On Technology Corp.
I added the diff file of drivers/bluetooth/btusb.c
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-23-generic 4.2.0-23.28
ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
Uname: Linux 4.2.0-23-generic i686
ApportVersion: 2.19.1-0ubuntu5
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: mark 1476 F pulseaudio
/dev/snd/controlC0: mark 1476 F pulseaudio
CurrentDesktop: Unity
Date: Tue Jan 19 17:03:18 2016
HibernationDevice: RESUME=UUID=66dc8cfd-62d6-411b-9edf-c509aac14318
InstallationDate: Installed on 2015-10-26 (85 days ago)
InstallationMedia: Ubuntu "Wily" - Build i386 LIVE Binary 20151022-23:55
MachineType: Acer Aspire V3-371
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic
root=UUID=403e935b-5da2-4b34-8dd7-14f1c0cf0846 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-4.2.0-23-generic N/A
linux-backports-modules-4.2.0-23-generic N/A
linux-firmware1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.28
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire V3-371
dmi.board.vendor: Acer
dmi.board.version: V1.28
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.28
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.28:bd08/21/2015:svnAcer:pnAspireV3-371:pvrV1.28:rvnAcer:rnAspireV3-371:rvrV1.28:cvnAcer:ct10:cvrV1.28:
dmi.product.name: Aspire V3-371
dmi.product.version: V1.28
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535802/+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 1433906] Re: Acer, Inc ID 5986:055a is useless after 14.04.2 installed.
Hi Joseph The patch has landed in this repository: https://git.linuxtv.org/media_tree.git/log/ While I have no experience with this process, I was speculating that this entire branch will be pulled into mainline when the next merge window opens. But like I said, I don't actually know what to expect next. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1433906 Title: Acer, Inc ID 5986:055a is useless after 14.04.2 installed. Status in HWE Next: Won't Fix Status in linux package in Ubuntu: In Progress Status in linux-lts-vivid package in Ubuntu: Triaged Status in linux-lts-xenial package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux package in Arch Linux: New Status in Fedora: Unknown Bug description: CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic) CID : 201408-15472 Lenovo E555 (A+A) with 14.04.2 (utopic) Steps: 1. Install 14.04.2 on E450 or E555. 2. Log in system and open a terminal. 3. $ gst-launch-0.10 v4l2src ! xvimagesink Expected result: Camara is activated Actual result: $ gst-launch-0.10 v4l2src ! xvimagesink Setting pipeline to PAUSED ... ERROR: Pipeline doesn't want to pause. ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Cannot identify device '/dev/video0'. Additional debug info: v4l2_calls.c(497): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: system error: No such file or directory Setting pipeline to NULL ... Freeing pipeline ... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 02:21:31 2015 InstallationDate: Installed on 2015-03-16 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1433906/+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 1638748] Re: Yakkety update to v4.8.6 stable release
** Changed in: linux (Ubuntu Yakkety) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1638748 Title: Yakkety update to v4.8.6 stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.8.6 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.8.6 stable release shall be applied: drm/vc4: Fix races when the CS reads from render targets. drm/prime: Pass the right module owner through to dma_buf_export() drm/i915/backlight: setup and cache pwm alternate increment value drm/i915/backlight: setup backlight pwm alternate increment on backlight enable drm/amdgpu: fix IB alignment for UVD drm/amdgpu/dce10: disable hpd on local panels drm/amdgpu/dce8: disable hpd on local panels drm/amdgpu/dce11: disable hpd on local panels drm/amdgpu/dce11: add missing drm_mode_config_cleanup call drm/amdgpu: initialize the context reset_counter in amdgpu_ctx_init drm/amdgpu: change vblank_time's calculation method to reduce computational error. drm/radeon: narrow asic_init for virtualization drm/radeon/si/dpm: fix phase shedding setup drm/radeon: change vblank_time's calculation method to reduce computational error. drm/vmwgfx: Limit the user-space command buffer size drm/fsl-dcu: fix endian issue when using clk_register_divider drm/amd/powerplay: fix mclk not switching back after multi-head was disabled HID: add quirk for Akai MIDImix. drm/i915/skl: Update plane watermarks atomically during plane updates drm/i915: Move CRTC updating in atomic_commit into it's own hook drm/i915/skl: Update DDB values atomically with wms/plane attrs drm/i915/skl: Don't try to update plane watermarks if they haven't changed drm/i915/gen9: only add the planes actually affected by ddb changes drm/i915/gen9: fix the WaWmMemoryReadLatency implementation drm/i915/gen9: minimum scanlines for Y tile is not always 4 drm/i915/gen9: fix plane_blocks_per_line on watermarks calculations drm/i915/gen9: fix the watermark res_blocks value drm/i915: SAGV is not SKL-only, so rename a few things drm/i915: introduce intel_has_sagv() drm/i915/kbl: KBL also needs to run the SAGV code Revert "drm/i915: Check live status before reading edid" drm/i915: Account for TSEG size when determining 865G stolen base drm/i915/skl: Ensure pipes with changed wms get added to the state drm/i915: Allow PCH DPLL sharing regardless of DPLL_SDVO_HIGH_SPEED drm/i915: Move long hpd handling into the hotplug work drm/i915: Allow DP to work w/o EDID drm/i915: Just clear the mmiodebug before a register access drm/i915: Unalias obj->phys_handle and obj->userptr posix_acl: Clear SGID bit when setting file permissions rt2x00usb: Fix error return code scsi: cxlflash: Remove the device cleanly in the system shutdown path genirq/generic_chip: Add irq_unmap callback coresight: Remove erroneous dma_free_coherent in tmc_probe uio: fix dmem_region_start computation ARM: clk-imx35: fix name for ckil clk spi: spi-fsl-dspi: Drop extra spi_master_put in device remove function i40e: remove a stray unlock i40e: fix broken i40e_config_rss_aq function mwifiex: correct aid value during tdls setup mwifiex: fix failed to reconnect after interface disabled/enabled ath10k: Add WMI_SERVICE_PERIODIC_CHAN_STAT_SUPPORT wmi service ath10k: fix sending frame in management path in push txq logic ath10k: fix reporting channel survey data ath10k: fix throughput regression in multi client mode crypto: marvell - Don't overwrite default creq->state during initialization crypto: gcm - Fix IV buffer size in crypto_gcm_setkey crypto: marvell - Update transformation context for each dequeued req crypto: arm/ghash-ce - add missing async import/export crypto: ccp - Fix return value check in ccp_dmaengine_register() hwrng: omap - Only fail if pm_runtime_get_sync returns < 0 ASoC: topology: Fix error return code in soc_tplg_dapm_widget_create() ASoC: dapm: Fix possible uninitialized variable in snd_soc_dapm_get_volsw() ASoC: dapm: Fix value setting for _ENUM_DOUBLE MUX's second channel ASoC: dapm: Fix kcontrol creation for output driver widget ASoC: sst-bxt-rt298: fix obsoleted initializers for array ASoC: sst-bxt-da7219_max98357a: fix
[Kernel-packages] [Bug 1633973] Re: Yakkety update to v4.8.2 stable release
** Changed in: linux (Ubuntu Yakkety) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633973 Title: Yakkety update to v4.8.2 stable release Status in linux package in Ubuntu: New Status in linux source package in Yakkety: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.8.2 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.8.2 stable release shall be applied: usb: storage: fix runtime pm issue in usb_stor_probe2 timekeeping: Fix __ktime_get_fast_ns() regression usb: dwc3: fix Clear Stall EP command failure phy: sun4i-usb: Use spinlock to guard phyctl register access ALSA: ali5451: Fix out-of-bound position reporting ALSA: usb-audio: Extend DragonFly dB scale quirk to cover other variants ALSA: usb-line6: use the same declaration as definition in header for MIDI manufacturer ID mfd: rtsx_usb: Avoid setting ucr->current_sg.status mfd: atmel-hlcdc: Do not sleep in atomic context mfd: 88pm80x: Double shifting bug in suspend/resume mfd: wm8350-i2c: Make sure the i2c regmap functions are compiled xen/x86: Update topology map for PV VCPUs KVM: PPC: Book3s PR: Allow access to unprivileged MMCR2 register KVM: MIPS: Drop other CPU ASIDs on guest MMU changes KVM: arm64: Require in-kernel irqchip for PMU support KVM: arm/arm64: vgic: Don't flush/sync without a working vgic KVM: PPC: BookE: Fix a sanity check arm64: fix dump_backtrace/unwind_frame with NULL tsk x86/boot: Fix kdump, cleanup aborted E820_PRAM max_pfn manipulation x86/irq: Prevent force migration of irqs which are not in the vector domain x86/pkeys: Make protection keys an "eager" feature x86/cpu: Rename Merrifield2 to Moorefield x86/platform/intel-mid: Add Intel Penwell to ID table x86/platform/intel-mid: Keep SRAM powered on at boot x86/apic: Get rid of apic_version[] array arch/x86: Handle non enumerated CPU after physical hotplug x86/mm/pkeys: Do not skip PKRU register if debug registers are not used x86/dumpstack: Fix x86_32 kernel_stack_pointer() previous stack access ARM: fix delays ARM: dts: mvebu: armada-390: add missing compatibility string and bracket ARM: dts: MSM8064 remove flags from SPMI/MPP IRQs ARM: dts: MSM8660 remove flags from SPMI/MPP IRQs ARM: cpuidle: Fix error return code Bluetooth: Add a new 04ca:3011 QCA_ROME device ima: use file_dentry() tpm: fix a race condition in tpm2_unseal_trusted() tpm_crb: fix crb_req_canceled behavior Linux 4.8.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633973/+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 1637517] Re: Yakkety update to v4.8.4 stable release
** Changed in: linux (Ubuntu Yakkety) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637517 Title: Yakkety update to v4.8.4 stable release Status in linux package in Ubuntu: New Status in linux source package in Yakkety: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.8.4 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.8.4 stable release shall be applied: serial: imx: Fix DCD reading BUG: atmel_serial: Interrupts not disabled on close serial: 8250_dw: Check the data->pclk when get apb_pclk serial: 8250_port: fix runtime PM use in __do_stop_tx_rs485() ARCv2: intc: Use kflag if STATUS32.IE must be reset ARCv2: fix local_save_flags debugfs: introduce a public file_operations accessor b43: fix debugfs crash b43legacy: fix debugfs crash carl9170: fix debugfs crashes Btrfs: fix free space tree bitmaps on big-endian systems Btrfs: fix mount -o clear_cache,space_cache=v2 Btrfs: catch invalid free space trees btrfs: assign error values to the correct bio structs mei: amthif: fix deadlock in initialization during a reset drivers: base: dma-mapping: page align the size when unmap_kernel_range IB/hfi1: Fix defered ack race with qp destroy clk: mvebu: fix setting unwanted flags in CP110 gate clock clk: mvebu: dynamically allocate resources in Armada CP110 system controller fuse: listxattr: verify xattr list fuse: invalidate dir dentry after chmod fuse: fix killing s[ug]id in setattr mm: filemap: fix mapping->nrpages double accounting in fuse i40e: avoid NULL pointer dereference and recursive errors on early PCI error xfs: change mailing list address mm: filemap: don't plant shadow entries without radix tree node brcmfmac: fix pmksa->bssid usage brcmfmac: fix memory leak in brcmf_fill_bss_param brcmfmac: use correct skb freeing helper when deleting flowring ASoC: nau8825: fix bug in FLL parameter ASoC: Intel: Atom: add a missing star in a memcpy call reiserfs: Unlock superblock before calling reiserfs_quota_on_mount() async_pq_val: fix DMA memory leak scsi: arcmsr: Simplify user_len checking ipc/sem.c: fix complex_count vs. simple op race mm/hugetlb: fix memory offline with hugepage size > memory block size vfs,mm: fix a dead loop in truncate_inode_pages_range() jbd2: fix lockdep annotation in add_transaction_credits() ext4: enforce online defrag restriction for encrypted files ext4: reinforce check of i_dtime when clearing high fields of uid and gid ext4: bugfix for mmaped pages in mpage_release_unused_pages() ext4: fix memory leak in ext4_insert_range() ext4: fix memory leak when symlink decryption fails ext4: allow DAX writeback for hole punch ext4: release bh in make_indexed_dir ext4: unmap metadata when zeroing blocks dlm: free workqueues after the connections vfs: move permission checking into notify_change() for utimes(NULL) cachefiles: Fix attempt to read i_blocks after deleting file [ver #2] drm: virtio: reinstate drm_virtio_set_busid() acpi, nfit: check for the correct event code in notifications cfq: fix starvation of asynchronous writes Linux 4.8.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637517/+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 1637520] Re: Yakkety update to v4.8.5 stable release
** Changed in: linux (Ubuntu Yakkety) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637520 Title: Yakkety update to v4.8.5 stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.8.5 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.8.5 stable release shall be applied: gpio: mpc8xxx: Correct irq handler function mei: fix return value on disconnection mei: me: add kaby point device ids regulator: tps65910: Work around silicon erratum SWCZ010 clk: imx6: initialize GPU clocks clk: imx6: fix i.MX6DL clock tree to reflect reality spi: spidev_test: Fix buffer overflow in unescape() PM / devfreq: event: remove duplicate devfreq_event_get_drvdata() ath10k: fix copy engine 5 destination ring stuck rtlwifi: Fix missing country code for Great Britain mmc: block: don't use CMD23 with very old MMC cards mmc: sdhci: cast unsigned int to unsigned long long to avoid unexpeted error PCI: Mark Atheros AR9580 to avoid bus reset PCI: tegra: Fix argument order in tegra_pcie_phy_disable() platform: don't return 0 from platform_get_irq[_byname]() on error cpufreq: ti: Use generic platdev driver cpufreq: conservative: Fix next frequency selection cpufreq: skip invalid entries when searching the frequency cpufreq: intel_pstate: Fix unsafe HWP MSR access cpufreq: fix overflow in cpufreq_table_find_index_dl() parisc: Increase KERNEL_INITIAL_SIZE for 32-bit SMP kernels parisc: Fix self-detected CPU stall warnings on Mako machines parisc: Fix kernel memory layout regarding position of __gp parisc: Increase initial kernel mapping size pstore/ramoops: fixup driver removal pstore/core: drop cmpxchg based updates pstore/ram: Use memcpy_toio instead of memcpy pstore/ram: Use memcpy_fromio() to save old buffer perf intel-pt: Fix snapshot overlap detection decoder errors perf intel-pt: Fix estimated timestamps for cycle-accurate mode perf intel-pt: Fix MTC timestamp calculation for large MTC periods dm: mark request_queue dead before destroying the DM device dm: return correct error code in dm_resume()'s retry loop dm rq: take request_queue lock while clearing QUEUE_FLAG_STOPPED dm mpath: check if path's request_queue is dying in activate_path() dm crypt: fix crash on exit powerpc/xmon: Don't use ld on 32-bit powerpc/vdso64: Use double word compare on pointers powerpc/powernv: Pass CPU-endian PE number to opal_pci_eeh_freeze_clear() powerpc/eeh: Null check uses of eeh_pe_bus_get powerpc/powernv: Use CPU-endian hub diag-data type in pnv_eeh_get_and_dump_hub_diag() powerpc/powernv: Use CPU-endian PEST in pnv_pci_dump_p7ioc_diag_data() powerpc/mm: Update FORCE_MAX_ZONEORDER range to allow hugetlb w/4K powerpc/mm/hash64: Fix might_have_hea() check IB/srp: Fix infinite loop when FMR sg[0].offset != 0 IB/core: correctly handle rdma_rw_init_mrs() failure ubi: Deal with interrupted erasures in WL zfcp: fix fc_host port_type with NPIV zfcp: fix ELS/GS request length for hardware data router zfcp: close window with unblocked rport during rport gone zfcp: retain trace level for SCSI and HBA FSF response records zfcp: restore: Dont use 0 to indicate invalid LUN in rec trace zfcp: trace on request for open and close of WKA port zfcp: restore tracing of handle for port and LUN with HBA records zfcp: fix D_ID field with actual value on tracing SAN responses zfcp: fix payload trace length for SAN request zfcp: trace full payload of all SAN records (req,resp,iels) scsi: zfcp: spin_lock_irqsave() is not nestable fbdev/efifb: Fix 16 color palette entry calculation ovl: Fix info leak in ovl_lookup_temp() ovl: copy_up_xattr(): use strnlen mb86a20s: fix the locking logic mb86a20s: fix demod settings cx231xx: don't return error on success cx231xx: fix GPIOs for Pixelview SBTVD hybrid cx231xx: can't proceed if I2C bus register fails ALSA: hda - Fix a failure of micmute led when having multi adcs MIPS: Fix -mabi=64 build of vdso.lds MIPS: ptrace: Fix regs_return_value for kernel context Input: i8042 - skip selftest on ASUS laptops Input: elantech - force needed quirks on Fujitsu H760 Input: elantech - add Fujitsu Lifebook E556 to force crc_enabled
[Kernel-packages] [Bug 1637512] Re: Yakkety update to v4.8.3 stable release
** Changed in: linux (Ubuntu Yakkety) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637512 Title: Yakkety update to v4.8.3 stable release Status in linux package in Ubuntu: New Status in linux source package in Yakkety: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.8.3 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.8.3 stable release shall be applied: v4l: rcar-fcp: Don't force users to check for disabled FCP support scsi: configure runtime pm before calling device_add in scsi_add_host_with_dma Make __xfs_xattr_put_listen preperly report errors. Linux 4.8.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637512/+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 1637473] Re: cleanup primary tree for linux-hwe layering issues
** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637473 Title: cleanup primary tree for linux-hwe layering issues Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Bug description: We have some minor issues in the primary tree which are highlighted by delta comparison with linux-hwe. Fix them up. 1) Vcs-Git: still points to xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637473/+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 1640028] Re: fsck or initramfs not working
My PC had an abnormal shutdown. Besides me trying to fix the initramfs , i mange to remove the grub loader and the grub folder. I tried to use boot repair it does not work, i have installed Linux on a new hard-drive , so on the new Linux installation i have installed boot repair, but i want to use boot repair to install grub on the other hard drive, if i do mange to install the new grub will it fix my initramfs problem? Thank you On Wed, Nov 9, 2016 at 9:05 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.9 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc4 > > > ** Changed in: linux (Ubuntu) >Importance: Undecided => High > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > ** Tags added: kernel-da-key > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1640028 > > Title: > fsck or initramfs not working > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > when I boot get to initramfs, when i type exit i get the following > error. > > ata1: failed command READ FDMA QUEDED. > Kenerl panic. > Kernel offset :disable > > 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: ubuntu 4323 F pulseaudio > CasperVersion: 1.376 > CurrentDesktop: Unity > Date: Tue Nov 8 06:07:36 2016 > LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi > file=/cdrom/preseed/username.seed cdrom-detect/try-usb=true noprompt > floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash --- > 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 > StagingDrivers: r8188eu > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/12/2013 > dmi.bios.vendor: Intel Corp. > dmi.bios.version: BEH6110H.86A.0120.2013.1112.1412 > dmi.board.name: DH61SA > dmi.board.vendor: Intel Corporation > dmi.board.version: AAG38870-201 > dmi.chassis.type: 3 > dmi.modalias: dmi:bvnIntelCorp.:bvrBEH6110H. > 86A.0120.2013.1112.1412:bd11/12/2013:svn:pn:pvr: > rvnIntelCorporation:rnDH61SA:rvrAAG38870-201:cvn:ct3:cvr: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1640028/+subscriptions > -- 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/1640028 Title: fsck or initramfs not working Status in linux package in Ubuntu: Incomplete Bug description: when I boot get to initramfs, when i type exit i get the following error. ata1: failed command READ FDMA QUEDED. Kenerl panic. Kernel offset :disable 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: ubuntu 4323 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Tue Nov 8 06:07:36 2016 LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash --- RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A
[Kernel-packages] [Bug 1641075] 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/1641075 Title: connected my android phone, htc one m8, unabe to mount. Status in linux package in Ubuntu: Confirmed Bug description: Unable to mount phone. It used to work fine in the past, now gone completely out. If I connect it, sometimes I get a message on the phone screen indidcating if I want to use it for file transfers or charging. When I choose file transfers phone tries to mount but fails. I get the message: Unable to open MTP device '[usb:002,073]' This is the output from:lsusb Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 007: ID 8087:07dc Intel Corp. Bus 002 Device 006: ID 5986:055e Acer, Inc Bus 002 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 002 Device 004: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 002 Device 096: ID 04e8:3469 Samsung Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub as you can see device is not listed, ie htc. this is the other output: dmesg | grep error [4.513851] usb 2-1: device not accepting address 10, error -71 [5.329827] usb 2-1: device not accepting address 12, error -71 [6.825737] usb 2-1: device not accepting address 15, error -71 [9.974461] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro [ 11.284758] iwlwifi :02:00.0: Direct firmware load for iwlwifi-3160-17.ucode failed with error -2 [ 17.657095] usb 2-1: can't read configurations, error -110 [ 23.776699] usb 2-1: device not accepting address 21, error -71 [ 25.324569] usb 2-1: device not accepting address 25, error -71 [ 30.748339] usb 2-1: device descriptor read/all, error -110 [ 31.564231] usb 2-1: device not accepting address 29, error -71 [ 2724.182039] usb 2-1: device not accepting address 75, error -71 [ 2741.132996] usb 2-1: device not accepting address 81, error -71 [ 2747.276635] usb 2-1: device not accepting address 84, error -71 [ 2763.979585] usb 2-1: device not accepting address 89, error -71 [ 2765.163503] usb 2-1: device not accepting address 92, error -71 [ 2889.015888] usb 2-1: device not accepting address 97, error -71 [ 2967.527023] usb 2-1: device not accepting address 125, error -71 [ 3056.901541] usb 2-1: device not accepting address 25, error -71 [ 3138.452524] usb 2-1: device descriptor read/all, error -110 [ 3227.907019] usb 2-1: device not accepting address 71, error -71 [ 3338.788209] usb 2-1: device descriptor read/all, error -110 This is not a cable issue as I checked it on an old ubuntu box, ie the firs 16.04 with no updates, ie kernel 31 one and it works fine on it. Could you pls look at it, thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: koli 1952 F pulseaudio /dev/snd/controlC1: koli 1952 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 11 10:00:59 2016 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=7f093ee2-a093-4cde-99c6-a60706e7059f HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-06-11 (152 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20354 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=0954c6f9-fd74-4c40-ad0b-03e7f73f5153 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 10:01:38.818: The udisks-daemon is running (name-owner :1.77). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias:
[Kernel-packages] [Bug 1641083] Re: linux: 4.8.0-28.30 -proposed tracker
It was not possible to create or handle the tracking bugs for the following packages (their tracking bugs based on this update must be handled manually): linux-lts-yakkety (16.04.1) ** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Confirmed ** Description changed: This bug is for tracking the 4.8.0-28.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Friday, 11. November 2016 10:30 UTC ** Description changed: This bug is for tracking the 4.8.0-28.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase:Packaging kernel-stable-phase-changed:Friday, 11. November 2016 10:30 UTC + + -- swm properties -- + derivative-trackers-created: true + phase: Packaging -- 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/1641083 Title: linux: 4.8.0-28.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-28.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase:Packaging kernel-stable-phase-changed:Friday, 11. November 2016 10:30 UTC -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1641083/+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 1641083] [NEW] linux: 4.8.0-28.30 -proposed tracker
Public bug reported: This bug is for tracking the 4.8.0-28.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase:Packaging kernel-stable-phase-changed:Friday, 11. November 2016 10:30 UTC -- swm properties -- derivative-trackers-created: true phase: Packaging ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Yakkety) Importance: Medium Status: Confirmed ** Tags: block-proposed block-proposed-yakkety kernel-release-tracking-bug yakkety ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Tags added: block-proposed-yakkety ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Tags added: yakkety ** Changed in: linux (Ubuntu Yakkety) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in:
[Kernel-packages] [Bug 1641075] [NEW] connected my android phone, htc one m8, unabe to mount.
Public bug reported: Unable to mount phone. It used to work fine in the past, now gone completely out. If I connect it, sometimes I get a message on the phone screen indidcating if I want to use it for file transfers or charging. When I choose file transfers phone tries to mount but fails. I get the message: Unable to open MTP device '[usb:002,073]' This is the output from:lsusb Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 007: ID 8087:07dc Intel Corp. Bus 002 Device 006: ID 5986:055e Acer, Inc Bus 002 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 002 Device 004: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 002 Device 096: ID 04e8:3469 Samsung Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub as you can see device is not listed, ie htc. this is the other output: dmesg | grep error [4.513851] usb 2-1: device not accepting address 10, error -71 [5.329827] usb 2-1: device not accepting address 12, error -71 [6.825737] usb 2-1: device not accepting address 15, error -71 [9.974461] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro [ 11.284758] iwlwifi :02:00.0: Direct firmware load for iwlwifi-3160-17.ucode failed with error -2 [ 17.657095] usb 2-1: can't read configurations, error -110 [ 23.776699] usb 2-1: device not accepting address 21, error -71 [ 25.324569] usb 2-1: device not accepting address 25, error -71 [ 30.748339] usb 2-1: device descriptor read/all, error -110 [ 31.564231] usb 2-1: device not accepting address 29, error -71 [ 2724.182039] usb 2-1: device not accepting address 75, error -71 [ 2741.132996] usb 2-1: device not accepting address 81, error -71 [ 2747.276635] usb 2-1: device not accepting address 84, error -71 [ 2763.979585] usb 2-1: device not accepting address 89, error -71 [ 2765.163503] usb 2-1: device not accepting address 92, error -71 [ 2889.015888] usb 2-1: device not accepting address 97, error -71 [ 2967.527023] usb 2-1: device not accepting address 125, error -71 [ 3056.901541] usb 2-1: device not accepting address 25, error -71 [ 3138.452524] usb 2-1: device descriptor read/all, error -110 [ 3227.907019] usb 2-1: device not accepting address 71, error -71 [ 3338.788209] usb 2-1: device descriptor read/all, error -110 This is not a cable issue as I checked it on an old ubuntu box, ie the firs 16.04 with no updates, ie kernel 31 one and it works fine on it. Could you pls look at it, thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: koli 1952 F pulseaudio /dev/snd/controlC1: koli 1952 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 11 10:00:59 2016 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=7f093ee2-a093-4cde-99c6-a60706e7059f HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-06-11 (152 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20354 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=0954c6f9-fd74-4c40-ad0b-03e7f73f5153 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 10:01:38.818: The udisks-daemon is running (name-owner :1.77). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70: dmi.product.name: 20354 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641075 Title: connected my android phone, htc one m8,
[Kernel-packages] [Bug 1641078] bootup console message
Default Comment by Bridge
** Attachment added: "bootup console message"
https://bugs.launchpad.net/bugs/1641078/+attachment/4775893/+files/UB01_IPL_Fail_SCSI_device_not_found_11_9_2016.txt
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1641078
Title:
System cannot be booted up when root filesystem is on an LVM on two
disks
Status in linux package in Ubuntu:
New
Bug description:
---Problem Description---
LVMed root file system acrossing multiple disks cannot be booted up
---uname output---
Linux ntc170 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 UTC 2016
s390x s390x s390x GNU/Linux
---Patches Installed---
n/a
Machine Type = z13
---System Hang---
cannot boot up the system after shutdown or reboot
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Created root file system on an LVM and the LVM crosses two disks. After shut
down or reboot the system, the system cannot be up.
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
Device driver error code:
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
lvmetad is not active yet, using direct activation during sysinit
Couldn't find device with uuid 7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V.
-Attach sysctl -a output output to the bug.
More detailed installation description:
The installation was on a FCP SCSI SAN volumes each with two active
paths. Multipath was involved. The system IPLed fine up to the point
that we expanded the /root filesystem to span volumes. At boot time,
the system was unable to locate the second segment of the /root
filesystem. The error message indicated this was due to lvmetad not
being not active.
Error message:
Begin: Running /scripts/local-block ... lvmetad is not active yet,
using direct activation during sysinit
Couldn't find device with uuid 7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V
Failed to find logical volume "ub01-vg/root"
PV Volume information:
physical_volumes {
pv0 {
id = "L2qixM-SKkF-rQsp-ddao-gagl-LwKV-7Bw1Dz"
device = "/dev/sdb5"# Hint only
status = ["ALLOCATABLE"]
flags = []
dev_size = 208713728# 99.5225 Gigabytes
pe_start = 2048
pe_count = 25477# 99.5195 Gigabytes
}
pv1 {
id = "7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V"
device = "/dev/sda"# Hint only
status = ["ALLOCATABLE"]
flags = []
dev_size = 209715200# 100 Gigabytes
pe_start = 2048
pe_count = 25599# 99.9961 Gigabytes
LV Volume Information:
logical_volumes {
root {
id = "qWuZeJ-Libv-DrEs-9b1a-p0QF-2Fj0-qgGsL8"
status = ["READ", "WRITE", "VISIBLE"]
flags = []
creation_host = "ub01"
creation_time = 1477515033# 2016-10-26
16:50:33 -0400
segment_count = 2
segment1 {
start_extent = 0
extent_count = 921# 3.59766 Gigabytes
type = "striped"
stripe_count = 1# linear
stripes = [
"pv0", 0
]
}
segment2 {
start_extent = 921
extent_count = 25344# 99 Gigabytes
type = "striped"
stripe_count = 1# linear
stripes = [
"pv1", 0
]
}
}
Additional testing has been done with CKD volumes and we see the same
behavior. Only the UUID of the fist volume in the VG can be located at boot,
and the same message: lvmetad is not active yet, using direct activation
during sysinit
Couldn't find device with uuid x is displayed for CKD
[Kernel-packages] [Bug 1641078] [NEW] System cannot be booted up when root filesystem is on an LVM on two disks
You have been subscribed to a public bug:
---Problem Description---
LVMed root file system acrossing multiple disks cannot be booted up
---uname output---
Linux ntc170 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 UTC 2016 s390x
s390x s390x GNU/Linux
---Patches Installed---
n/a
Machine Type = z13
---System Hang---
cannot boot up the system after shutdown or reboot
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Created root file system on an LVM and the LVM crosses two disks. After shut
down or reboot the system, the system cannot be up.
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
Device driver error code:
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
lvmetad is not active yet, using direct activation during sysinit
Couldn't find device with uuid 7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V.
-Attach sysctl -a output output to the bug.
More detailed installation description:
The installation was on a FCP SCSI SAN volumes each with two active
paths. Multipath was involved. The system IPLed fine up to the point
that we expanded the /root filesystem to span volumes. At boot time,
the system was unable to locate the second segment of the /root
filesystem. The error message indicated this was due to lvmetad not
being not active.
Error message:
Begin: Running /scripts/local-block ... lvmetad is not active yet,
using direct activation during sysinit
Couldn't find device with uuid 7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V
Failed to find logical volume "ub01-vg/root"
PV Volume information:
physical_volumes {
pv0 {
id = "L2qixM-SKkF-rQsp-ddao-gagl-LwKV-7Bw1Dz"
device = "/dev/sdb5"# Hint only
status = ["ALLOCATABLE"]
flags = []
dev_size = 208713728# 99.5225 Gigabytes
pe_start = 2048
pe_count = 25477# 99.5195 Gigabytes
}
pv1 {
id = "7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V"
device = "/dev/sda"# Hint only
status = ["ALLOCATABLE"]
flags = []
dev_size = 209715200# 100 Gigabytes
pe_start = 2048
pe_count = 25599# 99.9961 Gigabytes
LV Volume Information:
logical_volumes {
root {
id = "qWuZeJ-Libv-DrEs-9b1a-p0QF-2Fj0-qgGsL8"
status = ["READ", "WRITE", "VISIBLE"]
flags = []
creation_host = "ub01"
creation_time = 1477515033# 2016-10-26 16:50:33
-0400
segment_count = 2
segment1 {
start_extent = 0
extent_count = 921# 3.59766 Gigabytes
type = "striped"
stripe_count = 1# linear
stripes = [
"pv0", 0
]
}
segment2 {
start_extent = 921
extent_count = 25344# 99 Gigabytes
type = "striped"
stripe_count = 1# linear
stripes = [
"pv1", 0
]
}
}
Additional testing has been done with CKD volumes and we see the same behavior.
Only the UUID of the fist volume in the VG can be located at boot, and the
same message: lvmetad is not active yet, using direct activation during
sysinit
Couldn't find device with uuid x is displayed for CKD disks.
Just a different UUID is listed.
If the file /root file system only has one segment on the first volume, CKD or
SCSI volumes, the system will IPL. Because of this behavior, I do not believe
the problem is related to SAN disk or multipath. I think it is due to the
system not being able to read the UUID on any PV in the VG other then the IPL
disk.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-148452 severity-critical
targetmilestone-inin16041
--
System cannot be booted up when root filesystem is on an LVM on two disks
https://bugs.launchpad.net/bugs/1641078
You received this bug notification because you are a member of Kernel Packages,
which
[Kernel-packages] [Bug 1227996] Re: [Lenovo IdeaPad Yoga 13] ubuntu doesn't know about Yoga screen rotation keycodes: atkbd serio0: Use 'setkeycodes e03e ' to make it known.
went away for a long time, so I refused to do any package updates for several months and everything was fine. Now i did update of packages and thing came back :( -- 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/1227996 Title: [Lenovo IdeaPad Yoga 13] ubuntu doesn't know about Yoga screen rotation keycodes: atkbd serio0: Use 'setkeycodes e03e ' to make it known. Status in linux package in Ubuntu: Triaged Bug description: The following spam litters dmesg: [36294.989706] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [36294.995650] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [36294.995661] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [36296.016998] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [36296.017002] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [36296.021894] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [36296.021907] atkbd serio0: Use 'setkeycodes e03e ' to make it known. As can be seen, this occurs frequently. It might be related, but at times, the keyboard freezes for a few seconds and then starts sending a repeating character while no keys are pressed. This behavior is not stopped unless a key (any key) is pressed. The character that is output is a special character, but I don't know what combination it is specifically. This might be related to the fact that this is a lenovo yoga 13 ideapad. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-30-generic 3.8.0-30.44 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: noobermin 1991 F pulseaudio /dev/snd/pcmC0D0p: noobermin 1991 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Sep 20 02:07:54 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=7d95a03d-5f38-403f-84d9-51ebca691a4b InstallationDate: Installed on 2013-08-31 (19 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 20175 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=UUID=6a1575e6-9b6a-4086-988e-2efda2c80fd3 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-30-generic N/A linux-backports-modules-3.8.0-30-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN52WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN52WW:bd11/22/2012:svnLENOVO:pn20175:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13: dmi.product.name: 20175 dmi.product.version: Lenovo IdeaPad Yoga 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1227996/+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 1641049] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1641049/+attachment/4775849/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641049 Title: NFSv4 do not invalidate cached information about deleted files Status in linux package in Ubuntu: Incomplete Bug description: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1641049] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1641049/+attachment/4775853/+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/1641049 Title: NFSv4 do not invalidate cached information about deleted files Status in linux package in Ubuntu: Incomplete Bug description: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1641049] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1641049/+attachment/4775850/+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/1641049 Title: NFSv4 do not invalidate cached information about deleted files Status in linux package in Ubuntu: Incomplete Bug description: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1641049] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1641049/+attachment/4775851/+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/1641049 Title: NFSv4 do not invalidate cached information about deleted files Status in linux package in Ubuntu: Incomplete Bug description: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1641049] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1641049/+attachment/4775847/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641049 Title: NFSv4 do not invalidate cached information about deleted files Status in linux package in Ubuntu: Incomplete Bug description: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1641049] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1641049/+attachment/4775848/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641049 Title: NFSv4 do not invalidate cached information about deleted files Status in linux package in Ubuntu: Incomplete Bug description: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1641049] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1641049/+attachment/4775854/+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/1641049 Title: NFSv4 do not invalidate cached information about deleted files Status in linux package in Ubuntu: Incomplete Bug description: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1641049] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1641049/+attachment/4775852/+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/1641049 Title: NFSv4 do not invalidate cached information about deleted files Status in linux package in Ubuntu: Incomplete Bug description: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1641049] Re: NFSv4 do not invalidate cached information about deleted files
apport information ** Tags added: apport-collected ** Description changed: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Nov 8 03:13 seq + crw-rw 1 root audio 116, 33 Nov 8 03:13 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + 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: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 + InstallationDate: Installed on 2016-11-07 (3 days ago) + InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: + Bus 002 Device 002: ID 8087:8002 Intel Corp. + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub + Bus 001 Device 002: ID 8087:800a Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. PowerEdge R630 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + LC_CTYPE=en_US.UTF-8 + TERM=screen-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro + ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-45-generic N/A + linux-backports-modules-4.4.0-45-generic N/A + linux-firmware1.157.4 + RfKill: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 1641028] Re: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21)
** 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/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641049] [NEW] NFSv4 do not invalidate cached information about deleted files
Public bug reported: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug xenial ** Description changed: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. + I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. + Mounting nfs with lookupcache=positive do not fix this issue. + NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Nov 8 03:13 seq - crw-rw 1 root audio 116, 33 Nov 8 03:13 timer + total 0 + crw-rw 1 root audio 116, 1 Nov 8 03:13 seq + crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" -
[Kernel-packages] [Bug 1641049] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1641049 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/1641049 Title: NFSv4 do not invalidate cached information about deleted files Status in linux package in Ubuntu: Incomplete Bug description: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641049/+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 1641028] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775791/+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/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641028] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775790/+files/RfKill.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/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641028] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775792/+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/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641028] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775785/+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/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641028] Re: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21)
apport information ** Tags added: apport-collected yakkety ** Description changed: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. - Plugging in a USB headset and adjusting the volume levels for that - device works fine. + Plugging in a USB headset and adjusting the volume levels for that device works fine. + --- + ApportVersion: 2.20.3-0ubuntu8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: barryprice 4775 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.10 + HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d + InstallationDate: Installed on 2016-11-08 (2 days ago) + InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) + MachineType: ASUSTeK COMPUTER INC. UX390UAK + NonfreeKernelModules: zfs zunicode zcommon znvpair zavl + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 + RelatedPackageVersions: + linux-restricted-modules-4.8.0-27-generic N/A + linux-backports-modules-4.8.0-27-generic N/A + linux-firmware1.161 + Tags: yakkety + Uname: Linux 4.8.0-27-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/31/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: UX390UAK.303 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: UX390UAK + 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.name: UX390UAK + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775778/+files/AlsaInfo.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/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:
[Kernel-packages] [Bug 1641028] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775779/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641028] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775783/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641028] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775780/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641028] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775787/+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/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641028] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775789/+files/PulseList.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/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641028] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775784/+files/Lsusb.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/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641028] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775788/+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/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641028] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775786/+files/ProcEnviron.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/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641028] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775782/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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 1641028] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775781/+files/IwConfig.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/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) Status in linux package in Ubuntu: Confirmed Bug description: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: barryprice 4775 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d InstallationDate: Installed on 2016-11-08 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. UX390UAK NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK 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.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+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
