[Kernel-packages] [Bug 1611215] modoc (ppc64el) - tests ran: 10, failed: 1
*** This bug is a duplicate of bug 1612305 *** https://bugs.launchpad.net/bugs/1612305 tests ran: 10, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-35.54/modoc__4.4.0-35.54__2016-08-15_04-59-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/1611215 Title: linux: 4.4.0-35.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-35.54 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: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1611215/+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 1611215] onibi (i386) - tests ran: 136, failed: 0
*** This bug is a duplicate of bug 1612305 *** https://bugs.launchpad.net/bugs/1612305 tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-35.54/onibi__4.4.0-35.54__2016-08-15_04-31-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/1611215 Title: linux: 4.4.0-35.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-35.54 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: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1611215/+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 1612740] Re: linux-armadaxp: 3.2.0-1672.98 -proposed tracker
** 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/promote-to-proposed Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) => Ike Panhc (ikepanhc) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) => Ike Panhc (ikepanhc) ** Description changed: This bug is for tracking the 3.2.0-1672.98 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 -- kernel-stable-master-bug: 1612732 + kernel-stable-phase-changed:Monday, 15. August 2016 05:00 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the 3.2.0-1672.98 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 kernel-stable-master-bug: 1612732 - kernel-stable-phase-changed:Monday, 15. August 2016 05:00 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-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1612740 Title: linux-armadaxp: 3.2.0-1672.98 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid 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 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-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1672.98 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 kernel-stable-master-bug: 1612732 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612740/+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 1611215] dwalin (amd64) - tests ran: 10, failed: 0
*** This bug is a duplicate of bug 1612305 *** https://bugs.launchpad.net/bugs/1612305 tests ran: 10, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-35.54/dwalin__4.4.0-35.54__2016-08-15_04-00-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/1611215 Title: linux: 4.4.0-35.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-35.54 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: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1611215/+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 1318111] Re: Adds more and more copies of ‘crashkernel=384M-:128M’ in /etc/default/grub when upgrading or reinstalling grub-pc
I have the same bug on my Ubuntu 16.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1318111 Title: Adds more and more copies of ‘crashkernel=384M-:128M’ in /etc/default/grub when upgrading or reinstalling grub-pc Status in kexec-tools package in Ubuntu: Confirmed Status in kexec-tools source package in Trusty: Confirmed Bug description: # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M" # apt-get install --reinstall grub-pc … # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M crashkernel=384M-:128M" # apt-get install --reinstall grub-pc … # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M" # apt-get install --reinstall grub-pc … # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M" ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: kexec-tools 1:2.0.6-0ubuntu2 Uname: Linux 3.15.0-031500rc4-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.14.2-0ubuntu2 Architecture: amd64 Date: Fri May 9 22:39:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2010-12-05 (1251 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202) SourcePackage: kexec-tools UpgradeStatus: Upgraded to utopic on 2013-10-31 (190 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1318111/+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 1611215] modoc (ppc64el) - tests ran: 2, failed: 0
*** This bug is a duplicate of bug 1612305 *** https://bugs.launchpad.net/bugs/1612305 tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-35.54/modoc__4.4.0-35.54__2016-08-15_04-09-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/1611215 Title: linux: 4.4.0-35.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-35.54 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: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1611215/+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 1613158] Re: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0)
** Description changed: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0). I've tried: * Plain yakkety 4.4.0-34-generic * Mainline kernel 4.7 * Mainline kernel 4.8rc1 and only the first one works. Kernels 4.7 and 4.8rc1 freeze with a bright orange screen. Best I can tell, the frozen orange screen coincides with kernel log messages: Aug 15 12:24:23 x51 kernel: [1.761197] fb: switching to nouveaufb from simple Aug 15 12:24:23 x51 kernel: [1.761210] Console: switching to colour dummy device 80x25 + ... + Aug 15 12:24:26 x51 kernel: [ 11.896160] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.897225] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.898292] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.899358] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.900423] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.901489] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.902555] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.903621] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.904686] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.905753] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.906818] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.907883] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.908949] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.910014] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.911079] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.912145] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + Aug 15 12:24:26 x51 kernel: [ 11.913210] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] + ... + ... ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** 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/1613158 Title: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0) Status in linux package in Ubuntu: Confirmed Bug description: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0). I've tried: * Plain yakkety 4.4.0-34-generic * Mainline kernel 4.7 * Mainline kernel 4.8rc1 and only the first one works. Kernels 4.7 and 4.8rc1 freeze with a bright orange screen. Best I can tell, the frozen orange screen coincides with kernel log messages: Aug 15 12:24:23 x51 kernel: [1.761197] fb: switching to nouveaufb from simple Aug 15 12:24:23 x51 kernel: [1.761210] Console: switching to colour dummy device 80x25 ... Aug 15 12:24:26 x51 kernel: [ 11.896160] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.897225] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.898292] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.899358] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.900423] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.901489] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.902555] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.903621] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.904686] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.905753] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.906818] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.907883] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.908949] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.910014] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.911079] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.912145] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.913210] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] ... ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613158/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1613158] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1613158 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/1613158 Title: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0) Status in linux package in Ubuntu: Confirmed Bug description: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0). I've tried: * Plain yakkety 4.4.0-34-generic * Mainline kernel 4.7 * Mainline kernel 4.8rc1 and only the first one works. Kernels 4.7 and 4.8rc1 freeze with a bright orange screen. Best I can tell, the frozen orange screen coincides with kernel log messages: Aug 15 12:24:23 x51 kernel: [1.761197] fb: switching to nouveaufb from simple Aug 15 12:24:23 x51 kernel: [1.761210] Console: switching to colour dummy device 80x25 ... Aug 15 12:24:26 x51 kernel: [ 11.896160] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.897225] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.898292] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.899358] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.900423] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.901489] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.902555] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.903621] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.904686] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.905753] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.906818] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.907883] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.908949] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.910014] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.911079] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.912145] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.913210] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] ... ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613158/+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 1613157] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1613157 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/1613157 Title: [SRU] xgene_enet: 10g performance only hits ~75% on multi-client tests Status in linux package in Ubuntu: Incomplete Bug description: [Impact] During iperf testing of the xenial kernel, the line only achieves ~75% during multi-client testing. [Test Case] Run iperf with multiple clients [Regression Risk] The patches changes only affect the xgene_enet driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613157/+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 1613158] Re: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0)
Kernel log from 4.7.0 trying to boot ** Description changed: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0). I've tried: - * Plain yakkety 4.4.0-34-generic - * Mainline kernel 4.7 - * Mainline kernel 4.8rc1 + * Plain yakkety 4.4.0-34-generic + * Mainline kernel 4.7 + * Mainline kernel 4.8rc1 and only the first one works. Kernels 4.7 and 4.8rc1 freeze with a bright orange screen. Best I can tell, the frozen orange screen coincides with kernel log messages: - Aug 15 11:33:04 x51 kernel: [1.788277] fb: switching to nouveaufb from simple - Aug 15 11:33:04 x51 kernel: [1.788291] Console: switching to colour dummy device 80x25 - Aug 15 11:33:04 x51 kernel: [1.788401] nouveau :01:00.0: NVIDIA GM204 (124020a1) + Aug 15 12:24:23 x51 kernel: [1.761197] fb: switching to nouveaufb from simple + Aug 15 12:24:23 x51 kernel: [1.761210] Console: switching to colour dummy device 80x25 ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613158/+attachment/4721045/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613158 Title: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0) Status in linux package in Ubuntu: Confirmed Bug description: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0). I've tried: * Plain yakkety 4.4.0-34-generic * Mainline kernel 4.7 * Mainline kernel 4.8rc1 and only the first one works. Kernels 4.7 and 4.8rc1 freeze with a bright orange screen. Best I can tell, the frozen orange screen coincides with kernel log messages: Aug 15 12:24:23 x51 kernel: [1.761197] fb: switching to nouveaufb from simple Aug 15 12:24:23 x51 kernel: [1.761210] Console: switching to colour dummy device 80x25 ... Aug 15 12:24:26 x51 kernel: [ 11.896160] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.897225] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.898292] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.899358] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.900423] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.901489] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.902555] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.903621] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.904686] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.905753] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.906818] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.907883] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.908949] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.910014] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.911079] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.912145] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.913210] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] ... ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613158/+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 1580798] Re: Suspend breaks on gnome session not on unity session - dell xps 14z
[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/1580798 Title: Suspend breaks on gnome session not on unity session - dell xps 14z Status in linux package in Ubuntu: Expired Bug description: I've got two users on this computer. When using gnome 3 session the suspend behaves really quirky. After suspend it might have rendering problems or it doesn't come back or it comes back with a very slow response afterwards. In Unity the problem doesn't appear, so a hardware problem seems to not affect this other software. I'll try to make a screenshot of the rendering problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cruzyfer 13248 F pulseaudio CurrentDesktop: Unity Date: Wed May 11 19:07:00 2016 HibernationDevice: RESUME=UUID=4ce8949c-31c9-4b40-bb2f-613863afdb18 InstallationDate: Installed on 2014-12-06 (522 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. XPS L412Z ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=caa13b82-560e-4281-83c3-de58dcbd96ef ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-23 (17 days ago) dmi.bios.date: 11/15/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 008DD8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A03 dmi.modalias: dmi:bvnDellInc.:bvrA03:bd11/15/2011:svnDellInc.:pnXPSL412Z:pvrA03:rvnDellInc.:rn008DD8:rvrA00:cvnDellInc.:ct8:cvrA03: dmi.product.name: XPS L412Z dmi.product.version: A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580798/+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 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]
[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/1585434 Title: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Status in linux package in Ubuntu: Expired Bug description: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] ecryptfs_readpage: Error decrypting page; rc = [-4] I dont' have this issue showing in dmesg when using 3.19 kernel, only with later kernels. Is it related to selecting encrypted home on install or something? I don't notice any issues with performance because of it or have any other error messages. I am using default ubuntu xenial 16.04 with unity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cooloutac 2054 F pulseaudio /dev/snd/pcmC0D0p: cooloutac 2054 F...m pulseaudio /dev/snd/controlC0: cooloutac 2054 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 22:38:44 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1 InstallationDate: Installed on 2016-05-20 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Studio XPS 7100 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0NWWY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 7100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585434/+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 1613158] [NEW] Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0)
Public bug reported: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0). I've tried: * Plain yakkety 4.4.0-34-generic * Mainline kernel 4.7 * Mainline kernel 4.8rc1 and only the first one works. Kernels 4.7 and 4.8rc1 freeze with a bright orange screen. Best I can tell, the frozen orange screen coincides with kernel log messages: Aug 15 11:33:04 x51 kernel: [1.788277] fb: switching to nouveaufb from simple Aug 15 11:33:04 x51 kernel: [1.788291] Console: switching to colour dummy device 80x25 Aug 15 11:33:04 x51 kernel: [1.788401] nouveau :01:00.0: NVIDIA GM204 (124020a1) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1613158 Title: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0) Status in linux package in Ubuntu: New Bug description: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0). I've tried: * Plain yakkety 4.4.0-34-generic * Mainline kernel 4.7 * Mainline kernel 4.8rc1 and only the first one works. Kernels 4.7 and 4.8rc1 freeze with a bright orange screen. Best I can tell, the frozen orange screen coincides with kernel log messages: Aug 15 11:33:04 x51 kernel: [1.788277] fb: switching to nouveaufb from simple Aug 15 11:33:04 x51 kernel: [1.788291] Console: switching to colour dummy device 80x25 Aug 15 11:33:04 x51 kernel: [1.788401] nouveau :01:00.0: NVIDIA GM204 (124020a1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613158/+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 1612740] Re: linux-armadaxp: 3.2.0-1672.98 -proposed tracker
** Summary changed: - linux-armadaxp: -proposed tracker + linux-armadaxp: 3.2.0-1672.98 -proposed tracker ** Description changed: - This bug is for tracking the upload package. This - bug will contain status and testing results related to that upload. + This bug is for tracking the 3.2.0-1672.98 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 -- kernel-stable-master-bug: 1612732 ** Changed in: kernel-sru-workflow Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Ike Panhc (ikepanhc) ** Changed in: kernel-sru-workflow/verification-testing Assignee: Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) => Ike Panhc (ikepanhc) ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => In Progress ** Changed in: linux-armadaxp (Ubuntu Precise) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1612740 Title: linux-armadaxp: 3.2.0-1672.98 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New 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-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1672.98 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 -- kernel-stable-master-bug: 1612732 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612740/+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 1613157] [NEW] [SRU] xgene_enet: 10g performance only hits ~75% on multi-client tests
Public bug reported: [Impact] During iperf testing of the xenial kernel, the line only achieves ~75% during multi-client testing. [Test Case] Run iperf with multiple clients [Regression Risk] The patches changes only affect the xgene_enet driver ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Craig Magina (craig.magina) Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Craig Magina (craig.magina) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613157 Title: [SRU] xgene_enet: 10g performance only hits ~75% on multi-client tests Status in linux package in Ubuntu: New Bug description: [Impact] During iperf testing of the xenial kernel, the line only achieves ~75% during multi-client testing. [Test Case] Run iperf with multiple clients [Regression Risk] The patches changes only affect the xgene_enet driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613157/+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 1613158] [NEW] Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0)
You have been subscribed to a public bug: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0). I've tried: * Plain yakkety 4.4.0-34-generic * Mainline kernel 4.7 * Mainline kernel 4.8rc1 and only the first one works. Kernels 4.7 and 4.8rc1 freeze with a bright orange screen. Best I can tell, the frozen orange screen coincides with kernel log messages: Aug 15 11:33:04 x51 kernel: [1.788277] fb: switching to nouveaufb from simple Aug 15 11:33:04 x51 kernel: [1.788291] Console: switching to colour dummy device 80x25 Aug 15 11:33:04 x51 kernel: [1.788401] nouveau :01:00.0: NVIDIA GM204 (124020a1) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0) https://bugs.launchpad.net/bugs/1613158 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1611215] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 83, failed: 0
*** This bug is a duplicate of bug 1612305 *** https://bugs.launchpad.net/bugs/1612305 tests ran: 83, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-35.54/ms10-35-mcdivittB0-kernel__4.4.0-35.54__2016-08-15_02-58-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/1611215 Title: linux: 4.4.0-35.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-35.54 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: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1611215/+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 1611313] Re: linux-armadaxp: 3.2.0-1671.97 -proposed tracker
*** This bug is a duplicate of bug 1612740 *** https://bugs.launchpad.net/bugs/1612740 ** This bug has been marked a duplicate of bug 1612740 linux-armadaxp: 3.2.0-1672.98 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1611313 Title: linux-armadaxp: 3.2.0-1671.97 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid 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 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-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1671.97 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 kernel-stable-master-bug: 1611303 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1611313/+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 1611215] onibi (amd64) - tests ran: 136, failed: 0
*** This bug is a duplicate of bug 1612305 *** https://bugs.launchpad.net/bugs/1612305 tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-35.54/onibi__4.4.0-35.54__2016-08-15_03-03-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/1611215 Title: linux: 4.4.0-35.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-35.54 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: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1611215/+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 1611215] modoc (ppc64el) - tests ran: 26, failed: 4
*** This bug is a duplicate of bug 1612305 *** https://bugs.launchpad.net/bugs/1612305 tests ran: 26, failed: 4; http://kernel.ubuntu.com/testing/4.4.0-35.54/modoc__4.4.0-35.54__2016-08-15_03-33-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/1611215 Title: linux: 4.4.0-35.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-35.54 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: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1611215/+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 1611399] Re: [SRU] xgene_enet: an extra interrupt may be pending for an interrupt controller that doesn't support irq_disable and hardware with level interrupt
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Craig Magina (craig.magina)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1611399
Title:
[SRU] xgene_enet: an extra interrupt may be pending for an interrupt
controller that doesn't support irq_disable and hardware with level
interrupt
Status in linux package in Ubuntu:
Triaged
Bug description:
[Impact]
For interrupt controller that doesn't support irq_disable and hardware
with level interrupt, an extra interrupt may be pending. This patch fixes
the issue by setting IRQ_DISABLE_UNLAZY flag for the interrupt line,
as suggested by,
'commit e9849777d0e2 ("genirq: Add flag to force mask in
disable_irq[_nosync]()")'
[Test Case]
Run iperf on a merlin board to exercise the xgene_enet driver
[Regression Risk]
This commit only affects the xgene_enet driver
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611399/+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 1613134] Re: wacom touch screen does not recognize finger touch
** Description changed: After Updating to Xenail, the touch screen does not recognize finger touch as input, stylus and eraser are still recognized. This bug affects the Wacom Serial Penabled 2FG Touchscreen, which is built into the HP EliteBook 2760p and the Lenovo Thinkpad X201. It is already reported for other linux distributions. See bugreports: archlinux: https://bbs.archlinux.org/viewtopic.php?id=215014 linux kernel: https://bugzilla.kernel.org/show_bug.cgi?id=120011 xsetwacom lists the devices: - Wacom Serial Penabled 2FG Touchscreen Pen stylus id: 13 type: STYLUS - Wacom Serial Penabled 2FG Touchscreen Finger touchid: 14 type: TOUCH + Wacom Serial Penabled 2FG Touchscreen Pen stylus id: 13 type: STYLUS + Wacom Serial Penabled 2FG Touchscreen Finger touchid: 14 type: TOUCH Wacom Serial Penabled 2FG Touchscreen Pen eraser id: 16 type: ERASER + + a downgrade to Package: linux-image-4.2.0-42-generic 4.2.0-42.49 (from wily) brings back the finger touch. xsetwacom lists the available devices slightly different: + littlelion@PC00-C846:~$ xsetwacom list devices + Wacom Serial Penabled 2FG Touchscreen stylus id: 13 type: STYLUS + Wacom Serial Penabled 2FG Touchscreen eraser id: 15 type: ERASER + Wacom Serial Penabled 2FG Touchscreen touch id: 16 type: TOUCH + 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: littlelion 4149 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: littlelion 4149 F pulseaudio CurrentDesktop: Unity Date: Mon Aug 15 02:32:09 2016 HibernationDevice: RESUME=UUID=46ec6e40-eed3-4377-b3e1-4eed675fba2e InstallationDate: Installed on 2012-10-16 (1398 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: Hewlett-Packard HP EliteBook 2760p ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=81ff9b66-4d33-49d5-a76f-cf1418c3e354 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 + 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: Upgraded to xenial on 2016-08-06 (8 days ago) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SOU Ver. F.50 dmi.board.name: 162A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 05.40 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SOUVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook2760p:pvrA0005F02:rvnHewlett-Packard:rn162A:rvrKBCVersion05.40:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2760p dmi.product.version: A0005F02 dmi.sys.vendor: Hewlett-Packard -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613134 Title: wacom touch screen does not recognize finger touch Status in linux package in Ubuntu: Confirmed Bug description: After Updating to Xenail, the touch screen does not recognize finger touch as input, stylus and eraser are still recognized. This bug affects the Wacom Serial Penabled 2FG Touchscreen, which is built into the HP EliteBook 2760p and the Lenovo Thinkpad X201. It is already reported for other linux distributions. See bugreports: archlinux: https://bbs.archlinux.org/viewtopic.php?id=215014 linux kernel: https://bugzilla.kernel.org/show_bug.cgi?id=120011 xsetwacom lists the devices: Wacom Serial Penabled 2FG Touchscreen Pen stylus id: 13 type: STYLUS Wacom Serial Penabled 2FG Touchscreen Finger touchid: 14 type: TOUCH Wacom Serial Penabled 2FG Touchscreen Pen eraser id: 16 type: ERASER a downgrade to Package: linux-image-4.2.0-42-generic 4.2.0-42.49 (from wily) brings back the finger touch. xsetwacom lists the available devices slightly different: littlelion@PC00-C846:~$ xsetwacom list devices Wacom Serial Penabled 2FG Touchscreen stylus id: 13 type: STYLUS Wacom Serial Penabled 2FG Touchscreen eraser id: 15 type: ERASER Wacom Serial Penabled 2FG Touchscreen touch id: 16 type: TOUCH 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
[Kernel-packages] [Bug 1613134] 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/1613134 Title: wacom touch screen does not recognize finger touch Status in linux package in Ubuntu: Confirmed Bug description: After Updating to Xenail, the touch screen does not recognize finger touch as input, stylus and eraser are still recognized. This bug affects the Wacom Serial Penabled 2FG Touchscreen, which is built into the HP EliteBook 2760p and the Lenovo Thinkpad X201. It is already reported for other linux distributions. See bugreports: archlinux: https://bbs.archlinux.org/viewtopic.php?id=215014 linux kernel: https://bugzilla.kernel.org/show_bug.cgi?id=120011 xsetwacom lists the devices: Wacom Serial Penabled 2FG Touchscreen Pen stylus id: 13 type: STYLUS Wacom Serial Penabled 2FG Touchscreen Finger touchid: 14 type: TOUCH Wacom Serial Penabled 2FG Touchscreen Pen eraser id: 16 type: ERASER 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: littlelion 4149 F pulseaudio CurrentDesktop: Unity Date: Mon Aug 15 02:32:09 2016 HibernationDevice: RESUME=UUID=46ec6e40-eed3-4377-b3e1-4eed675fba2e InstallationDate: Installed on 2012-10-16 (1398 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: Hewlett-Packard HP EliteBook 2760p ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=81ff9b66-4d33-49d5-a76f-cf1418c3e354 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: Upgraded to xenial on 2016-08-06 (8 days ago) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SOU Ver. F.50 dmi.board.name: 162A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 05.40 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SOUVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook2760p:pvrA0005F02:rvnHewlett-Packard:rn162A:rvrKBCVersion05.40:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2760p dmi.product.version: A0005F02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613134/+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 1613134] [NEW] wacom touch screen does not recognize finger touch
Public bug reported: After Updating to Xenail, the touch screen does not recognize finger touch as input, stylus and eraser are still recognized. This bug affects the Wacom Serial Penabled 2FG Touchscreen, which is built into the HP EliteBook 2760p and the Lenovo Thinkpad X201. It is already reported for other linux distributions. See bugreports: archlinux: https://bbs.archlinux.org/viewtopic.php?id=215014 linux kernel: https://bugzilla.kernel.org/show_bug.cgi?id=120011 xsetwacom lists the devices: Wacom Serial Penabled 2FG Touchscreen Pen stylusid: 13 type: STYLUS Wacom Serial Penabled 2FG Touchscreen Finger touch id: 14 type: TOUCH Wacom Serial Penabled 2FG Touchscreen Pen eraserid: 16 type: ERASER 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: littlelion 4149 F pulseaudio CurrentDesktop: Unity Date: Mon Aug 15 02:32:09 2016 HibernationDevice: RESUME=UUID=46ec6e40-eed3-4377-b3e1-4eed675fba2e InstallationDate: Installed on 2012-10-16 (1398 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: Hewlett-Packard HP EliteBook 2760p ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=81ff9b66-4d33-49d5-a76f-cf1418c3e354 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: Upgraded to xenial on 2016-08-06 (8 days ago) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SOU Ver. F.50 dmi.board.name: 162A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 05.40 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SOUVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook2760p:pvrA0005F02:rvnHewlett-Packard:rn162A:rvrKBCVersion05.40:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2760p dmi.product.version: A0005F02 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613134 Title: wacom touch screen does not recognize finger touch Status in linux package in Ubuntu: Confirmed Bug description: After Updating to Xenail, the touch screen does not recognize finger touch as input, stylus and eraser are still recognized. This bug affects the Wacom Serial Penabled 2FG Touchscreen, which is built into the HP EliteBook 2760p and the Lenovo Thinkpad X201. It is already reported for other linux distributions. See bugreports: archlinux: https://bbs.archlinux.org/viewtopic.php?id=215014 linux kernel: https://bugzilla.kernel.org/show_bug.cgi?id=120011 xsetwacom lists the devices: Wacom Serial Penabled 2FG Touchscreen Pen stylus id: 13 type: STYLUS Wacom Serial Penabled 2FG Touchscreen Finger touchid: 14 type: TOUCH Wacom Serial Penabled 2FG Touchscreen Pen eraser id: 16 type: ERASER 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: littlelion 4149 F pulseaudio CurrentDesktop: Unity Date: Mon Aug 15 02:32:09 2016 HibernationDevice: RESUME=UUID=46ec6e40-eed3-4377-b3e1-4eed675fba2e InstallationDate: Installed on 2012-10-16 (1398 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: Hewlett-Packard HP EliteBook 2760p ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=81ff9b66-4d33-49d5-a76f-cf1418c3e354 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: Upgraded to xenial on 2016-08-06 (8 days ago) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SOU Ver. F.50 dmi.board.name: 162A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 05.40 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias:
[Kernel-packages] [Bug 1242321] Re: USB 3.0 Harddrive not recognised
Hi, The command 'sudo lsusb -v' do not solve the problem. The problem persist... It works just only one time in the USB 3.0 input, but once disconnected and re-connected, Ubuntu no longer recognizes it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1242321 Title: USB 3.0 Harddrive not recognised Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu is not recognising any device plugged into any USB 3.0 ports. Sometimes Ubuntu will freeze for a few seconds when you plug something into a USB 3.0 port; when Ubuntu comes out of the freeze, the device is still NOT recognised. No problems with USB 2.0 ports and devices. The USB 3.0 on this computer only works in Windows 7 (I'm dual booting Ubuntu 13.10 and Windows 7, both are 64-bit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242321/+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 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Had several other runs of success. I would like to see runs from others as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: memory_stress_ng, as part of server certification is failing for IBM Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is defined by the test locking up the server in an unrecoverable state which only a reboot will fix. I will be attaching screen and kern logs for the failures and a successful run on 14.04 on the same server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+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 1479136] Re: [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards
Same problem on RV710/M92. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1479136 Title: [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu-Mate 14.04.2 This is what I get if I run a kernel newer than 3.13: https://www.youtube.com/watch?v=nx2-Fvihzxg sorry for the link, I just don't know how to describe these artefacts verbally. (a storm of small horizontal moving blips from right to left ??) Those artefacts appear as soon as new kernel is selected in GRUB, and remain during the whole session. The lastest kernel (from the main repository that is) working without artifacts is v3.13.0.59. All later kernels have artifacts. All later kernels also are either "-utopic" or "-vivid" instead of "-trusty", but I do not know if it is related. GPU: Mobility Radeon HD 3200 (RS780M) System: Ubuntu Mate 14.04.2 32-bit Kernels tested: 3.13.0.59 (and earlier) , 3.16.0.45 , 3.19.0.25 Only 3.13.0.59 (and earlier) are without problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479136/+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 1613111] 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/1613111 Title: Lenovo Flex 3-1580 (80R4) Intel Backlight Issues Status in linux package in Ubuntu: Confirmed Bug description: This laptop suffers from the same issue as just about every Intel laptop I've used. xbacklight will not adjust brightness unless acpi_backlight=none is set in /etc/default/grub and the grub configuration rebuilt to use it as a kernel command line option. As a separate but related issue, the backlight keys do not work at all for this laptop, and I haven't yet figured out a solution for that. 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 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: karen 3647 F pulseaudio CurrentDesktop: GNOME Date: Sun Aug 14 16:14:31 2016 HibernationDevice: RESUME=UUID=94e950bd-4474-40e8-93c8-d9fb78cffee3 InstallationDate: Installed on 2016-08-12 (2 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f3:2089 Elan Microelectronics Corp. Bus 001 Device 002: ID 04f2:b50f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80R4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=eebf5f5f-0e70-4f2c-ae02-0a3d2218ea40 ro rootflags=subvol=@ quiet splash acpi_osi=Linux acpi_backlight=none 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: 05/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN28WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Flex 3-1580 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Flex 3-1580 dmi.modalias: dmi:bvnLENOVO:bvrD3CN28WW:bd05/09/2016:svnLENOVO:pn80R4:pvrFlex3-1580:rvnLENOVO:rnFlex3-1580:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrFlex3-1580: dmi.product.name: 80R4 dmi.product.version: Flex 3-1580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613111/+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 1613111] [NEW] Lenovo Flex 3-1580 (80R4) Intel Backlight Issues
Public bug reported: This laptop suffers from the same issue as just about every Intel laptop I've used. xbacklight will not adjust brightness unless acpi_backlight=none is set in /etc/default/grub and the grub configuration rebuilt to use it as a kernel command line option. As a separate but related issue, the backlight keys do not work at all for this laptop, and I haven't yet figured out a solution for that. 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 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: karen 3647 F pulseaudio CurrentDesktop: GNOME Date: Sun Aug 14 16:14:31 2016 HibernationDevice: RESUME=UUID=94e950bd-4474-40e8-93c8-d9fb78cffee3 InstallationDate: Installed on 2016-08-12 (2 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f3:2089 Elan Microelectronics Corp. Bus 001 Device 002: ID 04f2:b50f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80R4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=eebf5f5f-0e70-4f2c-ae02-0a3d2218ea40 ro rootflags=subvol=@ quiet splash acpi_osi=Linux acpi_backlight=none 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: 05/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN28WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Flex 3-1580 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Flex 3-1580 dmi.modalias: dmi:bvnLENOVO:bvrD3CN28WW:bd05/09/2016:svnLENOVO:pn80R4:pvrFlex3-1580:rvnLENOVO:rnFlex3-1580:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrFlex3-1580: dmi.product.name: 80R4 dmi.product.version: Flex 3-1580 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Summary changed: - Lenovo Flex Intel Backlight Issues + Lenovo Flex 3-1580 (80R4) Intel Backlight Issues -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613111 Title: Lenovo Flex 3-1580 (80R4) Intel Backlight Issues Status in linux package in Ubuntu: New Bug description: This laptop suffers from the same issue as just about every Intel laptop I've used. xbacklight will not adjust brightness unless acpi_backlight=none is set in /etc/default/grub and the grub configuration rebuilt to use it as a kernel command line option. As a separate but related issue, the backlight keys do not work at all for this laptop, and I haven't yet figured out a solution for that. 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 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: karen 3647 F pulseaudio CurrentDesktop: GNOME Date: Sun Aug 14 16:14:31 2016 HibernationDevice: RESUME=UUID=94e950bd-4474-40e8-93c8-d9fb78cffee3 InstallationDate: Installed on 2016-08-12 (2 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f3:2089 Elan Microelectronics Corp. Bus 001 Device 002: ID 04f2:b50f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80R4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=eebf5f5f-0e70-4f2c-ae02-0a3d2218ea40 ro rootflags=subvol=@ quiet splash acpi_osi=Linux acpi_backlight=none vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic
[Kernel-packages] [Bug 1613106] 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/1613106 Title: Sony VAIO PCG-61A12L (VPCEG16FM) Intel Backlight Issue Status in linux package in Ubuntu: Confirmed Bug description: The backlight for this model cannot be modified by the backlight keys unless a GRUB configuration is built with acpi_backlight=none set in /etc/default/grub. 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/pcmC0D0p: mmstick3054 F...m pulseaudio /dev/snd/controlC0: mmstick3054 F pulseaudio CurrentDesktop: GNOME Date: Sun Aug 14 15:43:13 2016 HibernationDevice: RESUME=UUID=43c727dc-4258-4b8f-b38d-ac0aaa416526 InstallationDate: Installed on 2016-08-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: Sony Corporation VPCEG16FM 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=/@/boot/vmlinuz-4.4.0-34-generic root=UUID=4001663d-ba36-4c89-a89a-bb248d1d261c ro rootflags=subvol=@ quiet splash acpi_osi=Linux acpi_backlight=none video.use_native_backlight=1 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: 05/02/2011 dmi.bios.vendor: INSYDE dmi.bios.version: R0210Z8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR0210Z8:bd05/02/2011:svnSonyCorporation:pnVPCEG16FM:pvrC900R1KJ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCEG16FM dmi.product.version: C900R1KJ dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613106/+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 1613107] 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/1613107 Title: Lenovo Flex ALPS GlidePoint Touchpad Issues Status in linux package in Ubuntu: Confirmed Bug description: The vertical sensitivity is too low, while the horizontal sensitivity is too high, causing for a very elongated oval shape when drawing a circle on the touchpad, among many other issues with the touchpad behavior out of the box. 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 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: karen 12660 F pulseaudio CurrentDesktop: GNOME Date: Sun Aug 14 15:44:42 2016 HibernationDevice: RESUME=UUID=94e950bd-4474-40e8-93c8-d9fb78cffee3 InstallationDate: Installed on 2016-08-12 (2 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 004: ID 04f3:2089 Elan Microelectronics Corp. Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80R4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=eebf5f5f-0e70-4f2c-ae02-0a3d2218ea40 ro rootflags=subvol=@ 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: 05/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN28WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Flex 3-1580 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Flex 3-1580 dmi.modalias: dmi:bvnLENOVO:bvrD3CN28WW:bd05/09/2016:svnLENOVO:pn80R4:pvrFlex3-1580:rvnLENOVO:rnFlex3-1580:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrFlex3-1580: dmi.product.name: 80R4 dmi.product.version: Flex 3-1580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613107/+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 1613107] [NEW] Lenovo Flex ALPS GlidePoint Touchpad Issues
Public bug reported: The vertical sensitivity is too low, while the horizontal sensitivity is too high, causing for a very elongated oval shape when drawing a circle on the touchpad, among many other issues with the touchpad behavior out of the box. 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 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: karen 12660 F pulseaudio CurrentDesktop: GNOME Date: Sun Aug 14 15:44:42 2016 HibernationDevice: RESUME=UUID=94e950bd-4474-40e8-93c8-d9fb78cffee3 InstallationDate: Installed on 2016-08-12 (2 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 004: ID 04f3:2089 Elan Microelectronics Corp. Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80R4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=eebf5f5f-0e70-4f2c-ae02-0a3d2218ea40 ro rootflags=subvol=@ 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: 05/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN28WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Flex 3-1580 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Flex 3-1580 dmi.modalias: dmi:bvnLENOVO:bvrD3CN28WW:bd05/09/2016:svnLENOVO:pn80R4:pvrFlex3-1580:rvnLENOVO:rnFlex3-1580:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrFlex3-1580: dmi.product.name: 80R4 dmi.product.version: Flex 3-1580 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613107 Title: Lenovo Flex ALPS GlidePoint Touchpad Issues Status in linux package in Ubuntu: Confirmed Bug description: The vertical sensitivity is too low, while the horizontal sensitivity is too high, causing for a very elongated oval shape when drawing a circle on the touchpad, among many other issues with the touchpad behavior out of the box. 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 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: karen 12660 F pulseaudio CurrentDesktop: GNOME Date: Sun Aug 14 15:44:42 2016 HibernationDevice: RESUME=UUID=94e950bd-4474-40e8-93c8-d9fb78cffee3 InstallationDate: Installed on 2016-08-12 (2 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 004: ID 04f3:2089 Elan Microelectronics Corp. Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80R4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=eebf5f5f-0e70-4f2c-ae02-0a3d2218ea40 ro rootflags=subvol=@ 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: 05/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN28WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Flex 3-1580 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Flex 3-1580 dmi.modalias:
[Kernel-packages] [Bug 1613106] [NEW] Sony VAIO PCG-61A12L (VPCEG16FM) Intel Backlight Issue
Public bug reported: The backlight for this model cannot be modified by the backlight keys unless a GRUB configuration is built with acpi_backlight=none set in /etc/default/grub. 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/pcmC0D0p: mmstick3054 F...m pulseaudio /dev/snd/controlC0: mmstick3054 F pulseaudio CurrentDesktop: GNOME Date: Sun Aug 14 15:43:13 2016 HibernationDevice: RESUME=UUID=43c727dc-4258-4b8f-b38d-ac0aaa416526 InstallationDate: Installed on 2016-08-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: Sony Corporation VPCEG16FM 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=/@/boot/vmlinuz-4.4.0-34-generic root=UUID=4001663d-ba36-4c89-a89a-bb248d1d261c ro rootflags=subvol=@ quiet splash acpi_osi=Linux acpi_backlight=none video.use_native_backlight=1 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: 05/02/2011 dmi.bios.vendor: INSYDE dmi.bios.version: R0210Z8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR0210Z8:bd05/02/2011:svnSonyCorporation:pnVPCEG16FM:pvrC900R1KJ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCEG16FM dmi.product.version: C900R1KJ dmi.sys.vendor: Sony Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Summary changed: - Sony VAIO PCG-61A12L Intel Backlight Issue + Sony VAIO PCG-61A12L (VPCEG16FM) Intel Backlight Issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613106 Title: Sony VAIO PCG-61A12L (VPCEG16FM) Intel Backlight Issue Status in linux package in Ubuntu: New Bug description: The backlight for this model cannot be modified by the backlight keys unless a GRUB configuration is built with acpi_backlight=none set in /etc/default/grub. 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/pcmC0D0p: mmstick3054 F...m pulseaudio /dev/snd/controlC0: mmstick3054 F pulseaudio CurrentDesktop: GNOME Date: Sun Aug 14 15:43:13 2016 HibernationDevice: RESUME=UUID=43c727dc-4258-4b8f-b38d-ac0aaa416526 InstallationDate: Installed on 2016-08-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: Sony Corporation VPCEG16FM 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=/@/boot/vmlinuz-4.4.0-34-generic root=UUID=4001663d-ba36-4c89-a89a-bb248d1d261c ro rootflags=subvol=@ quiet splash acpi_osi=Linux acpi_backlight=none video.use_native_backlight=1 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: 05/02/2011 dmi.bios.vendor: INSYDE dmi.bios.version: R0210Z8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR0210Z8:bd05/02/2011:svnSonyCorporation:pnVPCEG16FM:pvrC900R1KJ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCEG16FM dmi.product.version: C900R1KJ dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1380824] Re: Backlight not working on Samsung ATIV 8 laptop
I always find that setting acpi_backlight=None in /etc/default/grub and then running sudo update-grub && sudo reboot will fix this problem with Intel-based laptops quite easily. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380824 Title: Backlight not working on Samsung ATIV 8 laptop Status in linux package in Ubuntu: Incomplete Bug description: I have a 15" Samsung ATIV Book 8 laptop, np870z5e model from 2013. It features an Intel core-i7 cpu, and integrated Intel Hd4000 video card and also an ATI Radeon video card. According to Backlight debugging page[1], my case is "Backlight control does not work, but there are entries in /sys/class/backlight. " What works: Fn-F2, Fn-F3 keys works(Brightness down, brightness up), shows the brightness notification dialog, and also the /sys/class/backlight/intel_backlight/actual_brightness file changes too. It has no physical effect. It does not have any physical effect (brightness does not change), up until the brightness notification is zero (no bar on it), then the display switches off. raising the brightness switches the display back to the same brightness it was, and still not have any effect to the brightness. Semi works: Powering on the laptop starts with about 60% brightness. If I suspend-resume the laptop, it results 100% brightness. If I unplug the power cord (if it was plugged in when the laptop started), then it results 100% brightness. If I plug the power cord (if it was unplugged when the laptop started), then it results 100% brightness. I can't change the 100% brightness afterwards. What I have tried: a) xorg.conf file: # Fix Backlight issue Section "Device" Identifier "card0" Driver "intel" Option "Backlight" "intel_backlight" BusID "PCI:0:2:0" EndSection No effect. b) Kernel boot parameter in /etc/defaults/grub 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_osi=Linux acpi_backlight=vendor" GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video.use_bios_initial_backlight=0" I tried each one, with a power off - power on cycle, but none of it had any effect. I doublechecked it (after boot), with cat /proc/cmdline. Changing the /sys/class/backlight/intel_backlight/brightness values, has no physical effect, although the file do change (checked with cat). I'm desperately trying to solve this issue, because the screen is always at full brightness, and burns my eyes out. (300cd/m2 screen is extremely bright). Any help is much appreciated. [1]: https://wiki.ubuntu.com/Kernel/Debugging/Backlight ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lama 2528 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 14 00:38:17 2014 InstallationDate: Installed on 2014-01-13 (273 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic.efi.signed root=UUID=ba121a25-b094-49f5-96bf-ade769938060 ro quiet splash video.use_bios_initial_backlight=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-21-generic N/A linux-backports-modules-3.16.0-21-generic N/A linux-firmware 1.135 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-10-08 (5 days ago) dmi.bios.date: 06/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02ADH.008.130604.SK dmi.board.asset.tag: No Asset Tag dmi.board.name: NP870Z5E-X01HU dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02ADH.008.130604.SK:bd06/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP02ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP870Z5E-X01HU:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 870Z5E/880Z5E/680Z5E dmi.product.version: P02ADH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge
** Summary changed: - Kernel 4.4x results in blackscreen - Intel Ivybridge + Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge ** Description changed: When I install Ubuntu 16.04 on my computer the screen goes blank at login. I can blindly login and it boots but I cannot use the display (external monitor through HDMI). I've looked online for an answer to this issue but could not find a solution. However, many people report this issue in forums with the 4.4x kernel. On my main computer, I upgraded from 14.04 to 16.04.1. On this computer I was able to switch back to the 3.13 kernel which *does work*. On the same computer, if I use a 16.04 live CD, it does the same thing. The screen goes blank. UEFI may be part of the issue as well. I have it disabled in bios (set to legacy mode) but when I first boot, it seems to go into UEFI mode first and then, after rebooting with it shows me the list of kernels. I can select the kernel from there but if I use a 4.4x kernel, it blanks out at encryption passphrase screen. There are also people with similar issues on AskUbuntu. Here's some basic HW info. If you require more, please ask. - sudo lshw | head - zbox - description: Notebook - product: ZBOX-ID18 (NA) - vendor: ZOTAC - version: XX - serial: G211X - width: 64 bits - capabilities: smbios-2.7 dmi-2.7 vsyscall32 - configuration: boot=normal chassis=notebook family=NA sku=NA uuid=00020003-0004-0005-0006-000700080009 - *-core - + zbox + description: Notebook + product: ZBOX-ID18 (NA) + vendor: ZOTAC + version: XX + serial: G211X + width: 64 bits + capabilities: smbios-2.7 dmi-2.7 vsyscall32 + configuration: boot=normal chassis=notebook family=NA sku=NA uuid=00020003-0004-0005-0006-000700080009 + *-core sudo lshw -C display - *-display -description: VGA compatible controller -product: 3rd Gen Core processor Graphics Controller -vendor: Intel Corporation -physical id: 2 -bus info: pci@:00:02.0 -version: 09 -width: 64 bits -clock: 33MHz -capabilities: msi pm vga_controller bus_master cap_list rom -configuration: driver=i915 latency=0 -resources: irq:45 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) - + *-display + description: VGA compatible controller + product: 3rd Gen Core processor Graphics Controller + vendor: Intel Corporation + physical id: 2 + bus info: pci@:00:02.0 + version: 09 + width: 64 bits + clock: 33MHz + capabilities: msi pm vga_controller bus_master cap_list rom + configuration: driver=i915 latency=0 + resources: irq:45 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 - --- + --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: rmezger5536 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: user5536 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38 InstallationDate: Installed on 2014-07-23 (743 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313) MachineType: ZOTAC ZBOX-ID18 Package: linux (not installed) ProcEnviron: - LANGUAGE=en_US - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 PulseList: - Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied - No PulseAudio daemon running, or not running as session daemon. + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-3.13.0-92-generic N/A - linux-backports-modules-3.13.0-92-generic N/A - linux-firmware 1.157.2 + linux-restricted-modules-3.13.0-92-generic N/A + linux-backports-modules-3.13.0-92-generic N/A + linux-firmware 1.157.2 RfKill: - + StagingDrivers: rts5139 Tags: xenial staging Uname: Linux 3.13.0-92-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago) UserGroups: - + _MarkForUpload: True dmi.bios.date: 03/13/2014 dmi.bios.vendor: American Megatrends Inc.
[Kernel-packages] [Bug 1574047] Re: Lenovo G50-30 laptop freezes randomly
Christopher M. Penalver (penalvch), My laptop does not start after rebooting with the kernel-4.7.0-999_4.7.0-999.201607302201. What a tag I need to set in that case? ** Tags removed: kernel-fixed-upstream-4.6-rc7 ** Tags added: kernel-bug-exists-upstream-4.6-rc7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574047 Title: Lenovo G50-30 laptop freezes randomly Status in linux package in Ubuntu: Incomplete Bug description: Keyboard or mouse do not work when the system freezes. Have to press power key to shutdown. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lumiza 1614 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 19:17:13 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=00509798-f59d-4d52-9500-f9a446e82c61 InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 80G0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=44eeda32-7284-4e84-91ff-72fe3baefb7a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN47WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN47WW:bd04/16/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574047/+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 1562618] Re: whole OS freezes seemingly randomly
Hi, I've been on holiday, hence the delay in response. In the mean time I have experienced freezes again with both the intel and the rc5 kernel. Still no solution I guess. I will reinstall windoze when I have time and upgrade the SSD firmware as some suggested. Although I already read reports on that not solving the issue, I'll keep trying to find the issue. About bisecting: I read this may not be very useful because of the possibility of multiple bugs causing the freeze. Is it still usefull to do that? I'll keep you posted of my findings. I don't understand why this does not seem to be a problem in Windows and why intel doesn't step in to get this fixed with priority? Guess they want us to buy an AMD chipset next time. cheers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1562618 Title: whole OS freezes seemingly randomly Status in linux package in Ubuntu: Expired Bug description: I had some random freezes of the whole operating system. No caps lock response or terminal switching, nothng. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vincent1714 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 27 23:46:02 2016 HibernationDevice: RESUME=UUID=8180a7b6-a1c0-494a-9f65-99a7b54f6deb InstallationDate: Installed on 2015-11-01 (147 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20332 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=44fb018f-3dbd-4eb6-ab9a-6668de8d13d2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-03-25 (2 days ago) dmi.bios.date: 12/26/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 92CN26WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: AIUU1 dmi.board.vendor: LENOVO dmi.board.version: 31900042STD dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 11 dmi.modalias: dmi:bvnLENOVO:bvr92CN26WW(V1.06):bd12/26/2013:svnLENOVO:pn20332:pvrLenovoYoga211:rvnLENOVO:rnAIUU1:rvr31900042STD:cvnLENOVO:ct10:cvrLenovoYoga211: dmi.product.name: 20332 dmi.product.version: Lenovo Yoga 2 11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562618/+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 1610793] Re: Removing inline decl on include/linux/rcupdate.h file .
I present one patch , todo to solve this issue. ** Patch added: "Tested on linux-4.6.2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1610793/+attachment/4720683/+files/move_rcu_func.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1610793 Title: Removing inline decl on include/linux/rcupdate.h file . Status in linux package in Ubuntu: Confirmed Bug description: On this file inline declaration is used to surpress warnings message when building kernel. My opinion solve warnings message first.Inline declaration is not for surpress warning message. 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: asu4668 F pulseaudio CurrentDesktop: LXDE Date: Mon Aug 8 06:22:49 2016 InstallationDate: Installed on 2016-04-29 (100 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1610793/+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 1527922] Re: Recurrent problem with Wifi in Macbook Air 5, 2 Ubuntu 14.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1527922 Title: Recurrent problem with Wifi in Macbook Air 5,2 Ubuntu 14.04 Status in bcmwl package in Ubuntu: Confirmed Bug description: This is the typical dmesg result: [14901.908048] ERROR @wl_inform_single_bss : cfg80211_inform_bss_frame error [15100.343519] applesmc: send_byte(0x00, 0x0300) fail: 0x40 [15100.343523] applesmc: LKSB: write data fail ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-73.116-generic 3.13.11-ckt30 Uname: Linux 3.13.0-73-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 19 20:42:59 2015 InstallationDate: Installed on 2015-07-03 (168 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1527922/+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 1584456] Re: apparmor denial using ptmx char device
Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584456 Title: apparmor denial using ptmx char device Status in Snappy Launcher: Fix Committed Status in linux package in Ubuntu: Confirmed Bug description: - Finding issues running snaps (hello-world). - Same issue even installing with --devmode. Even running the snap binary as root - Using a custom kernel, this is on an Nvidia Tegra X1 custom board. = ubuntu@localhost:~$ hello-world.echo plop unable to mount '/dev/pts/ptmx'->'/dev/ptmx'. errmsg: Permission denied ubuntu@localhost:~$ sudo hello-world.echo plop unable to mount '/dev/pts/ptmx'->'/dev/ptmx'. errmsg: Permission denied dmesg shows: = [ 302.838046] type=1400 audit(1455208371.989:16): apparmor="DENIED" operation="mount" info="failed mntpnt match" error=-13 parent=911 profile="/usr/bin/ubuntu-core-launcher" name="/dev/ptmx/" pid=912 comm="ubuntu-core-lau" srcname="/dev/pts/ptmx/" flags="rw, bind" [ 308.080449] type=1400 audit(1455208377.229:17): apparmor="DENIED" operation="mount" info="failed mntpnt match" error=-13 parent=914 profile="/usr/bin/ubuntu-core-launcher" name="/dev/ptmx/" pid=915 comm="ubuntu-core-lau" srcname="/dev/pts/ptmx/" flags="rw, bind" This is with the "hello-world" snap installed with "snap install" Output of an ls over the device file: = ubuntu@localhost:~$ ls -lR /dev/ptmx /dev/pts crw-rw-rw- 1 root tty 5, 2 Feb 11 16:28 /dev/ptmx /dev/pts: total 0 c- 1 root root 5, 2 Jan 1 1970 ptmx To manage notifications about this bug go to: https://bugs.launchpad.net/snap-confine/+bug/1584456/+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 1173681] Re: 168c:002b [Asus U32U] asus_nb_wmi AR9285 ath9k not working after updating to Ubuntu 13.04 Raring
I confirm the problem and the workaround, my product_name is K501UX -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1173681 Title: 168c:002b [Asus U32U] asus_nb_wmi AR9285 ath9k not working after updating to Ubuntu 13.04 Raring Status in linux package in Ubuntu: Fix Released Bug description: update: updated the BIOS to the latest version but the problem persists. Booting with the older kernel (latest linux kernel from 12.10) every thing works fine. After upgrading to Raring Ringtail Ubuntu 13.04, with the new kernel, hardware get blocked/disabled and wireless doesn't work: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes 1: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no WORKAROUND - is only applicable to Asus Notebooks/netbooks that use the "asus_nb_wmi" driver: Create and edit asus_nb_wmi.conf file with this command: sudo echo "options asus_nb_wmi wapf=4" | sudo tee /etc/modprobe.d/asus_nb_wmi.conf For more detailed info of the workaround please see: http://ubuntuforums.org/showthread.php?t=2181558 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: x 1822 F pulseaudio CurrentDmesg: [ 370.100280] r8169 :04:00.2 eth1: link up [ 370.100322] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 891.718748] systemd-hostnamed[2649]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! [14119.241628] rtsx_pci :04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. Date: Sat Apr 27 17:31:51 2013 HibernationDevice: RESUME=UUID=e417e9f2-b63e-4b79-9be4-c21f55547205 InstallationDate: Installed on 2012-07-13 (287 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: ASUSTeK Computer Inc. U32U MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=3ad9d88b-a7a5-460f-ba15-a78dd7f2fc94 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-27 (0 days ago) dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U32U.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U32U 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.:bvrU32U.204:bd12/16/2011:svnASUSTeKComputerInc.:pnU32U:pvr1.0:rvnASUSTeKComputerInc.:rnU32U:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U32U 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/1173681/+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 1173681] Re: 168c:002b [Asus U32U] asus_nb_wmi AR9285 ath9k not working after updating to Ubuntu 13.04 Raring
The bug is marked as "fix released" but it's affecting me with all latest updates installed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1173681 Title: 168c:002b [Asus U32U] asus_nb_wmi AR9285 ath9k not working after updating to Ubuntu 13.04 Raring Status in linux package in Ubuntu: Fix Released Bug description: update: updated the BIOS to the latest version but the problem persists. Booting with the older kernel (latest linux kernel from 12.10) every thing works fine. After upgrading to Raring Ringtail Ubuntu 13.04, with the new kernel, hardware get blocked/disabled and wireless doesn't work: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes 1: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no WORKAROUND - is only applicable to Asus Notebooks/netbooks that use the "asus_nb_wmi" driver: Create and edit asus_nb_wmi.conf file with this command: sudo echo "options asus_nb_wmi wapf=4" | sudo tee /etc/modprobe.d/asus_nb_wmi.conf For more detailed info of the workaround please see: http://ubuntuforums.org/showthread.php?t=2181558 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: x 1822 F pulseaudio CurrentDmesg: [ 370.100280] r8169 :04:00.2 eth1: link up [ 370.100322] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 891.718748] systemd-hostnamed[2649]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! [14119.241628] rtsx_pci :04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. Date: Sat Apr 27 17:31:51 2013 HibernationDevice: RESUME=UUID=e417e9f2-b63e-4b79-9be4-c21f55547205 InstallationDate: Installed on 2012-07-13 (287 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: ASUSTeK Computer Inc. U32U MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=3ad9d88b-a7a5-460f-ba15-a78dd7f2fc94 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-27 (0 days ago) dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U32U.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U32U 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.:bvrU32U.204:bd12/16/2011:svnASUSTeKComputerInc.:pnU32U:pvr1.0:rvnASUSTeKComputerInc.:rnU32U:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U32U 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/1173681/+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 1581799] Re: radeon driver hangs : nothing else that static effect on display
So... no way I can solve? Has this bug been reported to upstream yet? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581799 Title: radeon driver hangs : nothing else that static effect on display Status in linux package in Ubuntu: Expired Bug description: Hi, since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard due to drop support of fglrx driver (that was working) and due to radeon opensource driver not working with my VGA. Mine video card: $ lspci -nn | grep VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645] $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) . --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: magowiz4930 F...m pulseaudio /dev/snd/pcmC0D0p: magowiz4930 F...m pulseaudio /dev/snd/controlC0: magowiz4930 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=472405e9-ecbe-44ee-9931-9eedcc0a759a InstallationDate: Installed on 2012-01-03 (1615 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=acd61f09-2fc9-4a54-bf0b-23f0a297d2e4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-26 (40 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare _MarkForUpload: True dmi.bios.date: 12/09/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1003 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F1A55-M LE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1003:bd12/09/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A55-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581799/+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 1548009] Re: ZFS pools should be automatically scrubbed
This works for me "in the wild" (i.e. waiting until today, which was the second Sunday of the month). I had two servers, one with 0.6.5.6-0ubuntu11 and one with 0.6.5.6-0ubuntu12. ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1548009 Title: ZFS pools should be automatically scrubbed Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Committed Bug description: [Impact] Xenial shipped with a cron job to automatically scrub ZFS pools, as desired by many users and as implemented by mdadm for traditional Linux software RAID. Unfortunately, this cron job does not work, because it needs a PATH line for /sbin, where the zpool utility lives. Given the existence of the cron job and various discussions on IRC, etc., users expect that scrubs are happening, when they are not. This means ZFS is not pre-emptively checking for (and correcting) corruption. The odds of disk corruption are admittedly very low, but violating users' expectations of data safety, especially when they've gone out of their way to use a filesystem which touts data safety, is bad. [Test Case] $ truncate -s 1G test.img $ sudo zpool create test `pwd`/test.img $ sudo zpool status test $ sudo vi /etc/cron.d/zfsutils-linux Modify /etc/cron.d/zfsutils-linux to run the cron job in a few minutes (modifying the date range if it's not currently the 8th through the 14th and the "-eq 0" check if it's not currently a Sunday). $ grep zfs /var/log/cron.log Verify in /var/log/cron.log that the job ran. $ sudo zpool status test Expected results: scan: scrub repaired 0 in ... on Actual results: scan: none requested Then, add the PATH line, update the time rules in the cron job, and repeat the test. Now it will work. - OR - The best test case is to leave the cron job file untouched, install the patched package, wait for the second Sunday of the month, and verify with zpool status that a scrub ran. I did this, on Xenial, with the package I built. The debdiff is in comment #11 and was accepted to Yakkety. If someone can get this in -proposed before the 14th, I'll gladly install the actual package from -proposed and make sure it runs correctly on the 14th. [Regression Potential] The patch only touches the cron.d file, which has only one cron job in it. This cron job is completely broken (inoperative) at the moment, so the regression potential is very low. ORIGINAL, PRE-SRU, DESCRIPTION: mdadm automatically checks MD arrays. ZFS should automatically scrub pools too. Scrubbing a pool allows ZFS to detect on-disk corruption and (when the pool has redundancy) correct it. Note that ZFS does not blindly assume the other copy is correct; it will only overwrite bad data with data that is known to be good (i.e. it passes the checksum). I've attached a debdiff which accomplishes this. It builds and installs cleanly. The meat of it is the scrub script I've been using on production systems, both servers and laptops, and recommending in my Ubuntu root- on-ZFS HOWTO, for years, which scrubs all *healthy* pools. If a pool is not healthy, scrubbing it is bad for two reasons: 1) It adds a lot of disk load which could theoretically lead to another failure. We should save that disk load for resilvering. 2) Performance is already less on a degraded pool and scrubbing can make that worse, even though scrubs are throttled. Arguably, I might be being too conservative here, but the marginal benefit of scrubbing a *degraded* pool is pretty minimal as pools should not be left degraded for very long. The cron.d in this patch scrubs on the second Sunday of the month. mdadm scrubs on the first Sunday of the month. This way, if a system has both MD and ZFS pools, the load doesn't all happen at the same time. If the system doesn't have both types, it shouldn't really matter which week. If you'd rather make it the same week as MD, I see no problem with that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1548009/+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 1587093] Re: "Reached target shutdown" message seen, but laptop won't turn off, just hangs and needs the laptop's button.
** Package changed: systemd (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1587093 Title: "Reached target shutdown" message seen, but laptop won't turn off, just hangs and needs the laptop's button. Status in linux package in Ubuntu: Fix Released 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/1587093/+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 1613027] 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/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Hopefully I'm reporting this in the correct area/group. Sorry if not. After upgrading to 16.04, my scanner is no longer detected by xsane (and other scan apps.) The model is 'Epson WF-3520' multi-function and is connected wirelessly to the network. The problem occurs on all my computers: A Dell 64 bit desktop, An Asus 64 bit laptop, A Medion 32 bit laptop. I've upgraded to the latest software released by the manufacturer on 2 computers, but it makes no difference. Printing works OK and also the scanner is detected if I connect using a USB cable (a second printer is installed though). The problem only occurs using the 'linux-image-4.4.0...' series of kernels. If I boot with any of the previous kernels available, 'linux-image-4.2.0...' or 'linux-image-3.19.0...' everything works OK. I am able to ping the scanner. I've tried a number of suggested fixes from searching around various forums, although many of these relate to 'back-end' scanners connected to a host for network access which is not applicable as mine is connected directly to the network. In any case none have worked. I have tried the following: . Removing all manufacturer software and /usr/sane.d/epkowa.conf . Comment out all entries in the /usr/sane.d/dll (Back-end related) . Comment out all entries in the /usr/sane.d/dll.conf.conf except 'net' and adding 'epkowa' (Back-end related) . Disable the firewall (ufw) . Specifically adding a port to use (1865) (ie. net 192.1... 1865 . Linking the libraries in /usr/lib/sane to /usr/lib/x86_64-linux-gnu/sane Other than that I'm at a loss and sticking with older kernels. Regards. 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: tony 4520 F pulseaudio /dev/snd/controlC1: tony 4520 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 14 16:37:16 2016 HibernationDevice: RESUME=UUID=762f657a-d174-4173-b09d-52d580c09a91 InstallationDate: Installed on 2013-10-01 (1047 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK Computer Inc. N71Jq ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=dea23950-d6b3-498c-abba-a94513b58579 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: Upgraded to xenial on 2016-07-30 (14 days ago) dmi.bios.date: 12/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N71Jq.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N71Jq 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.:bvrN71Jq.204:bd12/24/2009:svnASUSTeKComputerInc.:pnN71Jq:pvr1.0:rvnASUSTeKComputerInc.:rnN71Jq:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N71Jq 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/1613027/+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 1587093] [NEW] "Reached target shutdown" message seen, but laptop won't turn off, just hangs and needs the laptop's button.
You have been subscribed to a public bug: 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. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: xenial -- "Reached target shutdown" message seen, but laptop won't turn off, just hangs and needs the laptop's button. https://bugs.launchpad.net/bugs/1587093 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
After the last update my asus x540sa notebook seems to shut down and restart properly. Closing the lid still doesn't suspend the system though. -- You 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 1613027] [NEW] Network scanner not detected by xsane after upgrade to 16.04
Public bug reported: Hopefully I'm reporting this in the correct area/group. Sorry if not. After upgrading to 16.04, my scanner is no longer detected by xsane (and other scan apps.) The model is 'Epson WF-3520' multi-function and is connected wirelessly to the network. The problem occurs on all my computers: A Dell 64 bit desktop, An Asus 64 bit laptop, A Medion 32 bit laptop. I've upgraded to the latest software released by the manufacturer on 2 computers, but it makes no difference. Printing works OK and also the scanner is detected if I connect using a USB cable (a second printer is installed though). The problem only occurs using the 'linux-image-4.4.0...' series of kernels. If I boot with any of the previous kernels available, 'linux-image-4.2.0...' or 'linux-image-3.19.0...' everything works OK. I am able to ping the scanner. I've tried a number of suggested fixes from searching around various forums, although many of these relate to 'back-end' scanners connected to a host for network access which is not applicable as mine is connected directly to the network. In any case none have worked. I have tried the following: . Removing all manufacturer software and /usr/sane.d/epkowa.conf . Comment out all entries in the /usr/sane.d/dll (Back-end related) . Comment out all entries in the /usr/sane.d/dll.conf.conf except 'net' and adding 'epkowa' (Back-end related) . Disable the firewall (ufw) . Specifically adding a port to use (1865) (ie. net 192.1... 1865 . Linking the libraries in /usr/lib/sane to /usr/lib/x86_64-linux-gnu/sane Other than that I'm at a loss and sticking with older kernels. Regards. 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: tony 4520 F pulseaudio /dev/snd/controlC1: tony 4520 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 14 16:37:16 2016 HibernationDevice: RESUME=UUID=762f657a-d174-4173-b09d-52d580c09a91 InstallationDate: Installed on 2013-10-01 (1047 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK Computer Inc. N71Jq ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=dea23950-d6b3-498c-abba-a94513b58579 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: Upgraded to xenial on 2016-07-30 (14 days ago) dmi.bios.date: 12/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N71Jq.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N71Jq 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.:bvrN71Jq.204:bd12/24/2009:svnASUSTeKComputerInc.:pnN71Jq:pvr1.0:rvnASUSTeKComputerInc.:rnN71Jq:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N71Jq dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** 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/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 Status in linux package in Ubuntu: New Bug description: Hopefully I'm reporting this in the correct area/group. Sorry if not. After upgrading to 16.04, my scanner is no longer detected by xsane (and other scan apps.) The model is 'Epson WF-3520' multi-function and is connected wirelessly to the network. The problem occurs on all my computers: A Dell 64 bit desktop, An Asus 64 bit laptop, A Medion 32 bit laptop. I've upgraded to the latest software released by the manufacturer on 2 computers, but it makes no difference. Printing works OK and also the scanner is detected if I connect using a USB cable (a second printer is installed though). The problem only occurs using the 'linux-image-4.4.0...' series of kernels. If I boot with any of the previous kernels available, 'linux-image-4.2.0...' or 'linux-image-3.19.0...' everything works OK. I am able to ping the scanner. I've tried a number of suggested fixes from searching around various forums, although many of these relate to 'back-end' scanners connected to a host for network access which is not applicable as mine is connected directly to the network. In any case none have worked. I have tried the following: . Removing all manufacturer software and /usr/sane.d/epkowa.conf .
[Kernel-packages] [Bug 1612560] Re: 4.8 rc1 segfault : unchecked MSR access error
Issue still be worked out upstream http://www.gossamer-threads.com/lists/linux/kernel/2495437 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1612560 Title: 4.8 rc1 segfault : unchecked MSR access error Status in linux package in Ubuntu: Confirmed Bug description: Tested the 4.8 rc1 kernel from the unstable ppa on yakkety 64 bits, and get some issues (not fatal) Linux version 4.8.0-0-generic (buildd@lgw01-12) (gcc version 6.1.1 20160805 (Ubuntu 6.1.1-11ubuntu12) ) #1-Ubuntu SMP Thu Aug 11 17:03:49 UTC 2016 (Ubuntu 4.8.0-0.1-generic 4.8.0 rc1 ) NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. kernel: unchecked MSR access error: WRMSR to 0xdf (tried to write 0x00ff8001) at rIP: 0x96262124 (native_write_msr+0x4/0x20) kernel: 96206a7d 9a083a40d000 9a083fc0a380 001e kernel: 96206b53 9a083a40d000 kernel: 9a083fc0a380 96206e71 d61bffc01de0 kernel: Call Trace: kernel: [] ? x86_perf_event_set_period+0xcd/0x160 kernel: [] ? x86_pmu_start+0x43/0xf0 kernel: [] ? x86_pmu_enable+0x271/0x2e0 kernel: [] ? event_function+0x9d/0x160 kernel: [] ? perf_cgroup_attach+0x70/0x70 kernel: [] ? remote_function+0x3b/0x40 kernel: [] ? generic_exec_single+0x98/0x100 kernel: [] ? smp_call_function_single+0xdc/0x180 kernel: [] ? vprintk_emit+0x35a/0x520 kernel: [] ? event_function_call+0x115/0x120 kernel: [] ? perf_mux_hrtimer_handler+0x260/0x260 kernel: [] ? cpu_clock_event_read+0x30/0x30 kernel: [] ? perf_event_enable+0x15/0x30 kernel: [] ? watchdog_enable+0x155/0x1f0 kernel: [] ? smpboot_thread_fn+0x9c/0x180 kernel: [] ? __smpboot_create_thread.part.1+0xe0/0xe0 kernel: [] ? kthread+0xcd/0xf0 kernel: [] ? ret_from_fork+0x1f/0x40 kernel: [] ? kthread_create_on_node+0x1e0/0x1e0 --- ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem2982 F pulseaudio /dev/snd/pcmC0D0p: oem2982 F...m pulseaudio /dev/snd/controlC0: oem2982 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. lono wireless extensions. eth1 no wireless extensions. Lsusb: Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-0-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro ProcVersionSignature: Ubuntu 4.8.0-0.1-generic 4.8.0-rc1 RelatedPackageVersions: linux-restricted-modules-4.8.0-0-generic N/A linux-backports-modules-4.8.0-0-generic N/A linux-firmware 1.159 RfKill: Can't open RFKILL control device: No such file or directory Tags: yakkety Uname: Linux 4.8.0-0-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe 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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612560/+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 1612560] Re: 4.8 rc1 segfault : unchecked MSR access error
** Summary changed: - 4.8 rc1 segfault + 4.8 rc1 segfault : unchecked MSR access error -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1612560 Title: 4.8 rc1 segfault : unchecked MSR access error Status in linux package in Ubuntu: Confirmed Bug description: Tested the 4.8 rc1 kernel from the unstable ppa on yakkety 64 bits, and get some issues (not fatal) Linux version 4.8.0-0-generic (buildd@lgw01-12) (gcc version 6.1.1 20160805 (Ubuntu 6.1.1-11ubuntu12) ) #1-Ubuntu SMP Thu Aug 11 17:03:49 UTC 2016 (Ubuntu 4.8.0-0.1-generic 4.8.0 rc1 ) NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. kernel: unchecked MSR access error: WRMSR to 0xdf (tried to write 0x00ff8001) at rIP: 0x96262124 (native_write_msr+0x4/0x20) kernel: 96206a7d 9a083a40d000 9a083fc0a380 001e kernel: 96206b53 9a083a40d000 kernel: 9a083fc0a380 96206e71 d61bffc01de0 kernel: Call Trace: kernel: [] ? x86_perf_event_set_period+0xcd/0x160 kernel: [] ? x86_pmu_start+0x43/0xf0 kernel: [] ? x86_pmu_enable+0x271/0x2e0 kernel: [] ? event_function+0x9d/0x160 kernel: [] ? perf_cgroup_attach+0x70/0x70 kernel: [] ? remote_function+0x3b/0x40 kernel: [] ? generic_exec_single+0x98/0x100 kernel: [] ? smp_call_function_single+0xdc/0x180 kernel: [] ? vprintk_emit+0x35a/0x520 kernel: [] ? event_function_call+0x115/0x120 kernel: [] ? perf_mux_hrtimer_handler+0x260/0x260 kernel: [] ? cpu_clock_event_read+0x30/0x30 kernel: [] ? perf_event_enable+0x15/0x30 kernel: [] ? watchdog_enable+0x155/0x1f0 kernel: [] ? smpboot_thread_fn+0x9c/0x180 kernel: [] ? __smpboot_create_thread.part.1+0xe0/0xe0 kernel: [] ? kthread+0xcd/0xf0 kernel: [] ? ret_from_fork+0x1f/0x40 kernel: [] ? kthread_create_on_node+0x1e0/0x1e0 --- ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem2982 F pulseaudio /dev/snd/pcmC0D0p: oem2982 F...m pulseaudio /dev/snd/controlC0: oem2982 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. lono wireless extensions. eth1 no wireless extensions. Lsusb: Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-0-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro ProcVersionSignature: Ubuntu 4.8.0-0.1-generic 4.8.0-rc1 RelatedPackageVersions: linux-restricted-modules-4.8.0-0-generic N/A linux-backports-modules-4.8.0-0-generic N/A linux-firmware 1.159 RfKill: Can't open RFKILL control device: No such file or directory Tags: yakkety Uname: Linux 4.8.0-0-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe 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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
** Package changed: systemd (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/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] [NEW] Poweroff or reboot hangs. Laptop won't shutdown. 16.04
You have been subscribed to a public bug: 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. ** Affects: linux (Ubuntu) Importance: Critical Assignee: damiano (damiano1996) Status: Confirmed ** Tags: xenial -- Poweroff or reboot hangs. Laptop won't shutdown. 16.04 https://bugs.launchpad.net/bugs/1594023 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
