[Kernel-packages] [Bug 1591289] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 10, failed: 2
tests ran: 10, failed: 2; http://kernel.ubuntu.com/testing/4.4.0-25.44/ms10-35-mcdivittB0-kernel__4.4.0-25.44__2016-06-16_05-41-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/1591289 Title: linux: 4.4.0-25.44 -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: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1591289] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 10, failed: 2
tests ran: 10, failed: 2; http://kernel.ubuntu.com/testing/4.4.0-25.44/ms10-34-mcdivittB0-kernel__4.4.0-25.44__2016-06-16_05-43-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/1591289 Title: linux: 4.4.0-25.44 -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: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1593124] [NEW] Palm rejection for MS Precision Touchpad causes touchpad unusable
Public bug reported: Sometimes touchpad doesn't work properly after palm is rejected. The pointer either jumping around (described on bugzilla[1]) or doesn't move at all (in our cases). This problem is introduced with commit: 25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm rejection if device implements confidence usage), by reverting it the touchpad can work properly. We also contacted with Synaptics, and they provided a workaround to fix this issue. Not sure if the workaround will be upstreamed and needs to keep co-working with them. Commit 25a84db applies to Xenial and Yakkety so only these two release were affected. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Phidias (phidias-chiang) Status: New ** Tags: originate-from-1580427 somerville 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/1593124 Title: Palm rejection for MS Precision Touchpad causes touchpad unusable Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: Sometimes touchpad doesn't work properly after palm is rejected. The pointer either jumping around (described on bugzilla[1]) or doesn't move at all (in our cases). This problem is introduced with commit: 25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm rejection if device implements confidence usage), by reverting it the touchpad can work properly. We also contacted with Synaptics, and they provided a workaround to fix this issue. Not sure if the workaround will be upstreamed and needs to keep co-working with them. Commit 25a84db applies to Xenial and Yakkety so only these two release were affected. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1593124/+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 1590655] Re: [Hyper-V] storvsc messages for CD-ROM medium not present tray closed
I verified the lp1590655 test kernel and the storvsc bulk messages are no longer showing up. Please continue with merging this patch in all current releases. Thanks Joe! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1590655 Title: [Hyper-V] storvsc messages for CD-ROM medium not present tray closed Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Vivid: Triaged Status in linux source package in Wily: Triaged Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Triaged Bug description: The below can be seen with any distribution running on a Generation 2 VM. There is a verified patch for this, however it has been scheduled only for the 4.8 scsi-queue. As it a small patch which has been verified by KY and also accepted in the patch queue, will you be able to include this as part of the 16.04 rebase to 4.6, and as well for 14.04 and 15.10? Patch can be found at https://patchwork.kernel.org/patch/9131929/ Description of problem: When starting and shutting down a Gen2 VM, at least 20-30 messages are recorded for storvsc with the below sample: [storvsc] Sense Key : Not Ready [current] [storvsc] Add. Sense: Medium not present - tray closed Steps to Reproduce: 1. create a Generation2 VM 2. start VM and observe the system logs 3. multiple messages for the cd-rom are recorded from storvsc Actual results: even without a CD-ROM unit attached, the messages would appear. Having an ISO attached or not would still produce the same messages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590655/+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 1592930] Re: failures building userspace packages that include ethtool.h
** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592930 Title: failures building userspace packages that include ethtool.h Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Current -proposed kernel produces errors when building userspace packages that require ethtool.h from linux-headers. This was noted by Iain Lane when building systemd with this kernel: In file included from ../src/udev/net/ethtool-util.c:22:0: /usr/include/linux/ethtool.h: In function ‘ethtool_validate_speed’: /usr/include/linux/ethtool.h:1321:18: error: ‘INT_MAX’ undeclared (first use in this function) return speed <= INT_MAX || speed == SPEED_UNKNOWN; ^ /usr/include/linux/ethtool.h:1321:18: note: each undeclared identifier is reported only once for each function it appears in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592930/+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 1592923] Re: Display artificats when using external display with Ubuntu 16.04 on Lenovo X1 Carbon (Broadwell)
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.13-xenial/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => 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/1592923 Title: Display artificats when using external display with Ubuntu 16.04 on Lenovo X1 Carbon (Broadwell) Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: After upgrading this laptop from 14.04 (LTS-Wily X & Kernel stack) to 16.04, I am no longer able to usefully use external displays. There are artifacts on both displays that get worse with mouse movement. Upgrading to a 4.7rc3 mainline kernel from the Ubuntu kernel PPA fixed the problem. (I'm using the mini-DP port on the laptop and have tried several different converters and monitors.) --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: helen 2118 F pulseaudio /dev/snd/controlC0: helen 2118 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (54 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: LENOVO 20BS0061ZA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-25-generic.efi.signed root=UUID=fc75b093-6f8c-4b7e-946c-71df6814ab6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13 RelatedPackageVersions: linux-restricted-modules-4.4.0-25-generic N/A linux-backports-modules-4.4.0-25-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-25-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-06-14 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/13/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET32W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BS0061ZA dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BS0061ZA:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS0061ZA:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BS0061ZA dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592923/+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 1592813] Re: System freezes if memory is full
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7-rc1 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc3-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592813 Title: System freezes if memory is full Status in linux package in Ubuntu: Incomplete Bug description: If one or more process becames near of using 100% of system ram memory, Ubuntu will completely freeze. It is not possible even to switch to a VT to try to kill one or more procs. First I tought it could be some problem with swap and I tried to disable my swap partition, but didn't make a difference. Before using Ubuntu 14.04 64bit, I was using 8.04 32bits and this problem never happende with it. If the memory was near 100%, new apps would crash when trying to malloc, but the system would still be rock solid allowing me to close running apps to free memory. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-46-generic 3.13.0-46.79 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: renato 2391 F pulseaudio CurrentDesktop: MATE Date: Wed Jun 15 09:52:27 2016 HibernationDevice: RESUME=UUID=4f544f74-0b59-4895-959b-9a2e60ce4485 InstallationDate: Installed on 2015-03-10 (462 days ago) InstallationMedia: Ubuntu MATE 14.04.1 "Trusty Tahr" - final amd64 (2014) MachineType: ASUSTeK Computer Inc. M51Sn ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=818b643f-29ae-4599-8039-470975a54543 ro biosdevname=0 quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-46-generic N/A linux-backports-modules-3.13.0-46-generic N/A linux-firmware 1.127.22 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M51Sn 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.:bvr305:bd05/04/2008:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M51Sn 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/1592813/+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 1592917] Re: do-release-upgrade stuck when dealing with apparmor profile for cupsd
** Package changed: linux (Ubuntu) => apparmor (Ubuntu) ** Changed in: apparmor (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592917 Title: do-release-upgrade stuck when dealing with apparmor profile for cupsd Status in apparmor package in Ubuntu: New Bug description: On an up-to-date 14.04.x, I started do-release-upgrade -d to upgrade to ubuntu 16.04. At about 50% of the installation of packages, do-release-upgrade stucks in the following manner: - cpu runs at 0%~ and there is no disk I/O for about 15 minutes now - do-release-upgrade does not terminate, and there is no visible progress at all. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 3220 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=28eded29-f9e6-44b5-9e54-c4dd60c8e3cd InstallationDate: Installed on 2014-11-29 (564 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0c45:6419 Microdia Integrated Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E5510 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-38-generic root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.2.0-38-generic N/A linux-backports-modules-4.2.0-38-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.2.0-38-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-06-15 (0 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 023HKR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1592917/+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 1593124] Re: Palm rejection for MS Precision Touchpad causes touchpad unusable
** Tags added: originate-from-1580427 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1593124 Title: Palm rejection for MS Precision Touchpad causes touchpad unusable Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: Sometimes touchpad doesn't work properly after palm is rejected. The pointer either jumping around (described on bugzilla[1]) or doesn't move at all (in our cases). This problem is introduced with commit: 25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm rejection if device implements confidence usage), by reverting it the touchpad can work properly. We also contacted with Synaptics, and they provided a workaround to fix this issue. Not sure if the workaround will be upstreamed and needs to keep co-working with them. Commit 25a84db applies to Xenial and Yakkety so only these two release were affected. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1593124/+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 1591289] onza (amd64) - tests ran: 30, failed: 1
tests ran: 30, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-25.44/onza__4.4.0-25.44__2016-06-16_06-15-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/1591289 Title: linux: 4.4.0-25.44 -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: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1593124] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1593124 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/1593124 Title: Palm rejection for MS Precision Touchpad causes touchpad unusable Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Sometimes touchpad doesn't work properly after palm is rejected. The pointer either jumping around (described on bugzilla[1]) or doesn't move at all (in our cases). This problem is introduced with commit: 25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm rejection if device implements confidence usage), by reverting it the touchpad can work properly. We also contacted with Synaptics, and they provided a workaround to fix this issue. Not sure if the workaround will be upstreamed and needs to keep co-working with them. Commit 25a84db applies to Xenial and Yakkety so only these two release were affected. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1593124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1592566] Re: can't write to a BTRFS disk with my powermac
I installed Lubuntu a month ago, and I first selected BTRFS for the root filesystem, as on my amd64 machines. It didn't work so I choose ext4 for the root file system. Last week, when I first tried tu use my BTRFS fomated external drive, the kernel was in version 4.4.0-22. I couldn't write to it, as I can't now with version 4.4.0.24. ppc64 kernels are not available on http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc3-yakkety/. I will try to compile it from sources, and let you know if it works. Thanks a lot for your help! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592566 Title: can't write to a BTRFS disk with my powermac Status in linux package in Ubuntu: Incomplete Bug description: Hi, When I try to write to my BTRFS formated external disk, I get an error message explaining the file system is mounted read only. Indeed, I can still read data in it. A dmesg shows the following errors: [ 143.354977] usb 1-2: new high-speed USB device number 4 using ehci-pci [ 143.564941] usb 1-2: New USB device found, idVendor=04e8, idProduct=61b5 [ 143.564955] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 143.564963] usb 1-2: Product: Samsung M3 Portable [ 143.564971] usb 1-2: Manufacturer: Samsung M3 Portable [ 143.564978] usb 1-2: SerialNumber: D93E7DFA199A [ 143.668941] usbcore: registered new interface driver usb-storage [ 143.694409] scsi host5: uas [ 143.694601] usbcore: registered new interface driver uas [ 143.696560] scsi 5:0:0:0: Direct-Access Samsung M3 Portable 1402 PQ: 0 ANSI: 6 [ 143.698592] sd 5:0:0:0: Attached scsi generic sg3 type 0 [ 147.091177] sd 5:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) [ 147.091194] sd 5:0:0:0: [sdc] 4096-byte physical blocks [ 147.092774] sd 5:0:0:0: [sdc] Write Protect is off [ 147.092785] sd 5:0:0:0: [sdc] Mode Sense: 53 00 00 08 [ 147.093629] sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 147.109068] sdc: sdc1 [ 147.113161] sd 5:0:0:0: [sdc] Attached SCSI disk [ 147.744379] BTRFS: device fsid bf584dbe-6bf6-4847-8b32-cb0d22bead69 devid 1 transid 17546 /dev/sdc1 [ 148.044853] BTRFS info (device sdc1): disk space caching is enabled [ 148.044867] BTRFS: has skinny extents [ 181.329491] BTRFS: Transaction aborted (error -17) [ 181.329573] [ cut here ] [ 181.329577] WARNING: at /build/linux-t3xCGW/linux-4.4.0/fs/btrfs/extent-tree.c:2927 [ 181.329580] Modules linked in: uas usb_storage drbg ansi_cprng ctr ccm arc4 zd1211rw mac80211 cfg80211 input_leds mac_hid snd_aoa_codec_onyx snd_aoa snd_seq_midi snd_seq_midi_event rtc_generic snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore shpchp uio_pdrv_genirq uio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq windfarm_cpufreq_clamp windfarm_smu_sensors windfarm_smu_controls windfarm_pm112 windfarm_pid sil164 hid_generic nouveau windfarm_lm75_sensor windfarm_max6690_sensor i2c_algo_bit firewire_ohci windfarm_smu_sat windfarm_core firewire_core ttm crc_itu_t drm_kms_helper usbhid ata_generic hid drm tg3 ptp uninorth_agp pps_core [ 181.329658] CPU: 0 PID: 1490 Comm: btrfs-transacti Not tainted 4.4.0-24-powerpc64-smp #43-Ubuntu [ 181.329663] task: c0007a633db0 ti: c0007d2c task.ti: c0007d2c [ 181.329666] NIP: d1d99274 LR: d1d99270 CTR: [ 181.329670] REGS: c0007d2c3690 TRAP: 0700 Not tainted (4.4.0-24-powerpc64-smp) [ 181.329672] MSR: 90029032 CR: 24f72442 XER: 2000 [ 181.329683] SOFTE: 1 GPR00: d1d99270 c0007d2c3910 d1e8f2d0 0026 GPR04: c0025de09ad0 c0025de0c360 0036 02ab GPR08: 0007 c10150fc 00025cdf6000 0018 GPR12: 48f72444 cfdc c00f9f40 c0007d082b80 GPR16: GPR20: c0007de65800 0001 c0007b765090 GPR24: c0007b784170 c0007b784160 c0007b784000 GPR28: c0007de65800 c0007b765000 c0024e12bc00 ffef [ 181.329801] NIP [d1d99274] .btrfs_run_delayed_refs+0x364/0x3a0 [btrfs] [ 181.329846] LR [d1d99270] .btrfs_run_delayed_refs+0x360/0x3a0 [btrfs] [ 181.329848] Call Trace: [ 181.329894] [c0007d2c3910] [d1d99270] .btrfs_run_delayed_refs+0x360/0x3a0 [btrfs] (unreliable) [ 181.329941] [c0007d2c39e0] [d1d9a5e0] .btrfs_write_dirty_block_groups+0x1d0/0x300 [btrfs] [ 181.329995] [c0007d2c3ab0] [
[Kernel-packages] [Bug 1590655] Re: [Hyper-V] storvsc messages for CD-ROM medium not present tray closed
** Changed in: linux (Ubuntu Vivid) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Wily) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Trusty) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1590655 Title: [Hyper-V] storvsc messages for CD-ROM medium not present tray closed Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Triaged Bug description: The below can be seen with any distribution running on a Generation 2 VM. There is a verified patch for this, however it has been scheduled only for the 4.8 scsi-queue. As it a small patch which has been verified by KY and also accepted in the patch queue, will you be able to include this as part of the 16.04 rebase to 4.6, and as well for 14.04 and 15.10? Patch can be found at https://patchwork.kernel.org/patch/9131929/ Description of problem: When starting and shutting down a Gen2 VM, at least 20-30 messages are recorded for storvsc with the below sample: [storvsc] Sense Key : Not Ready [current] [storvsc] Add. Sense: Medium not present - tray closed Steps to Reproduce: 1. create a Generation2 VM 2. start VM and observe the system logs 3. multiple messages for the cd-rom are recorded from storvsc Actual results: even without a CD-ROM unit attached, the messages would appear. Having an ISO attached or not would still produce the same messages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590655/+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 1591301] cavac (amd64) - tests ran: 65, failed: 0
tests ran: 65, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-39.46/cavac__4.2.0-39.46__2016-06-16_07-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/1591301 Title: linux: 4.2.0-39.46 -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 Wily: New Bug description: This bug is for tracking the 4.2.0-39.46 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591301/+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 1591301] onibi (amd64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-39.46/onibi__4.2.0-39.46__2016-06-16_07-20-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591301 Title: linux: 4.2.0-39.46 -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 Wily: New Bug description: This bug is for tracking the 4.2.0-39.46 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591301/+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 1591289] Re: linux: 4.4.0-25.44 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591289 Title: linux: 4.4.0-25.44 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1591301] Re: linux: 4.2.0-39.46 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591301 Title: linux: 4.2.0-39.46 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-39.46 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591301/+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 1591307] Re: linux: 3.19.0-62.70 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591307 Title: linux: 3.19.0-62.70 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-62.70 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591307/+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 1591324] Re: linux-lts-utopic: 3.16.0-74.96~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1591324 Title: linux-lts-utopic: 3.16.0-74.96~14.04.1 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-74.96~14.04.1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591324/+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 1591315] Re: linux: 3.13.0-89.136 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591315 Title: linux: 3.13.0-89.136 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-89.136 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591315/+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 1592745] Re: Wacom Intuos 3 USB problems
Tried another thing: attached the tablet to colleague's MacBook ... and from that moment it works without problems. I don't understand it. Is possible, that MacOS silently updated tablet's firmare and fixed some bug, which caused problems with ehci driver? Is any way, how to check actual tablet firmware? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592745 Title: Wacom Intuos 3 USB problems Status in linux package in Ubuntu: Incomplete Bug description: With fresh install of 16.04 I have problems with Wacom Intuos 3 tablet. It sometimes works for while after attaching, but later it stops working and blue led on tablet flashes. When I try to unplug it a plug it again, I see related errors in kern.log: Jun 15 12:07:14 infiwo kernel: [ 5663.315610] usb 2-1.1: new full-speed USB device number 16 using ehci-pci Jun 15 12:07:14 infiwo kernel: [ 5663.387619] usb 2-1.1: device descriptor read/64, error -32 Jun 15 12:07:14 infiwo kernel: [ 5663.586269] usb 2-1.1: New USB device found, idVendor=056a, idProduct=00b1 Jun 15 12:07:14 infiwo kernel: [ 5663.586274] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 15 12:07:14 infiwo kernel: [ 5663.586277] usb 2-1.1: Product: PTZ-630 Jun 15 12:07:14 infiwo kernel: [ 5663.586279] usb 2-1.1: Manufacturer: Tablet Jun 15 12:07:14 infiwo kernel: [ 5663.589111] input: Wacom Intuos3 6x8 Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:056A:00B1.0015/input/input61 Jun 15 12:07:14 infiwo kernel: [ 5663.589441] input: Wacom Intuos3 6x8 Pad as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:056A:00B1.0015/input/input63 Jun 15 12:07:14 infiwo kernel: [ 5663.589803] wacom 0003:056A:00B1.0015: hidraw0: USB HID v1.00 Mouse [Tablet PTZ-630] on usb-:00:1d.0-1.1/input0 Jun 15 12:07:15 infiwo kernel: [ 5664.667703] usb 2-1.1: reset full-speed USB device number 16 using ehci-pci Jun 15 12:07:16 infiwo kernel: [ 5664.739716] usb 2-1.1: device descriptor read/64, error -32 Jun 15 12:07:17 infiwo kernel: [ 5666.627852] usb 2-1.1: reset full-speed USB device number 16 using ehci-pci Jun 15 12:07:17 infiwo kernel: [ 5666.699867] usb 2-1.1: device descriptor read/64, error -32 Jun 15 12:07:19 infiwo kernel: [ 5668.588016] usb 2-1.1: reset full-speed USB device number 16 using ehci-pci Jun 15 12:07:19 infiwo kernel: [ 5668.660023] usb 2-1.1: device descriptor read/64, error -32 Jun 15 12:07:21 infiwo kernel: [ 5670.548171] usb 2-1.1: reset full-speed USB device number 16 using ehci-pci Jun 15 12:07:21 infiwo kernel: [ 5670.620196] usb 2-1.1: device descriptor read/64, error -32 Jun 15 12:07:23 infiwo kernel: [ 5672.520332] usb 2-1.1: reset full-speed USB device number 16 using ehci-pci Jun 15 12:07:23 infiwo kernel: [ 5672.592336] usb 2-1.1: device descriptor read/64, error -32 Jun 15 12:07:25 infiwo kernel: [ 5674.480485] usb 2-1.1: reset full-speed USB device number 16 using ehci-pci ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.24.25 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: disnel 2069 F pulseaudio /dev/snd/controlC0: disnel 2069 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 15 12:08:26 2016 HibernationDevice: RESUME=UUID=ab6ad920-d563-4121-8073-e80d5e9b454e InstallationDate: Installed on 2016-06-14 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. eno1 no wireless extensions. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=615648ea-b585-4a04-9853-0a98eaa41577 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BAP6710H.86A.0079.2012.0622.1722 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DP67DE dmi.board.vendor: Intel Corporation dmi.board.version: AAG10217-204 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBAP6710H.86A.0079.2012.0622.1722:bd06/22/2012:svn:pn:pvr:rvnIntelCorporation:rnDP67DE:rvrAAG10217-204:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.n
[Kernel-packages] [Bug 1593134] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1593134 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 ** Changed in: linux (Ubuntu Xenial) 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/1593134 Title: build squashfs into xenial kernels by default Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: snapd is seeded in all images in xenial by default and snaps are squashfs files. the snappy images need squashfs available at boot time and use official kernels. currently squashfs is the only module that forces us to re-pack initrds to add it everywhere for snappy images, in that light it would be really helpful to have squashfs built into the kernel instead of it being a module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593134/+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 1593134] [NEW] build squashfs into xenial kernels by default
Public bug reported: snapd is seeded in all images in xenial by default and snaps are squashfs files. the snappy images need squashfs available at boot time and use official kernels. currently squashfs is the only module that forces us to re-pack initrds to add it everywhere for snappy images, in that light it would be really helpful to have squashfs built into the kernel instead of it being a module. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1593134 Title: build squashfs into xenial kernels by default Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: snapd is seeded in all images in xenial by default and snaps are squashfs files. the snappy images need squashfs available at boot time and use official kernels. currently squashfs is the only module that forces us to re-pack initrds to add it everywhere for snappy images, in that light it would be really helpful to have squashfs built into the kernel instead of it being a module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593134/+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 1531768] Re: [arm64] lockups when idle if tickless (nohz=on) is used
Hang still occurs with xenial kernel and one instance of nice -n 19 dd if=/dev/zero of=/dev/null bs=1024 & I have now rebooted and started four dd's, so that all four CPUs should remain busy constantly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1531768 Title: [arm64] lockups when idle if tickless (nohz=on) is used Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I want to use for armhf autopkgtesting in LXD). I started with wily as that has lxd available (it's not yet available in trusty nor the PPA for arm64). However, pretty much any LXD task that I do (I haven't tried much else) on this machine takes unbearably long. A simple "lxc profile set default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes. I see tons of [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0 [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds. in dmesg (the attached apport info has the complete dmesg). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 09:18 seq crw-rw 1 root audio 116, 33 Jan 7 09:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Jan 7 09:24:01 2016 IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. Lspci: 00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008] Subsystem: Red Hat, Inc Device [1af4:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+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 1557288] Re: zfs support on s390
*** This bug is a duplicate of bug 1519814 *** https://bugs.launchpad.net/bugs/1519814 On 2016-03-15 10:53:09, this bug report https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1557288 got marked as a duplicate of https://bugs.launchpad.net/bugs/1519814 which is fix released since 2016-03-29. Please fix bugproxy to propagate bugs marked as duplicates of another bug number, and/or adjust status of the bugzilla issue. -- 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/1557288 Title: zfs support on s390 Status in zfs-linux package in Ubuntu: New Bug description: == Comment: #0 - Heinz-Werner Seeck - 2016-03-14 13:00:57 == zfs support on s390 == Comment: #3 - SANDHYA VENUGOPALA - 2016-03-14 23:57:54 == Heinz-Werner Seeck, Please describe what is expected from Canonical for this issue. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1557288/+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 1591301] onibi (i386) - tests ran: 2, failed: 2
tests ran: 2, failed: 2; http://kernel.ubuntu.com/testing/4.2.0-39.46/onibi__4.2.0-39.46__2016-06-16_07-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/1591301 Title: linux: 4.2.0-39.46 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-39.46 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591301/+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 1591301] cavac (i386) - tests ran: 65, failed: 65
tests ran: 65, failed: 65; http://kernel.ubuntu.com/testing/4.2.0-39.46/cavac__4.2.0-39.46__2016-06-16_07-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/1591301 Title: linux: 4.2.0-39.46 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-39.46 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591301/+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 1591289] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 3, failed: 1
tests ran: 3, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-24.43/ms10-34-mcdivittB0-kernel__4.4.0-24.43__2016-06-16_07-06-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/1591289 Title: linux: 4.4.0-25.44 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1593134] Re: build squashfs into xenial kernels by default
** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1593134 Title: build squashfs into xenial kernels by default Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: snapd is seeded in all images in xenial by default and snaps are squashfs files. the snappy images need squashfs available at boot time and use official kernels. currently squashfs is the only module that forces us to re-pack initrds to add it everywhere for snappy images, in that light it would be really helpful to have squashfs built into the kernel instead of it being a module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593134/+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 1593134] Re: build squashfs into xenial kernels by default
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Triaged ** Tags added: kernel-da-key ** Tags added: 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/1593134 Title: build squashfs into xenial kernels by default Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: snapd is seeded in all images in xenial by default and snaps are squashfs files. the snappy images need squashfs available at boot time and use official kernels. currently squashfs is the only module that forces us to re-pack initrds to add it everywhere for snappy images, in that light it would be really helpful to have squashfs built into the kernel instead of it being a module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593134/+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 1591289] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 3, failed: 1
tests ran: 3, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-25.44/ms10-35-mcdivittB0-kernel__4.4.0-25.44__2016-06-16_07-15-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/1591289 Title: linux: 4.4.0-25.44 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1531768] Re: [arm64] lockups when idle if tickless (nohz=on) is used
If 4 dd's work OK, it may be worth running a minimal sleep loop: while true; do sleep 0.5; done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1531768 Title: [arm64] lockups when idle if tickless (nohz=on) is used Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I want to use for armhf autopkgtesting in LXD). I started with wily as that has lxd available (it's not yet available in trusty nor the PPA for arm64). However, pretty much any LXD task that I do (I haven't tried much else) on this machine takes unbearably long. A simple "lxc profile set default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes. I see tons of [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0 [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds. in dmesg (the attached apport info has the complete dmesg). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 09:18 seq crw-rw 1 root audio 116, 33 Jan 7 09:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Jan 7 09:24:01 2016 IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. Lspci: 00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008] Subsystem: Red Hat, Inc Device [1af4:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+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 1557288] Re: zfs support on s390
*** This bug is a duplicate of bug 1519814 *** https://bugs.launchpad.net/bugs/1519814 ** Also affects: ubuntu-z-systems Importance: Undecided Status: New -- 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/1557288 Title: zfs support on s390 Status in Ubuntu on IBM z Systems: New Status in zfs-linux package in Ubuntu: New Bug description: == Comment: #0 - Heinz-Werner Seeck - 2016-03-14 13:00:57 == zfs support on s390 == Comment: #3 - SANDHYA VENUGOPALA - 2016-03-14 23:57:54 == Heinz-Werner Seeck, Please describe what is expected from Canonical for this issue. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1557288/+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 1531768] Re: [arm64] lockups when idle if tickless (nohz=on) is used
FTR, running the trusty kernel on xenial userspace does not work: http://paste.ubuntu.com/17392362/ cking | pitti, syscall 384 on aarch64 is getrandom() and that does not exist on trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1531768 Title: [arm64] lockups when idle if tickless (nohz=on) is used Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I want to use for armhf autopkgtesting in LXD). I started with wily as that has lxd available (it's not yet available in trusty nor the PPA for arm64). However, pretty much any LXD task that I do (I haven't tried much else) on this machine takes unbearably long. A simple "lxc profile set default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes. I see tons of [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0 [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds. in dmesg (the attached apport info has the complete dmesg). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 09:18 seq crw-rw 1 root audio 116, 33 Jan 7 09:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Jan 7 09:24:01 2016 IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. Lspci: 00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008] Subsystem: Red Hat, Inc Device [1af4:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+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 1591329] Re: linux: 3.2.0-105.146 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Daniel Manrique (roadmr) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591329 Title: linux: 3.2.0-105.146 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug is for tracking the 3.2.0-105.146 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591329/+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 1571798] Re: Broadwell ECRC Support missing in Ubuntu
I built the next test kernel, up to the following commit: afa3536be88b435a057cb727b48fd3d760a497d2 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1571798 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1571798 Title: Broadwell ECRC Support missing in Ubuntu Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: Here is the problem statement from the Dell team: When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel Quick Assist Card, the memory location that corresponds to ECRC is set to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot. This causes the card to not function unless we implement the following workaround using setpci. “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for the Intel Quick Assit Card. We’ve verified the memory location is correct when booting to other OSes, such as RHEL 7.2 and Windows Server 2012 R2. If there is any information you can give as to why this may be occurring in Ubuntu or where we may start to debug when the memory is changed, we would appreciate it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+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 1591289] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 23, failed: 1
tests ran: 23, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-24.43/ms10-35-mcdivittB0-kernel__4.4.0-24.43__2016-06-16_08-23-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/1591289 Title: linux: 4.4.0-25.44 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1559308] Re: Plugging HDMI screen in causes system hang
Still freezes when using DisplayPort on kernel 4.4.0-24. Tested with http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc3-yakkety/ and DP works fine - however, display is not recognized when using VGA. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559308 Title: Plugging HDMI screen in causes system hang Status in linux package in Ubuntu: Fix Committed Bug description: I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1 using 4.4.0-13-generic and the Nouveau drivers. If I plug in an external HDMI monitor (FHD) either into either HDMI port (there's one on the machine and there's one available via a usb 3.1 extra adaptor) then the whole system hangs, completely unresponsive and needing a hard reboot. Before hanging the 2nd display gets an image as expected, but the laptop's screen flashes randomly, sometimes you see weird artifacts. Then the hang comes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 18 20:43:42 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06e4] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4] InstallationDate: Installed on 2016-03-15 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 18 17:28:07 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Unknown chipset: NV117 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5182 vendor SHP xserver.version: 2:1.18.1-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559308/+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 1591433] Re: linux-lts-trusty: 3.13.0-89.136~precise1 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Daniel Manrique (roadmr) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1591433 Title: linux-lts-trusty: 3.13.0-89.136~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-89.136~precise1 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: 1591315 phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591433/+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 1528466] Re: Mellanox ConnectX4 MTU limits: max and min
** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1528466
Title:
Mellanox ConnectX4 MTU limits: max and min
Status in linux package in Ubuntu:
Fix Released
Status in linux-lts-wily package in Ubuntu:
Fix Released
Status in linux source package in Wily:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Bug description:
Max MTU limit should be 9978
Tested on Ubuntu 14.04.4 daily build, this issue exist also in 15.10.
reproduce
# ifconfig p2p1 mtu 900
SIOCSIFMTU: Invalid argument
# dmesg
[62898.559808] mlx5_core :20:00.0 p2p1: mlx5e_change_mtu: Bad MTU
(900) > (1) Max
[63058.512668] command failed, status bad parameter(0x3), syndrome 0x648afc
Upstream commit that fix the issue
commit 60825c35bf023553f8524f6695f176236e54df97
Author: Doron Tsur
Date: Thu Nov 12 19:35:27 2015 +0200
net/mlx5e: Max mtu comparison fix
On change mtu the driver compares between hardware queried mtu and
software requested mtu. We need to compare between software
representation of the queried mtu and the requested mtu.
Fixes: facc9699f0fe ('net/mlx5e: Fix HW MTU settings')
Signed-off-by: Doron Tsur
Signed-off-by: Saeed Mahameed
Signed-off-by: Or Gerlitz
Signed-off-by: David S. Miller
# cat /etc/os-release
NAME="Ubuntu"
VERSION="14.04.3 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.3 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/";
SUPPORT_URL="http://help.ubuntu.com/";
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
# uname -r
4.2.0-22-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528466/+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 1590798] Re: Can't connect/pair Bose Soundlink II Headphones to Ubuntu 16.04
*** This bug is a duplicate of bug 1589889 *** https://bugs.launchpad.net/bugs/1589889 I have followed the fix suggestion in bug #1589889. This has resulted in some progress in that I can now connect to the headphones, and once the headphones did register the laptop. But they disconnected straight away, and hasn't registered again since then. I've tried the blueman manager as it tends to put out a bit more information than the standard bluetooth manager and i get the following: Connection Failed: blueman.bluez.errors.DBusFailedError: Protocol not available This device registers as several different components and when I specifically try to connect to the serial port I get the following message Connection Failed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/blueman/services/meta/SerialService.py", line 29, in connect port_id = create_rfcomm_device(Adapter(props['Adapter']).get_properties()['Address'], props['Address'], 1) File "_blueman.pyx", line 218, in _blueman.create_rfcomm_device (_blueman.c:2127) Exception: Can't connect RFCOMM socket -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1590798 Title: Can't connect/pair Bose Soundlink II Headphones to Ubuntu 16.04 Status in bluez package in Ubuntu: New Bug description: I've recently started using 16.04 on a Dell XPS 15 9550 and I'm unable to pair my Bose Soundlink II headphones. I've tried using the stock and blueman bluetooth managers and neither will work. When I use bluetoothctl and run "pair [Device ID]" I get the following error: Failed to pair: org.bluez.Error.AuthenticationFailed I have seen several references to this online but believe there are still problems in 16.04 bluez: Installed: 5.37-0ubuntu5 Candidate: 5.37-0ubuntu5 Version table: *** 5.37-0ubuntu5 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1590798/+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 1585462] Re: Dell Latitude E7440 crash on lid close (MATE 16.04)
I just upgraded to 16.04 and I started having the exact same issue. I'm attaching my output of apport. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1585462 Title: Dell Latitude E7440 crash on lid close (MATE 16.04) Status in linux package in Ubuntu: Incomplete Bug description: Fresh install of 16.04 (installed twice, now -- same issue both times; apt-get update; apt-get dist-upgrade run in both cases, so latest packages). On lid close, system hard freezes, requiring power cycle. On opening lid, is frozen on lockscreen. No mouse movement, no keyboard movement, does nothing. Freezes ~80% of the time; occasionally (perhaps related to WiFi not being enabled), it suspends properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585462/+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 1585462] Re: Dell Latitude E7440 crash on lid close (MATE 16.04)
Re-attacching output of apport. ** Attachment added: "output of apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585462/+attachment/4684837/+files/apport-collect-1585462.txt.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1585462 Title: Dell Latitude E7440 crash on lid close (MATE 16.04) Status in linux package in Ubuntu: Incomplete Bug description: Fresh install of 16.04 (installed twice, now -- same issue both times; apt-get update; apt-get dist-upgrade run in both cases, so latest packages). On lid close, system hard freezes, requiring power cycle. On opening lid, is frozen on lockscreen. No mouse movement, no keyboard movement, does nothing. Freezes ~80% of the time; occasionally (perhaps related to WiFi not being enabled), it suspends properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585462/+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 1591301] alkaid (amd64) - tests ran: 83, failed: 0
tests ran: 83, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-39.46/alkaid__4.2.0-39.46__2016-06-16_06-17-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/1591301 Title: linux: 4.2.0-39.46 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-39.46 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591301/+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 1591301] phact (amd64) - tests ran: 83, failed: 0
tests ran: 83, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-39.46/phact__4.2.0-39.46__2016-06-16_06-12-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/1591301 Title: linux: 4.2.0-39.46 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-39.46 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591301/+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 1591301] onibi (amd64) - tests ran: 65, failed: 0
tests ran: 65, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-39.46/onibi__4.2.0-39.46__2016-06-16_08-26-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/1591301 Title: linux: 4.2.0-39.46 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-39.46 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591301/+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 1593124] Re: Palm rejection for MS Precision Touchpad causes touchpad unusable
** Changed in: hwe-next Assignee: (unassigned) => Phidias (phidias-chiang) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: hwe-next 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/1593124 Title: Palm rejection for MS Precision Touchpad causes touchpad unusable Status in HWE Next: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Sometimes touchpad doesn't work properly after palm is rejected. The pointer either jumping around (described on bugzilla[1]) or doesn't move at all (in our cases). This problem is introduced with commit: 25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm rejection if device implements confidence usage), by reverting it the touchpad can work properly. We also contacted with Synaptics, and they provided a workaround to fix this issue. Not sure if the workaround will be upstreamed and needs to keep co-working with them. Commit 25a84db applies to Xenial and Yakkety so only these two release were affected. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1593124/+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 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
@pavel See https://wiki.ubuntu.com/Kernel/MainlineBuilds and try which newer kernel solves the 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/1550779 Title: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches Status in linux package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+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 1591301] onibi (i386) - tests ran: 65, failed: 65
tests ran: 65, failed: 65; http://kernel.ubuntu.com/testing/4.2.0-39.46/onibi__4.2.0-39.46__2016-06-16_09-28-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/1591301 Title: linux: 4.2.0-39.46 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-39.46 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591301/+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 1590798] Re: Can't connect/pair Bose Soundlink II Headphones to Ubuntu 16.04
** This bug is no longer a duplicate of bug 1589889 Bluetooth search gets nothing on Dell XPS 15 9550 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1590798 Title: Can't connect/pair Bose Soundlink II Headphones to Ubuntu 16.04 Status in bluez package in Ubuntu: New Bug description: I've recently started using 16.04 on a Dell XPS 15 9550 and I'm unable to pair my Bose Soundlink II headphones. I've tried using the stock and blueman bluetooth managers and neither will work. When I use bluetoothctl and run "pair [Device ID]" I get the following error: Failed to pair: org.bluez.Error.AuthenticationFailed I have seen several references to this online but believe there are still problems in 16.04 bluez: Installed: 5.37-0ubuntu5 Candidate: 5.37-0ubuntu5 Version table: *** 5.37-0ubuntu5 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1590798/+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 1591315] Re: linux: 3.13.0-89.136 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Yung Shen (kaxing) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591315 Title: linux: 3.13.0-89.136 -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: In Progress 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-89.136 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591315/+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 1592531] Re: Cannot compile module tda10071
Config attached ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592531 Title: Cannot compile module tda10071 Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu 16.10, Kernel source 4.4.0.24.25 Can't compile tda10071 as a module: Building modules, stage 2. Kernel: arch/x86/boot/bzImage is ready (#2) MODPOST 408 modules ERROR: "__devm_regmap_init_i2c" [drivers/media/dvb-frontends/tda10071.ko] undefined! scripts/Makefile.modpost:91: recipe for target '__modpost' failed make[1]: *** [__modpost] Error 1 Makefile:1118: recipe for target 'modules' failed make: *** [modules] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592531/+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 1591433] Re: linux-lts-trusty: 3.13.0-89.136~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Assignee: Daniel Manrique (roadmr) => Yung Shen (kaxing) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1591433 Title: linux-lts-trusty: 3.13.0-89.136~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-89.136~precise1 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: 1591315 phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591433/+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 1592933] Re: there are several errors on booting my laptop (xubuntu 16.04 64 bits)
After shutting the laptop down with kernel 4.4.0.25 the system shut down the regular way (2 minutes 35 seconds, blank screen), but on booting the next day, the bios recognized 4 GiB RAM. After BIOS the log that start appearing on 00:48 stopped on the first four lines providing information, which allowed me to copy them: /dev/sda1: clean, 116918/19275776 files, 66284199/77094912 blocks [10.368134] systemd[1]: paths.target: job paths.target/start deleted to break ordering cycle starting with basic.target/start [10.368234] systemd[1]: systemd-ask-password-plymouth.path: Job systemd ask-password-plymouth.path/deleted to break ordering cycle starting with basic.target/start [10.368324] systemd[1]: plymouth-start.service: Job plymouth-start.service/start deleted to break ordering cycle starting with plymouth-quit-wait.service/start After that and seeing nothing else I powered the laptop off, rebooted it and I was back to 2 GiB RAM and a slow functioning machine from which I am writing these lines. ** Summary changed: - there are several errors on booting my laptop (xubuntu 16.04 64 bits) + there are several errors on booting my laptop (xubuntu 16.04 64 bits), ordering cycle broken ** Description changed: Best I could think of is recording a video, so you see what I endure every time I power on the laptop: https://vid.me/9eRl it's comments are self explanatory: Booting on M7X-SUN 00:39: those are several inode errors, those appear because I had to reboot the laptop several times (because the first or second time on powering the laptop I just got a blank screen). 00:48: that huge list of things being loaded is nowehere in /var/log/syslog, dmesg or kern.log to be seen. Where do I find that information that tells me what is going in in plain text format? Green is OK, red is FAILED + + The first four lines of the list read as follows: + + /dev/sda1: clean, 116918/19275776 files, 66284199/77094912 blocks + [10.368134] systemd[1]: paths.target: job paths.target/start deleted to break ordering cycle starting with basic.target/start + [10.368234] systemd[1]: systemd-ask-password-plymouth.path: Job systemd ask-password-plymouth.path/deleted to break ordering cycle starting with basic.target/start + [10.368324] systemd[1]: plymouth-start.service: Job plymouth-start.service/start deleted to break ordering cycle starting with plymouth-quit-wait.service/start 01:21: from this moment on, blank screen with just a cursor. It stays like that usually for 30 to 40 seconds with no mention of tty1 (see next) 01:38: thats tty1 asking me an username and if I enter it, a password, I usually don't write anything and let the laptop go on to login screen. 02:01: blank screen (this is new, usually the login screen should appear now) 03:00: not recorded, but log in screen appeared. I dont know if this is related to my other bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589109 , because on shutting down I also don't see what is going on... somebody suggested to execute 'systemd-analyze plot > boot.svg' which does not show that huge list I mention on 00:48, but I append it here, as it may be useful for you... How Do I solve all those problems and get my fully 4 GiB of ram to work instead of the 2 just right now? Between 2 and 3 minutes just to boot a laptop is too much time. - --- + --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2012-04-12 (1525 days ago) InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) Package: linux (not installed) Tags: xenial Uname: Linux 4.7.0-040700rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape video _MarkForUpload: True ** Description changed: Best I could think of is recording a video, so you see what I endure every time I power on the laptop: https://vid.me/9eRl it's comments are self explanatory: Booting on M7X-SUN 00:39: those are several inode errors, those appear because I had to reboot the laptop several times (because the first or second time on powering the laptop I just got a blank screen). 00:48: that huge list of things being loaded is nowehere in /var/log/syslog, dmesg or kern.log to be seen. Where do I find that information that tells me what is going in in plain text format? Green is OK, red is FAILED - The first four lines of the list read as follows: + Right after the several inode errors some information about the ordering + cycle appears: They read as follows (see #8 for more information): /dev/sda1: clean, 116918/19275776 files, 66284199/77094912 blocks [10.368134] systemd[1]:
[Kernel-packages] [Bug 1592933] Re: there are several errors on booting my laptop (xubuntu 16.04 64 bits), ordering cycle broken
/var/log/dmesg's last date of modification was 04/26/2015, which I simply don't understand, but inside the file: [6.118458] init: plymouth-upstart-bridge respawning too fast, stopped [ 31.833709] Adding 4189180k swap on /dev/sda5. Priority:-1 extents:1 across:4189180k FS where are the missing 26 seconds, where the ordering cycle would appear? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592933 Title: there are several errors on booting my laptop (xubuntu 16.04 64 bits), ordering cycle broken Status in linux package in Ubuntu: Confirmed Bug description: Best I could think of is recording a video, so you see what I endure every time I power on the laptop: https://vid.me/9eRl it's comments are self explanatory: Booting on M7X-SUN 00:39: those are several inode errors, those appear because I had to reboot the laptop several times (because the first or second time on powering the laptop I just got a blank screen). 00:48: that huge list of things being loaded is nowehere in /var/log/syslog, dmesg or kern.log to be seen. Where do I find that information that tells me what is going in in plain text format? Green is OK, red is FAILED Right after the several inode errors some information about the ordering cycle appears: They read as follows (see #8 for more information): /dev/sda1: clean, 116918/19275776 files, 66284199/77094912 blocks [10.368134] systemd[1]: paths.target: job paths.target/start deleted to break ordering cycle starting with basic.target/start [10.368234] systemd[1]: systemd-ask-password-plymouth.path: Job systemd ask-password-plymouth.path/deleted to break ordering cycle starting with basic.target/start [10.368324] systemd[1]: plymouth-start.service: Job plymouth-start.service/start deleted to break ordering cycle starting with plymouth-quit-wait.service/start 01:21: from this moment on, blank screen with just a cursor. It stays like that usually for 30 to 40 seconds with no mention of tty1 (see next) 01:38: thats tty1 asking me an username and if I enter it, a password, I usually don't write anything and let the laptop go on to login screen. 02:01: blank screen (this is new, usually the login screen should appear now) 03:00: not recorded, but log in screen appeared. I dont know if this is related to my other bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589109 , because on shutting down I also don't see what is going on... somebody suggested to execute 'systemd-analyze plot > boot.svg' which does not show that huge list I mention on 00:48, but I append it here, as it may be useful for you... How Do I solve all those problems and get my fully 4 GiB of ram to work instead of the 2 just right now? Between 2 and 3 minutes just to boot a laptop is too much time. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2012-04-12 (1525 days ago) InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) Package: linux (not installed) Tags: xenial Uname: Linux 4.7.0-040700rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592933/+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 1591289] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-24.43/ms10-34-mcdivittB0-kernel__4.4.0-24.43__2016-06-16_09-49-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/1591289 Title: linux: 4.4.0-25.44 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1592933] Re: there are several errors on booting my laptop (xubuntu 16.04 64 bits), ordering cycle broken
** Description changed: Best I could think of is recording a video, so you see what I endure every time I power on the laptop: https://vid.me/9eRl it's comments are self explanatory: Booting on M7X-SUN 00:39: those are several inode errors, those appear because I had to reboot the laptop several times (because the first or second time on powering the laptop I just got a blank screen). 00:48: that huge list of things being loaded is nowehere in /var/log/syslog, dmesg or kern.log to be seen. Where do I find that information that tells me what is going in in plain text format? Green is OK, red is FAILED Right after the several inode errors some information about the ordering cycle appears: They read as follows (see #8 for more information): /dev/sda1: clean, 116918/19275776 files, 66284199/77094912 blocks [10.368134] systemd[1]: paths.target: job paths.target/start deleted to break ordering cycle starting with basic.target/start [10.368234] systemd[1]: systemd-ask-password-plymouth.path: Job systemd ask-password-plymouth.path/deleted to break ordering cycle starting with basic.target/start [10.368324] systemd[1]: plymouth-start.service: Job plymouth-start.service/start deleted to break ordering cycle starting with plymouth-quit-wait.service/start + + the very first entrance (in yellow) reads: dependency failed for PNFS + block 01:21: from this moment on, blank screen with just a cursor. It stays like that usually for 30 to 40 seconds with no mention of tty1 (see next) 01:38: thats tty1 asking me an username and if I enter it, a password, I usually don't write anything and let the laptop go on to login screen. 02:01: blank screen (this is new, usually the login screen should appear now) 03:00: not recorded, but log in screen appeared. I dont know if this is related to my other bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589109 , because on shutting down I also don't see what is going on... somebody suggested to execute 'systemd-analyze plot > boot.svg' which does not show that huge list I mention on 00:48, but I append it here, as it may be useful for you... How Do I solve all those problems and get my fully 4 GiB of ram to work instead of the 2 just right now? Between 2 and 3 minutes just to boot a laptop is too much time. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2012-04-12 (1525 days ago) InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) Package: linux (not installed) Tags: xenial Uname: Linux 4.7.0-040700rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape video _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592933 Title: there are several errors on booting my laptop (xubuntu 16.04 64 bits), ordering cycle broken Status in linux package in Ubuntu: Confirmed Bug description: Best I could think of is recording a video, so you see what I endure every time I power on the laptop: https://vid.me/9eRl it's comments are self explanatory: Booting on M7X-SUN 00:39: those are several inode errors, those appear because I had to reboot the laptop several times (because the first or second time on powering the laptop I just got a blank screen). 00:48: that huge list of things being loaded is nowehere in /var/log/syslog, dmesg or kern.log to be seen. Where do I find that information that tells me what is going in in plain text format? Green is OK, red is FAILED Right after the several inode errors some information about the ordering cycle appears: They read as follows (see #8 for more information): /dev/sda1: clean, 116918/19275776 files, 66284199/77094912 blocks [10.368134] systemd[1]: paths.target: job paths.target/start deleted to break ordering cycle starting with basic.target/start [10.368234] systemd[1]: systemd-ask-password-plymouth.path: Job systemd ask-password-plymouth.path/deleted to break ordering cycle starting with basic.target/start [10.368324] systemd[1]: plymouth-start.service: Job plymouth-start.service/start deleted to break ordering cycle starting with plymouth-quit-wait.service/start the very first entrance (in yellow) reads: dependency failed for PNFS block 01:21: from this moment on, blank screen with just a cursor. It stays like that usually for 30 to 40 seconds with no mention of tty1 (see next) 01:38: thats tty1 asking me an username and if I enter it, a password, I usually don't write anything and let the lapt
[Kernel-packages] [Bug 1584066] Re: CAPI: CGZIP Wrong CAPI MMIO timeout (256usec desired but 1usec default setting in cxl.ko driver)
** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1584066 Title: CAPI: CGZIP Wrong CAPI MMIO timeout (256usec desired but 1usec default setting in cxl.ko driver) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: ---Problem Description--- MMIO timeout for CAPI driver is too small for CGZIP application. 1usec default should be replaced by 256usec, which prevents cxl driver output in kernel log. ---uname output--- 4.2.0-34-generic ---Additional Hardware Info--- Nallatech FPGA card with CGZIP bitstream. Machine Type = Tuleta, but also others ---Steps to Reproduce--- Do extensive stress test using CGZIP card. Patch for this fix has been accepted to ppc-linux git tree viz commit https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=4aec6ec0da9c72c0fa1a5b0d1133707481347bb3 Required for gzip capi adapter for 14.04.5. So would like the fix in 16.04, so that it can roll "naturally" in 14.04.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584066/+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 1591289] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-24.43/ms10-34-mcdivittB0-kernel__4.4.0-24.43__2016-06-16_11-01-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/1591289 Title: linux: 4.4.0-25.44 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1509489] Proposed package removed from archive
The version of linux-mako in the proposed pocket of Wily that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1509489 Title: [SRU] seccomp filters backport for Mako Status in linux-mako package in Ubuntu: Fix Released Status in linux-mako source package in Vivid: Fix Committed Status in linux-mako source package in Wily: Won't Fix Status in linux-mako source package in Xenial: Fix Released Bug description: [Impact] * The snappy confinement model utilizes both apparmor and seccomp filters, and while the former is supported by the phone kernel, the latter is not. Snappy cannot be used on the mako, krillin, or vegetahd without seccomp filters being backported. [Test Case] * Run the tests located here: http://kernel.ubuntu.com/git/kyrofa/ubuntu- vivid.git/tree/tools/testing/selftests/seccomp?h=backport_seccomp_filters&id=555777b2449cb4a69604998e8550001231a0f6af They will fail without this change. [Regression Potential] * Potential AppArmor regression regarding its use of no_new_privs, since it was previously a fake implementation to facilitate the v3 backport. [Other Info] * Backport is from mainline. * Backport only includes seccomp filters introduced in v3.5 (e.g. does not include syscall or tsync). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1509489/+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 1513463] Proposed package removed from archive
The version of linux-mako in the proposed pocket of Wily that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1513463 Title: [SRU] Kernel too big for boot partition Status in linux-mako package in Ubuntu: Fix Released Status in linux-mako source package in Vivid: Fix Committed Status in linux-mako source package in Wily: Won't Fix Status in linux-mako source package in Xenial: Fix Released Bug description: [Impact] * Recent additions to the mako kernel have made it too big for the mako boot partition. Without this patch, a boot.img cannot be created. [Test Case] 1. Compile the mako kernel without this patch. 2. Attempt to create a boot.img 3. Notice that the kernel is too big. 4. Apply this patch. 5. Run steps 1-2 again. 6. Notice that the kernel is no longer too big. [Regression Potential] * This patch removes ext2 and ext3 and enables ext4's backward- compatibility mode for them instead. The only regression potential is within ext4's backward-compatibility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1513463/+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 1509489] Proposed package removed from archive
The version of linux-mako in the proposed pocket of Wily that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1509489 Title: [SRU] seccomp filters backport for Mako Status in linux-mako package in Ubuntu: Fix Released Status in linux-mako source package in Vivid: Fix Committed Status in linux-mako source package in Wily: Won't Fix Status in linux-mako source package in Xenial: Fix Released Bug description: [Impact] * The snappy confinement model utilizes both apparmor and seccomp filters, and while the former is supported by the phone kernel, the latter is not. Snappy cannot be used on the mako, krillin, or vegetahd without seccomp filters being backported. [Test Case] * Run the tests located here: http://kernel.ubuntu.com/git/kyrofa/ubuntu- vivid.git/tree/tools/testing/selftests/seccomp?h=backport_seccomp_filters&id=555777b2449cb4a69604998e8550001231a0f6af They will fail without this change. [Regression Potential] * Potential AppArmor regression regarding its use of no_new_privs, since it was previously a fake implementation to facilitate the v3 backport. [Other Info] * Backport is from mainline. * Backport only includes seccomp filters introduced in v3.5 (e.g. does not include syscall or tsync). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1509489/+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 1513207] Proposed package removed from archive
The version of linux-mako in the proposed pocket of Wily that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1513207 Title: [SRU] Enable squashfs support Status in linux-mako package in Ubuntu: Fix Released Status in linux-mako source package in Vivid: Fix Committed Status in linux-mako source package in Wily: Won't Fix Status in linux-mako source package in Xenial: Fix Released Bug description: [Impact] * The Snappy packaging format will soon move to utilizing a squashfs image per package. However, when that change happens such snaps will fail to install on the Mako due to squashfs support not being enabled. [Test Case] 1. Install squashfs-tools. 2. Create a directory containing generic data (e.g. a text file). 3. Turn that directory into a squashfs image: $ mksquashfs foo.sqsh 4. Attempt to mount that directory: $ sudo mount foo.sqsh /mnt 5. Notice that without this patch, the mount fails due to an unknown filesystem type, whereas it succeeds with this patch applied, and contains the content created in step (2). [Regression Potential] * None known; this only enables squashfs. [Other Info] * These flags were simply copied from the current trusty config. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1513207/+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 1513207] Proposed package removed from archive
The version of linux-mako in the proposed pocket of Wily that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1513207 Title: [SRU] Enable squashfs support Status in linux-mako package in Ubuntu: Fix Released Status in linux-mako source package in Vivid: Fix Committed Status in linux-mako source package in Wily: Won't Fix Status in linux-mako source package in Xenial: Fix Released Bug description: [Impact] * The Snappy packaging format will soon move to utilizing a squashfs image per package. However, when that change happens such snaps will fail to install on the Mako due to squashfs support not being enabled. [Test Case] 1. Install squashfs-tools. 2. Create a directory containing generic data (e.g. a text file). 3. Turn that directory into a squashfs image: $ mksquashfs foo.sqsh 4. Attempt to mount that directory: $ sudo mount foo.sqsh /mnt 5. Notice that without this patch, the mount fails due to an unknown filesystem type, whereas it succeeds with this patch applied, and contains the content created in step (2). [Regression Potential] * None known; this only enables squashfs. [Other Info] * These flags were simply copied from the current trusty config. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1513207/+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 1513463] Proposed package removed from archive
The version of linux-mako in the proposed pocket of Wily that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1513463 Title: [SRU] Kernel too big for boot partition Status in linux-mako package in Ubuntu: Fix Released Status in linux-mako source package in Vivid: Fix Committed Status in linux-mako source package in Wily: Won't Fix Status in linux-mako source package in Xenial: Fix Released Bug description: [Impact] * Recent additions to the mako kernel have made it too big for the mako boot partition. Without this patch, a boot.img cannot be created. [Test Case] 1. Compile the mako kernel without this patch. 2. Attempt to create a boot.img 3. Notice that the kernel is too big. 4. Apply this patch. 5. Run steps 1-2 again. 6. Notice that the kernel is no longer too big. [Regression Potential] * This patch removes ext2 and ext3 and enables ext4's backward- compatibility mode for them instead. The only regression potential is within ext4's backward-compatibility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1513463/+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 1513207] Proposed package removed from archive
The version of linux-mako in the proposed pocket of Wily that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1513207 Title: [SRU] Enable squashfs support Status in linux-mako package in Ubuntu: Fix Released Status in linux-mako source package in Vivid: Fix Committed Status in linux-mako source package in Wily: Won't Fix Status in linux-mako source package in Xenial: Fix Released Bug description: [Impact] * The Snappy packaging format will soon move to utilizing a squashfs image per package. However, when that change happens such snaps will fail to install on the Mako due to squashfs support not being enabled. [Test Case] 1. Install squashfs-tools. 2. Create a directory containing generic data (e.g. a text file). 3. Turn that directory into a squashfs image: $ mksquashfs foo.sqsh 4. Attempt to mount that directory: $ sudo mount foo.sqsh /mnt 5. Notice that without this patch, the mount fails due to an unknown filesystem type, whereas it succeeds with this patch applied, and contains the content created in step (2). [Regression Potential] * None known; this only enables squashfs. [Other Info] * These flags were simply copied from the current trusty config. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1513207/+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 1509489] Proposed package removed from archive
The version of linux-mako in the proposed pocket of Wily that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1509489 Title: [SRU] seccomp filters backport for Mako Status in linux-mako package in Ubuntu: Fix Released Status in linux-mako source package in Vivid: Fix Committed Status in linux-mako source package in Wily: Won't Fix Status in linux-mako source package in Xenial: Fix Released Bug description: [Impact] * The snappy confinement model utilizes both apparmor and seccomp filters, and while the former is supported by the phone kernel, the latter is not. Snappy cannot be used on the mako, krillin, or vegetahd without seccomp filters being backported. [Test Case] * Run the tests located here: http://kernel.ubuntu.com/git/kyrofa/ubuntu- vivid.git/tree/tools/testing/selftests/seccomp?h=backport_seccomp_filters&id=555777b2449cb4a69604998e8550001231a0f6af They will fail without this change. [Regression Potential] * Potential AppArmor regression regarding its use of no_new_privs, since it was previously a fake implementation to facilitate the v3 backport. [Other Info] * Backport is from mainline. * Backport only includes seccomp filters introduced in v3.5 (e.g. does not include syscall or tsync). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1509489/+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 1513207] Proposed package removed from archive
The version of linux-mako in the proposed pocket of Wily that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Changed in: linux-mako (Ubuntu Wily) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1513207 Title: [SRU] Enable squashfs support Status in linux-mako package in Ubuntu: Fix Released Status in linux-mako source package in Vivid: Fix Committed Status in linux-mako source package in Wily: Won't Fix Status in linux-mako source package in Xenial: Fix Released Bug description: [Impact] * The Snappy packaging format will soon move to utilizing a squashfs image per package. However, when that change happens such snaps will fail to install on the Mako due to squashfs support not being enabled. [Test Case] 1. Install squashfs-tools. 2. Create a directory containing generic data (e.g. a text file). 3. Turn that directory into a squashfs image: $ mksquashfs foo.sqsh 4. Attempt to mount that directory: $ sudo mount foo.sqsh /mnt 5. Notice that without this patch, the mount fails due to an unknown filesystem type, whereas it succeeds with this patch applied, and contains the content created in step (2). [Regression Potential] * None known; this only enables squashfs. [Other Info] * These flags were simply copied from the current trusty config. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1513207/+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 1513463] Proposed package removed from archive
The version of linux-mako in the proposed pocket of Wily that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Changed in: linux-mako (Ubuntu Wily) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1513463 Title: [SRU] Kernel too big for boot partition Status in linux-mako package in Ubuntu: Fix Released Status in linux-mako source package in Vivid: Fix Committed Status in linux-mako source package in Wily: Won't Fix Status in linux-mako source package in Xenial: Fix Released Bug description: [Impact] * Recent additions to the mako kernel have made it too big for the mako boot partition. Without this patch, a boot.img cannot be created. [Test Case] 1. Compile the mako kernel without this patch. 2. Attempt to create a boot.img 3. Notice that the kernel is too big. 4. Apply this patch. 5. Run steps 1-2 again. 6. Notice that the kernel is no longer too big. [Regression Potential] * This patch removes ext2 and ext3 and enables ext4's backward- compatibility mode for them instead. The only regression potential is within ext4's backward-compatibility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1513463/+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 1509489] Proposed package removed from archive
The version of linux-mako in the proposed pocket of Wily that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Changed in: linux-mako (Ubuntu Wily) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1509489 Title: [SRU] seccomp filters backport for Mako Status in linux-mako package in Ubuntu: Fix Released Status in linux-mako source package in Vivid: Fix Committed Status in linux-mako source package in Wily: Won't Fix Status in linux-mako source package in Xenial: Fix Released Bug description: [Impact] * The snappy confinement model utilizes both apparmor and seccomp filters, and while the former is supported by the phone kernel, the latter is not. Snappy cannot be used on the mako, krillin, or vegetahd without seccomp filters being backported. [Test Case] * Run the tests located here: http://kernel.ubuntu.com/git/kyrofa/ubuntu- vivid.git/tree/tools/testing/selftests/seccomp?h=backport_seccomp_filters&id=555777b2449cb4a69604998e8550001231a0f6af They will fail without this change. [Regression Potential] * Potential AppArmor regression regarding its use of no_new_privs, since it was previously a fake implementation to facilitate the v3 backport. [Other Info] * Backport is from mainline. * Backport only includes seccomp filters introduced in v3.5 (e.g. does not include syscall or tsync). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1509489/+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 1513463] Proposed package removed from archive
The version of linux-mako in the proposed pocket of Wily that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1513463 Title: [SRU] Kernel too big for boot partition Status in linux-mako package in Ubuntu: Fix Released Status in linux-mako source package in Vivid: Fix Committed Status in linux-mako source package in Wily: Won't Fix Status in linux-mako source package in Xenial: Fix Released Bug description: [Impact] * Recent additions to the mako kernel have made it too big for the mako boot partition. Without this patch, a boot.img cannot be created. [Test Case] 1. Compile the mako kernel without this patch. 2. Attempt to create a boot.img 3. Notice that the kernel is too big. 4. Apply this patch. 5. Run steps 1-2 again. 6. Notice that the kernel is no longer too big. [Regression Potential] * This patch removes ext2 and ext3 and enables ext4's backward- compatibility mode for them instead. The only regression potential is within ext4's backward-compatibility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1513463/+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 1591289] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 65, failed: 0
tests ran: 65, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-24.43/ms10-34-mcdivittB0-kernel__4.4.0-24.43__2016-06-16_11-19-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/1591289 Title: linux: 4.4.0-25.44 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1580560] Re: ILAB_TUC - PowerKVM guest ilp1fc85apa4 hit svc path missing during SVC CCL EI
Hi Canonical, Trusty 3.13 / 14.04 is OK, but the commits are not applied in the HWE branch for 14.04.x, which are the required target. That was what I had in mind when requested for 14.04.x -- sorry if that wasn't explicit enough. Can we get them for linux-lts-xenial / 14.04.x latest? 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/1580560 Title: ILAB_TUC - PowerKVM guest ilp1fc85apa4 hit svc path missing during SVC CCL EI Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Bug description: Hi Canonical, This a "duplicate" of LP #1580557 comment #1 (yes, a comment). (It seems there was a problem in the bug bridge and it merged 2 bugs.) This is about including these 2 upstream commits for the lpfc driver: Mauricio Faria De Oliveira 2016-05-11 08:37:31 BRT Hi Canonical, The 2 upstream commits that resolve this problem are: 0290217ad830f2813bb9ed5f51af686c0c591f28 lpfc: Correct loss of target discovery after cable swap. be6bb94100dc6803a530e20aad05360e6267f56b lpfc: Fix premature release of rpi bit in bitmask Please pull them into 14.04.x. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1567781] Re: unable to handle kernel NULL pointer dereference at 00000134
Dear Chris and Uli, I have installed Lubuntu 16.04 on another disk with pokini1. Running kernel 4.4.0 does not produce the bug anymore. But, the Gui is still broken, just no more kernel NULL pointer dereference error. I had to change the display also and it is not HDMI. I had gotten following info from Uli: cause of problem is the GMA500 driver which causes the issues when used with an HDMI display and the 1920x1080 resolution. So far I was able to verify that. The issue is related to the HDMI resolution and hence the driver. My bios has two options for the shared memory for the display: - 128 MiB and - 256 MiB I use since the very first installation the 256MiB option in then which never gave issues. Seems that the current GMA500 driver needs more than 256 MiB or some checks on available memory are not done properly... I shall try now to blacklist the GMA500 driver and will let you know Thahnks for your help and patience. regards hjl -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1567781 Title: unable to handle kernel NULL pointer dereference at 0134 Status in linux package in Ubuntu: Incomplete Bug description: Problem is found in dmesg output: [ 11.660671] BUG: unable to handle kernel NULL pointer dereference at 0134 [ 11.660688] IP: [] mutex_lock+0x12/0x30 [ 11.660706] *pdpt = 33ee5001 *pde = [ 11.660714] Oops: 0002 [#1] SMP [ 11.660723] Modules linked in: nfsd auth_rpcgss nfs_acl lockd parport_pc grace ppdev lp sunrpc parport autofs4 hid_generic hid_cherry pata_acpi usbhid hid psmouse gma500_gfx i2c_algo_bit r8169 drm_kms_helper drm sdhci_pci pata_sch sdhci mii video [ 11.660772] CPU: 1 PID: 242 Comm: plymouthd Not tainted 4.2.0-35-generic #40-Ubuntu [ 11.660779] Hardware name: CompuLab CM-iAM/SBC-FITPC2i/CM-iAM/SBC-FITPC2i, BIOS NAPA0001.86C..D.1009141059 09/14/2010 [ 11.660785] task: f5cf08c0 ti: f2364000 task.ti: f2364000 [ 11.660792] EIP: 0060:[] EFLAGS: 00010286 CPU: 1 [ 11.660798] EIP is at mutex_lock+0x12/0x30 [ 11.660804] EAX: 0134 EBX: 0134 ECX: EDX: 8000 [ 11.660810] ESI: EDI: EBP: f2365ea8 ESP: f2365ea4 [ 11.660815] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 11.660820] CR0: 80050033 CR2: 0134 CR3: 31a1d540 CR4: 06f0 [ 11.660824] Stack: [ 11.660828] f19f93a0 f2365ec0 f8586171 f326dea0 f1ad7000 f1a0a400 f2365ec8 [ 11.660842] f858621f f2365edc f845ff47 f1a0a400 f1a0a400 f1a0a400 f2365eec f84b6019 [ 11.660856] f2365f04 c11b2de4 f2365f04 f856a78a f74d59d0 f1a0a400 [ 11.660869] Call Trace: [ 11.660935] [] __drm_modeset_lock_all+0x91/0x130 [drm] [ 11.660986] [] drm_modeset_lock_all+0xf/0x30 [drm] [ 11.661018] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x17/0x50 [drm_kms_helper] [ 11.661048] [] psb_driver_lastclose+0x19/0x50 [gma500_gfx] [ 11.661060] [] ? kfree+0x134/0x140 [ 11.661110] [] drm_lastclose+0x2a/0x140 [drm] [ 11.661159] [] drm_release+0x29f/0x490 [drm] [ 11.661170] [] __fput+0xcf/0x210 [ 11.661179] [] fput+0xd/0x10 [ 11.661189] [] task_work_run+0x7f/0xa0 [ 11.661200] [] do_notify_resume+0x75/0x80 [ 11.661209] [] work_notifysig+0x16/0x1b [ 11.661215] Code: 00 00 c3 8d b6 00 00 00 00 31 c0 5d c3 8d b6 00 00 00 00 8d bf 00 00 00 00 55 89 e5 53 3e 8d 74 26 00 89 c3 e8 60 ef ff ff 89 d8 ff 08 79 05 e8 74 07 00 00 64 a1 c8 c0 bf c1 89 43 10 5b 5d [ 11.661311] EIP: [] mutex_lock+0x12/0x30 SS:ESP 0068:f2365ea4 [ 11.661323] CR2: 0134 [ 11.661332] ---[ end trace 3bb80835d39a3e44 ]--- ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-35-generic 4.2.0-35.40 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Apr 8 08:21:26 2016 HibernationDevice: RESUME=UUID=fda9b258-61a9-4bc5-974e-738538cee628 InstallationDate: Installed on 2013-07-09 (1003 days ago) InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) MachineType: CompuLab CM-iAM/SBC-FITPC2i ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=41b7698f-f3fa-4940-8e13-9378c5021e90 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard
[Kernel-packages] [Bug 1591289] Re: linux: 4.4.0-25.44 -proposed tracker
USN needed ** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591289 Title: linux: 4.4.0-25.44 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1567781] Re: unable to handle kernel NULL pointer dereference at 00000134
Dear Chris and Uli, I booted the pokini now with HDMI and the issue is back: - ... [5.998669] BUG: unable to handle kernel paging request at 206e7676 [5.998689] IP: [] mutex_lock+0x12/0x30 [5.998704] *pdpt = 320fb001 *pde = [5.998712] Oops: 0002 [#1] SMP [5.998720] Modules linked in: autofs4 hid_generic hid_cherry usbhid hid pata_acpi psmouse gma500_gfx r8169 sdhci_pci i2c_algo_bit drm_kms_helper pata_sch sdhci syscopyarea sysfillrect sysimgblt fb_sys_fops drm mii fjes video [5.998768] CPU: 0 PID: 346 Comm: plymouthd Not tainted 4.4.0-21-generic #37-Ubuntu [5.998775] Hardware name: CompuLab CM-iAM/SBC-FITPC2i/CM-iAM/SBC-FITPC2i, BIOS NAPA0001.86C..D.1009141059 09/14/2010 [5.998782] task: f20db480 ti: f5a7a000 task.ti: f5a7a000 [5.998788] EIP: 0060:[] EFLAGS: 00010286 CPU: 0 [5.998795] EIP is at mutex_lock+0x12/0x30 [5.998801] EAX: 206e7676 EBX: 206e7676 ECX: EDX: 8000 [5.998807] ESI: 206e754a EDI: 206e754a EBP: f5a7be88 ESP: f5a7be84 [5.998813] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [5.998818] CR0: 80050033 CR2: 206e7676 CR3: 335a0480 CR4: 06f0 [5.998823] Stack: [5.998828] f3574ce0 f5a7be98 f8531021 f59d2100 f5a0bc00 f5a7beac f8586e50 f5a0bc00 [5.998842] f5a0bc00 f5a0bc00 f5a7bebc f8b07039 f19809c0 0001 f5a7bed4 f851589a [5.998857] f74bcc00 f5a0bc00 f5a7bf18 f8515c4f [5.998870] Call Trace: [5.999009] [] drm_modeset_lock_all+0x31/0xb0 [drm] [5.999072] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x20/0x70 [drm_kms_helper] [5.999127] [] psb_driver_lastclose+0x19/0x50 [gma500_gfx] [5.999187] [] drm_lastclose+0x2a/0x140 [drm] [5.999236] [] drm_release+0x29f/0x490 [drm] [5.999247] [] __fput+0xcf/0x210 [5.999255] [] fput+0xd/0x10 [5.999264] [] task_work_run+0x7f/0xa0 [5.999275] [] exit_to_usermode_loop+0xd5/0xe0 [5.999284] [] do_fast_syscall_32+0x147/0x150 [5.999295] [] sysenter_past_esp+0x3d/0x61 [5.999301] Code: 00 00 c3 8d b6 00 00 00 00 31 c0 5d c3 8d b6 00 00 00 00 8d bf 00 00 00 00 55 89 e5 53 3e 8d 74 26 00 89 c3 e8 70 ef ff ff 89 d8 ff 08 79 05 e8 74 07 00 00 64 a1 a8 72 c5 c1 89 43 10 5b 5d [5.999402] EIP: [] mutex_lock+0x12/0x30 SS:ESP 0068:f5a7be84 [5.999414] CR2: 206e7676 [5.999422] ---[ end trace 1d5c4a6d9395cec3 ]--- - I hope that helps now to continue... when I run the pokini with a non-HDMI display I get the graphical gui, not completely because the menues and the like is missing (seems still some components do not work properly), but at least I can login and open some terminal windows. regards hjl -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1567781 Title: unable to handle kernel NULL pointer dereference at 0134 Status in linux package in Ubuntu: Incomplete Bug description: Problem is found in dmesg output: [ 11.660671] BUG: unable to handle kernel NULL pointer dereference at 0134 [ 11.660688] IP: [] mutex_lock+0x12/0x30 [ 11.660706] *pdpt = 33ee5001 *pde = [ 11.660714] Oops: 0002 [#1] SMP [ 11.660723] Modules linked in: nfsd auth_rpcgss nfs_acl lockd parport_pc grace ppdev lp sunrpc parport autofs4 hid_generic hid_cherry pata_acpi usbhid hid psmouse gma500_gfx i2c_algo_bit r8169 drm_kms_helper drm sdhci_pci pata_sch sdhci mii video [ 11.660772] CPU: 1 PID: 242 Comm: plymouthd Not tainted 4.2.0-35-generic #40-Ubuntu [ 11.660779] Hardware name: CompuLab CM-iAM/SBC-FITPC2i/CM-iAM/SBC-FITPC2i, BIOS NAPA0001.86C..D.1009141059 09/14/2010 [ 11.660785] task: f5cf08c0 ti: f2364000 task.ti: f2364000 [ 11.660792] EIP: 0060:[] EFLAGS: 00010286 CPU: 1 [ 11.660798] EIP is at mutex_lock+0x12/0x30 [ 11.660804] EAX: 0134 EBX: 0134 ECX: EDX: 8000 [ 11.660810] ESI: EDI: EBP: f2365ea8 ESP: f2365ea4 [ 11.660815] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 11.660820] CR0: 80050033 CR2: 0134 CR3: 31a1d540 CR4: 06f0 [ 11.660824] Stack: [ 11.660828] f19f93a0 f2365ec0 f8586171 f326dea0 f1ad7000 f1a0a400 f2365ec8 [ 11.660842] f858621f f2365edc f845ff47 f1a0a400 f1a0a400 f1a0a400 f2365eec f84b6019 [ 11.660856] f2365f04 c11b2de4 f2365f04 f856a78a f74d59d0 f1a0a400 [ 11.660869] Call Trace: [ 11.660935] [] __drm_modeset_lock_all+0x91/0x130 [drm] [ 11.660986] [] drm_modeset_lock_all+0xf/0x30 [drm] [ 11.661018] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x17/0x50 [drm_kms_helper] [ 11.661048] [] psb_driver_lastclose+0x19/0x50 [gma500_gfx] [ 11.661060] [] ? kfree+0x134/0x140 [ 11.661110] [] drm_lastclose+0x2a/0x140 [drm] [ 11.661159] [] drm_release
[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Precise) 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/1579190 Title: Key 5 automatically pressed on some Logitech wireless keyboards Status in linux package in Ubuntu: Confirmed Status in linux source package in Precise: Confirmed Status in linux source package in Trusty: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: I have a K520 Logitech keyboard and sometimes something starts to keep pressing key 5. It mostly happens when I leave the computer alone for some time, but sometimes also just during regular usage. It seems that this is a Linux specific issue as no one is complaining about this issue under Windows, but a couple of people are complaining for different versions of Ubuntu. It is always 5 and WladyXX3740 claims on the Logitech forum that: "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably kernel related." Here is where most of the people are complaining: https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639 I discovered that this is related to my Logitech keyboard by running this command: xinput test-xi2 --root Here is the device list: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech K520 id=10 [slave pointer (2)] ⎜ ↳ Logitech M310/M310t id=11 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ DELL Wireless hotkeys id=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] And some extract from the output when this happens: EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 12 (PropertyEvent) property: 308 'Synaptics Off' changed: modified EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 ef
[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Vivid) 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/1579190 Title: Key 5 automatically pressed on some Logitech wireless keyboards Status in linux package in Ubuntu: Confirmed Status in linux source package in Precise: Confirmed Status in linux source package in Trusty: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: I have a K520 Logitech keyboard and sometimes something starts to keep pressing key 5. It mostly happens when I leave the computer alone for some time, but sometimes also just during regular usage. It seems that this is a Linux specific issue as no one is complaining about this issue under Windows, but a couple of people are complaining for different versions of Ubuntu. It is always 5 and WladyXX3740 claims on the Logitech forum that: "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably kernel related." Here is where most of the people are complaining: https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639 I discovered that this is related to my Logitech keyboard by running this command: xinput test-xi2 --root Here is the device list: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech K520 id=10 [slave pointer (2)] ⎜ ↳ Logitech M310/M310t id=11 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ DELL Wireless hotkeys id=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] And some extract from the output when this happens: EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 12 (PropertyEvent) property: 308 'Synaptics Off' changed: modified EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effe
[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Trusty) 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/1579190 Title: Key 5 automatically pressed on some Logitech wireless keyboards Status in linux package in Ubuntu: Confirmed Status in linux source package in Precise: Confirmed Status in linux source package in Trusty: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: I have a K520 Logitech keyboard and sometimes something starts to keep pressing key 5. It mostly happens when I leave the computer alone for some time, but sometimes also just during regular usage. It seems that this is a Linux specific issue as no one is complaining about this issue under Windows, but a couple of people are complaining for different versions of Ubuntu. It is always 5 and WladyXX3740 claims on the Logitech forum that: "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably kernel related." Here is where most of the people are complaining: https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639 I discovered that this is related to my Logitech keyboard by running this command: xinput test-xi2 --root Here is the device list: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech K520 id=10 [slave pointer (2)] ⎜ ↳ Logitech M310/M310t id=11 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ DELL Wireless hotkeys id=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] And some extract from the output when this happens: EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 12 (PropertyEvent) property: 308 'Synaptics Off' changed: modified EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 eff
[Kernel-packages] [Bug 1591289] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-24.43/ms10-35-mcdivittB0-kernel__4.4.0-24.43__2016-06-16_12-08-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/1591289 Title: linux: 4.4.0-25.44 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1591289] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 83, failed: 0
tests ran: 83, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-25.44/ms10-35-mcdivittB0-kernel__4.4.0-25.44__2016-06-16_10-43-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/1591289 Title: linux: 4.4.0-25.44 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1588871] Re: CVE-2016-1583
** Information type changed from Private Security to Public Security -- 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/1588871 Title: CVE-2016-1583 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Released Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wi
[Kernel-packages] [Bug 1580560] Re: ILAB_TUC - PowerKVM guest ilp1fc85apa4 hit svc path missing during SVC CCL EI
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580560 Title: ILAB_TUC - PowerKVM guest ilp1fc85apa4 hit svc path missing during SVC CCL EI Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Bug description: Hi Canonical, This a "duplicate" of LP #1580557 comment #1 (yes, a comment). (It seems there was a problem in the bug bridge and it merged 2 bugs.) This is about including these 2 upstream commits for the lpfc driver: Mauricio Faria De Oliveira 2016-05-11 08:37:31 BRT Hi Canonical, The 2 upstream commits that resolve this problem are: 0290217ad830f2813bb9ed5f51af686c0c591f28 lpfc: Correct loss of target discovery after cable swap. be6bb94100dc6803a530e20aad05360e6267f56b lpfc: Fix premature release of rpi bit in bitmask Please pull them into 14.04.x. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580560/+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 1557751] Comment bridged from LTC Bugzilla
--- Comment From hbath...@in.ibm.com 2016-06-16 07:53 EDT--- (In reply to comment #15) > After talking with upstream, the new version should come sometimes in may > with support for newer kernels. At the moment, this message can be > disregarded as a warning since there is no kernel specific issue up to k4.5 Hi Louis, Now that we have makedumpfile v1.6.0 that supports kernel till v4.5.3, can we expect that to be pushed into trusty & xenial as well? Thanks Hari -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1557751 Title: makedumpfile generates kernel version error Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Trusty: Confirmed Bug description: == Comment: #7 - Vaishnavi Bhat - 2016-03-15 06:16:53 == The following warning is generated by makedumpfile * running makedumpfile --dump-dmesg /proc/vmcore /mnt/201602030129/dmesg.201602030129 The kernel version is not supported. The created dumpfile may be incomplete. The makedumpfile version on your machine is # makedumpfile -v makedumpfile: version 1.5.5 (released on 18 Dec 2013) I did a #sudo apt-get source makedumpfile and checked for the sources. In the makedumpfile.h , the LATEST_VERSION is set to #define OLDEST_VERSION KERNEL_VERSION(2, 6, 15)/* linux-2.6.15 */ #define LATEST_VERSION KERNEL_VERSION(4, 1, 0)/* linux-4.1.0 */ where as kernel version on the machine is # uname -r 4.2.0-27-generic Hence we see this mismatch and message as "The kernel version is not supported." We need canonical to change the value of LATEST_VERSION so that we do not see this message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1557751/+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 1591289] onza (amd64) - tests ran: 26, failed: 1
tests ran: 26, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-25.44/onza__4.4.0-25.44__2016-06-16_08-20-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591289 Title: linux: 4.4.0-25.44 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1591289] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 65, failed: 0
tests ran: 65, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-25.44/ms10-35-mcdivittB0-kernel__4.4.0-25.44__2016-06-16_12-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/1591289 Title: linux: 4.4.0-25.44 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-25.44 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591289/+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 1592597] Re: 3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630
Testing the latest upstream kernel will tell us if this bug is already fixed in mainline. If it is fixed, we can then work to identify the commit that fixes the bug. An alternative would be to perform a kernel bisect, which will identify the commit that introduced the regression. However, that will require testing about 7 - 10 test kernels. Is it not possible to test any test kernels on the affected system? ** Tags added: needs-bisect regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592597 Title: 3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630 Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Incomplete Bug description: Following recent update to 3.13.0-88, R630 on Trusty panics on boot. Recovery boot just hangs. 3.13.0-87 was able to be booted normally once, then kernel panics on subsequent attempts. Booting is successful with the previously running kernel, 3.13.0-61. will upload an sosreport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592597/+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 1528910] Re: Marvell wireless driver update for FCC regulation
** Tags removed: verification-needed-vivid verification-needed-xenial ** Tags added: verification-don-xenial verification-done-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1528910 Title: Marvell wireless driver update for FCC regulation Status in HWE Next: Fix Committed Status in HWE Next vivid series: Fix Released Status in HWE Next xenial series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: Background: · Marvell will provide a FW which will read the OTP (and driver updates to support this function) · For US, it will disable changes to country code · For non-US, it will allow changes to country code by either SW method · Below userspace command. This can be issued at any time. “iw reg set ”. · Specifying country code through module parameter while loading the driver: “insmod mwifiex.ko reg_alpha2=” Driver information: $ modinfo mwifiex_pcie filename: /lib/modules/3.19.0-34-generic/kernel/drivers/net/wireless/mwifiex/mwifiex_pcie.ko firmware: mrvl/pcie8897_uapsta.bin firmware: mrvl/pcie8766_uapsta.bin license: GPL v2 version: 1.0 description: Marvell WiFi-Ex PCI-Express Driver version 1.0 author: Marvell International Ltd. srcversion: 695CB2D80C705025E9AA751 alias: pci:v11ABd2B38sv*sd*bc*sc*i* alias: pci:v11ABd2B30sv*sd*bc*sc*i* depends: mwifiex intree: Y vermagic: 3.19.0-34-generic SMP mod_unload modversions To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1528910/+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 1512997] Re: Support Edge Gateway's WIFI LED
** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1512997 Title: Support Edge Gateway's WIFI LED Status in HWE Next: Fix Committed Status in HWE Next vivid series: Fix Released Status in HWE Next xenial series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: The WIFI LED of Marvell 88W8897 is not enabled by default (there's no code for controlling LED in mwifiex). It is requested to be ON and OFF when the radio is on and off accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1512997/+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 1512999] Re: Support Edge Gateway's Bluetooth LED
** Tags removed: verification-needed-xenial ** Tags added: verification-failed-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/1512999 Title: Support Edge Gateway's Bluetooth LED Status in HWE Next: Fix Committed Status in HWE Next vivid series: Fix Released Status in HWE Next xenial series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: The Bluetooth LED of Marvell 88W8897 is not enabled by default (there's no code for controlling LED). It is requested to be ON and OFF when the radio is on and off accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1512999/+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 1570899] Re: Suspend problem with kernel 4.4
Yesterday I got an automatic update of kernel to 4.4.0.24 - still can't suspend properly. My system is Lenovo Z51 with Kubuntu (16.04, of course). The problem disappears after switching to kernel 4.4.8. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570899 Title: Suspend problem with kernel 4.4 Status in linux package in Ubuntu: Confirmed Bug description: When I install the linux kernel 4.4 (any of it) my laptop won't go to suspend when I close the lid or press the suspend (sleep button) this does not happen with kernel 4.2.0-27 (not sure of other 4.2 kernels). My laptop is a Lenovo G50-70 with a Radeon R5 M230. (linux Mint 17.3 Cinammon) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570899/+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 1591307] Re: linux: 3.19.0-62.70 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591307 Title: linux: 3.19.0-62.70 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-62.70 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591307/+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 1574036] Re: Sleep with ubuntu 16.04 with kernel 4.4
Shouldn't this be marked as a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570899 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574036 Title: Sleep with ubuntu 16.04 with kernel 4.4 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I upgraded my samsung series 7 ultra from ubuntu 15.10 to 16.04. After this I was not able to suspend the computer. The screen became black but the fan continued to work. I tried to restore the previous kernel: from 4.4 to 4.2 and the sleep function works properly Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574036/+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 1591301] Re: linux: 4.2.0-39.46 -proposed tracker
USN Needed ** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591301 Title: linux: 4.2.0-39.46 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-39.46 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591301/+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 1593226] [NEW] [Acer Aspire ES1-411] Ubuntu freezes occasionally
Public bug reported: I am running Ubuntu 16.04 and my notebook freezes occasionally. I am running Ubuntu on an Acer Aspire ES1-411 (P6B1). There's also an identical Bug filled with Acer Aspire ES1-311 and both Ubuntu 15.04 & 15.10 by Christian Wansart here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509723 I have no clue what causes this, my system just freezes and I can't do anything anymore. When it happens, I have tried the following secuence without any luck, I have to power down manually: 1. ALT + F2, type xkill + ENTER. 2. Press Alt+Ctrl+F1. 3. While holding Alt and the SysReq (Print Screen) keys, type REISUB. Last time I was only viewing a Youtube video using Firefox. I checked some log files but I couldn't find anything suspicious. Any ideas? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dnaranjor 1503 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 16 09:00:34 2016 HibernationDevice: RESUME=UUID=5023d49a-acd1-475f-8593-d3da289e4859 InstallationDate: Installed on 2016-06-02 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire ES1-411 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=e6ddc4d0-aaa8-4e28-9d68-6b37358246b6 ro quiet splash reboot=pci vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA42_BM dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd12/10/2014:svnAcer:pnAspireES1-411:pvrV1.08:rvnAcer:rnEA42_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-411 dmi.product.version: V1.08 dmi.sys.vendor: Acer ** 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/1593226 Title: [Acer Aspire ES1-411] Ubuntu freezes occasionally Status in linux package in Ubuntu: New Bug description: I am running Ubuntu 16.04 and my notebook freezes occasionally. I am running Ubuntu on an Acer Aspire ES1-411 (P6B1). There's also an identical Bug filled with Acer Aspire ES1-311 and both Ubuntu 15.04 & 15.10 by Christian Wansart here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509723 I have no clue what causes this, my system just freezes and I can't do anything anymore. When it happens, I have tried the following secuence without any luck, I have to power down manually: 1. ALT + F2, type xkill + ENTER. 2. Press Alt+Ctrl+F1. 3. While holding Alt and the SysReq (Print Screen) keys, type REISUB. Last time I was only viewing a Youtube video using Firefox. I checked some log files but I couldn't find anything suspicious. Any ideas? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dnaranjor 1503 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 16 09:00:34 2016 HibernationDevice: RESUME=UUID=5023d49a-acd1-475f-8593-d3da289e4859 InstallationDate: Installed on 2016-06-02 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire ES1-411 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=e6ddc4d0-aaa8-4e28-9d68-6b37358246b6 ro quiet splash reboot=pci vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA42_BM dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.c
[Kernel-packages] [Bug 1593226] 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/1593226 Title: [Acer Aspire ES1-411] Ubuntu freezes occasionally Status in linux package in Ubuntu: Incomplete Bug description: I am running Ubuntu 16.04 and my notebook freezes occasionally. I am running Ubuntu on an Acer Aspire ES1-411 (P6B1). There's also an identical Bug filled with Acer Aspire ES1-311 and both Ubuntu 15.04 & 15.10 by Christian Wansart here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509723 I have no clue what causes this, my system just freezes and I can't do anything anymore. When it happens, I have tried the following secuence without any luck, I have to power down manually: 1. ALT + F2, type xkill + ENTER. 2. Press Alt+Ctrl+F1. 3. While holding Alt and the SysReq (Print Screen) keys, type REISUB. Last time I was only viewing a Youtube video using Firefox. I checked some log files but I couldn't find anything suspicious. Any ideas? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dnaranjor 1503 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 16 09:00:34 2016 HibernationDevice: RESUME=UUID=5023d49a-acd1-475f-8593-d3da289e4859 InstallationDate: Installed on 2016-06-02 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire ES1-411 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=e6ddc4d0-aaa8-4e28-9d68-6b37358246b6 ro quiet splash reboot=pci vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA42_BM dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd12/10/2014:svnAcer:pnAspireES1-411:pvrV1.08:rvnAcer:rnEA42_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-411 dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593226/+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 1593235] [NEW] ovs/gre, vxlan, geneve: interface deletion are not notified via netlink with linux >= 4.3
Public bug reported: These upstream patches are needed: ovs/gre,geneve: fix error path when creating an iface http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=106da663ff495e0aea3ac15b8317aa410754fcac ovs/vxlan: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=cf5da330bbdd0c06b05c525a3d1d58ccd82c87a6 ovs/gre: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=da6f1da819d4b9c081a477dec74dc468a0b44290 ovs/geneve: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=41009481b690493c169ce85f591b9d32c6fd9422 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 6wind -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1593235 Title: ovs/gre,vxlan, geneve: interface deletion are not notified via netlink with linux >= 4.3 Status in linux package in Ubuntu: Incomplete Bug description: These upstream patches are needed: ovs/gre,geneve: fix error path when creating an iface http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=106da663ff495e0aea3ac15b8317aa410754fcac ovs/vxlan: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=cf5da330bbdd0c06b05c525a3d1d58ccd82c87a6 ovs/gre: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=da6f1da819d4b9c081a477dec74dc468a0b44290 ovs/geneve: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=41009481b690493c169ce85f591b9d32c6fd9422 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593235/+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 1591301] alkaid (amd64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-39.46/alkaid__4.2.0-39.46__2016-06-16_13-17-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/1591301 Title: linux: 4.2.0-39.46 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-39.46 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591301/+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 1593235] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1593235 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/1593235 Title: ovs/gre,vxlan, geneve: interface deletion are not notified via netlink with linux >= 4.3 Status in linux package in Ubuntu: Triaged Status in linux source package in Wily: Triaged Status in linux source package in Xenial: Triaged Bug description: These upstream patches are needed: ovs/gre,geneve: fix error path when creating an iface http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=106da663ff495e0aea3ac15b8317aa410754fcac ovs/vxlan: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=cf5da330bbdd0c06b05c525a3d1d58ccd82c87a6 ovs/gre: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=da6f1da819d4b9c081a477dec74dc468a0b44290 ovs/geneve: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=41009481b690493c169ce85f591b9d32c6fd9422 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593235/+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 1591315] Re: linux: 3.13.0-89.136 -proposed tracker
USN needed. ** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591315 Title: linux: 3.13.0-89.136 -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: In Progress 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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-89.136 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1591315/+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
